Four signals to hand over on
These are worth wiring as explicit conditions rather than hoping the model notices.
- The customer asks for a person. Always honour this immediately, first time, with no retention attempt.
- The same question has been asked twice. A repeat means the answer did not land, and a third phrasing will not fix it.
- The conversation turns to money that is not on the price list — discounts, credit terms, custom scope.
- Sentiment turns. Frustration compounds fast on a channel people use with their friends.
Ground the answers, and know when there is no ground
An AI agent should answer from your own material rather than from general knowledge. In Waboxa, replies are drafted from documents you upload, and the document each reply drew on is recorded on the message — so a wrong answer points you at the file that caused it.
The corollary matters more: when retrieval finds nothing relevant, the honest move is to hand over rather than to improvise. An agent that says 'let me get someone who can answer that properly' is doing its job.
Hand over to a person, not to a queue
A handoff that clears the AI flag and leaves the thread unassigned has not handed anything over. Someone specific has to own it, the thread has to be marked assigned, and the AI has to stop replying so it cannot talk over the human who just arrived.
Give the human what the AI already knows
The rep picking up should not have to re-read forty messages. The full history, the qualification result and the score should already be attached to the thread.
Done properly, handover is not an escalation. It is a colleague joining a conversation already in progress, with the notes in front of them.