Back to all articlesBusiness messaging foundations

Decide whether customers need a new messaging channel at all

Alactic Editorial10 min read

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

A customer asks whether they can message your business. A competitor adds a chat button. Your team proposes a new inbox. None of those events, alone, establishes that customers need another channel.

Your business needs customer messaging when there is credible evidence that a meaningful customer task is difficult through existing channels, that messaging addresses the difficulty, and that your team can support it without creating a new service failure. Otherwise, improve the current route or gather more evidence before buying tools.

The useful question is not whether messaging is popular. It is: Which customers cannot complete which tasks today, and why would messaging change that? The completed worksheet below shows how to answer that question without turning a channel preference into a business case.

1. Define the blocked task before discussing the channel

Start with a task narrow enough to examine. “Improve customer communication” is too broad. “Let customers correct an appointment detail without waiting on the phone” describes something observable.

For each candidate task, write down the intended outcome, the current contact route, and the point where customers encounter difficulty. Distinguish inability to make contact from inability to get an answer. A new inbox might address the first while leaving the second untouched.

  • Access problem: Customers cannot use the available route when they need it, or the route is difficult for them to use.
  • Process problem: Customers can make contact, but staff lack the information, ownership, or authority needed to resolve the request.
  • Information problem: Customers contact the business because an answer is missing, unclear, or out of date.
  • Capacity problem: Requests arrive faster than the team can handle them.

These problems can overlap. Classifying them still matters because the remedy differs. Messaging does not supply missing appointment information, decide who owns a complaint, or create staff time. It may make submitting a request easier while making the unresolved queue larger.

2. Keep preferences, difficulties, and behaviour separate

Build your decision from distinct types of evidence rather than a single vote for messaging.

  • Actual contact difficulties: Records or specific accounts of customers failing, waiting, repeating themselves, or abandoning a task.
  • Stated preferences: What customers say they would like to use, ideally tied to a particular task and circumstance.
  • Observed behaviour: What customers actually do when routes are available, including switching channels and making repeat attempts.
  • Underserved tasks: Important jobs that existing routes do not serve adequately, including needs hidden by low contact volume.
  • Plausible alternatives: Changes that could remove the difficulty without adding a channel.

Do not treat these categories as interchangeable. A request for messaging can reveal a genuine preference without proving that the customer would use it for an urgent issue. Heavy phone use can reflect convenience, but it can also reflect having no workable alternative.

Low contact volume is similarly ambiguous. Customers may have everything they need, or they may have given up. Where the evidence cannot distinguish those explanations, record the uncertainty rather than choosing the explanation that supports the proposed purchase.

Use existing contact records, specific customer accounts, and a small review of unresolved tasks. You do not need to launch a formal feedback programme to establish whether there is a problem worth investigating.

3. Completed hypothetical customer-demand evidence worksheet

Fictional worked example: The business, observations, counts, time periods, and targets in this worksheet are hypothetical. They illustrate a decision method, not customer research findings or Alactic results.

A fictional equipment-servicing business takes bookings through its website and handles questions by phone and email. Its leadership is considering customer messaging. The operations lead reviews a hypothetical fortnight of contact records and a small set of customer accounts.

Decision under review: Should the business introduce messaging for appointment-related requests? The review excludes promotions and broader sales conversations.

Worksheet entry A: Correcting appointment details

  • Customer task: Correct an address or access instruction before a scheduled visit.
  • Actual contact difficulty: In the hypothetical review, 14 customers made repeat attempts about corrections. Nine first tried calling during a busy period; five emailed but were unsure whether anyone had seen the correction.
  • Stated preference: Six customers specifically requested a written, asynchronous way to submit a correction without staying on the phone.
  • Observed behaviour: Eight of the 14 used both phone and email for the same correction. This shows unresolved uncertainty, not necessarily demand for another channel.
  • Underserved need: Submit a short correction and receive a reliable confirmation that it has been handled.
  • Plausible non-messaging remedy: Assign ownership of correction emails, publish realistic handling expectations, and acknowledge completion rather than receipt alone.
  • Interpretation: There is credible task friction and some support for asynchronous contact. Evidence does not yet show that email itself is the obstacle.
  • Next decision: Repair the email workflow first, then reassess repeat attempts.

Worksheet entry B: Sending a photo before a visit

  • Customer task: Send a photo of equipment so the business can assess what information is needed before the visit.
  • Actual contact difficulty: Seven hypothetical customers reported difficulty using the website attachment form. Staff records noted failed submissions but did not establish the cause.
  • Stated preference: Five asked whether they could send the photo through a familiar messaging service.
  • Observed behaviour: Four eventually sent email attachments; three did not complete submission. There is no evidence about whether those three abandoned the booking.
  • Underserved need: Submit an image from a phone and know whether it reached the responsible team.
  • Plausible non-messaging remedy: Investigate the attachment form, make requirements clearer, or provide a clearly explained email alternative.
  • Interpretation: Messaging is plausible, but the present evidence cannot separate a broken submission route from a durable channel need.
  • Next decision: Gather more evidence by observing the failed task and testing the repaired route before introducing another inbox.

