Tell customers where messaging ends and another channel begins
Prepared with AI assistance by Alactic Editorial. Examples identified as hypothetical are illustrative, not customer results.
“Please call our service team” leaves several questions unanswered: Why can’t this be resolved here? Will someone be expecting the call? Does the customer need to explain everything again? And what happens to the request already made in messaging?
To set expectations when moving customers from messaging to another channel, explain the reason for the move, identify who must act next, describe what information will and will not carry over, and give a recovery route. Make those statements before asking the customer to leave the conversation.
The goal is not to promise a seamless experience that the business cannot support. It is to make the boundary understandable enough that customers can choose their next step without guessing.
1. Define what ends, not just where to go
A destination is not an explanation. An email address tells customers where to write, but not whether messaging support has finished its work or whether the email starts a separate request.
For each channel boundary, distinguish three things:
- What messaging can still do: explain options, answer general questions, or help the customer find the correct route.
- What requires another channel: the specific action or decision that cannot be completed in this conversation.
- What changes after the move: the responsible team, the next action, and the information the customer may need to provide again.
A useful explanation is task-specific. “The repairs desk needs to ask follow-up questions while you are beside the equipment” explains the purpose of a call. “This is our process” does not.
Also distinguish a required move from a suggested one. If a call is simply easier for the team, do not describe it as the only way forward. If messaging genuinely cannot complete the task, say what remains possible there rather than implying that all help has ended.
2. Make a small, testable transition promise
A transition message should answer six questions. They need not appear as six separate sentences, but none should be left to inference.
- Why move? Name the task-specific reason.
- Who acts next? Say whether the customer must call, submit something, or wait for contact.
- Who takes responsibility next? Name a recognisable team or service route, not an unexplained internal label.
- What carries over? State only what the next person can genuinely use.
- What must be repeated? Identify likely repetition, including any checks that must happen again.
- What if the move fails? Give a route for reporting an inaccessible form, an unanswered request, or an unsuitable channel.
There are different levels of continuity. At the weakest level, the customer starts a new request. At another level, they can quote a reference that helps locate an existing request. At a stronger level, the receiving team can see some prior information. These are not interchangeable.
A reference number is not proof that the next adviser can read the conversation. Even where information is available, the customer may still need to confirm details. Describe that limit directly rather than promising “You won’t need to repeat anything.”
3. Use a filled channel-transition matrix
Fictional worked example: The following matrix describes a hypothetical equipment supplier. Its routes, responsibilities, reference numbers, and timing commitments are illustrative, not Alactic features or customer results. Each numbered entry is one matrix row, presented as a reusable record.
Row A: Messaging to a customer-initiated service call
- Request and reason: A customer wants help identifying an equipment fault. The service desk needs a live exchange while the customer can access the model label and describe the symptoms.
- Next responsible party: The customer calls; the service desk takes the next stage.
- Customer choices: Call when beside the equipment, or ask in messaging about an alternative if a voice call is unsuitable. Messaging can still explain what to prepare.
- Continuity limit: The desk can locate the request using reference R-214, but cannot see the messaging conversation. The customer must restate the symptoms and confirm the model.
- Recovery: If the customer cannot reach the desk, they can return to messaging and report that the call did not connect. Messaging can explain the available alternatives, not promise an immediate callback.
- Reusable message brief: Explain why a live exchange helps; identify who calls; name the desk; list the details to have ready; disclose that the conversation is not visible; offer a route for customers who cannot use voice.
Row B: Messaging to an email review
- Request and reason: A customer disputes an invoice item. The billing team reviews invoice queries through its email route; messaging can explain that route but cannot make the adjustment.
- Next responsible party: The customer emails the billing team. The billing team replies by email.
- Customer choices: Use the published billing email route, or ask in messaging for help understanding what to include. There is no promise that messaging can submit the query on the customer’s behalf.
- Continuity limit: The email begins a separate review. The customer must include the invoice reference and disputed item. The messaging exchange is not attached.
- Timing: The hypothetical team aims to give an initial reply within two business days, not resolve every dispute within that period.
- Recovery: After that period, the customer can reply to the same email asking for an update or return to messaging for routing help.
- Reusable message brief: Separate review from resolution; specify the minimum details needed; disclose the separate request; identify where the reply will arrive; explain what to do if it does not.
Row C: Messaging to a customer-requested callback
- Request and reason: A customer wants to discuss a complex installation estimate. A scheduled conversation allows the estimating team to work through the questions together.
- Next responsible party: The customer chooses whether to request a callback. Once the request is confirmed, the estimating team is responsible for calling within the agreed period.
- Customer choices: Request a callback or continue with general written questions. A detailed estimate discussion requires the estimating team, but a call is not presented as compulsory for every enquiry.
- Continuity limit: The estimating team has the enquiry reference and broad topic, not the complete messaging conversation. The customer may need to repeat requirements.
- Timing: A callback is described as requested until the business confirms a period. No customer is told to wait for an unconfirmed appointment.
- Recovery: If the confirmed period passes, the customer can return to messaging with the enquiry reference and request a new arrangement.
- Reusable message brief: Ask whether a callback is wanted; distinguish request from confirmation; state what context the caller will have; explain the missed-callback route.
Row D: Messaging to an online service form
- Request and reason: A customer wants to arrange a return. The returns form collects the details needed to assess the request; discussing a return in messaging does not submit it.
- Next responsible party: The customer submits the form. The returns team then reviews the submission.
- Customer choices: Use the form or ask for an assisted alternative if they cannot access or complete it. The alternative must be confirmed, not invented in the message.
- Continuity limit: The form does not contain the messaging history. The customer must enter the order reference, item, and reason again. Submission is not approval.
- Recovery: If no submission confirmation appears, the customer should not assume the request was received. They can return to messaging for help establishing the next step.
- Reusable message brief: Explain why the form is needed; list what to prepare; distinguish submission from approval; describe the expected confirmation; provide help if the form fails.
4. Turn the matrix into messages people can use
The matrix is a decision aid, not text to paste in full. Convert the relevant row into a short explanation that answers the customer’s immediate concerns.
Hypothetical message for Row A:
The service desk needs to ask follow-up questions while you are beside the equipment, so the next step is a call to that team. Please use the service number on your order confirmation and quote R-214. They can locate the request, but they cannot read this conversation, so you will need to describe the fault again and confirm the model. If a voice call is unsuitable or you cannot connect, reply here so we can explain the available alternatives.
Hypothetical message for Row B:
The billing team needs to review the disputed item through its email route; I cannot adjust it in this conversation. Please use the billing email address on your invoice and include the invoice reference and the item you are querying. That starts a separate review, and this chat will not be attached. The team aims to send an initial email reply within two business days; that is not a resolution deadline. If you have no reply after that, follow up on the same email or return here for routing help.
Both messages acknowledge an inconvenience rather than hiding it. If the repetition is substantial, explain the minimum the customer needs to repeat. Do not ask them to recreate the entire conversation when a short description will do.
5. Offer choices without disguising the limits
Choice is useful only when each option is real. “Call or email us” is misleading if the email team will simply tell the customer to call.
Describe alternatives by what they can accomplish. For example, messaging might help the customer prepare details, while a specialist route makes the decision. That is a meaningful distinction even when messaging cannot finish the request.
Customers may be unable to use voice, open a form, or access the email address associated with an earlier enquiry. Ask what makes the proposed route difficult without demanding unnecessary personal explanations. Then identify an available alternative or explain that one still needs to be established.
There is a trade-off between brevity and completeness. Put the reason, next actor, and important continuity limit in the first message. Add preparation details when relevant. Do not bury “you must submit a new request” beneath a long list of helpful tips.
6. Plan for the transition that does not happen
A transition can fail before the receiving team does any work. The customer may not place the call, may misunderstand who is calling, or may submit a form without seeing confirmation.
- The customer thought someone would call: Clarify who was expected to act. Offer the next available route without treating the misunderstanding as customer error.
- The receiving team cannot find the request: Correct the earlier continuity claim. Say what information is now needed rather than insisting the reference should work.
- The customer refuses to repeat the story: Acknowledge the burden, explain the actual visibility limit, and identify the shortest useful restatement. Do not claim to have transferred context unless that is confirmed.
- The expected reply does not arrive: Use the stated recovery route. Avoid creating another request unless that is genuinely necessary.
- The suggested route is inaccessible: Stop repeating the same instruction. Establish an alternative before presenting it as available.
“You are now with billing” should mean billing has actually taken responsibility, not merely that the customer has been shown an email address. When that has not happened, say “Your next step is to contact billing.”
7. Check the promises against observable evidence
Before publishing transition wording, verify each claim separately. Can the receiving team actually use the reference? Can it see the conversation, a summary, or neither? Is the response period a supported commitment or just a hopeful estimate?
Keep timing states distinct: a request can be suggested, submitted, acknowledged, accepted, or resolved. A message should describe the state that exists, not the one expected later.
Likewise, confirm what happens to the messaging conversation. If it will close, say so and explain how to ask for routing help again. If it remains available only for general questions, do not imply that it will provide progress updates.
These checks concern the customer-facing promise. They do not require describing internal systems or technical arrangements to the customer.
8. Test one boundary before rewriting every message
Start with the transition that produces the most visible confusion. Fill one matrix row, verify its claims, and replace the current wording.
Hypothetical review plan: Examine the next ten transitions using that wording. Record whether each message explained the reason, identified the next actor, named the receiving team, disclosed continuity limits, and supplied a recovery route. Separately note customer replies such as “Will they call me?” or “Do I have to explain this again?”
Count clear messages separately from completed transitions. A well-explained move can still fail because the route is unavailable; a completed move can still leave the customer confused.
Use the review to change a specific sentence or correct a specific promise. The useful outcome is not simply fewer messages in the original channel. It is fewer customers left uncertain about who acts next and what starting the next step will require.
Put the next conversation to work.
Explore Alactic Communications for WhatsApp conversations, campaigns and AI-assisted workflows. Choose the product and plan that fit your team.
Explore Communications