Getting the reply is the easy vanity metric. The expensive part is what your team does in the next hour. Agencies lose booked conversations when every "interesting, tell me more" sits in the same pile as "send times" and "not this quarter."
Reply intent triage tells you what the message is. This post is about the next action map: book, nurture, or disqualify. Those three exits keep multi-client shared inboxes honest.
Start with a short taxonomy, then force an exit
Operator playbooks from FirstSales, LeadMagic, ReplyWorks, and Allston Labs converge on a small set of buckets. You do not need twenty labels. You need enough categories that each one points to a different next action.
A practical map for agency outbound:
| Reply shape | Next action | SLA instinct |
|---|---|---|
| Clear meeting interest | Book | Minutes, not hours |
| Question or conditional interest | Answer short, then book offer | Same business day |
| Soft "not now" with a date | Nurture with a dated follow-up | Within 24 hours |
| Objection with a real signal | Clarify once, then book or nurture | Same day |
| Wrong person / referral | Extract intro, suppress original | Same day |
| Hard no / unsubscribe | Disqualify + suppress | Immediate |
| OOO / bounce | Pause or fix, do not "sell" | System first |
| Ambiguous or hostile | Human review, often disqualify | Same day |
If a category does not change the next action, merge it. Taxonomy without routing is theater.
Book means calendar ownership, not more email
Clear interest ("send times," "let's talk," "how do we start") should exit the sequence and enter booking. FirstSales' rule is blunt: interested reply plus any positive signal means drop the calendar link, do not wait for a perfect essay. ReplyWorks adds the ops layer: route, triage in under about 90 seconds, respond inside a few hours, then hand off.
Agency trap: the shared inbox owner keeps polishing a reply while the client's AE calendar sits empty. Write the handoff once. Who books? Whose calendar? What happens if the prospect asks pricing before a call? Put those answers in the client workspace, not in Slack lore.
Speed matters. LeadMagic cites the familiar cold-email pattern that replies within about 15 minutes convert far better than replies that wait a full day. You do not need to worship one vendor's multiplier. You do need a written SLA for book-path replies that is measured in minutes during business hours.
Nurture is a dated promise, not a softer pitch
"Not now" and "check back in Q3" are not meeting interest. They are nurture. Acknowledge the timeframe they gave you. Set the follow-up date they named. Do not ask "when would be better" after they already told you.
Conditional interest ("if you can do X," "depends on price") sits between book and nurture. Answer the condition in a few sentences, then offer a call for specifics. If they go quiet after a clear answer, move them to nurture rather than endless objection ping-pong.
Nurture exits should still stop the aggressive sequence. Sequences must stop on reply. Keeping someone in a five-step cold cadence after they said "next quarter" is how you earn the hard no later.
Disqualify is a first-class product action
Hard no, unsubscribe, hostile, and clear bad-fit positives all belong on the disqualify path. Suppress immediately. Do not argue. Do not "one last value email."
Also disqualify polite interest that fails ICP on a second look. ReplyWorks notes that a meaningful slice of "positive" replies come from people who should not have been on the list. Booking those meetings burns client trust. Mark the row, suppress, and feed the miss back into campaign entry rules.
How agencies keep the map consistent across clients
- One shared category set for the agency, with client-specific calendar and voice rules inside each isolated workspace
- Templates per exit (book / nurture / disqualify), customized in the first sentence only
- Stop-on-reply enforced so no exit fights an automated follow-up
- Daily review of misroutes: nurture that should have booked, book attempts that should have been suppressed
GTM's motion is find, qualify, write, send, reply, book. The reply step only pays when every positive category has a next action and an owner. If you want that operating model in client-isolated workspaces, join the waitlist at https://trygtm.com/waitlist.
Measure the map, not just the reply rate
Track book-path speed, nurture follow-through on the promised date, and suppress latency on hard nos. A high positive reply rate with slow booking is still a leak. Put those three exits on the weekly client scorecard so AMs argue about routing quality instead of vibes.
Sources
- https://firstsales.io/blog/reply-handling-playbook/
- https://leadmagic.io/gtm-skills/reply-handling
- https://replyworks.io/playbooks/reply-ops-positive-replies/
- https://allstonlabs.com/library/replies/classification
- /workspace/trygtm/knowledge/product.md