Pular para o conteúdo
NovoVeja como
Novo

Set a per-sender daily send ceiling

Cap how many emails any single sender sends per day across campaigns and warmup combined, with auto-ramp and nightly tuning staying under your limit.

Publicado
Leitura
2 min de leitura

Warmup and your live campaigns both send from the same inbox, and together they decide how much a single sender pushes out in a day. A new send ceiling lets you put a hard cap on that combined daily volume, so no one sender ever sends more than you're comfortable with.

What changed

A connector's sending-config section now has a Send ceiling input. It's a cap you set, and it bounds the combined daily volume for that sender — campaign sends and warmup counted together, not separately. That's the key part: the ceiling covers everything the inbox sends in a day, so warmup can't quietly push you past the limit on top of your campaign volume.

The automatic warmup ramp still works as before, adjusting the warmup level underneath your ceiling — but it never goes above it. And the nightly auto-adjust, which tunes sending volume on its own, clamps to your ceiling last, so whatever it decides, your cap has the final word.

Leaving the field blank means no cap, so sending behaves exactly as it did before for any sender you don't want to limit.

This release also cleaned up a confusing signal: a connector that's still warming and doesn't have a placement score yet now shows a "placement pending" state instead of a misleading 0%.

How to use it

  1. Open the connector you want to limit and go to its sending configuration.
  2. Find the Send ceiling input in the sending-config section.
  3. Enter the maximum number of emails you want this sender to send per day, counting campaign sends and warmup together.
  4. To remove the limit, leave the field blank.
  5. Save the configuration.

Why it matters

A single inbox sending too much in a day is one of the fastest ways to hurt deliverability, and warmup quietly adding to your campaign volume makes that easy to miss. The send ceiling gives you one number that bounds the whole picture: set it, and both the warmup ramp and the nightly auto-adjust stay underneath it, with your cap applied last so nothing overrides it. You keep the benefit of automatic ramping without ever wondering whether a sender went over — and where you don't want a limit, leaving it blank changes nothing.

Availability

Available now in each connector's sending configuration.

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.

Comece seu teste de $1 Ver preços

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