# Chatbot-to-Agent Handoffs: Keep the Customer Case Moving

Use a fictional case to review chatbot-to-agent continuity: context, acceptance, ownership, and the next customer update.

- Canonical URL: https://www.harmate.com/en/blog/chatbot-to-agent-handoffs-keep-the-customer-case-moving
- Author: Harmate Team
- Published: 2026-11-15
- Updated: 2026-11-15T01:49:38.756953+00:00
- Language: en

## Content

# Chatbot-to-Agent Handoffs: Keep the Customer Case Moving

Sending a conversation to a queue does not guarantee that an agent will take over. A useful handoff carries the relevant facts, gives the next action an owner, and tells the customer what to expect. The example below is fictional. It offers a way to inspect continuity; it does not describe a Harmate feature or a universal service rule.

## Prepare a case someone can pick up

Imagine Léa contacting a fictional retailer because a parcel is marked delivered, but she cannot find it. She has checked the parcel room twice and says this is her second attempt. She asks to speak with a person.

The chatbot’s last summary reads: “Parcel not received. Carrier says delivered. Parcel room checked.” It leaves out the previous contact and the request for a person. 

A useful transfer packet separates several kinds of information:

- **Customer request:** speak with a person and get a next step for the parcel.
- **Reported facts:** she checked the parcel room twice; she says this is a second attempt.
- **Observed record:** tracking displays “delivered” at 9:41. That does not establish that she received the parcel.
- **Unknowns:** delivery photo, exact location, reference for the earlier contact, and the result of any carrier review.
- **Next action:** check the earlier case and delivery evidence, then contact the appropriate team if needed.

This separation keeps a customer statement from being presented as proof and a tracking status from being presented as a resolution. It also lets the receiving agent see what to verify without asking the customer to repeat checks already recorded.

## Sending is not acceptance

In this scenario, the chatbot sends the case to the fictional Delivery Support queue at 10:12. Agent Samir accepts it at 10:15, confirms that the request, completed checks, and unknowns are visible, and takes ownership of the next action. That is when the case has an identifiable owner.

| Time | Handoff state | Evidence to record |
|---|---|---|
| 10:12 | Sent, not yet accepted | Summary transferred and receiving queue |
| 10:15 | Accepted by Samir | Named owner, visible checks, assigned next action |
| By 2 p.m. | Customer update due | Update sent, or delay explained with a realistic new time |

If the queue receives the case but nobody accepts it, the handoff is still incomplete. The team needs to notice the unowned case, assign it, and tell the customer if the update will be late. A “sent” event proves neither ownership nor resolution.

## Make the next update credible

The customer message should say what was transferred, identify who is taking over when known, and give an update time the team can meet. In this example, the fictional team promises another update by 2 p.m., even if its review is still in progress. That time belongs to the scenario; each organization must use its own approved commitments.

To review a handoff, ask four concrete questions: Does the customer know when to expect an update? Can the agent see confirmed facts and unknowns? Has a person accepted the case? Are the next action and its owner recorded? A “no” identifies what is still missing. For testing the clarification turns before a transfer, see [Chatbot Test Cases for Multi-Turn Conversations](https://www.harmate.com/en/blog/chatbot-test-cases-for-multi-turn-conversations).

## Debrief a failed transfer

If nobody has taken the case by the promised time, do not describe the initial transfer as successful. The queue lead should assign an owner, the agent should give an honest update about the delay, and the team should set a new realistic time. The customer should not have to repeat a recorded check unless a specific detail needs confirmation.

This is a designed tabletop case, not a trial with real customers or agents. It measures no resolution rate or satisfaction gain. Replace the roles, transfer rules, and times with the procedures your team has actually approved.

If a communication preference belongs in the handoff, keep it separate from the order record. The [three-part persona template](https://www.harmate.com/en/blog/synthetic-persona-template-a-minimal-card-for-testing-an-ai-assistant) separates the requested format, the facts, and the handoff policy.