Skip to content

Transfer or return a conversation

Transfer a conversation when another processor or queue is better placed to help. Check the current ownership before acting.

Transfer safely

  1. Open the conversation and confirm that you are allowed to manage it.
  2. Choose Transfer.
  3. Select the intended available processor or return it to a queue.
  4. Check the destination shown in the confirmation dialog.
  5. Confirm the transfer and inspect the resulting state.

The new owner must still have the required membership, Ticket Processing access, queue rights and capacity. An old browser view does not retain permission to reply after ownership changes.

Return to Sherpa

Use the explicit return-to-AI action when automated assistance should resume. Do not assume Sherpa takes over simply because a processor stops typing. New customer actions remain subject to the current conversation state and permissions.

Connection loss and waiting

If a processor loses the connection, availability eventually becomes stale. Eos can return the conversation to a waiting state after the recovery window. The customer should see a truthful waiting state rather than a claim that a person is present.

A timeout does not silently create another ticket. Offer ticket follow-up or continued waiting as appropriate.

Check the result

Verify the owner, queue and state. If a public reply was being sent during transfer, inspect the actual transcript before retrying it. See the conversation states reference.