Back to all articlesBusiness messaging foundations

Choose which customer requests belong in messaging

Alactic Editorial11 min read

Prepared with AI assistance by Alactic Editorial. Examples identified as hypothetical are illustrative, not customer results.

A customer asks a routine question, then adds a technical fault, several documents, and a deadline that cannot wait for an asynchronous reply. Your team keeps answering in the same thread because moving the request feels unhelpful. Soon, the conversation is longer, the evidence is scattered, and nobody is sure whether messaging can actually finish the job.

Business messaging should support requests that can be resolved through short, understandable exchanges using information the team is authorised to access. It should conditionally support requests that remain manageable only within clear limits. It should not be the working channel for requests that require richer evidence, a different review environment, or intervention faster than the channel can reliably provide.

The useful boundary is not simply which topics customers may mention. It is what work your team can responsibly complete in the thread—and what happens when that limit is reached.

1. Separate receiving a request from resolving it

Customers will send requests through whichever route is easiest to find. Publishing a messaging policy will not prevent a complicated complaint or an urgent problem from arriving there.

Define two separate commitments:

  • Receiving: The team can acknowledge the request, explain the channel boundary, and identify an appropriate next route during its stated operating hours.
  • Resolving: The team can do the substantive work, reach an outcome, and communicate it within the messaging environment.

A request can be acceptable to receive without being suitable to resolve in chat. That distinction lets staff help without implying that every message creates a supported service commitment.

Use three classifications:

  • Supported: Messaging can ordinarily carry the request from question to answer.
  • Conditionally supported: Messaging can carry a defined portion of the work, provided stated conditions remain true.
  • Unsupported for resolution: Messaging is not the working environment for the request. Staff explain why and provide an alternative route.

Apply the classification to the work required, not just the customer's opening sentence. A simple delivery question may become a complaint requiring investigation. A technical question may need only one approved instruction—or a supervised diagnostic session.

2. Judge suitability against the work, not the convenience

Before assigning a request type to messaging, ask what successful resolution requires.

  • Evidence: Can staff understand the issue from a short description and existing records, or do they need multiple files, versions, detailed logs, or side-by-side comparison?
  • Interaction: Can the customer pause between replies, or does the task require continuous guidance and immediate clarification?
  • Access: Can the assigned staff member legitimately view the information and perform the requested action?
  • Time: Can the request tolerate the channel's actual response pattern, rather than the response speed the customer hopes for?
  • Closure: Can both sides recognise when the request is complete, or will the thread become an open-ended substitute for a case workspace?

Do not average these factors into a reassuring score. One hard constraint can make messaging unsuitable even when everything else looks straightforward. An apparently simple request is still a poor fit if it needs immediate intervention that the messaging team cannot provide.

Customer preference matters, but it does not remove a channel's limitations. Offer a choice among suitable routes where possible; do not present an unsuitable route as equivalent merely because it is convenient.

3. A completed hypothetical channel-fit matrix

Fictional worked example: the matrix below is a recommended design for a hypothetical equipment supplier with messaging support, a support form, scheduled technical sessions, a document-review portal, a complaints team, and a staffed urgent-support phone route during published hours. These routes and service arrangements are assumptions, not Alactic features or customer results.

Each entry contains the same fields so it can function as a matrix without hiding the conditions in footnotes.

Routine questions: supported

  • Included work: Published opening hours, product-use questions covered by approved guidance, and straightforward status questions that staff are authorised to answer.
  • Why messaging fits: The answer is bounded, little new evidence is needed, and the customer can read it asynchronously.
  • Boundary: Stop treating the request as routine when it requires investigation, access the agent does not have, or a disputed decision.
  • Alternative route: The support form for investigation, or an appropriate account-access route where verification is required.
  • Customer explanation: I can answer general questions here. This part needs an account review, so please use our account-support route. We can include a summary so you do not need to explain the issue again.
  • Completion signal: The question is answered, or the receiving route has accepted the unresolved work.

Complex troubleshooting: conditionally supported

  • Included work: Clarifying the symptom and walking through a short, approved sequence of low-risk checks that the customer can comfortably follow.
  • Why the condition matters: Text can support simple checks, but branching instructions and uncertain observations can make a long thread harder to interpret.
  • Boundary: Move the work when approved checks do not clarify the issue, instructions become ambiguous, or diagnosis requires live observation or substantial evidence.
  • Alternative route: A scheduled technical session or a support case with an appropriate evidence-submission route.
  • Customer explanation: The checks we can explain clearly in chat have not identified the cause. A technical session will let us work through the behaviour together. We will pass on the checks already completed.
  • Completion signal: The approved check resolves the issue, or a technical case or session is accepted with the prior steps recorded.

Document-heavy requests: unsupported for substantive review

  • Included work: Explaining which review route to use and how the customer can find its submission instructions.
  • Why messaging does not fit: The review depends on keeping documents, versions, and comments together in a purpose-built working environment.
  • Boundary: Do not begin reviewing a growing bundle of attachments in chat and then ask the customer to rebuild it elsewhere.
  • Alternative route: The designated document-review portal, with a support route for customers who cannot use it.
  • Customer explanation: This review needs the documents and their versions kept together. Please use our document-review route rather than sending the files here. If that route is difficult to use, tell us and we will help identify another supported option.
  • Completion signal: The submission is accepted in the review environment; sending a link alone does not establish that.

