Saltar al contenido
NuevoVer cómo
Nuevo

A/B test your emails and send windows, with automatic winners

Write two versions of an email step, or test two sending time-windows against each other, and let FirstSales split the sends, watch the results, and automatically promote the winner to the rest of your audience.

"Which subject line works better?" is a question you can only answer by trying both. Until now, trying both inside a campaign meant guessing, or running two campaigns and eyeballing the results. FirstSales now runs the experiment for you. Write two versions, and it splits the sends, measures what actually earns replies, and promotes the winner on its own.

What changed

There are two kinds of test you can run, and both end the same way, with FirstSales picking the winner so you don't have to babysit it.

Content variants

On any email step in a campaign, you can now add a second version, a different subject, a different body, or both, and FirstSales splits your sends across the variants. Add as many as you want to test. Each is labeled by letter (A, B, and so on). There's a guardrail so you can't accidentally delete a step's only remaining version. It works in both campaign modes, autopilot and template, with the panel adapting to the mode you're in.

Send windows

Some audiences reply in the morning. Some reply at night. In a campaign's Settings, you can now turn on a send-window test that pits two different sending time-windows against each other. Set a start and end hour for Group A and for Group B, and FirstSales learns which window your audience actually responds to. The form checks that your windows make sense, so you can't set a start after an end or make both windows identical.

The automatic winner

This is the part that changes how you work. Once a test is running, you don't have to watch it. FirstSales collects real results as your campaign sends, and your per-step analytics show the variants side by side, each as its own row, with a Leading badge on whichever is ahead by reply rate. A send-window test shows a "collecting data" state while it gathers responses.

When one version is a clear, confident winner, and enough messages have gone out for that result to be trustworthy, FirstSales promotes it automatically. The rest of your audience starts getting the winning email, the analytics row updates with a "Winner, auto-promoted" badge, and the losing variant is dimmed and marked "No longer sending." Send-window tests lock in their winner with a confidence figure shown right in analytics.

Want to keep experimenting? A Resume test button on the step undoes the promotion and puts it back into testing.

How to use it

Content-variant test:

  1. Open your campaign and go to the campaign builder.
  2. Select the email step you want to test.
  3. In the email template panel, click Add variant to create version B (A stays your original). Write its subject and body. Add more variants if you like.
  4. Keep the campaign running. FirstSales splits sends across the variants.
  5. Watch the campaign's per-step Analytics. The front-runner shows a Leading badge, and the system promotes the winner on its own.

Send-window test:

  1. Open your campaign and go to the Settings tab.
  2. Turn on the send-window test.
  3. Set Group A's start and end hour, and Group B's. Make the two windows different and valid.
  4. Save. FirstSales sends across both windows and gathers results.
  5. Open Analytics to watch it collect, then lock in a winner with a confidence figure.

Why it matters

Most teams know they should A/B test and don't, because the manual version is tedious. Set up two campaigns, wait, remember to check back, read the numbers, manually switch everyone to the winner, hope you didn't call it too early. Every one of those steps is a place to give up. Automating the whole loop (split, measure, decide, promote) means the test happens whether or not you have the discipline to run it by hand, and the winner reaches your audience the moment it's proven rather than whenever you next remember to look.

Calling the winner automatically also protects you from the most common testing mistake: declaring victory too soon, off a handful of sends, on a difference that's really just noise. FirstSales waits until enough has gone out for the result to hold up before it commits, and if you disagree, Resume test hands the decision back to you. It pairs naturally with the template sequence library and with the self-learning AI and AI Instructions that shape your drafts in the first place.

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.