How to pair website chat, WhatsApp and Messenger with SMS for follow-up: consent, timing, message design and setup in AI SNS CHAT, with its limits.
A chat ends, the visitor closes the tab, and the open question (a quote, a booking, a missing document) goes quiet. Follow-up is where many support conversations are won or lost, and no single channel covers it well. This article shows how to split the work between chat and SMS, how to handle consent, and how to set it up in AI SNS CHAT without promising things the product does not do.
Why one channel is rarely enough for follow-up
Website chat is excellent while the visitor is on the page. The moment they leave, you have no way to reach them unless they have given you something to reach them with. Email is slow and often unread. Messenger and WhatsApp work well, but only for people who already use them with you.
SMS fills a specific gap. It needs no app, no login and no open browser tab. A short text arrives on the lock screen of almost any phone in the US, UK or Asia-Pacific. That makes it a good second step when a conversation needs a nudge.
The mistake is treating SMS as a replacement for chat. It works better as a bridge: chat does the explaining and collecting, and SMS carries a small, timely reminder or a reply back into the conversation.
What each channel is good at
The two channels have different strengths. Plan around them instead of copying the same message into both.
A simple rule follows from this. Use chat to do the thinking and SMS to do the nudging. If a message needs more than two or three sentences, it probably belongs in chat, on a page, or in an email, with SMS used only to point to it.
Consent comes before any text
Collecting a phone number inside a chat is easy. Having permission to text it is a separate question, and the rules differ by country. This article is not legal advice, so check the requirements that apply to your markets and your industry.
Good habits hold up almost anywhere:
- Ask for the number for a stated purpose. "Can I text you the booking confirmation?" is clear. "What's your number?" is vague.
- Record what the customer agreed to. Store the consent as a field on the contact so that anyone on your team can see it later.
- Make stopping easy. Every marketing-style message should carry a way to opt out, and a STOP request should be honoured immediately.
- Keep to the purpose. A number given for a delivery update is not an invitation to send promotions.
Four follow-up patterns that work
Most good SMS-plus-chat follow-up falls into one of four patterns. Each starts in chat and ends with one clear action.
1. The booking reminder
The customer arranges an appointment or call through chat. Close to the time, a short text confirms the details and asks for a simple reply if the time no longer works.
2. The unfinished enquiry
The visitor asks about pricing or availability, gives a phone number and consent, then leaves before deciding. A single text the same day, sent with the context of the chat, reopens the conversation.
3. The missing detail
The agent needs an order number, a photo or a form that the customer did not have to hand. The customer says "I'll send it later". A text with a plain request and a link brings them back.
4. The human callback
A question is too complex for the AI agent, so a person takes over. If it will take time to resolve, a text lets the customer know it has not been forgotten and invites a reply in whichever channel suits them.
- 01Customer chats on the website
- 02Agent collects phone number and consent
- 03Conversation pauses or ends
- 04Customer replies by text and the thread continues
Writing the follow-up message
SMS punishes waffle. A good follow-up has four parts: who you are, why you are writing, what to do next, and how to stop.
Compare two versions of the same reminder:
- Weak: "Hi, just following up on your recent enquiry. Please let us know if you have any questions or would like to proceed."
- Stronger: "Hi Mei, this is Harbour Dental. You asked about a check-up on Thursday morning. Reply YES and we'll hold 9:30 for you. Reply STOP to opt out."
(The business and customer in that example are invented for illustration.)
The stronger version names the business, refers to the earlier chat, offers one simple reply and gives a way out. Keep these principles in mind:
- One message, one ask. Do not stack three questions into a text.
- Use the customer's own words. Pull the topic from the conversation instead of a generic template.
- Write in their language. If the chat was in Japanese or Spanish, follow up in the same language.
- Send at a sensible hour. A text at 3 a.m. local time costs you more goodwill than it earns.
Timing and measuring what matters
Timing depends on the purpose. A reminder belongs close to the event. An unfinished enquiry is usually best followed up the same day or the next, while the question is still fresh. A "we're still working on it" note should arrive before the customer starts to wonder.
Track a few simple numbers instead of vanity counts. The figures below are a hypothetical illustration of how you might compare follow-up methods, not real results.
What you actually want to know is whether the follow-up produced a booking, a resolved ticket or a reopened conversation. Compare these against a group of customers who received no follow-up, and review the unsubscribe rate as well. A rising opt-out rate means your messages are too frequent or too generic.
Common pitfalls to avoid:
- Texting people who never gave you a number or never agreed to be contacted.
- Sending the same message to everyone regardless of what they asked.
- Following up on a conversation that was already resolved.
- Forgetting to tell the human team that a text went out, so they answer the customer from a different angle.
Doing this in AI SNS CHAT
A few details about how AI SNS CHAT handles outbound contact will save you from a wrong assumption. The platform does not run SMS or email marketing campaigns. That is a deliberate choice because of consent law. Its Outbound campaigns feature (sidebar, "Outbound Beta", Standard plan or higher) sends one-to-one messages on chat channels, only to people who have already messaged you first, and every message carries a STOP opt-out. WhatsApp sends are limited to the 24-hour window. So the pattern below treats SMS as a two-way channel the customer opens, not a broadcast tool.
1. Capture the number and the consent. Add the "Collect leads" Action or a custom form to your agent. Leads appear under Activity → Leads, and every lead also creates a contact. In Contacts, define custom attributes such as "Phone" and "OK to text". The description of each field tells the agent when to ask for it, so you can write "Ask for a mobile number only if the visitor wants a booking confirmation, and ask whether they agree to receive texts." Contacts can be exported as CSV.
2. Connect the SMS channel. SMS is in the deploy list under Channels in the sidebar, alongside the chat widget, WhatsApp, Messenger and others. See /connections for the full list of channels and which are live. Several channels can serve the same agent, so the answers and guardrails you have already written for web chat carry across.
3. Review conversations in one place. Every channel except email is logged under Activity → Chat logs, where you can filter, flag, escalate, resolve and export. (Email conversations are in Inbox.) Use the thumbs up and down ratings to spot follow-ups that confuse people.
4. Let a person step in. In Chat logs you can take over a conversation, which pauses the bot. Live translation helps when the customer writes in another language, and saved replies speed up repeated answers. You can also edit a reply into the ideal answer to train the agent.
5. Route handoffs sensibly. Under Helpdesk → Scheduling (Standard or higher) you set shifts per person and timezone, and handoffs go to whoever is on shift. Alerts can go to Slack, Teams, LINE WORKS, WhatsApp, email or a webhook. When a handoff happens, the customer message includes a "what happens next" line based on the rota, and the server never invents a wait time.
Plan limits apply. Integrations need Hobby or higher, and the number of Actions per agent depends on the plan. Check /pricing and /features for current details, and /security for how data is protected. Each reply uses one credit.
Frequently asked questions
Can AI SNS CHAT send bulk promotional SMS messages?
No. SMS and email marketing campaigns are intentionally not offered. Outbound campaigns reach only people who messaged you first, one-to-one on chat channels, with a STOP opt-out in every message.
How do I get a phone number from a chat visitor?
Use the "Collect leads" Action or a custom form, and create a custom attribute for the number and for consent. The field description tells the agent when and how to ask. Each lead creates a contact you can review and export.
Where do I see SMS conversations?
Conversations on every channel other than email appear under Activity → Chat logs, where you can filter, resolve, escalate and export them. Email conversations live in Inbox instead.
What happens if the customer needs a person after a text exchange?
Take over the conversation from Chat logs and the bot pauses. If you have set shifts under Helpdesk → Scheduling, handoffs are assigned to whoever is on duty, and alerts can reach your team in Slack, Teams or email.
Should I send the follow-up by SMS or WhatsApp?
Use whichever channel the customer already used with you. WhatsApp suits people who messaged you there, but sends are limited to the 24-hour window. SMS suits people who gave you only a mobile number.


