Julia Guallar is a Customer Success Manager at Landbot, focused on onboarding, retention and expansion: helping teams turn their bots into real results across web and WhatsApp.
Service message · UK$0.0220Per message in the UK since Oct 1, 20263× Brazil's rateMeta rate card · Oct 2026
Service message · Spain$0.0200Per message in Spain since Oct 1, 2026No volume discountMeta rate card · Oct 2026
Your brand Web chat · onlineON YOUR SITE
✦ WhatsApp-style web chat
Hi, what's my outstanding balance?
Hi Ana 👋 Your balance is €1,240. Next payment: €120 on December 5.
Set up a payment plan · Download statement
Service message · Brazil$0.0068Per message in Brazil since Oct 1, 2026Same chat, a third of the UK priceMeta rate card · Oct 2026
Worked example · Spain−54%Meta fees with both levers$14,220 saved a yearLandbot estimate
TL;DR:
How can I lower my WhatsApp API cost now that service messages are billed?
This guide explains two ways to cut billed messages: a WhatsApp-style web chat on your site, or a branded web form opened from the WhatsApp chat.
Your customers don't love WhatsApp for the logo. They love it because it's a chat they already know how to use, and you can give them that same chat on your own website.
Key Takeaways
Every service reply now has a price: since October 1, 2026, Meta bills each message in the 24-hour window at the local utility rate.
Many WhatsApp conversations don't need WhatsApp: balance checks, payment plans, and FAQs work just as well on your site.
There are two ways to move a task: a web chat that feels like WhatsApp, or a branded form opened from the WhatsApp chat.
Two levers stack: moving conversations and trimming wasted bot messages cut billable volume by about half in our example.
WhatsApp keeps the jobs only it can do: notifications, reminders, and follow-ups.
Why Did WhatsApp Get More Expensive in October 2026?
WhatsApp got more expensive because Meta started charging for service messages on October 1, 2026. Replies inside the 24-hour window, free since November 2024, are now billed per message, so your WhatsApp API cost grows with every answer. Each country pays its own utility rate, per Meta's pricing documentation.
There's no volume discount on service messages. Meta was explicit: there are no volume tiers for service messages, so the per-message rate stays flat however much you send.
The rate depends on the country. The same conversation costs very different amounts in Brazil, Spain, or the UK.
So if you want to lower your WhatsApp API cost, start by knowing what each flow costs you today.
$0.0220
EVIDENCE · META RATE CARDis the service message rate in the UK from October 1, 2026, over three times Brazil's $0.0068 (Meta's official rate card)
Every message your bot sends now has a line on an invoice, so where a conversation happens is a budget decision.
Which Conversations Actually Need to Happen on WhatsApp?
The conversations that need WhatsApp are the ones only WhatsApp can do well: proactive notifications, reminders, and follow-ups to customers who are away from your site. Tasks a customer starts, like checking a balance or agreeing a payment plan, can usually happen on your website just as well.
Sorting your flows is the first real step to reduce WhatsApp API costs:
Conversation type
Typical example
Best channel
Proactive notification
Payment reminder, delivery update
WhatsApp
Async follow-up
"Your document was approved"
WhatsApp
Self-service task
Check a balance, download a statement
Web chat
Structured form
Payment plan, booking, address change
Web chat
FAQ
Opening hours, fees, requirements
Web chat
Complex case
Dispute, complaint
Either, with human handoff
What Are the Two Ways to Move a Conversation Off WhatsApp?
There are two ways to move a conversation off billed WhatsApp messages. If the customer is already on your website, give them a web chat that feels like WhatsApp. If they start on WhatsApp, keep the chat there and send one link to a branded web form for the long task, then send the result back.
Option 1: WhatsApp-style web chat
Option 2: Branded form from WhatsApp
Where it starts
Your website or app
A WhatsApp conversation
What the customer sees
Bubbles, quick replies, read ticks
Your brand: steps, a progress bar, a review screen
Best for
FAQs, balance checks, self-service
Long tasks: payment plans, bookings, applications
Billable WhatsApp messages
None
About three: the link, the result, a follow-up
Option 1: A Web Chat That Feels Like WhatsApp
Customers resist a web chat that feels like a downgrade. Make it feel like WhatsApp and most won't notice the switch. For the basics, see our guide to chatbot design for non-designers.
Familiar visuals: chat bubbles, a header with your avatar and name, and read ticks.
Messaging-app rhythm: one message at a time, and buttons instead of long fields.
Full-screen on mobile: a shareable link that opens the chat directly, not a tiny widget in a corner.
Y
Your brand● online
Hi, what's my outstanding balance?Hi Ana 👋 Your balance is €1,240. Next payment: €120 on December 5.Set up a payment planDownload statement
Same bubbles as WhatsApp, no Meta fee per message.
Option 2: A Branded Form That Opens From the Chat
The customer stays in WhatsApp. When the conversation turns into a long task, like a payment plan, the bot sends one link. It opens a web form with your colors and layout, pre-filled with the customer's name and balance, with steps, a progress bar, and a review screen. On submit, the result returns to the same WhatsApp chat inside the 24-hour window. Ten messages become three, and the form works 24/7.
Full transparency: Landbot is our product. With Landbot, the same chatbot or AI Agent can run on your website and on WhatsApp, so you build the flow once. You can style the web version as a messaging app or as a form in your own brand with custom CSS, without waiting on your dev team.
You could cut roughly half of your billable WhatsApp volume by combining two levers. Move routine conversations to your website, and trim the messages your bot sends before it helps anyone. Here's how that plays out for a hypothetical company.
Imagine a consumer-lending company in Spain with 25,000 WhatsApp conversations a month and 4.4 billable messages each, about 110,000 messages. Agents handle payment plans from 8:00 to 17:00. At $0.020 per message, that's about $2,200 a month in Meta fees.
Lever 1: Move 30% of Conversations to Web Chat
If 30% of customers start on your website instead, volume drops to about 77,000 billable messages. Savings: about $660 a month.
Lever 2: Trim the Messages Nobody Needed
About a third of bot messages fire before the customer can choose anything. Merge them into one welcome with the menu, and replace "Anything else?" loops with one list. Each remaining conversation drops to about 2.9 messages.
Scenario
Billable messages / month
Meta fees / month
Today
~110,000
~$2,200
Lever 1: 30% to web chat
~77,000
~$1,540
Levers 1 + 2
~50,750
~$1,015
Combined savings: about $1,185 a month, or $14,220 a year, a 54% cut. The same plan in the UK saves about $15,600 a year; in Brazil, about $4,800.
The bigger win may not be the fee. A payment-plan form runs 24/7, so a customer who writes at 21:00 gets a plan that night. For a lender, that's recovered revenue, not just saved cost.
Calculate Your Own Savings
Enter your numbers and move the sliders to see what each lever saves.
Landbot · Calculator
WhatsApp Savings Calculator
Meta service message rates from the October 1, 2026 rate card (USD). Change any value.
Estimate of Meta service fees only. Excludes marketing templates and your chatbot platform plan. Rates from Meta's official rate card; check your country's current rate.
The Stay-or-Move Test: Should This Flow Leave WhatsApp?
The Stay-or-Move Test tells you, flow by flow, whether a conversation should stay on WhatsApp or move to your web chat. Score each of your main flows from 0 (never) to 10 (always) on the four questions below. A high total means the flow is a strong candidate to move.
Landbot · Framework
The Stay-or-Move Test
Whether a flow should stay on WhatsApp or move to your web chat. Score each question 0 to 10.
1
5
Does this conversation start while the customer is on your website or app?
A flow triggered by a WhatsApp reminder scores low. A question asked from your help center scores high.
0 · never10 · always
2
5
Is it a structured task with a clear end, like a booking or a payment plan?
An open complaint scores low. A form with fixed steps scores high.
0 · never10 · always
3
5
Can the customer finish in one sitting, without later messages from you?
A flow that waits days for a document scores low.
0 · never10 · always
4
5
Can you recognize the customer on web, through a login or a personalized link?
An anonymous visitor with no way to verify scores low.
0 · never10 · always
Your score
20 / 40
Hybrid
Fix first:Start on web chat, send the result or reminder on WhatsApp
Trim the flow: one welcome message, one menu, no loops
16–27
Hybrid
Start on web chat, send the result or reminder on WhatsApp
28–40
Move to web chat
Add a WhatsApp-style web chat on the page where this question starts
Keep WhatsApp for what only WhatsApp can do. Pay for everything else once, on your site.
How Do You Move Conversations Without Losing Customers?
You move conversations without losing customers by changing where they start. Nobody gets forced off WhatsApp. Put the web chat where customers already are and link to it from your own channels. Keep WhatsApp open for anyone who prefers it, then check that resolution and satisfaction hold.
1. Link to the Web Version From Every Channel
Swap the main "Message us on WhatsApp" buttons on your site, starting with the help center and account area. Point emails, SMS, invoices, and QR codes to the web chat or form. Inside WhatsApp, replace the flow where agents collect data one message at a time with one link to a branded form.
2. Measure Before You Scale
Track resolution rate, CSAT, and escalation rate for both channels. If the web version holds up, move the next flow. If it drops, fix the design first.
Do
Don't
Style the web chat like a messaging app, or the form like your brand
Send customers to a generic, unbranded form
Keep the same agent, tone, and knowledge on both channels
Your Four-Week Plan to Lower Your WhatsApp API Cost
Week
Do this
Nov 23–27
Export last month's conversations by flow and count billable messages per flow
Nov 30–Dec 4
Run the Stay-or-Move Test on your top five flows and trim the welcome sequence
Dec 7–11
Launch a WhatsApp-style web chat on the help center and account area, then swap the site buttons
Dec 14–18
Compare resolution and CSAT by channel, then move the next flow or adjust the design
Keep the Chat Your Customers Like, Pay Only for What Needs WhatsApp
Since October, the way to cut your WhatsApp API cost isn't fewer replies. It's to stop paying Meta for conversations that could happen on your website, in a chat that feels like WhatsApp or a form in your own brand.
Your customers want a chat, not a channel. Give them the same chat where it costs you nothing per message.
Book a demo and our team will run your numbers, or try Landbot free and build one agent for web and WhatsApp.
One agent for your website and WhatsApp · Built without code
Frequently Asked Questions
Not if the web version gives the same answers in a familiar format. Start with customers who are already on your site, keep WhatsApp available, and watch CSAT for two weeks.
Yes, from Meta's side. Conversations on your website don't go through the WhatsApp Business Platform, so Meta doesn't bill them. Compare your chatbot platform's plan with the WhatsApp API cost you avoid.
Yes. The link is one billable service message, and so is the outcome you send back. That's still far cheaper than ten back-and-forth messages to collect the same data one question at a time.
Not at first. A conversation that starts from a Click-to-WhatsApp ad or a Facebook call-to-action button opens a 72-hour free entry point window, and service messages inside it aren't charged. After that window, the normal per-message rate applies.
If your WhatsApp flow is already built in Landbot, you can reuse it on web the same day and restyle the web chat to a messaging-app look without code. Most teams start with one flow, like balance checks, then add more.
Julia Guallar is a Customer Success Manager at Landbot, focused on onboarding, retention and expansion: helping teams turn their bots into real results across web and WhatsApp.