Customer support · Human handoff · Inbox
Human handoff done right: when your AI agent should step aside
The handoff is where customer trust in AI support is won or lost. When to hand off, what to pass along, and how to set up your team to pick up cleanly.
The Convosphere team ·
Ask customers what they dislike about support chatbots and you will hear the same complaint: “I couldn’t get to a person.” The bot loops, rephrases the same unhelpful answer, and hides the exit.
The fix is not a smarter bot. It is a better handoff: the moment the AI agent recognises it should step aside and passes the conversation to a person who can finish the job.
Why the handoff matters more than the answer rate
It is tempting to judge an AI agent only by how many conversations it resolves alone. But a customer who was handed to a person quickly, with nothing to repeat, usually leaves happier than one who fought an agent for ten minutes before giving up.
A good handoff turns the agent’s limits into a feature. The agent handles what it can, and your team gets conversations that are already summarised, with the customer’s details collected and the question clarified.
When to hand off
Write these rules into your agent’s instructions explicitly. The common ones:
The knowledge isn’t there. If the answer is not in the content you connected, the agent should say so and offer a person, not improvise. This is also your best signal about which content to add next.
The customer asks. “Can I talk to a human?” should always work, first time, with no persuasion attempts.
The stakes are high. Refunds, cancellations, account changes, complaints, legal or medical questions. Even when the agent could answer, a person should own the outcome.
The customer is frustrated. Repeated questions, strong language or the same issue raised twice are signs to stop and escalate.
The request needs judgement. Exceptions to policy, custom quotes and partnership enquiries belong with your team.
What to pass along
A handoff that makes the customer repeat themselves is barely a handoff. Your team should receive:
- The full transcript, not a one-line summary
- What the customer wants, in one sentence
- Details already collected: name, email, order or account number
- What the agent already tried, including any sources it quoted
In Convosphere, the conversation lands in the shared inbox with the complete history. Your team can reply directly, turn it into a ticket, and use suggested replies that draw on the same knowledge base the agent uses.
Set your team up to pick up cleanly
Decide who owns the inbox. Handoffs that sit unassigned are worse than no handoff. Assign an owner per shift or per channel.
Tell customers what happens next. The agent should say something like: “I’ve passed this to our team. They’ll reply here during business hours.” Set expectations you can meet.
Close the loop. When your team resolves a handed-off conversation, ask whether the agent could have handled it with better knowledge. If yes, add that content.
Measure the handoff, not just the bot
Track these alongside your usual support metrics:
- Handoff rate: the share of conversations passed to a person. Too low can mean the agent is guessing; too high means it needs more knowledge.
- Time to first human reply after a handoff.
- Repeat questions: how often customers have to restate their issue after the handoff. The target is zero.
- Top handoff reasons: your roadmap for new knowledge and actions.
The goal: an agent customers don’t mind talking to
Customers don’t hate AI support. They hate being trapped. An agent that answers what it knows, admits what it doesn’t, and hands over gracefully earns the right to handle more over time.
Try it: Start free. Human handoff, the shared inbox and tickets are included from the Professional plan. See pricing.