Turquoise and peach ceramic speech bubbles connected by a cream paper bridge carrying a cobalt marker toward a brass tray.
Original AI-generated editorial illustration; not a real account, product sale or completed job. View full-size image.

A live chat handover should tell the next agent what the customer is trying to do, what has been confirmed and what action is still needed. Link to the authorised conversation record, separate internal context from the customer-facing reply, and name the next owner. Don't promise a resolution or response time you can't authorise.

This is a proposed support workflow using an invented conversation about a downloadable workshop pack. No real customer, support account or response-speed test is represented. Follow the organisation's actual access, verification and escalation procedures before handling a live request.

1. Start with the customer's unfinished task

In the fictional conversation, a customer says they cannot find the download they expected. The unfinished task is getting access to the correct material. The agent hasn't yet confirmed the order, the customer's access rights or the cause of the problem. Keep those points separate from what the customer reported.

A handover opening could read: “Customer reports a missing download. No access change has been made. Next agent needs to follow the approved verification process and check the relevant record.” That wording preserves uncertainty without repeating the entire conversation.

Use a reference to the authorised support record rather than copying personal details into an informal team message. Ask for the access needed to do the assigned work. Don't expand the task into account changes or data collection because it might make the investigation easier. The virtual assistant guide covers defining the boundaries of delegated work.

2. Separate reports, checks and decisions

Use distinct fields for what the customer said, what the agent checked and what an authorised person decided. “Customer reports a failed link” differs from “agent confirmed the link fails.” A confident summary can otherwise turn a report into an apparent finding.

For a practice handover, use a compact record:

Field Example entry
Customer's task Obtain the expected workshop pack
Confirmed action No replacement access issued
Open question Relevant record still needs checking
Next owner Assigned support agent, using the approved queue

The entries are fictional. Add a time or record reference only when it comes from the real system. Avoid invented urgency labels or claims that a particular person has accepted the task. If ownership is still being arranged, state that clearly.

3. Separate the customer reply from internal context

Zendesk's ticket-comment guidance distinguishes public replies from internal notes. Public comments can be read by people with ticket access, including copied recipients; internal notes are for agents rather than the requester or copied end users. Check the intended channel before submitting a comment.

Keep the customer's next instruction in the customer-facing reply. Put the investigation context in the approved internal place. Internal visibility is not a reason to copy passwords, full payment details or unrelated personal information into a note. If sensitive material has already been posted, follow the organisation's escalation procedure; changing the conversation summary doesn't remove the original.

For the fictional missing-download request, a customer reply might explain the next approved verification step. The internal note could say that no access change has been authorised. Neither message should announce that a replacement has been sent when it hasn't.

4. Record the next action and its stopping point

Tell the next agent what to do after reviewing the existing record and when to stop for an authorised decision. A useful next action is specific enough to perform without inventing a policy. “Check everything” leaves the scope open; “approve the request” assumes authority the receiving agent may not have.

In the practice case, the next agent follows the approved verification process and checks whether the requested material corresponds to the relevant record. If that cannot be established, the agent uses the agreed escalation route. The handover should not contain a workaround for bypassing that check.

State what the customer has already been told about the next step. If no response time was authorised, don't turn a friendly estimate into a promise. The client onboarding handover guide can help distinguish receiving a task from being allowed to perform every action associated with it.

5. Review a prepared reply before applying it

Zendesk's macro documentation describes macros as prepared responses or actions applied manually. Its preview shows the fields and elements a macro may change. A macro can affect more than the visible wording, so inspect the proposed changes and edit the response for the current request before submitting.

In this fictional exercise, a prepared reply referring to a replacement file would be inappropriate before a replacement is authorised. Review names, references and any implied completed action. A fluent template can still describe the wrong state of the conversation. These documentation features do not prove that a particular account has the permissions or setup required for your task.

6. Check that the handover reached an owner

Saving a note doesn't establish that another agent has taken responsibility. Use the organisation's actual assignment or queue process, then check the resulting state. If ownership remains uncertain, preserve that uncertainty in the handover instead of closing the conversation as resolved.

Read the summary once as the receiving agent. Can you locate the source conversation, identify the unconfirmed point and find the next permitted action? If the answer depends on a private side conversation, put the necessary context in the approved record without copying unrelated information.

The community moderation handover guide concerns a different task: handling community rules and moderation decisions. Customer support needs its own request history and action boundaries.

7. Practise without a live customer record

Use the invented missing-download conversation to write a handover, a proposed customer reply and an internal note. Ask a reviewer to identify which statements are reports and which are confirmed actions. Then ask them what would require escalation. If they infer that access was issued, revise the wording before treating the exercise as complete.

Deliver the example with the current procedure references and a list of unresolved setup questions. Don't publish a real conversation as a portfolio sample or claim a tested resolution rate from this exercise. The goal is a clear transfer of work that the next authorised person can continue safely.