Reply Handling

Convert reply volume into pipeline.

Every cold sequence eventually produces replies. The system that routes them, classifies them, and books meetings is what separates outbound that works from outbound that wastes everyone's time.

The plan

The 7-step reply-handling plan.

Seven steps from centralizing inboxes to measuring the pipeline math. Each step links to the deep reference if you want to go further. Each step also has the obvious alternative: have us do it.

  1. Step 1

    1. Centralize all reply destinations

    One unified inbox view across all sending mailboxes. Whether it's a unified inbox tool or a daily triage spreadsheet — replies cannot live in 8 separate Gmail accounts.

    Why: Decentralized replies = missed pipeline. Even a 4-hour delay on a hot reply drops conversion materially.

  2. Step 2

    2. Classify every reply

    4 categories: Interested / Not now / Wrong person / Objection. Plus auto-reply detection (out of office, bounce).

    Why: Different replies need different responses. Treating all replies the same is the most common operational mistake.

  3. Step 3

    3. Route to the right person

    Interested + Objection → AE. Wrong person → re-target ask. Not-now → nurture sequence. Auto-replies → suppress for 30 days.

    Why: AEs are scarce. SDRs shouldn't handle objections that close deals. Automated routing is the leverage.

  4. Step 4

    4. Hit the 24h SLA on interested replies

    Reply to anyone interested within 24 hours. Calendar link with options, not a back-and-forth.

    Why: Interest decays. 24h response converts at 40-60%; 72h converts at 15-25%. The window is fast.

  5. Step 5

    5. Handle objections with a library

    Build a 12-15 objection response library — pricing, timing, authority, alternative-vendor, no-budget. AE has a starting point, not a from-scratch reply.

    Why: Objection responses converge to the same 12 patterns. A library accelerates the AE and improves consistency.

  6. Step 6

    6. Nurture not-yet-ready prospects

    30/60/90-day cadence with content asset, case study, or trigger-event re-engagement.

    Why: Most B2B pipeline closes 60-180 days after first conversation. Nurture keeps the prospect warm without overwhelming.

  7. Step 7

    7. Measure the pipeline math

    Track: reply rate → meeting-booked → opp-created → closed-won. Per cluster, per channel, per ICP segment.

    Why: Without this funnel, you can't tell whether the issue is copy, ICP, or sales motion. Pipeline math is the diagnostic.

What you're setting up

The four layers, in plain English.

Reply handling has four layers. Each layer answers one specific question the operator faces before pipeline gets booked: who sees the reply, who answers it, who follows up, and whether the funnel is healthy.

Triage

Centralize, classify, route. Replies arrive across 8 mailboxes and four intent categories — the triage layer is what turns that noise into the right action by the right person within the right window.

Conversion

Meeting booking and objection handling. The mechanics that turn an interested reply into a calendar event and an objection into a continued conversation rather than a closed-lost.

Nurture

Re-engagement cadences for not-yet-ready prospects. Most B2B pipeline closes 60-180 days after first conversation — nurture is where that pipeline lives.

Measurement

Pipeline conversion math and unit economics. The funnel from reply → meeting-booked → opp-created → closed-won, segmented by cluster, channel, and ICP.

Reference

Go deeper — the operational reference.

For the operator who actually wants to learn this. Seven chapters covering every reply category, every routing rule, every failure mode we've hit in production. Read by chapter to debug something specific, or read in order to build the reply layer from scratch.

Skip the build

We operate reply handling as a service.

Classification, routing, 24h SLA on hot replies, AE handoff with full context. Replies don't sit in 8 inboxes — they reach the right person within hours.

Book a call →