Skip to content
NewSee how

Launch readiness: required vs optional components

The six components a campaign must have before it can launch, plus the optional ones worth adding.

Tutorials
Campaigns
min read
5 min
steps
7 · Beginner

  1. Find the Setup Progress panel

    Open your campaign's Info tab. Near the top, a Setup Progress card shows a fraction like 2/6 with a progress bar - that's how many of the six required items are done.

    Find the Setup Progress panel

  2. Confirm Campaign details

    Campaign details checks off automatically once the campaign has a name - it shows the campaign name underneath when complete.

  3. Add Contacts

    Contacts added stays unchecked until at least one contact list is attached. Click the row to jump straight to adding lists.

  4. Connect Email connectors

    Email connectors needs at least one connected sending mailbox. Click the row to open your connector settings.

  5. Build the Workflow

    Workflow built checks off once your canvas has nodes configured - it shows the node count, e.g. “6 nodes configured”.

  6. Set the Schedule and Calendar

    Schedule configured requires a sending schedule to be set. Calendar connected only applies to campaigns with a meeting goal - connect a calendar so meeting booking works.

  7. Reach 6/6 before launching

    Each completed item turns green with a checkmark and the fraction climbs toward 6/6. Work through any unchecked row - clicking it takes you straight to the place to fix it.

Pro tips

  • Click a row to jump straight there

    Every unfinished checklist item is itself a shortcut - click it instead of hunting through tabs for the setting it needs.

  • Calendar only applies to meeting goals

    If your campaign's goal isn't meeting-booking, that row won't gate you - it's conditional on the goal you picked.

  • Workflow built means configured, not just present

    The node count only increments for nodes that are actually configured, not just dropped on the canvas.

  • Check Setup Progress before Test Workflow

    A campaign under 6/6 can still fail a test run for the same reasons the checklist is flagging - clear it first.

Frequently asked questions

Where do I find launch readiness?

On the campaign's Info tab, in the Setup Progress card at the top - it shows a running count like 2/6.

What are the six Setup Progress items?

Campaign details, Contacts added, Email connectors, Workflow built, Schedule configured, and Calendar connected.

Does Calendar connected always need to be checked?

No - it only matters for campaigns with a meeting-booking goal. Other campaigns can reach full readiness without it.

How do I fix an unchecked item?

Click the row itself - each incomplete item links directly to the tab or panel where you complete it.

Does Workflow built just mean I added nodes?

It means the nodes on your canvas are actually configured, not merely placed - it shows a count like “6 nodes configured”.

Is there a separate Launch confirmation after 6/6?

Reaching 6/6 clears every tracked setup gap; use Test Workflow to verify the sequence runs before sending to real contacts.

Campaigns

Outreach that keeps going after you log off.Leads, emails, follow-ups and replies, handled.

Connect unlimited mailboxes and let AI agents find leads, write each email and follow up. Or send your own templates in manual mode. From $29/mo.

Start your $1 trial See pricing

$1 for 3 days · Cancel anytime · No contract

Install with AI

Your coding agent sets up the FirstSales CLI and skills for you.

Prompt for 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.
Developer docs ↗npm: @firstsales.io/cli ↗GitHub: firstsales-skills ↗