Missed replies

Your sequencer is missing replies. Here is where they are.

Smartlead, Instantly and EmailBison see the replies they sent for. The forward to a colleague, the answer from a new address, the CC, the reply that arrives after the sequence ended: none of those have a campaign to attach to. Master Inbox reads the mailbox itself, so they land anyway.

Book a demo See pricing

Free missed-reply audit before any commitment. Free 7-day POC. Unlimited users on every plan.

Master Inbox threading forwarded, CC and new-address replies to the original prospect

Six ways a reply goes missing

Every one came up on a sales call in the last six months. None is a sequencer bug. A sequencer can only see what it sent for.

1. The internal forward

Your prospect forwards the email to the person who actually decides. That person replies from their own address. There is no campaign for that address.

2. The CC and the new address

The prospect loops in an assistant, or answers from a second account. Same conversation, different sender, invisible to campaign attribution.

3. The reply-to domain

Replies to the reply-to address on your main domain land in a mailbox the sequencer is not tracking. One in-house team lost both capture and analytics this way.

4. The out-of-sequence answer

A prospect replies three weeks after the last step, to a sequence that is no longer active. Agencies running ten workspaces told us these are the ones they lose.

5. The rotated or disconnected mailbox

A mailbox drops out of rotation or loses its connection. Replies keep arriving in it. Nothing downstream knows.

6. The out-of-office chain

An auto-reply names a colleague and a return date. Treated as noise, it is a lead with a name and a follow-up date attached.

Internal data across connected workspaces puts these at roughly 12% of all replies. The forward and the new address are most of it.

"The missed-reply thing is genius. It's like a no-brainer. So I missed a reply that's like a potential meeting booked."Adrian B., agency founder, on a demo call, after seeing the replies his sequencer webhook had not carried.

What one missed reply costs

The math is uncomfortable because it is simple.

The reply is the expensive part. Everything before it, the list, the mailboxes, the copy, the sending, was spent to earn it. A missed reply wastes all of it.
It is usually the warm one. Forwards happen when a prospect is interested enough to involve a colleague. The forward is the buying signal, and it is the reply most likely to be lost.
Agencies pay twice. One founder put a single reply at twelve to fifteen thousand dollars of contract value, and knew of one that had been missed. An agency's missed reply is also a client's reason to churn.
You cannot see the ones you missed. Which is why the audit connects a workspace and counts them, instead of asking you to guess.

Put your own reply rate and deal size into the calculator to see what the 12% is worth to you.

How Master Inbox catches them

Three mechanisms, none of which depend on the sequencer noticing.

1It reads the mailbox, not the webhook

Every sending mailbox is connected directly, in bulk from Zapmail, InboxKit or HyperTide or by CSV. A reply is a reply whether or not a campaign claims it. Sequencer webhooks run alongside as a second source.

2One Master Thread per prospect

Forwards, CC replies, new addresses and new subject lines are threaded to the prospect they belong to, so the person who replies from a second account is not a stranger.

3Nothing fails silently

A mailbox that disconnects fires an event. Out-of-office replies get their own label with the return date and the colleague's name. Warm-up mail is excluded before it can hide a real reply.

Then the reply is labeled, put in the Needs Reply view, posted to Slack with a draft, or answered by a reply agent. What happens next.

Count yours before you decide

The free missed-reply audit takes one call.

Connect one workspace

Your sequencer by API key and the mailboxes behind it, live on the call.

Backfill and label

Master Inbox reads the history and labels it on your own key, including the replies with no campaign attached.

See the number

The replies your sequencer reported, next to the replies that were actually in the mailboxes. Then decide.

Explore more: vs Smartlead's inbox, vs Instantly Unibox, The better unibox, Speed to lead

Questions we get

Why does my sequencer miss replies at all?

A sequencer tracks replies to the campaigns it sent, from the address it wrote to. A forward, a CC, a reply from a new address, a reply to your reply-to domain, or a reply after the sequence ended has no campaign to attach to, so it is not counted as a reply.

Is this a Smartlead, Instantly or EmailBison problem?

It is how campaign-based attribution works, in every sequencer. The sending tools are good at sending. Reply capture across every mailbox is a different job.

How many replies are we talking about?

Internal data across connected workspaces puts replies a sequencer never reports at roughly 12% of the total. Your number depends on how often prospects forward and how many mailboxes you rotate, which is what the audit measures.

Does Master Inbox need the sequencer webhook?

No, but it uses it. Mailboxes are read directly, which is how forwards and new addresses are seen. Sequencer webhooks run alongside as a second source, and account-level webhooks act as a safety net.

What happens to out-of-office replies?

They get their own label. The return date and any colleague named inside become a follow-up, and a workflow can set the reminder automatically.

What is the free missed-reply audit?

One call. We connect a workspace, backfill and label the history on your own key, and show you the replies that were in the mailboxes but not in the sequencer's count. Then you decide whether to run the free 7-day POC.

See it on your own inboxes

Book the free missed-reply audit. We connect one workspace on the call and count the replies your sequencer never showed you.

Book a demo