Moving a WhatsApp chatbot to SMS or Telegram
The October 2026 WhatsApp service-message fees give some teams a reason to reconsider a WhatsApp-only chatbot. Moving channels can help, but it changes the user journey as well as the bill. Here is how to assess the options without losing the people your service needs to reach.
Since 1 October 2026, Meta charges for delivered outbound WhatsApp service messages after the first 1,000 per business phone number each month. An exception exists for eligible government and nonprofit organisations through 2027, but nonprofit status alone does not establish that your account has the waiver. Confirm eligibility and your actual charges before planning a move.
Why reassess a WhatsApp-only chatbot?
Service messages are the non-template replies a chatbot or support team sends within an open 24-hour customer service window. They used to be free at Meta's platform layer. Under the current service-message rules, their volume can now matter as much as template volume to a programme budget. Meta's monthly free tier and eligibility policy must both be applied to your own account. Your messaging provider may also charge separately.
This does not mean every chatbot should leave WhatsApp. Many audiences already use it, and moving them introduces friction. The useful question is whether every interaction needs to happen there, or whether another channel can serve a particular audience and journey better.
Compare the channels for your audience
| Channel | What to test | Cost and delivery considerations |
|---|---|---|
| Existing audience reach, familiar media and interactive journeys. | Model Meta service and template charges, provider fees, and any confirmed waiver. Keep the channel if its reach justifies its cost. | |
| SMS | Whether users can complete a shorter, text-first journey on any SMS-capable phone. | Outbound SMS is normally charged by a gateway; long or Unicode messages may use multiple billable segments. Inbound costs and delivery vary by provider and route. |
| Telegram | Whether your audience already uses Telegram or will adopt it for this service. | Bot messaging has a different commercial model, but onboarding, connectivity, support and any paid infrastructure still matter. Do not assume Telegram has WhatsApp's reach. |
The lowest price per message is not necessarily the lowest cost per completed outcome. Compare successful registrations, resolved queries or completed lessons, not only message totals.
What must change when you move?
A chatbot is not a file that can simply be copied to another channel. Each route has different interaction and identity rules. Before migrating, inventory:
| Area | What to check |
|---|---|
| Audience and permission | Who can you reach on the new channel, and what consent or opt-in must be collected again? Do not assume WhatsApp consent covers SMS or Telegram. |
| Journey design | Replace channel-specific buttons, lists, media or templates with interactions that work in the destination channel. SMS usually needs concise numbered replies and clear recovery paths. |
| Identity and continuity | Decide how a user's existing record is matched to a new channel without exposing personal information or creating duplicates. |
| Integrations and reporting | Recheck external APIs, helpdesk handover, analytics, message status and data-retention requirements. |
| Support and failure modes | Test delivery gaps, unexpected replies, opt-outs, inaccessible media and a route back to a person. |
A phased approach is usually safer
- Measure
Export several months of outbound non-template WhatsApp volume, template volume, unique users and completed outcomes. Separate users by country and confirm the actual billing and waiver status.
- Choose one journey
Select a high-volume, low-complexity use case and compare WhatsApp, SMS and Telegram against audience access and total operating cost.
- Adapt and pilot
Rebuild channel-specific steps, test consent and identity matching, and run a small pilot with real users before making the new route prominent.
- Offer a choice
Where the audience is mixed, keep WhatsApp available while introducing the new route. Move traffic based on observed completion and support needs, not just a fee forecast.
Where RapidPro fits
RapidPro provides a way to operate messaging workflows across channels, including SMS, Telegram and WhatsApp, rather than rebuilding an entire service around one provider. That does not make flows automatically identical or erase channel fees. It gives a team a common place to design journeys, integrate systems and compare outcomes while adapting each route to its users.
For programmes that need control over hosting location, code and database access, BotFlow Host operates dedicated RapidPro infrastructure. We can assess an existing chatbot, plan a channel pilot and specify the migration work before recommending a full switch.
The decision
First confirm what your WhatsApp account is actually charged, including whether a waiver has been granted. Then compare channels against reach, completion, consent and total cost. The best outcome may be a multi-channel service, not abandoning WhatsApp altogether.
Considering another channel for your chatbot?
We can review your message volumes and user journeys, then scope a WhatsApp, SMS or Telegram pilot around the people you need to reach.