Pular para o conteúdo
NovoVeja como
Melhoria

Clearer campaign launch blockers

When a campaign can't launch, FirstSales now lists exactly which components are missing instead of a generic error.

A campaign that won't launch used to tell you very little about why. You'd hit the launch button, get a generic error, and start manually checking tabs — is there a sender connected? Does the contact list have anyone in it? Is the sequence complete? — until you found the gap. When you're ready to send, that's friction at exactly the wrong moment. The campaign checklist replaces that process with a short, specific to-do list.

Know what's blocking you

If a campaign can't launch, FirstSales now lists exactly which components are missing instead of surfacing a generic error. You see the specific gap — no sender connected, empty contact list, incomplete sequence — and can fix everything in one pass before trying again.

How to use it

  1. Open your campaign's Info tab — the Setup Progress checklist tracks every launch requirement in one place.
  2. Completed steps show a green check. Steps that remain tell you exactly what to configure, in plain terms rather than error codes.
  3. Click any pending step to jump straight to the right section of the campaign builder — no manual navigation needed.

Why a checklist is better than an error message

An error message tells you something is wrong. A checklist tells you everything that's wrong and gives you a path to fix each item. For someone launching their third campaign this week, that distinction is minor — they know the product and can diagnose quickly. For someone setting up a campaign for the first time, or returning to a draft they started two days ago, a checklist is the difference between a five-minute fix and a twenty-minute investigation.

The checklist also serves a different purpose for teams managing multiple campaigns across different workspaces: it acts as a launch quality gate. Every requirement is visible before you go live, which means fewer campaigns that start but underperform because a sender wasn't connected to the right account, a tracking domain wasn't configured, or a contact list was accidentally left empty after a filter was applied.

For cold outreach specifically, the cost of a misconfigured launch is real. A campaign that goes out with the wrong sender, without tracking enabled, or to an incomplete list wastes your sending reputation and your prospects' attention. Fixing it after the fact means pausing, correcting, and resuming — a sequence that has already interrupted the cadence you designed.

Auto-assignment of tracking domain

Also in this release: FirstSales now automatically assigns the tracking domain that matches your sender's email domain. Previously, selecting a tracking domain was a manual step that was easy to skip or misconfigure — especially when running multiple sending accounts across different domains. The auto-assignment removes it from the checklist entirely for most campaigns, cutting one more thing to get right before launch. One fewer step between ready and live.

Todas as novidades

Prospecção que continua quando você desconecta.Leads, emails, follow-ups e respostas, resolvidos.

Conecte caixas ilimitadas e deixe os agentes de IA encontrarem leads, escreverem cada email e fazerem follow-up. Ou envie seus próprios modelos no modo manual. A partir de $29/mês.

$1 por 3 dias · Cancele quando quiser · Sem contrato

Instalar com IA

Seu agente de código configura a CLI e as skills do FirstSales para você.

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.