Saltar al contenido
NuevoVer cómo
Nuevo

New sending guardrails auto-pause unhealthy mailboxes

FirstSales now watches every connected mailbox's health in real time and automatically pauses sending the moment one looks risky, so a single bad mailbox never drags down your deliverability.

Publicado
Lectura
3 min de lectura

Cold email lives and dies by sender reputation. One mailbox quietly going bad, more bounces, more spam-folder placement, can drag down every other mailbox sharing your domain, sometimes before anyone notices. Catching that in time used to mean someone on your team watching dashboards, refreshing stats, and making a judgment call about when to pull a mailbox out of rotation. That's a manual chore that competes with actually running campaigns, and it's the kind of thing that gets skipped on a busy week, which is exactly when a bad mailbox does the most damage. Now FirstSales watches for you, continuously, across every mailbox you've connected.

What changed

FirstSales continuously monitors the health of every mailbox you've connected for sending. This isn't a one-time check when you connect a mailbox, it's ongoing, running in the background for as long as that mailbox is sending on your behalf. The moment a mailbox's health drops to a level that would put deliverability or your domain reputation at risk, FirstSales automatically holds sending from that mailbox. No alert to act on, no button to click, the hold happens on its own.

Your other, healthy mailboxes keep sending without interruption. This is the part that matters most: a problem with one mailbox doesn't ripple out and stall your whole campaign. FirstSales isolates the risk to the mailbox that's actually degraded and lets everything else keep working exactly as it was.

The at-risk mailbox stays paused until it recovers, then resumes automatically. You don't need to remember to check on it, re-enable it, or decide when it's safe again. FirstSales handles the full cycle: detect the degradation, hold the mailbox, watch for recovery, resume sending. This runs across all your connected mailboxes at once, whether you have two or twenty, so the coverage scales with however many senders you're running. You don't need to check anything, flip a switch, or babysit a dashboard to get this protection. It's on by default for every connected sender, with nothing to configure.

How to use it

  1. Go to the Connectors page in your FirstSales account.
  2. Review the list of your connected sending mailboxes. Each one shows its current health status, so you can see at a glance which mailboxes are sending normally and which are being watched more closely.
  3. Keep sending as normal. There's no setup step here, no toggle to find, no threshold to set. If a mailbox's health degrades to a risky level, FirstSales pauses it automatically, no action needed from you.
  4. Check back on the Connectors page any time to see which mailboxes are actively sending and which are being protected while they recover. This is useful if you're troubleshooting a dip in reply rates or just want visibility into what's happening across your sending infrastructure.
  5. Once a paused mailbox's health improves, FirstSales resumes sending from it automatically, picking back up without you having to intervene or re-trigger anything.

There's genuinely nothing to configure here. If a mailbox is connected to FirstSales for sending, it's monitored, and the guardrail is active from the moment you connect it.

Why it matters

A single unhealthy mailbox sending at full volume is how good campaigns go bad: bounces climb, messages start landing in spam instead of the inbox, and your domain's long-term reputation takes a hit that's slow and painful to earn back. Reputation damage doesn't stay contained to the one mailbox that caused it either, it can bleed into how mailboxes on the same domain get treated by inbox providers, which is why catching the problem early matters so much.

Automatic guardrails catch the problem before it becomes your problem. Your healthy mailboxes keep landing in the inbox uninterrupted, your at-risk mailbox gets a chance to recover instead of digging a deeper hole by continuing to send while unhealthy, and you get to run campaigns without treating mailbox health as a manual chore you have to remember. Whether you're running two mailboxes or twenty, the same protection applies to each one, continuously, without you having to watch it happen.

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.

Empieza tu prueba de $1 Ver precios

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