A customer can begin a case in chat and finish it in email without thinking of it as a new case. The support record often treats the second message as a fresh contact. The result is a repeated story, a lost promise, and sometimes a duplicate refund review. A channel-switch note links the records and carries the customer goal across the gap. The note is small, but it decides whether the customer has to start over.

Confirm the switch is real

A customer may send an email after a chat ends because the chat window closed, not because they chose a new channel. Read the first email for a reference to the chat or to the same request. If the link is clear, treat it as a continuation rather than a new case. If the link is unclear, ask one short question before opening a second record.

Check whether the customer used a different address or account. A switch can hide a change of identity that affects verification and refunds. Record the address used in each channel and the account that owns the order. The case should show which identity was verified and when.

Create the link in the case tool before writing a reply. Use the customer identifier and the order key, not only the subject line. Add the chat identifier to the email case and the email identifier to the chat case. A two-way link is easier to follow than a note that points in one direction.

Give the new case an owner at the moment of the switch. An unowned email case can wait in a general queue while the chat case sits closed. The owner should be the agent best placed to continue the work, not simply the next person available. If no one can take it, put it in a named triage queue with a time limit.

Carry the context forward

Write a short summary of the customer goal in the new case. Name the problem, the requested outcome, and the deadline the customer cares about. Do not copy the entire chat transcript into the email thread. A summary that fits on one screen is more likely to be read.

List the promises made in chat with their times and conditions. A promise to call back at three o clock must survive the channel switch. If the promise cannot be kept on the new channel, say so before the customer asks. The new owner should never discover a promise by reading old messages.

Handle the attachments

Check whether the chat attachments are available in the email tool. Some chat files expire or are stored in a separate system. Download the important files and attach them to the case record. Record the file name, the date, and the source channel.

Tell the customer if a file cannot be opened on the new channel. Ask for a new copy only when the original is truly unusable. A customer who has to resend a receipt three times will lose confidence in the case. Confirm the file is readable before promising a review.

Set the reply channel

Tell the customer which channel will own the next reply. If the answer will arrive by email, say when and from which address. If the team may call, ask for a good time and a safe number. The customer should not have to watch two channels for one answer.

Update the contact preference on the customer record. A preference recorded in chat may not reach the email tool. Check that the new preference appears where the next agent will see it. A preference that lives in one channel is a hidden source of failed contact.

Close the old channel

Close the chat case with a pointer to the email case. Do not mark it resolved if the request is still open. Use a closure reason that says the work moved, and include the new case identifier. A false resolution will hide the work from the queue report.

Check the chat queue for a duplicate case created by the same customer. A customer may open a new chat while waiting for the email reply. Merge the duplicate into the linked case and note the reason. Two open cases for one request will produce two different answers.

Tell the customer what to expect

Send one short message that confirms the switch and the next step. Name the channel, the expected time, and the information the team still needs. Avoid repeating the whole history in the message. The customer wants to know that the case survived, not to read it again.

Give the customer a way to add information without starting over. A reply to the email thread is usually enough. If the team needs a file, say which format will work. Clear instructions reduce the chance of a third channel appearing.

Review the switches

Count the channel switches by reason and by queue. A switch caused by a chat timeout is a coverage problem, while a switch caused by a missing attachment is a tool problem. Report the reasons separately so the fix lands in the right place. The count alone will not explain the cause.

Read a sample of switched cases for context loss. Look for promises that were missed, files that were resent, and questions that were asked twice. Share one good example and one gap with the team each month. The review should improve the note, not blame the customer for switching.

A channel switch should feel like a continuation to the customer and like one case to the agent. The note links the records, carries the goal and the promises, and moves the files without loss. It also says which channel owns the next reply. When the handoff is written, a change of channel does not become a change of story.