The customer explains the problem again
An assistant gathers an order reference, asks the customer to repeat a troubleshooting step and eventually offers a human agent. The agent opens an empty ticket and asks for the order reference. The automation has consumed the customer's effort without transferring its value.
A handoff should preserve useful work and transfer responsibility. It is not merely a change in the speaker shown above the message box. The receiving person needs to know what the customer is trying to achieve, what is established, what was attempted and why the automated path stopped. The customer needs to know who is now responsible.
Define the point where the assistant should stop
Escalation rules should follow the limits of authority and evidence. A disputed charge, conflicting account records or a request outside the assistant's allowed actions can justify human review. The exact rules belong to the support operation, not to a model's general willingness to continue answering.
Customers should also have an understandable route to request a person. Repeatedly rephrasing the same answer after that request is not persistence; it delays the intended outcome. If no live agent is available, the interface should explain the available asynchronous route without implying that someone has joined.
An illustrative delivery case might reach a genuine limit when tracking and warehouse records disagree. The assistant can collect the relevant references and state the disagreement. It should not invent a delivery promise simply to avoid escalation or close the conversation with an unsupported answer.
Transfer a structured case with evidence
The receiving record should contain the customer's goal, relevant verified identifiers, actions already taken and the unresolved question. Separate customer statements from system observations and model inferences. A fluent summary that blurs these categories can be more dangerous than a longer transcript.
Include links to the source conversation and relevant authorised records, not every payload the assistant encountered. The agent should be able to inspect evidence without receiving unrelated private information. Keep original wording available where nuance matters, particularly when the customer disputes what happened.
Record any action with side effects and its result. If a replacement was requested but acceptance is uncertain, say so explicitly. Otherwise a human may repeat it and create another shipment. The handoff should reveal unfinished work, not smooth it into a reassuring narrative.
Make ownership and waiting visible
Creating a ticket is not the same as assigning it. The support system needs a durable case reference, a responsible queue or person and a route for failed assignment. If the transfer fails, the assistant should preserve the case and explain the failure instead of announcing success.
Status changes also need to reach people using assistive technology. W3C explains that relevant status messages can be exposed programmatically without moving focus. Its status-message guidance applies to updates such as waiting or successful submission, not just visible toast messages.
Avoid promises about response time that the operation cannot support. Say whether the conversation continues here or by another channel, and preserve that choice in the case. The uncomfortable part is staffing: an excellent transfer into an unowned queue still produces an abandoned customer.
Rehearse the transfer this week
Choose a support scenario the assistant should not resolve alone. Have someone act as the customer and someone else receive the case without watching the conversation. The receiver should explain the goal, evidence, previous actions and next decision from the handoff alone.
Repeat with no available agent, a failed ticket creation and an uncertain external action. Check that the customer sees an accurate status and does not have to reconstruct the entire history. Measure the continuity of the work, not merely whether the automation produced a ticket identifier. That is the difference between ending a chat and transferring a case.