Worksheet entry C: Getting an arrival update

  • Customer task: Find out whether a scheduled visit is still expected within the communicated arrival period.
  • Actual contact difficulty: Eighteen hypothetical callers wanted updates. In 12 cases, the person answering had no newer information to provide.
  • Stated preference: Several callers wanted an update without making a call; the review did not consistently record a preferred channel.
  • Observed behaviour: Customers called again when no useful update was available.
  • Underserved need: Obtain accurate, timely information, rather than merely reach a different contact point.
  • Plausible non-messaging remedy: Establish who updates arrival information and how staff communicate changes through existing routes.
  • Interpretation: The dominant failure is missing information. A messaging channel would inherit it.
  • Next decision: Improve the update process; do not use these calls as evidence for launching messaging.

Worksheet entry D: Contacting the business outside phone hours

  • Customer task: Leave a non-urgent booking question when calling is impractical.
  • Actual contact difficulty: Staff noted unanswered calls outside opening hours, but the review could not connect them to identifiable tasks or outcomes.
  • Stated preference: Two hypothetical customers said messaging would be convenient.
  • Observed behaviour: Some customers already sent evening emails, but the review did not establish how many received useful replies or booked later.
  • Underserved need: Possible out-of-hours submission need; scale and consequences remain unknown.
  • Plausible non-messaging remedy: Make the email route and response expectations easier to find.
  • Interpretation: A plausible hypothesis, not enough evidence for a launch.
  • Next decision: Review specific missed-contact cases and the visibility of existing asynchronous contact options.

Overall worksheet decision: Do not launch a general messaging channel yet. Repair correction handling and arrival information, investigate photo submission, and clarify the out-of-hours evidence. This is a decision to address demonstrated problems first, not a claim that messaging will never be useful.

4. Compare messaging with the smallest credible alternative

The comparison should not be “messaging versus doing nothing.” Compare messaging with the least disruptive change that could plausibly solve the same task.

For appointment corrections, that alternative might be a better-owned email queue. For a missing answer, it might be clearer information before the customer starts contacting you. For a failed submission, it might be repairing the existing form.

Compare each option on the same questions:

  1. Does it remove the specific obstacle, or merely move the request?
  2. Can customers discover and use it in the circumstances that caused the difficulty?
  3. Who owns the request through to resolution?
  4. What new work, duplicate contact, or uncertainty could it create?
  5. What outcome would show that it helped?

Messaging may still be the stronger option. For example, a task may require short exchanges that customers cannot conveniently handle through the current routes. But record that mechanism explicitly. “Customers like messaging” is weaker than “customers need to clarify a detail asynchronously, and the available routes prevent them from completing that exchange.”

5. Choose among three decisions, not just yes or no

Introduce messaging in a bounded test when the task failure is established, messaging has a credible advantage over realistic alternatives, and someone can own the work. Define which tasks the test serves and which remain elsewhere.

Improve an existing channel when the dominant cause is unclear information, poor routing, slow handling, or a defective submission route. Recheck the original problem after the repair rather than assuming that completing the repair proves success.

Gather more evidence when the task, cause, or consequence remains uncertain. Specify the missing fact. “We need more research” is open-ended; “we need to see why customers cannot submit photos from their phones” is actionable.

Do not average strong and weak evidence into an artificial score. A serious obstacle affecting a small but clearly identified group may justify action. A large collection of vague preferences may not. Explain whose needs the decision serves and whose remain unresolved.

6. Make any test capable of disproving the idea

If messaging survives the comparison, test the customer problem rather than the attractiveness of a new contact button. Message volume alone is not success: it may represent contacts moved from email, duplicate requests, or new confusion.

Choose a primary outcome tied to the task, then watch for displaced work. Useful measures include completed tasks, repeat contact for the same issue, time to a useful answer, unresolved requests, and staff handling effort. Record definitions before the test so a receipt acknowledgement does not become a completed resolution.

For a hypothetical appointment-correction test, the primary outcome could be fewer repeat attempts per correction. Supporting observations could include whether corrections reach the responsible team and whether customers understand when a change is confirmed. A guardrail could be no increase in corrections left unresolved before visits.

Keep other major changes visible. If staffing, response ownership, and the channel all change together, an improved result does not establish which change mattered. You may still have improved service, but the evidence for keeping the extra channel remains weaker.

7. Plan for failure and make the next action measurable

A channel test can fail even when customers use it. Staff may lack access to answers, customers may interpret submission as confirmation, or urgent requests may enter a queue intended for non-urgent work. These are reasons to narrow, repair, or stop the test—not to count activity as success.

Before opening a new route, decide how unresolved requests will reach a responsible person. Keep existing routes available for customers who cannot or do not want to use messaging. If the test ends, finish outstanding conversations and clearly direct future requests to a supported route rather than leaving an unattended inbox.

Your next action is to complete a worksheet entry for one disputed task, not to select a platform. Record a concrete difficulty, separate preference from behaviour, name a non-messaging remedy, and write the missing evidence or decision.

For the fictional business above, the next step is a hypothetical two-week correction-email repair. The operations lead would track repeat attempts, completed corrections, and requests still unresolved before visits. A hypothetical decision threshold might be a reduction from 14 repeat-contact cases to seven or fewer, with no increase in unresolved corrections, provided task volume is comparable.

That threshold is an internal test choice, not a benchmark. If volume changes substantially, compare repeat-contact rates and inspect the cases rather than relying on counts alone. If the repair works, defer the channel launch. If it does not, examine whether the remaining obstacle is genuinely something messaging can remove.

Customer messagingChannel strategyCustomer experienceDemand evidence

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