Playbook

The Reply-Handling Playbook

For teams that work hard for replies and then improvise with them.

You leave with a six-route sorting rule, a script per route, a one-working-day standard and the log that stops good replies dying in the inbox.

By Intandemly team · Updated 24 Oct 2026 · 6 min read · Free, no sign-up

Preview

On this page

What you'll get

  • 7 copy-ready blocks
  • 6 min read

Replies are what the whole outbound machine exists to produce, and many teams have no process for them at all: the send gets a cadence, the catch gets a shrug. This playbook routes every reply one of six ways, inside one working day, with a script for each.

The standard

Every reply gets a human answer within one working day.
Every reply gets logged against its account, including the no.
No reply is ever answered by the next email in the sequence.

The third line needs software discipline: a reply pauses the cadence instantly, for every address at that account. A scheduled chaser landing after a human answer undoes months of looking competent. Where replies fit in the wider machine is the cold email process on one page.

Route 1: The yes ("let us talk")

"Good to hear, [first name]. Two slots: [slot 1] or [slot 2], 20
minutes. So I prepare properly: is [the problem from your email] the
right thing to focus on, or is something nearer the top of the list?"

Book from the reply itself, never "what works for you?" (that is two more emails). The added question turns the booking into the first minute of discovery.

Route 2: The maybe ("send me more information")

"Happy to. So I send one page instead of a brochure: is the question
cost, how it works, or whether it fits [their situation]? One line back
and the right page comes over today."

"Send more info" is either a brush-off or a real question wearing a vague coat. The one-line question finds out which, and the promised page must actually be one page.

Route 3: The not now ("try me next quarter")

"Will do, and thanks for saying so rather than going quiet. I will come
back in [month]. If [trigger worth watching] happens before that, worth
a call sooner? Either way, nothing more from me until then."

Log the month, set the reminder, go silent. The promise of silence is what makes the comeback email welcome. The wider rhythm is the follow-up sequence.

Route 4: The no ("not interested")

"Understood, and I appreciate the straight answer. I will close this
off. If it is useful to know, was it timing, fit, or just too many
emails like mine? One word helps me bother fewer people."

Most will not answer; the ones who do hand you list intelligence nobody sells. Either way the account note says no, with a date, and the cadence stops for good.

Route 5: The referral ("talk to my colleague")

"Thank you, that is genuinely helpful. I will write to [name] and say
you pointed me, unless you would rather I kept you out of it. If it is
easier to forward something, here is a short note written for them."

Attach the forwardable, which is exactly what the forwardable note is for. A referral is the account opening a second door; treat the referrer as a future champion and the new name as a committee entry, not a fresh cold lead.

Route 6: The angry reply ("stop emailing me")

"Done, and apologies for the intrusion. I have removed you and
[company] from our outreach. If anything from us reaches you again,
reply to this and I will fix it personally."

No justification, no "per my earlier email", no unsubscribe-link lecture. Suppress the whole account for a cooling period, honour it, and log it where the next campaign will see it. One angry reply handled gracefully is forgotten; one argued with is screenshotted.

The reply log

Four fields per reply, thirty seconds: account, route (1 to 6), what they actually said (quoted), next action with date. A week of logs tells you what the sends cannot: which messages earn routes 1 and 2, which segments produce angry 6s, and which not-nows cluster around a budget season you should plan for.

Worked example (illustrative, not a real company)

Illustrative example

Monday morning, Tessaro Analytics has four replies from last week's sends. The yes from Northfield Logistics books by 9:15 with two slots offered. The "send more info" from a mid-tier account gets the one-line question and comes back with "cost, mainly": route 2 becomes a real conversation. A "not interested" earns the graceful close and a one-word answer, "vendor", which moves the account's revisit date to their renewal season. And an irritated "how did you get this address?" gets route 6's apology and suppression, no argument. Four replies, four routes, all closed by lunch, all logged. All names are invented.

Five mistakes to avoid

  1. Leaving the yes until tomorrow. Reply interest has a half-life of hours. The one-working-day standard exists for routes 2 to 6; route 1 deserves same-morning.
  2. Answering "send more info" with a brochure. The vague ask gets a clarifying question, not an attachment avalanche. One page, aimed, after one line back.
  3. Hearing not-now as rejection. It is the most honest reply on the list and the cheapest pipeline you will ever build, if the month gets logged and the silence promise kept.
  4. Arguing with the no or the angry reply. Both are final in the thread and neither is final for the account. Grace now is what keeps the other doors in the building open.
  5. Not logging because the reply was small. The log's value is the pattern across twenty replies, and patterns are made of the ones that felt too minor to record.

Why this works on named accounts

Outbound teams measure everything about the send and almost nothing about the catch. Yet the reply is the expensive moment: weeks of list building, research and cadence discipline produced it, and one slow or clumsy answer spends it all. On named accounts the stakes double, because every reply, including the no, is a person inside a company you chose, telling you something true about it. The playbook exists so that nothing that rare gets improvised.
How account-based selling works →

Common questions

How fast should you respond to an outbound reply?

Interested replies the same morning where possible; everything else within one working day. Speed signals that working with you will feel like this, and it is the cheapest differentiator in outbound: many vendors take days, because their process ends at the send.

What do you say when a prospect replies "not interested"?

Thank them for the straight answer, close the thread, and ask one optional question: was it timing, fit or volume? Then actually stop. The account note records the no and any answer; the graceful exit is what makes a future conversation possible when the situation changes.

Should a referral reply be treated as a new cold contact?

No. Write to the new person within a day, name the referrer with their permission and carry the context over so nobody repeats themselves. A referred introduction converts at a different rate than cold outreach precisely because it is not cold; starting the sequence from scratch throws that away.

More from the Academy

Playbook5 min read

Cold Email Process on One Page

For anyone whose cold email is a pile of tactics instead of a process.

You leave with the six steps on one page, the order teams often get wrong, safe sending volumes and a weekly review that catches problems early.

Script8 min read

Follow-Up Email Sequence After No Reply

For sellers whose first email to a senior buyer went unanswered.

You leave with five follow-ups that each add something new, replies for the three answers you will get, a stop rule and a tracker.

Sales hack4 min read

The Forwardable Note: Get Introduced Inside an Account

For sellers with one friendly contact in an account and nobody else.

You leave with the ask, a note your contact can forward in ten seconds and the thank-you that keeps them involved.

Want this in your inbox?

Optional. We use your email only to send you this, nothing else.

Want this run on your key accounts?

Tell us which accounts you need to open. We will show you how we would work them.