Channel & Messaging

WABA (WhatsApp Business API)

The official Meta interface that allows chatbot platforms to send and receive WhatsApp messages at scale. Controls verification, rate limits, the 24-hour messaging window, and per-conversation billing.

WABA is the technical foundation for any AI chatbot claiming “WhatsApp integration.” Without WABA approval, a platform cannot send programmatic WhatsApp messages — it can only use the WhatsApp Business App, which is designed for individual operators, not software automation.

Why it matters

Every AI chatbot platform claiming WhatsApp support is really claiming WABA access via a Business Solution Provider (BSP). The platform doesn’t talk directly to WhatsApp users — it routes through Meta’s approved infrastructure. This means the platform’s WABA-readiness and its choice of BSP define what’s actually possible on the channel.

Practical consequence: if a chatbot vendor’s WhatsApp “integration” is actually a QR-code-based WhatsApp Web session rather than WABA, you will hit rate limits within hours of any real traffic volume. Ask vendors specifically: “Are you a Meta-approved BSP or do you route through a BSP?” Both paths work, but routing through a BSP adds latency and a per-message fee ($0.004–$0.008/message depending on BSP).

How WABA approval actually works

  1. Register on Meta Business Manager — your business entity, not just an account.
  2. Submit the WABA application — handled by your BSP (ManyChat, Tidio routes through 360dialog, Freshchat is a direct BSP). Meta reviews the application.
  3. Verify the phone number — must be a dedicated number, not your personal WhatsApp.
  4. Get approved — typically 2–6 weeks. Cannot launch on WhatsApp during this window.
  5. Create message templates — “marketing”, “utility”, “authentication”, and “service” templates require separate Meta approval (1–7 business days each).

After approval, you have a WABA with:

  • A rate limit (starts at 1,000 unique users/day for new WA accounts, upgrades to 10,000 and 100,000 via quality rating)
  • Access to conversation-based billing (Meta’s per-conversation fees, not per-message)
  • The 24-hour messaging window rule

Real-world example

A Shopify DTC brand setting up WhatsApp abandoned-cart recovery using Tidio:

  1. Brand applies for WABA through 360dialog (Tidio’s BSP) — 3-week approval
  2. Configures abandoned-cart trigger in Tidio (1-2 hours setup)
  3. Submits “abandoned cart recovery” as a marketing template to Meta — 3-day review
  4. Goes live — first 1,000 conversations/month are free (Meta’s free tier); each conversation after that costs $0.014–$0.063 depending on country
  5. Monthly WhatsApp API cost at 3,000 conversations/mo: roughly $140–$200 in Meta fees + $0.004/conversation BSP fee via 360dialog + Tidio subscription

Total first-month cost including WABA setup: ~$200–$260 in WhatsApp fees alone, before the platform subscription.

Key terms to understand alongside WABA

  • BSP — the intermediary company between your chatbot platform and Meta’s API
  • Conversation-based pricing — how Meta bills for WhatsApp messages (per conversation, not per message)
  • 24-hour messaging window — the rule governing when you can send messages for free vs when Meta charges
  • Opt-in — the legal requirement to get explicit user consent before sending marketing messages on WhatsApp

Go deeper

Find your platform