Complaints: conditionally supported

  • Included work: Hearing the concern, acknowledging its substance, clarifying the outcome sought, and resolving a straightforward issue within the agent's authority.
  • Why the condition matters: Dissatisfaction alone does not make messaging unsuitable. The limit is the investigation, evidence, or decision authority required.
  • Boundary: Move the substantive work when the complaint requires cross-team investigation, a document review, or a decision the messaging team cannot make.
  • Alternative route: A complaints case with a named receiving team and a stated next-update arrangement.
  • Customer explanation: I understand that you want an explanation and a review of the outcome. That review needs our complaints team. With your agreement, we will pass on a summary and explain how you will receive the next update.
  • Completion signal: An authorised resolution is communicated, or the complaints team accepts ownership and the customer knows how to follow up.

Time-critical requests: unsupported for urgent resolution

  • Included work: Clearly stating that messaging is not continuously monitored and directing the customer to the published urgent-support route.
  • Why messaging does not fit: An asynchronous exchange cannot substitute for a staffed route designed for immediate interaction.
  • Boundary: Do not invite the customer to wait for a chat reply when delay would defeat the purpose of the request.
  • Alternative route: The supplier's staffed urgent-support phone route during its published hours. Outside those hours, provide the actual available route or state the limitation plainly.
  • Customer explanation: This inbox is not continuously monitored and is not suitable for immediate assistance. Please use our published urgent-support phone route if it is open. Its current hours are listed with the contact details.
  • Completion signal: Staff have given accurate routing information without implying that an urgent response or successful connection is guaranteed.

4. Make conditional support a real boundary

Conditionally supported is useful only when staff can recognise when the condition has failed. Otherwise it becomes a softer label for accepting everything.

Write each condition as an observable event. “Move complex issues” leaves too much room for interpretation. “Move the request when diagnosis needs live observation” tells staff what changes the channel decision.

For the hypothetical troubleshooting row, a team could allow one approved check sequence before reassessing channel fit. That is a fictional operating choice, not a universal message limit. A customer who needs longer to describe a symptom should not be redirected merely for writing more messages.

Keep the distinction between task difficulty and communication preference. A customer may prefer written communication or be unable to use a phone route. In that case, look for a suitable written case environment rather than forcing a call or leaving the work indefinitely in chat.

5. Redirect the work without making the customer restart

A useful redirect explains the limitation, the benefit of the new route, and the next step. “Contact another department” does none of those things.

Where the receiving process permits it, prepare a concise handover containing:

  • The customer's stated problem and requested outcome.
  • Relevant steps already completed and their observed results.
  • The reason the work no longer fits messaging.
  • The receiving route and how the customer will recognise acceptance.

Transfer only information appropriate for that route and within the team's permissions. This is a workflow recommendation, not an instruction to gather additional sensitive material in chat.

Be precise about handover status. “Here is the submission route,” “we have submitted the request,” and “the receiving team has accepted it” describe different events. Do not collapse them into “all sorted.”

If follow-up happens through WhatsApp, the channel-fit decision does not replace its messaging requirements. Under the WhatsApp Business Messaging Policy, recipient permission matters, opt-outs must be honoured, and approved templates are used to initiate Platform conversations and outside the 24-hour customer-service window. A user message opens or resets that window. Template approval does not guarantee delivery; check current official requirements before implementing follow-up.

6. Recover when the alternative route fails

A boundary is not workable if its alternative is unavailable, inaccessible, or repeatedly sends customers back to messaging.

Give staff a recovery option for common failures:

  • The link does not work: Check the destination and offer an existing supported submission route. Do not ask the customer to retry indefinitely.
  • The customer cannot use the route: Identify another suitable format or arrange assistance through the receiving team.
  • The receiving team rejects the case: Resolve the ownership disagreement internally rather than making the customer negotiate between teams.
  • No suitable route exists: State the current service limitation honestly and assign someone to address the gap. Do not disguise the gap as a customer mistake.

Some continuity messages can remain in the original thread while substantive work happens elsewhere. Make clear which location owns the work so the customer does not maintain two competing accounts of the same request.

7. Publish the boundary customers actually need

The internal matrix should be detailed. The customer-facing explanation should be short and visible near the messaging entry point.

For the fictional supplier, it could read:

Use messaging for routine questions and basic product guidance. Some technical issues, complaints requiring investigation, and document reviews need a separate support route; we will explain the next step. This inbox is not continuously monitored and is not an urgent-support channel. See our contact information for available urgent-support hours and routes.

Do not claim support is immediate unless the operation actually provides it. If automated replies help customers navigate these boundaries, include a clear path to a human rather than a loop of repeated routing options.

Check every destination before publishing. A well-written explanation cannot compensate for an unstaffed phone line or an abandoned form.

8. Test the matrix against actual work

Start by reviewing a small, defined sample of recent conversations. A hypothetical pilot could examine 25 conversations across one working week; those numbers are a practical starting choice, not a benchmark.

For each conversation, record its request type, proposed classification, point at which messaging stopped fitting, alternative route, and whether that route accepted the work. Also note avoidable repetition and any customer who returned because the redirect failed.

Use the review to answer three measurable questions:

  1. How many requests could staff classify without debating the boundary?
  2. How many redirects reached an accepted destination rather than stopping at a link?
  3. How many customers had to repeat information already available to the team?

A high redirect count is not automatically good or bad. It may expose unsuitable demand, an overly restrictive matrix, or weak support in another channel. Examine the reasons before changing the boundary.

The next action is concrete: fill these five request categories with your actual routes, verify who receives each one, and test the customer explanations against recent conversations. Where you cannot name a workable alternative, you have found a service-design gap—not a finished messaging policy.

Business messagingCustomer supportChannel strategyService boundaries

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