woman, girl, lady, young, talk, talkig, mobile, phone, smart phone, smartphone, cell phone, closeup, portrait, human, female, technology, device, nails, eyelashes, face, hand, fingers, talk, talk, talk, talk, talk, phone, phone, smart phone, cell phone, cell phone, cell phone, nails
Photo by kaboompics on Pixabay

Routing & Automation

Part of Live chat and messaging support

Preserving context when a conversation changes channels

Carry the issue, verification status, open action and reply route when a support conversation changes channels, while checking delivery limits.

Desk Service Operations · · 3 min read

When a customer moves from chat or messaging to email, phone or another supported route, carry forward the context the next agent needs. Keep the work on the same case where the system supports it.

A shared inbox does not prove that a new contact has been matched to the right person or issue.

Record what the next agent needs

Before changing channels, leave a short handoff covering:

  • The customer’s question and what has already been answered.
  • Details supplied by the customer, distinguished from details verified elsewhere.
  • The open action, its owner and any promised update.
  • The address, number or account intended for the next reply, and whether it has been verified as appropriate.
  • Private staff notes that must stay separate from customer-facing text.

Keep the original messages available where possible. A summary helps the next agent act, but it may omit a qualification in the customer’s own account.

Mark uncertain details as uncertain. Avoid copying unnecessary personal information into a new note.

Identity verification in one exchange should not be assumed sufficient for every later disclosure or channel.

Key steps to preserve context when switching support channels

  • Summarise the customer’s question and what’s already been answered
  • Distinguish customer-supplied details from verified information
  • Document open actions, owners, and promised updates
  • Confirm the correct reply address, number or account is used and verified
  • Keep private staff notes separate from customer-facing text

Check that the switch is supported

Zendesk’s Agent Workspace can handle multiple channels within a ticket, but available reply choices depend on the configured channels and conversation state. Its documentation gives email follow-up after a chat ends as an example.

An email reply requires an available customer email address; an ended live chat cannot be resumed through the chat composer.

Help Scout creates an Inbox conversation containing the chat transcript and internal notes when live chat ends. An optional transcript emailed to the customer excludes private notes.

If the chat was never accepted by a Help Scout user, Help Scout says no email transcript goes to the customer. The Inbox conversation remains available for the team to follow up by email.

If a channel change creates a new record, link it to the original where the system permits. Make one record responsible for the next customer reply.

Similar names alone are not a reliable basis for merging contacts. Verify the destination and identity under the organisation’s procedure before sharing account details.

Channel switching support in Zendesk vs Help Scout

  • Zendesk Agent WorkspaceSupports multiple channels within one ticket; email follow-up possible after chat if email is available
  • Help Scout InboxCreates an Inbox conversation with chat transcript and internal notes; optional email transcript sent to customer (excludes private notes)
  • Unaccepted live chat in Help ScoutNo email transcript sent to customer; Inbox conversation remains for team follow-up
  • Draft messages across channelsNot carried over; drafts remain tied to original channel composer

Check the next reply

The receiving agent needs the last public message and relevant private context before replying. Check both the destination channel and whether the composer is set to a public reply or an internal note.

In Zendesk, drafts remain with their respective channel composers. Switching channels does not carry draft text into the new composer.

Some social messaging channels restrict when an agent can reply. Zendesk documents channel-dependent timeouts.

If the original route has expired, arrange a supported alternative. Keep the customer contact open until the next step is clear.

Before sending, confirm the composer is set to a public reply. For an email follow-up, confirm a customer email address is available on the record.

Verifying context before replying after a channel change

  1. Review the last public message and relevant private notes
  2. Ensure the composer is set to public reply, not internal note
  3. Confirm a valid customer email address is on record for email replies
  4. Check for channel-specific reply restrictions or timeouts
  5. If original route expired, arrange a supported alternative and keep contact open

More in Routing & Automation