The WhatsApp Business API via Twilio, explained

The WhatsApp Business API is Meta's programmatic messaging platform, and Twilio is one of the official ways to access it. You don't install an app or scan a QR code the way you would with WhatsApp Business on a phone. Instead, your systems send and receive WhatsApp messages through Twilio's API, the same way they already send SMS, so a lead can message your WhatsApp number and land straight in your CRM or automation.

What you're actually connecting to

Twilio doesn't own WhatsApp — it's an approved Business Solution Provider sitting between your application and Meta's WhatsApp Business Platform. Your number gets registered with Meta, your business gets verified, and Twilio exposes it through the same API shape as its SMS and voice products. If your CRM or booking system already talks to Twilio for SMS, adding WhatsApp is mostly configuration, not a rebuild.

Template messages vs. session messages

This is the single most misunderstood part of the API, and it's the part that trips up almost every first-time setup:

• Session messages can be free-form, written however you want, but only inside a 24-hour window that opens the moment a customer messages you first. Once that window closes, free-form messages stop being deliverable.
• Template messages are pre-written, pre-approved message formats you use to message someone outside that 24-hour window, or to start a conversation nobody initiated. Every template has to be submitted to Meta and approved before it can send.

In practice, this means a reactive use case — someone messages you, you reply — mostly runs on cheap, flexible session messages. A proactive use case — appointment reminders, order updates, re-engagement — depends entirely on templates being approved ahead of time. Plan the template library before you plan the campaign.

How pricing actually works

WhatsApp billing is conversation-based, not per-message, and it's billed by Meta on top of Twilio's own per-message fee:

• A conversation is a 24-hour window of messaging between you and one customer, regardless of how many individual messages pass inside it. You're billed once per conversation, not once per message.
• User-initiated conversations (the customer messages you first) are typically cheaper than business-initiated conversations (you message them first using a template) — Meta's rates vary by country and update periodically.
• On top of Meta's conversation fee, Twilio charges its own small per-message fee for handling the delivery. Neither cost is fixed forever; check current rates before quoting a client a number.

The practical upshot: a support-heavy use case where customers message first stays relatively cheap. A marketing-heavy use case where you're initiating conversations with templates costs meaningfully more, and needs to be budgeted as its own line item, not folded into "we're already paying for SMS."

The approval process

Two separate approvals stand between you and a live number, and both are Meta's call, not Twilio's:

• Business verification. Meta verifies your business identity through Meta Business Manager — legal name, address, and supporting documents, checked against public records, similar in spirit to how carriers verify A2P 10DLC brands for SMS.
• Template approval. Every message template you plan to send outside the 24-hour window gets submitted to Meta for review. Vague or promotional-sounding templates get rejected; specific, clearly-scoped templates with real variable placeholders (order number, appointment time) get approved faster.

Business verification is typically the slower of the two the first time you do it — plan for it to take longer than a same-day turnaround. Template approval is usually faster once your business is verified, but a rejected template still has to be resubmitted from scratch, so writing it correctly the first time matters.

Real setup steps

• Start in the Twilio sandbox. Twilio provides a shared sandbox number so you can test message flows immediately, before any Meta approval is in place. Good for proving the integration works, not for production traffic.
• Create a Meta Business Manager account if you don't already have one, and complete business verification.
• Register a WhatsApp sender — either a new number bought through Twilio or an existing number, migrated over.
• Submit your message templates for the specific use cases you need: appointment reminders, order confirmations, support replies, whatever applies.
• Connect the API to your actual system — CRM, booking tool, or automation platform — so incoming messages route somewhere and outgoing messages fire on real triggers, not manually.

Done piece by piece, this is a real setup project, not a checkbox. VIPBizExpert wires the whole thing — verification, templates, and the CRM connection — into one working system instead of leaving it as five disconnected steps.