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
| Property | Web chat | WhatsApp and SMS |
|---|---|---|
| Where the conversation starts | On your website | On the customer's own phone |
| Pace | Usually real time | Asynchronous, sometimes hours or days apart |
| Identity | Often anonymous until the customer shares something | Tied to a phone number |
| Rules | Your own | The provider's and the law's, on top of your own |
| Reply length | Can be longer | Should 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
- 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.
- 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.
- Tone and length. Write short replies, one or two sentences, with a clear next step. Avoid tables and long lists. See tone and personality.
- 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.
- 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
- Get knowledge and handoff working in web chat.
- Confirm with the vendor what is available in your configuration.
- Start one messaging channel with a narrow set of questions.
- 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.
