Blog

The outage nobody notices until the weekly call: how to monitor cold email campaigns

Sunny Ray · · 5 min read

Deliverability Operations

The most expensive outage in outbound is the one nobody notices until the weekly call. A stopped campaign looks exactly like a quiet week. No error, no bounce spike, just fewer replies, and everyone assumes the market is slow.

For months that was how we found problems. A client campaign would go down and the first anyone heard of it was the weekly sync, when someone asked why replies had dried up. By June we had had enough, and on a June 16 call I told a client what we had built: a read-only dashboard that goes red if any customer campaign stops.

So how do you know if your cold email campaign has stopped sending? You do not wait to notice. You build the alert so the system tells you.

Why campaigns die quietly

A campaign can stop for a dozen boring reasons. A mailbox disconnects. Warmup stalls. A domain gets flagged. A list runs out. Someone pauses a campaign to fix a typo and forgets to resume it.

The June 16 working session with our web partner had a live example. Mailboxes on one campaign had stalled during warming, and Charles needed to add the remaining mailboxes to get back to full sending capacity. Nobody had done anything wrong. The campaign was just quietly running at a fraction of its volume.

In May I had bookmarked a warning from another operator that default settings in a sending tool can route most of your email to spam while every dashboard looks fine. That is the scariest version. The numbers you watch keep moving, and the email is not landing.

What a dead week costs

Do the math on a new engagement. Our timeline for a new client, as I laid it out on the same June 16 call: two weeks of mailbox warmup, first emails in week three, meetings starting in week four. If a campaign dies in week three and nobody notices for a week, you just lost the first stretch of real sending and pushed the first meetings back.

The client feels it before you can explain it. On a June 9 call we went through one client's early numbers: 17 replies, 8 interested, about 8 meetings booked, roughly one a day since launch. Strong. And the client was still nervous and complaining about missed meetings. Charles's read was that the fix was over-communication. When a client cannot see what is happening, they assume the worst, even when the numbers are good.

Read-only access and a red alert

The first fix was internal. A read-only view across every customer campaign, built to flag in red the moment any one of them stops. Read-only matters: the person watching cannot break anything, and the view can sit open all day.

The rule is simple. Red on the dashboard means someone looks at it today, not at the weekly sync.

One URL per client

The second fix was for clients. On our June 19 team call Amir showed his first version of an Instantly dashboard by client: every client gets their own URL with their own campaign stats.

That is over-communication on autopilot. The nervous client can open a link at midnight and see sends, replies and meetings. They stop asking "is it working?" because they can check. And when something does break, they see it at the same time you do, which forces you to have the answer ready.

A chat agent for campaign questions

The third piece was the one I was most excited about. Amir built a chat-based agent for running Instantly campaigns. It covered creating and updating campaigns, setting up mailboxes, warming them up, connecting lists and pausing. It could also answer the question everyone asks: how is this campaign doing?

That last part changes who can check. Charles does not need to click through six tabs to see why one campaign is soft. He asks, and the agent pulls the stats. The plan from that call was a dedicated setup session to configure it and hand it to Charles.

Watch the replies, not just the sends

A campaign can be sending perfectly and still be failing, because the replies are sitting unread. On the June 16 working session our web partner, who was running a campaign of his own, got the same advice we give clients: the unified inbox is the place to monitor, filtered to the replies marked interested, so the signal is not buried under auto-replies and unsubscribes.

His campaign had about 90 leads with 20 to 25% qualified, with volume around 15 a day. At that volume we recommended letting AI handle the replies and the booking link, with a manual review still worth doing while volume is low. Monitoring is not only "is it sending." It is "is anyone answering the people who answered us."

What we still hadn't built

Honesty about the gap: as of that June 19 call, the alerting that would ping a phone if a campaign stopped, by SMS or an alarm, was not built yet. It was on the list as a future addition. The red dashboard only helps if someone is looking at it.

That is the next layer for anyone running more than a handful of campaigns. A dashboard is a place you visit. An alert is a thing that finds you.

What to monitor every day

Five questions, two minutes, every morning. Or one alert that asks them for you.

If you want to see what runs behind every campaign we operate, see what runs behind every show.

Frequently asked questions

How do I know if my cold email campaign stopped sending?

Do not rely on noticing fewer replies. Use a dashboard that flags any campaign or mailbox that stops sending, and check daily volume per mailbox against what it should be.

Should cold email clients get a live dashboard?

Yes. A per-client link with their own stats answers 'is it working?' before they ask, and it forces you to be ready when something breaks.

What should I monitor daily in Instantly?

Campaign status, mailbox connections and daily volume, warmup progress, bounce changes by domain, and unanswered interested replies.

How fast should I react to a campaign outage?

The same day. On a new engagement with two weeks of warmup, losing a week of sending pushes back the first meetings and costs client trust.

Related posts