Human Handoff Threshold Mapping (Delivery)

Human Handoff Threshold Mapping (Delivery)

1. 01

   Baseline the client's current containment and transfer rates before touching agent configuration

   Pull 30 days of ticket volume by intent from the client's helpdesk, then split it into resolved-by-human, resolved-by-macro, and abandoned. Without that baseline you cannot prove the agent moved anything at the 60-day retainer review.

2. 02

   Rank intents by cost of a wrong answer, not by volume

   A billing dispute misread costs more than a password reset misread. Score each intent on refund exposure, regulatory sensitivity, and churn risk, then sort descending.

3. 03

   Set three confidence bands and assign a distinct action to each

   High confidence answers autonomously, mid confidence drafts a reply for a human to approve in one click, low confidence routes straight to a queue. Two bands is not enough; the middle band is where most client complaints originate.

4. 04

   Write the escalation trigger list in plain language the client can edit

   Include explicit phrases (cancel, lawyer, refund, chargeback), sentiment collapse after two turns, and any mention of a named account manager. Store the list in the client's own workspace so they own future edits.

5. 05

   Wire the handoff into the ticketing system with full context attached

   The human agent should open a ticket that already contains the transcript, the intent label, the confidence score, and the customer's account tier. Re-asking the customer to repeat themselves is the single most cited failure in post-handoff surveys.

6. 06

   Define the queue routing rule and the maximum wait before a human picks up

   Route by intent owner, not by round-robin. Cap the wait at a number the client agrees to in writing, and configure a fallback message that fires if the cap is breached.

7. 07

   Replay 50 real transcripts per week and move the bands

   Sample across all three confidence bands, flag every case where the agent should have escalated earlier, and adjust thresholds. Treat the bands as a tuning parameter, not a launch decision.

8. 08

   Report containment, escalation rate, and post-handoff CSAT as one linked metric set

   Containment alone rewards an agent that refuses to escalate. Present the three numbers together so the client sees the trade-off rather than a single flattering figure.