Reply handling: the outbound layer everyone forgets to build
Replies are where outbound turns into pipeline, and where most programmes leak. How to classify, route and act on every reply automatically, and what to measure.
17 Nov 2025 · 2 min read · by HeiSyn
Ask a team with a stalled outbound programme where the replies go, and the answer is usually an inbox one person checks between meetings. The programme is generating interest and losing it in the gap between the reply and the CRM. Reply handling is a system, and it is the cheapest part of the engine to get right.
Classify every reply
Each inbound reply gets a label: interested, question, not now, wrong person with a referral, wrong person without one, out of office, unsubscribe, bounce. A language model classifies these reliably when given the thread and the list of labels; a rules pass handles the obvious ones (auto-replies, bounces) before the model sees anything. Log the label on the contact.
Act on the label
Interested: create the deal, assign the owner, attach the thread, create a task due today, ping the owner. Question: same, but flag that a specific answer is needed. Referral: create the new contact, note who referred them, and start a new short sequence that mentions the referral. Not now: pause the sequence and schedule a re-engagement in the number of weeks they suggested. Out of office: parse the return date and resume after it. Unsubscribe: suppress across every domain, permanently.
Close the loop with the sender
The person who receives the deal should be able to reply from their own inbox with the whole history visible. That means the thread lives in the CRM, not in a sending tool's dashboard. Keep the sending inbox for sequences only; move conversations to the rep the moment they become conversations.
Measure the leak
Two numbers: time from interested reply to first human response, and the share of interested replies that became a booked meeting. If the first is over an hour or the second under a third, the leak is in handling, not in the list or the copy. Fix that before spending anything on more volume.
Questions people ask next
- Can a model reliably classify replies?
- Yes for the common categories, with a small test set to confirm. Interested, not now, unsubscribe, out of office and wrong person are distinguished well. The harder cases — a question that hides an objection, a polite decline that reads as interest — should route to a person when the model's confidence is low.
- Who should the interested reply go to?
- Whoever will have the conversation, in their own mailbox, with the thread attached — usually the account executive for the segment, not the person whose name was on the sending inbox. Reassigning the thread within minutes and having the rep reply from their own address is what turns a reply into a meeting.
- What about replies that arrive weeks after the sequence ended?
- They are the best kind — the prospect kept the email. The system should still classify and route them, attach the original thread, and alert the rep with a note that this is a late reply, so the reply is treated as warm rather than lost in an inbox nobody watches any more.
Want this built for your team?
A free scoping call: we map your motion, name the number that should move, and quote a fixed-scope build.
