Zum Inhalt springen
NeuSo funktioniert es
Fehlerbehebung

Campaigns that stopped scheduling are sending again

The full pipeline from draft through validation, billing, and scheduling was fixed and verified end to end. Meeting slot offers, replies, and follow ups all draft reliably again.

Some campaigns stopped scheduling sends. The full chain from draft to validation, billing, scheduling, and delivery has been fixed and checked end to end, and meeting slot-offers, replies, and follow-ups are drafting reliably again.

What changed

A number of campaigns got stuck somewhere between a draft being written and an email actually going out. Sends weren't getting scheduled, even in cases where everything upstream, the draft itself, its approval, looked fine on the surface. This turned out to trace through several distinct stages of the pipeline a draft moves through before it becomes a delivered email: draft approval, content validation, billing checks that confirm the send is covered, the scheduler that decides when it goes out, and finally delivery itself.

Each stage of that chain has been fixed individually, and the fix was verified end to end rather than at any single point in isolation. That distinction matters: it's possible to fix one stage of a pipeline like this and still have campaigns get stuck at a different stage that looks fine until you actually trace a real draft all the way through it. This fix was checked by following real drafts through the entire chain, from the moment they're written to the moment they're delivered, to confirm nothing else was quietly breaking along the way.

That verification specifically covered campaigns offering meeting time slots, which depend on precise scheduling to be useful at all, along with campaigns handling replies and follow-ups, which depend on the same chain working correctly every time a contact responds or a sequence advances. Drafts for all of these now generate reliably and flow through validation, billing, and scheduling to an actual delivered send.

How to use it

There's nothing to do to benefit from this fix directly. If you had a campaign that had stopped scheduling sends, check its status now: it should be scheduling and sending normally, including any meeting slot-offers, reply drafts, or follow-ups that were part of it.

If you're not seeing that, check the campaign's activity log for any specific error message tied to a contact or a send before reaching out, since a genuinely new issue would show up there differently than the stuck-scheduling pattern this fix addressed. Most campaigns affected by the underlying issue should now be moving through the full pipeline without you needing to intervene at all.

Why it matters

A campaign that silently stops sending is worse than one that fails loudly with a clear error, because nothing in your view tells you it's stopped until you happen to notice the symptoms yourself, replies have gone quiet longer than they should, a meeting slot offer never actually reached a contact who was ready for one, or a follow-up that should have gone out days ago never did. By the time you notice, you've often already lost the momentum with whoever was affected.

Fixing and verifying the whole chain, rather than just the symptom that was most visible or most frequently reported, matters because a partial fix would have left some campaigns still stuck at whatever stage wasn't addressed. Verifying meeting slot-offers, replies, and follow-ups specifically, rather than just first-touch drafts, means the fix holds across the different ways a campaign actually uses this pipeline, not just the simplest case.

The meeting slot-offer case deserves particular mention, since it's the most timing-sensitive use of this pipeline. Offering a prospect a specific slot to meet only works if the offer actually reaches them and the follow-through, confirming, rescheduling, sending a reminder, keeps working after it. A break anywhere in the chain from draft to delivery turns a meeting offer that looked sent from your side into one the prospect never actually saw, with no signal back to you that anything went wrong until the meeting simply doesn't happen.

Checking campaigns that depend on fast replies

If you run campaigns that depend heavily on replies and follow-ups moving quickly, for example a sequence built around booking meetings within a specific window, it's worth reviewing recent activity on those campaigns now to confirm sends are landing on the schedule you expect. Most campaigns affected by the underlying issue should already be caught up, but if a specific campaign still looks off, checking its activity log for a real error is a better next step than assuming the same stuck-scheduling issue is still present.

Going forward, this fix doesn't change anything about how you build or run a campaign. Draft, validation, billing, scheduling, and delivery all continue to work the way they're supposed to; this was about making sure they actually do that reliably, end to end, rather than changing what any of those stages does.

What to expect from here

An outreach system is only as reliable as its weakest connection between stages. A campaign can have a perfectly good draft, pass validation, clear billing, and still fail to send if the handoff into scheduling breaks, and from your side that failure is indistinguishable from a campaign that simply has nothing left to send. Verifying the full chain end to end, rather than fixing and declaring done at whichever stage seemed most likely responsible, is what it actually takes to trust that a campaign showing as active is going to keep sending.

For campaigns that stalled during the period this issue was present, the practical outcome is straightforward: contacts who were waiting on a meeting offer, a reply, or a follow-up that never arrived should now be moving again, with the same draft quality and timing you'd expect from a campaign that was never affected. There's no separate action needed to re-enable a previously stuck campaign; the fix applies automatically to how the whole pipeline processes it going forward. If you were holding off on relying on a campaign type that seemed unreliable during this period, meeting slot-offers in particular, this is the point at which it's worth trusting it again. Build and run campaigns the way you always have; the reliability of the pipeline underneath them is what changed here, not anything you need to do differently on your side.

Availability

This applies to all campaigns, including those using meeting slot-offers, reply handling, and follow-up sequences.

Alle Neuigkeiten

Akquise, die weiterläuft, wenn du offline bist.Leads, E-Mails, Follow-ups und Antworten, erledigt.

Verbinde unbegrenzte Postfächer und lass KI-Agenten Leads finden, jede E-Mail schreiben und nachfassen. Oder sende deine eigenen Vorlagen im manuellen Modus. Ab $29/Monat.

$1 für 3 Tage · Jederzeit kündbar · Kein Vertrag

Mit KI installieren

Dein Coding-Agent richtet die FirstSales CLI und Skills für dich ein.

Prompt für 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.