Migrate WhatsApp away from Twilio

Overview

Wazzap doesn't integrate with Twilio, it replaces it. Both tools route WhatsApp messages into HighLevel's Conversations tab, but they take very different paths. Twilio uses the Meta Business API with templates, BSP onboarding, and per-conversation pricing. Wazzap uses the same protocol as WhatsApp Web, scan a QR and you're live.

Why teams leave Twilio

• No per-conversation fees. Twilio bills you for every 24-hour conversation window in addition to the Meta charge. Wazzap is a flat monthly subscription, unlimited messages.
• No templates. Meta's template approval process can take days for new campaigns. With Wazzap any text goes out instantly.
• No BSP onboarding. Skip the back-and-forth verification and live with your existing WhatsApp number.
• Voice notes, stickers, reactions. Twilio's WhatsApp connector strips many of these. Wazzap forwards them through to HighLevel exactly as your customers sent them.

Migrate from Twilio to Wazzap

1. Inventory your current setup

Before you change anything, write down what's wired up:

• Which HighLevel sub-accounts route WhatsApp through Twilio today.
• Which Twilio numbers map to which HighLevel locations.
• Which automations send WhatsApp template messages, those will need to be revisited.
• Any custom code calling Twilio's API directly, that will need to point at Wazzap's API.

2. Connect your number to Wazzap

Follow the Getting started flow. Important: connect the same number you've been using with Twilio. WhatsApp allows multiple linked devices, so you don't need to detach Twilio yet.

1. Open Wazzap, click Connect a number.
2. On your phone go to WhatsApp, Settings, Linked Devices, Link a Device.
3. Scan the QR. Pairing is instant.

3. Remap HighLevel to Wazzap

In HighLevel, switch the conversation provider on the affected sub-account from the Twilio WhatsApp connector to Wazzap. The HighLevel CRM integration guide covers the mapping in detail.

Existing chats migrate by phone number, so the same contact thread continues, the only difference is the new provider on top.

4. Turn off Twilio

Once you've verified messages flow both ways through Wazzap for a few days, you can safely decommission the Twilio side:

1. Release the Twilio number (or keep it if you also use SMS).
2. Delete the Twilio WhatsApp sender from your Twilio console.
3. Cancel the per-conversation billing on Meta's side.
4. Remove the Twilio API credentials from any custom workflows.

Cost comparison

For a sub-account running 10,000 WhatsApp conversations per month, the rough comparison looks like this:

Twilio path
  Meta conversation fees:    ~$70-180/mo (variable by region)
  Twilio platform fees:      ~$50-120/mo
  Phone number rental:       ~$15/mo
  Template approval delays:  days per new campaign
  -------------------------------------------------
Wazzap path
  Flat subscription:         $19-99/mo depending on plan
  Phone number:              your own SIM
  Template approval:         none required

Troubleshooting

I pair the QR but HighLevel still shows Twilio as the provider

You need to switch the conversation provider at the sub-account level inside HighLevel. Go to Settings, Integrations in that sub-account, set Wazzap as the WhatsApp provider, and save.

Old Twilio messages don't show as Wazzap messages

Historical messages stay tied to the provider that delivered them. That's normal and expected, nothing to fix. New messages from the same contact will appear under Wazzap.

Customer says they didn't receive a message

If Twilio is still active on the same WhatsApp number, both providers compete for the session. WhatsApp will route to whichever device paired last. Disconnect Twilio's linked device on the phone to avoid the race condition.