Still Saying WABA? WhatsApp Account vs Messaging Account — What Marketing and IT Need
Published
On this page
Key takeaways
- The legacy WABA is becoming WhatsApp Business Account (numbers / identity) and Messaging Account (templates, billing, webhooks).
- Your WABA ID often becomes the Messaging Account ID; numbers usually stay — staged migration per Meta’s account model.
- Marketing should know which account owns templates and invoices; IT should plan for future API IDs — BSPs handle the detail.
- Cleaner accounts do not relax send limits or quality — see why sends stop.
IT says “WABA moved to Messaging Account”; marketing thinks you must re-apply for the number. Usually the customer-facing number stays — only back-office cabinets change.
Plain-language summary of Meta’s rollout (from H2 2026). Hong Kong is our primary market; the model is global for Taiwan, Singapore and APAC on Cloud API.
One WABA used to hold everything
Previously one WhatsApp Business Account bundled:
- Business phone and display name
- Message templates and review status
- Billing and webhook subscriptions
- Often partner (BSP) access too
Switching inbox vendors or adding a second integrator raised: where are templates approved? who is billed? where are reports?
Two cabinets; customers still see one number
| WhatsApp Business Account | Messaging Account | |
|---|---|---|
| Think of it as | Storefront + phone line | Template back office + billing |
| Contains | Phone number (username later) | Templates, payment methods, webhooks |
| Who cares most | Brand, support lead | Marketing, finance, integrations |
| Changing BSP | Number usually stays | Per-partner Messaging Accounts possible, billing isolated |
Users still save one verified business chat. You gain clarity on who owns which templates and invoices.
Meta Business Suite may show separate WhatsApp Accounts and Messaging Accounts tabs after migration — reorganisation, not deletion.
What changes in daily work?
Marketing / ops
- New campaigns: which Messaging Account owns the template? If you run both a legacy inbox and UFOSEND, avoid duplicate approvals for the same copy.
- Reporting: Meta message fees and BSP fees may sit in different views — reconcile account names.
IT (three sentences)
- Short term: phone number IDs mostly keep working;
waba_idoften still points at the Messaging Account. - Mid term: some API paths move to WhatsApp Business Account IDs — let your BSP track it; marketing does not need to memorise IDs.
- Coexistence numbers (app + API) follow the new model; throughput rules stay in current docs.
What to do now
- Inventory: how many numbers, BSPs, and where templates live.
- 30-minute BSP sync: migration timing, webhooks, billing entity, which Messaging Account UFOSEND runs.
- Customer-facing: same wa.me / business number — internal governance only.
Evaluating Wati or Sleekflow? Account layers make who owns which Messaging Account even more important — alternative guide.
Sending rules are unchanged
Rolling limits, template quality, opt-in still apply. The new model helps multi-partner billing, not cold-list blasting — sending reliably.
FAQ
Do we re-onboard from zero?
Most live businesses migrate automatically — follow Meta notices and Manager status.
Is the word WABA dead?
Colloquially people still say WABA. In docs, Messaging Account ≈ templates/billing; WhatsApp Business Account ≈ numbers.
Where is apply-and-verify covered?
Service and verification: WhatsApp; policy depth: Hong Kong guide.
Further reading
Structure and timing follow Meta developer documentation; whether your business has migrated is shown in WhatsApp Manager.