Back to blog
Sales & bookings3 min readAbdirahman Hersi, Founder

WhatsApp and SMS Customer Service with an AI Agent: What to Decide First

Messaging channels need different rules from web chat. How to think about consent, tone, length and handoff before an AI agent starts replying on WhatsApp or SMS.

A chat conversation with replies and a typing indicator
Sales & bookings

WhatsApp and SMS are asynchronous and personal channels. Decide who may write to whom, how consent is handled, how short and clear replies should be and when a person takes over. Availability depends on provider and configuration, so confirm it before you promise customers the channel.

Customers like writing on WhatsApp and SMS because they are familiar channels, they need no form and the conversation stays on the phone. For a business they are also channels with different rules from web chat. An SMS is personal, a WhatsApp thread can run for days, and the rules about who may write to whom are set by providers and by law. This article goes through what you need to decide before an AI agent starts replying.

Web chat and messaging channels are different

PropertyWeb chatWhatsApp and SMS
Where the conversation startsOn your websiteOn the customer's own phone
PaceUsually real timeAsynchronous, sometimes hours or days apart
IdentityOften anonymous until the customer shares somethingTied to a phone number
RulesYour ownThe provider's and the law's, on top of your own
Reply lengthCan be longerShould be short

The availability of WhatsApp and SMS depends on provider and configuration. Web chat is the simplest place to begin, and messaging channels can follow once knowledge and handoff work. Read about channels for an overview, and about WhatsApp and SMS separately.

Five things to decide first

  1. Who writes first. Replying to a message the customer sent is different from sending outbound messages. Assume the customer makes first contact, and clarify the rules before you do anything else.
  2. Consent and personal data. A phone number is personal data. Decide what you store, for how long and who can access it. See GDPR and data storage, and assess the requirements with qualified advice.
  3. Tone and length. Write short replies, one or two sentences, with a clear next step. Avoid tables and long lists. See tone and personality.
  4. Response time expectations. A customer can write at ten in the evening. Decide what the AI agent replies then, and what the customer is told about when a person will respond.
  5. Handoff. Decide which cases always go to a person and what travels with them. See when the AI should escalate and human handoff.

What works well in messaging channels

  • Simple questions with short answers: opening hours, address, how to book.
  • Reminders and confirmations when a booking is set up.
  • Collecting details before a person takes over.
  • Cases that are not urgent and that the customer is happy to resolve when it suits them.

What needs care

  • Sensitive cases. Health, money and complaints do not belong in an automatic thread without a clear route to a person.
  • Long conversations. When a thread grows and changes subject, the risk that the AI agent loses context is higher. Offer a handover instead of continuing.
  • Attachments and images. Decide what happens when the customer sends something the agent cannot interpret.
  • Tone. A messaging channel feels personal. A stiff reply is more noticeable there than on a website.

Test the channel before launch

Send real messages from real phones. Try short and long questions, typos, a message in another language, a message that arrives three hours later and one that just says "hello?". Check how long replies are split in SMS, that handoff works and that nobody receives an answer they should not. How to test an AI agent before you launch it has a test plan you can adapt.

Build in the right order

  1. Get knowledge and handoff working in web chat.
  2. Confirm with the vendor what is available in your configuration.
  3. Start one messaging channel with a narrow set of questions.
  4. Follow up handovers and misunderstandings, and adjust before you widen.

See how Aveexia works, read about pricing or apply for access if you want to begin.

Frequently asked questions

Are WhatsApp and SMS available to everyone?

Not necessarily. Availability and flow depend on which provider and configuration is used. Ask what applies to you before you promise customers a new channel.

Does the customer need to give consent?

It depends on who makes first contact and which rules the provider and the law set. Replying to messages a customer sent is different from sending outbound messages. Assess the requirements with qualified advice.

How long should replies be?

Short. One or two sentences and a clear next step work better than a long paragraph. SMS also has its own length limits, so test how long replies are split.

When should a person take over?

For complaints, sensitive cases, judgement calls and when the customer asks. Because the channel is asynchronous, the customer should be told when to expect a reply.

Ready to see it in action?

Book a demo