A customer asks to speak with a person. The agent says it has handed the conversation over. The conversation moves into another queue, but nobody watching that queue gets a useful alert. For the customer, the handoff made the service slower while promising the opposite.

A question in Intercom's community asks who receives notifications during a handoff when staff are not watching the dashboard. That is the right operational question, since a changed assignment field is one step in getting an answer to the customer.

Name the human response that should happen#

For each escalation route, specify the receiving team, when it is staffed, and how the next person discovers the request. An urgent billing dispute and a technical investigation reach different queues. The agent should use a maintained routing rule based on the customer's issue, and never the team name that appears most often in retrieved notes.

Define what counts as receipt: accepting the conversation, taking an assigned task, or acknowledging an alert in a staffed channel, depending on the team. Delivering an alert does not prove a person accepted responsibility. If the support system already records an equivalent action, rely on it.

The customer-facing message should match that state. "Your request is in the billing queue; the team responds during these hours" differs from "A specialist is reviewing it now." The agent says the latter only when the system supports it, so staff do not inherit a promise the automation invented.

Give the recipient a packet they can act on#

An escalation contains the customer's unresolved question, the facts already established, steps already attempted, and the requested next decision. Keep the customer's own description when it carries information a summary would flatten.

Recipient needs	Useful content	Common handoff failure
Why this needs a person	Explicit unresolved question	Generic "customer needs help"
What has been tried	Steps and observed results	Another request to restart
Who owns the next reply	Team and accepted assignee	Several people merely notified
When to intervene	Response target and working hours	Unlimited waiting

Link detailed logs instead of pasting every retrieved document, and include the conversation link and the exact account. A support lead should be able to decide quickly whether to accept or reroute.

Test the unattended case#

Run a trial when the first recipient is unavailable. Verify where the request appears, who is alerted, what the customer sees, and what happens after the response target is missed.

Also test a customer who asks for a person twice. The second message should attach to the active handoff and create no second conversation for another team. A materially changed request can be rerouted, which differs from duplicating the same escalation because the customer is impatient.

If notification delivery fails, keep the conversation and its existing owner. Retry the notification through the agreed route without repeating the customer promise. If the receiving team rejects the assignment, capture why and route once to the correct destination. A case that bounces repeatedly between two rules needs a named supervisor decision.

An absent human is a staffing condition, an unread alert is a notification condition, and an incomplete packet is a preparation condition. Keep them separate so the team fixes the actual delay.

Measure the gap customers experience#

Review elapsed time from the request for a person to accepted ownership, then to a useful response. Include abandoned conversations, since excluding them rewards a workflow for losing customers before anyone replies.

Keep examples of successful and failed handoffs, with sensitive details removed, to check changes to the agent's routing instructions.

Deixic's existing-agent path lets teams keep the agent they already use and route its calls through Deixic for policy, approvals, and history. Activity details separate a requested action from its result. Start with tool connections and check the handoff operations each connector lists.