The Deep Agent Studio agent handles repetitive requests, your advisors keep tricky cases. The line between them is called the handoff — and it is a feature to design, not an admission of failure. Done well, customers never repeat themselves and advisors resume in one sentence. Done poorly, you lose the trust earned so far.
The 5 signals that trigger a handoff
Hand off as soon as one signal appears: the case is out of scope (unknown procedure), the customer is upset or shows it (damaged parcel, repeated error), the sensitive action could not be SMS-verified, the customer explicitly asks for a human, or the agent still hesitates between two intents after rechecking. In Deep Agent Studio, each signal is a flow block: you set the threshold once, the agent applies it every time, at 11:47 PM as at 9 AM.
- Out of scope or unknown procedure
- Upset customer or emotional situation
- Failed or refused OTP verification
- Explicit request for a human
- Persistent doubt between two intents
What should the advisor get? Full context
A handoff with no context is a second call in disguise. Advisors must see at a glance: detected intent (billing, delivery, access), identity verified or not with check time, two-line summary, ticket number and full history. Deep Agent Studio forwards all of it automatically: nobody re-asks “what was this about?”. That context pack is the difference between a 30-second and a 6-minute takeover.
How to announce it: three sentences that work
Customers accept handoffs when they understand why and what happens next. Say it plainly, with ticket and timing:
I'm passing your file to the advisor with intent and verification already done — ticket RC-2048, reply in a few minutes, no need to repeat yourself.
Avoid vagueness (“I'll escalate this”) and jargon (“level-2 escalation”). State who takes over, with what, and by when. Then close the loop: the advisor confirms takeover in the same thread, not in another tool.
Advisor side: the one-sentence takeover
The ideal takeover fits in one sentence: “Hi Awa, I see the 5,000 FCFA double charge verified at 11:48 PM, I'm issuing the refund.” Everything is there: name, intent, amount, verification, action. Train teams on this format and track takeover time: it should fall week after week while post-handoff satisfaction rises.
Measure and improve: the 4 handoff metrics
- Handoff rate per intent: if delivery spikes, your procedure or API needs review.
- Advisor takeover time: aim for a steady fall.
- Post-handoff satisfaction: the true judge of transmitted context quality.
- Emerging transferred intents: your roadmap for the next flows to automate.
Every conversation thus becomes useful insight: you know what customers ask, where the agent suffices and where humans add most.
Concrete example: double charge at 11:47 PM
Awa writes on WhatsApp: “Hi, I was charged twice this month.” The agent detects billing intent, sends an SMS code, checks it, queries the invoice, confirms the 5,000 FCFA double charge and issues the refund with ticket RC-2048 in 38 seconds. But imagine an unusual amount or a recently changed account: the agent does not force it. It announces the handoff with context already gathered, the advisor resumes in one sentence and validates. The customer got an answer at 11:48 PM, not next morning at 9 AM — the whole Deep Agent Studio promise: AI acting fast, humans securing when needed.
Successful-handoff checklist
- Handoff threshold set per intent in the flow
- Context passed: intent, identity, summary, ticket, history
- Clear customer message: who, what, by when
- One-sentence advisor takeover, in the same thread
- Weekly handoff review to improve the agent
FAQ
Is frequent handoff a failure? No, if each handoff is clean and measured. A 20–30% rate at launch on a new intent is healthy; it should fall as the flow matures.
Should customers repeat themselves? Never. If they do, your handoff block passes too little context: fix it first.
Do advisors need a separate tool? No. The Deep Agent Studio inbox keeps the same thread, ticket and history. Advisors resume where the agent stopped.
