The Reply Just Came In: Routing Decisions Across a Nurture Quarter
Objective: Play through 3 stages of a quarter as the marketing ops lead deciding how to route AI-classified lead replies, applying the lesson's intent-classification and guardrail principles at each decision point.
You run marketing ops at Halo Top, the low-calorie ice cream brand acquired by Wells Enterprises. Your team just turned on AI intent classification for inbound replies, and the first real cases are landing in your queue.
At each stage, read the AI's classification and the situation, then choose the routing action, optimal choices follow the lesson's guardrails, costly ones skip a guardrail and cause a downstream problem.
Before you start
What you'll need
Free path (everything below is enough to finish)
Free tier includes workflow triggers on custom properties, enough to build this routing logic for real
Paid upgrades (optional, faster/deeper)
The free CRM tier can branch workflows on a manually-tagged intent field; Marketing Hub adds the AI classification step itself at higher reply volumes.
Needed once reply volume outgrows what free-tier workflow rules can branch on
The process
Simulation
Week 1: A 'ready-to-buy' reply lands
Week 1A prospect replies to a follow-up: 'Yes, let's move forward, can we get on a call this week?' The AI intent classifier tags it ready-to-buy.
Reply queue: 1 new. AI tag: ready-to-buy. Confidence: high.
How do you route this reply?
Final deliverable
A completed 3-stage routing log showing which action was taken at each decision point and why.
See a reference example
Walker & Company Brands, reply-routing log Week 1: ready-to-buy reply -> Slack alert sent to rep within 8 minutes, call booked same day. Week 3: not-now reply (mentioned Q3) -> check-in task auto-scheduled for Q3 start date. Week 8: churn-risk flag on Acct #4410 -> held for human check, rep confirmed planned pause, discount skipped.
Success criteria
You're done when you can:
- Routes the ready-to-buy reply for immediate rep alert, not a batch review
- Distinguishes not-now from a hard no and schedules a dated check-in instead of unsubscribing
- Holds the churn-risk discount for a human check instead of letting it auto-send