Please note that 'Variables' are now called 'Fields' in Landbot's platform.
This guide breaks down the two-layer bill: Twilio charges a flat $0.005 per message (inbound and outbound), then passes Meta’s per-message fees through on top — marketing, utility, and authentication templates each carry their own rate by country, while service replies inside the 24-hour window are free from Meta for now. A typical example: 5,000 marketing templates plus 3,000 service replies to Brazil runs about $369/month, ~85% of it Meta’s share.
Twilio WhatsApp pricing confuses people for one simple reason: every conversation generates two bills. One from Twilio, for carrying the message. One from Meta, for the right to send it. Twilio’s pricing page quotes its own fee clearly, then points you to Meta’s rate cards for the rest — and Meta’s rates change by message category, by recipient country, and are counted per message rather than per conversation. So “what does WhatsApp on Twilio cost?” has no single number. It has a formula.
This article gives you the formula, the current rates, and three worked scenarios so you can put a real monthly figure on it before you commit. It’s a pricing explainer, not a comparison — if you’re weighing Twilio against a no-code platform head to head, that’s the job of our Landbot vs Twilio comparison page.
How Twilio WhatsApp pricing works: one conversation, two bills
Twilio is a WhatsApp Business Solution Provider: it gives you API access to WhatsApp, and bills you for usage. The total cost of any message is:
Meta’s per-message fee (varies) + Twilio’s platform fee ($0.005) = what you pay
Layer by layer:
Twilio’s fee: $0.005 per message, inbound and outbound. Every message that moves through the API — a marketing template you send, a customer’s reply coming in, your agent’s answer going out — costs half a cent from Twilio. Inbound messages are the line most people forget to budget.
Meta’s fee: passed through at cost. Twilio adds no markup to Meta’s rates; it simply forwards them. The rate depends on the template category (marketing, utility, authentication) and the recipient’s country code.
A phone number. A Twilio number starts at around $1.15/month for a US local number (rates vary by country and type), or you can register a number you already own as a WhatsApp sender at no extra Twilio charge.
Edge fees worth knowing.
- Messages that end in a “Failed” status incur a $0.001 processing fee
- The optional Messaging Engagement Suite (link shortening, click tracking, and message scheduling) adds $0.015 per message after the first 1,000 free each month
- On Twilio Flex, this $0.005 fee is waived — Flex bills per seat instead
There’s no setup fee or monthly platform minimum for WhatsApp on Twilio: registering a WhatsApp sender is free, and you pay as you go from the first message.
Twilio WhatsApp integration: what you need before you can send
A Twilio WhatsApp integration needs four things:
- a Twilio account,
- a phone number (Twilio-bought or your own),
- a Meta Business account that passes business verification,
- approved message templates for anything you send outside the 24-hour window.
Templates are submitted through the Twilio Console under one of Meta’s three categories — and if Meta decides you miscategorized a template (say, marketing dressed up as utility), it recategorizes it and bills accordingly. For testing, Twilio’s WhatsApp Sandbox is free.
A worked example, line by line
Say you send 5,000 marketing templates to customers in Brazil this month, 3,000 of them reply, and you answer each reply once inside the 24-hour window:
| Line item | Math | Cost |
|---|---|---|
| 5,000 marketing templates — Meta fee (Brazil, $0.0625/msg) | 5,000 × $0.0625 | $312.50 |
| 5,000 marketing templates — Twilio fee | 5,000 × $0.005 | $25.00 |
| 3,000 inbound replies — Meta fee | free | $0.00 |
| 3,000 inbound replies — Twilio fee | 3,000 × $0.005 | $15.00 |
| 3,000 service replies in the 24h window — Meta fee | free | $0.00 |
| 3,000 service replies — Twilio fee | 3,000 × $0.005 | $15.00 |
| Phone number (US local) | flat | $1.15 |
| Total | $368.65 |
Two things to notice. Meta’s marketing fee is about 85% of the bill — the category you send in matters far more than the provider you send through. And Twilio’s half-cent applied 11,000 times ($55) is the part that scales with conversation depth, not campaign size.
WhatsApp Business API pricing: what Meta charges in 2026
Meta’s side of the bill applies identically no matter which provider you use — Twilio, 360dialog, Vonage, or a no-code platform like Landbot. Since July 1, 2025, WhatsApp Business API pricing is per message delivered, replacing the old per-conversation model where one template opened a 24-hour window of unlimited included messages. Now every template message is billed individually, in one of three categories:
Marketing — promotions, offers, back-in-stock alerts, newsletters. The most expensive category everywhere.
Utility — order confirmations, shipping updates, billing reminders tied to an existing transaction. Cheap, and free when sent inside an open customer service window.
Authentication — one-time passcodes. Priced separately, with its own rate and volume tiers.
Service messages — free-form replies inside the 24-hour customer service window — carry no Meta fee. The window opens (or refreshes) every time a customer messages you. A conversation that starts from a Click-to-WhatsApp ad on Facebook or Instagram works a little differently: reply within 24 hours and you unlock a bonus 72-hour window where any message type is free.
How rates compare
Rates vary by the recipient’s country code, not your business location. The table below covers Marketing and Utility, the two categories that make up most of a typical WhatsApp bill — Authentication runs on its own rate card, so check Meta’s pricing tool for your recipient country if you’re budgeting OTP messages. Sample rates from Meta’s rate card (USD, per delivered message):
| Recipient country | Marketing | Utility |
|---|---|---|
| United States | $0.0250* | $0.0034 |
| Brazil | $0.0625 | $0.0068 |
| United Kingdom | $0.0635 | $0.0220 |
*Rate published on Meta’s rate card; delivery of marketing templates to US numbers has been paused since April 2025, so this rate currently can’t be used. Meta updates rates quarterly, so confirm the current figure for your country before finalizing a budget.
Three planning notes. First, the US marketing pause is real and still in effect: for US audiences, only utility, authentication, and service messages get delivered. Second, Meta introduced volume-tier discounts — but only for utility and authentication; marketing pays full rate at any volume. Third, undelivered messages aren’t charged by Meta (Twilio’s $0.001 failed-message fee still applies).
Meta has confirmed that service messages and utility templates sent inside an open customer service window — both free today — become chargeable starting October 1, 2026, with exact rates due to be published by September 1, 2026.
Twilio Conversations API pricing
A separate Twilio product that often gets tangled into WhatsApp budgeting: the Conversations API, Twilio’s orchestration layer for multi-party, multi-channel threads (chat, SMS, WhatsApp, Messenger). It’s priced per active user per month: the first 200 are free, then $0.05 per user, dropping to $0.0475 above 5,000 users and $0.045 above 10,000, plus $0.25/GB/month for stored media. The key budgeting point: Conversations API fees come on top of standard WhatsApp per-message rates, not instead of them. If you only send and receive WhatsApp messages through the Programmable Messaging API, you don’t pay it at all.
What Twilio WhatsApp costs at typical volumes
Three scenarios using the rates above: Twilio’s flat $0.005 applies to every message regardless of direction or category, while Meta only charges for template messages sent outside a free customer-service window — which is why inbound replies and in-window service messages carry a $0 Meta cost below. Phone number excluded for clarity.
| Scenario | Volume | Meta fees | Twilio fees | Monthly total |
|---|---|---|---|---|
| Support-only, US customers | 2,000 inbound + 2,000 replies in window + 500 utility follow-ups | $1.70 (500 × $0.0034) | $22.50 (4,500 msgs × $0.005) | ~$24 |
| Marketing + support, Brazil | 5,000 marketing + 3,000 inbound + 3,000 replies | $312.50 (5,000 × $0.0625) | $55.00 (11,000 msgs × $0.005) | ~$368 |
| Campaign-heavy, Germany | 20,000 marketing + 10,000 inbound + 10,000 replies | $2,730.00 (20,000 × $0.1365) | $200.00 (40,000 msgs × $0.005) | $2,930 |
The pattern: support-led WhatsApp is remarkably cheap on usage-based pricing, because Meta charges nothing inside the window. Marketing-led WhatsApp is dominated by Meta’s category rates, and no provider — Twilio or anyone else — can discount those.
When Twilio makes sense — and when a flat-tier platform does
What Twilio’s pricing buys you is raw infrastructure at near-cost. What it doesn’t include is everything that turns an API into a working WhatsApp channel: the bot logic, the flow builder, the inbox for human takeover, the integrations. You build those, or you buy a platform that has them.
Twilio is the right call when:
- You have a developer team that will own the integration and the conversation logic
- You want SMS, voice, and WhatsApp in one stack with one vendor (that’s the intent behind most generic “Twilio pricing” searches — WhatsApp is one channel of many)
- Your volumes are spiky or support-led, where pay-per-message beats any flat tier
- You’re building something custom enough that no platform’s builder fits
A flat-tier, no-code platform makes more sense when:
- Marketing or sales owns the WhatsApp channel and can’t wait on an engineering sprint
- You want lead-gen flows, campaigns, and human handoff working in days, not quarters
- You’d rather budget a predictable subscription than reconcile a usage invoice
That second profile is what Landbot is built for. WhatsApp Pro runs €200/month (€160/month billed annually) for 3 seats and 10,000 service messages, plus the visual bot builder, campaigns, and a shared inbox — none of which Twilio includes at any price. An extra WhatsApp number is €100/month, extra seats €25/month. Where Twilio bills every message with no ceiling, Landbot bills one flat number for the platform and bundles a chunk of usage into it; Meta’s per-message fees still apply once you’re past what’s included, same as through any other provider. There’s a free Sandbox plan (1 seat, 100 chats/month) to test the builder, and a 14-day trial with full Pro features, no card required.
And to be plain about it, because this is where WhatsApp pricing articles tend to blur: Meta’s per-message fees apply on Landbot too. They apply on every provider. A platform subscription replaces Twilio’s per-message platform layer and the build cost — it never replaces Meta’s bill.
Which should you pick?
| If you… | Then |
|---|---|
| Have devs and want WhatsApp + SMS + voice in one API stack | Twilio |
| Run support-led WhatsApp with spiky volume and want pure pay-per-use | Twilio |
| Want marketing-owned WhatsApp lead gen live without engineering | Landbot |
| Want a flat, predictable platform invoice (Meta fees aside) | Landbot |
| Are building a custom product where WhatsApp is one embedded channel | Twilio |
| Are still validating whether WhatsApp is your channel at all | Either — both Sandboxes are free to test |
For a feature-by-feature breakdown of the two, see Landbot vs Twilio.
Frequently asked questions
How much does Twilio charge for WhatsApp messages?
Twilio charges $0.005 per WhatsApp message, inbound and outbound, plus Meta’s per-message fee passed through at cost. A marketing template to Brazil costs $0.0625 (Meta) + $0.005 (Twilio) = $0.0675; a service reply inside the 24-hour window costs just the $0.005 Twilio fee, because Meta charges nothing for it.
How does WhatsApp Business API pricing work in 2026?
Since July 1, 2025, Meta bills per message delivered, in three template categories: marketing (most expensive), utility, and authentication. Rates depend on the recipient’s country. Service messages — free-form replies inside the 24-hour customer service window — are free from Meta, and utility templates sent inside that window are free too. Volume discounts exist only for utility and authentication, not marketing.
Is the WhatsApp API free?
Access to the API itself carries no license fee, but you can’t use it directly — you go through a provider, and messages cost money. On Twilio you pay $0.005 per message plus Meta’s rates. On subscription platforms the provider fee is baked into the plan. Meta’s per-message fees for template messages are unavoidable on every provider; only service replies inside the 24-hour window are free from Meta.
Do Meta’s WhatsApp fees apply on every provider?
Yes. Meta charges the same per-message rates whether you connect through Twilio, 360dialog, Vonage, Landbot, or anyone else. Providers differ in what they add on top: a per-message platform fee (Twilio’s $0.005), a monthly subscription (Landbot’s WhatsApp Pro at €200/month, €160/month billed annually), or a markup on Meta’s rates (some resellers — worth checking). Any provider claiming to waive Meta’s fees is absorbing them into another price.
What are the best Twilio alternatives for WhatsApp?
It depends on what you’re replacing. For raw API access with a different fee structure: 360dialog (flat monthly fee, no per-message markup) or Vonage. For a no-code platform with bot building, campaigns, and a team inbox included: Landbot, which starts WhatsApp plans at €200/month (€160/month billed annually) with a free Sandbox to test. We compare the trade-offs in detail on our Twilio alternatives page.
Can I send WhatsApp marketing messages to US numbers?
Not currently. Meta paused marketing template delivery to US phone numbers in April 2025, and the pause remains in effect. Utility, authentication, and service messages to US numbers work normally — US utility templates cost $0.0034 plus Twilio’s $0.005.
So — is Twilio WhatsApp pricing expensive?
For what it is — metered infrastructure with Meta’s rates passed through untouched — no; it’s about as close to cost as WhatsApp API access gets. The real question is whether metered infrastructure is what you’re actually shopping for. If your team will build on the API, Twilio’s two-layer bill is transparent and fair. If what you actually need is the layer on top — flows, campaigns, handoff, no code — then you’re pricing the wrong product, and a platform subscription with Meta’s fees on top is the number to compare. Run the math from this article for your volumes and countries; if the platform route wins, try Landbot free for 14 days — Pro features, no card — and put a real figure next to it.
.png)
.avif)

.avif)
.avif)
%20(1).png)
.avif)