Saltar al contenido
NuevoVer cómo
Corrección

Clearer campaign launch blockers and activation requirements

Campaign launch now separates real blockers from optional tips, checks your plan or credit entitlement up front, and stops falsely warning brand-new accounts about exhausted credit.

Trying to launch a campaign and hitting a wall is frustrating; hitting a wall that does not explain itself is worse. Campaign activation could fail in ways that were hard to interpret, and brand-new accounts could be told their credit was exhausted before they had spent a thing.

What was happening

Campaign launch readiness mixed two very different kinds of feedback together: hard blockers that genuinely prevent a launch, and softer recommendations that are worth doing but do not actually stop you. Presented side by side without distinction, it was not clear which items you had to resolve and which were merely advice — so a launch could feel blocked by something that was only a suggestion, or a real blocker could get lost among optional tips. Activation also did not check your billing and credit entitlement up front. If your plan or credit balance did not permit activation, the attempt would fail later in a way that did not point clearly at the cause, leaving you to guess why it would not go. And brand-new organizations, which have no usage history at all, could be shown a "credit exhausted" alert before they had consumed anything — a zero balance of usage being misread as a depleted one.

What we fixed

Launch readiness now clearly separates required blockers from optional recommendations, so you can see at a glance what truly must be resolved before you can launch versus what is simply a good idea. Activation is checked against an active billing or credit entitlement up front: if your plan or credits do not allow it, you get a clear, immediate reason instead of an opaque failure further down the line. And brand-new organizations with no usage history no longer trigger a false "credit exhausted" alert — having consumed nothing yet is correctly treated as a fresh start, not an exhausted balance.

Why it matters

When a launch is blocked, you now know exactly why and what to do about it. The distinction between must-fix and nice-to-have means you do not waste time on recommendations you could safely launch without, and you do not miss the one thing actually standing in your way — you can fix the real blocker and launch, instead of working through a list where everything looks equally urgent. Checking entitlement up front turns a confusing late failure into a clear, immediate explanation tied to your plan or credits, so a billing limit reads as a billing limit rather than a mysterious dead end. And new accounts get a clean first impression instead of an alarming and wrong warning before they have even started — so your first campaign launches on facts about your account, not a misreading of an empty one.

Todas las novedades

Prospección que sigue cuando te desconectas.Leads, emails, seguimientos y respuestas, resueltos.

Conecta buzones ilimitados y deja que los agentes de IA busquen leads, escriban cada email y hagan seguimiento. O envía tus propias plantillas en modo manual. Desde $29/mes.

$1 por 3 días · Cancela cuando quieras · Sin contrato

Instalar con IA

Tu agente de código configura la CLI y las skills de FirstSales por ti.

Prompt para Claude Code

I'm setting up FirstSales (https://firstsales.io), an AI outbound sales platform: campaigns, contacts, a reply inbox, deliverability and lead signals. Help me get my workspace sending real, good emails end to end, from Claude Code.

Read these first so you know how FirstSales works:
- Developer docs and API: https://developer.firstsales.io
- CLI: https://www.npmjs.com/package/@firstsales.io/cli
- Skills for coding agents: https://github.com/firstsalesio/firstsales-skills (read README.md and GUIDE.md)

Setup
1. Install the CLI: npm install -g @firstsales.io/cli
2. Install the FirstSales skills:
   claude plugin marketplace add firstsalesio/firstsales-skills
   claude plugin install firstsales@firstsales
3. Ask me if I already have a FirstSales account. If not, send me to https://app.firstsales.io to sign up.
4. Ask me to create an API key under Settings → API → API Keys, with only the scopes we need.
   Never ask me to paste the key into this chat. Tell me to run this in my own terminal, so the key stays hidden:
   read -rs FS_KEY && firstsales auth login --api-key "$FS_KEY"; unset FS_KEY
5. Run `firstsales whoami` and tell me which workspace and organisation we are connected to.

Then ask me about my business: what I sell, who I sell to (roles, company size, countries), my best customers, and what I use today for outbound (tools, lists, mailboxes). Walk me through:
1. Teaching FirstSales my business: website, offer, proof points and case studies in the knowledge base, so the AI writes like someone who knows the product.
2. Connecting my sending mailboxes and checking my sending domain: SPF, DKIM, DMARC and warm-up. If anything is unhealthy, tell me the exact DNS record to add.
3. Bringing in contacts: import my CSV or CRM export into a clean list, remove duplicates and bad emails, and block domains I must never email (customers, competitors, my own).
4. Building my first campaign: the right list, senders, steps and timing. Write the sequence with me, show me the drafts, and do not launch until I say yes.
5. Setting up Signals if it fits: find people engaging with LinkedIn posts about topics my buyers care about, and turn them into leads.
6. Inviting my team and giving each person the right access.

Once campaigns run, show me how to work the reply inbox from here: which replies need an answer, draft responses in my voice, and move good conversations into deals. If I use Cal.com, connect it so follow-ups can offer my booking link (not the first email).

Throughout, as you learn about my business, proactively suggest and help create:
- Reply templates for the questions and objections my prospects are likely to raise, based on my product, site and codebase if you can see them.
- Campaign ideas and segments worth testing, with the reason for each.

Safety rules:
- Show every change as a dry run (--dry-run) first and wait for my yes. Never send emails, launch campaigns or delete anything without my yes.
- Tell me before anything that spends credits, and how many.

Be opinionated. If the docs give a sensible default, just use it. Don't make me choose between five options.