TABLE OF CONTENTS
Related Articles
December 22, 2022
|
10
MIN READ
Raquel Magalhães
Editorial Writer & Social Media Manager
Case Studies
Generate high quality leads, lower your spend.

Two ways to move conversations off billed WhatsApp messages, a worked example, a four-question test, and a calculator to see what you would save.

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.
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.
Our breakdown of the October WhatsApp Business API pricing change covers the details. Two matter here:
So if you want to lower your WhatsApp API cost, start by knowing what each flow costs you today.
Every message your bot sends now has a line on an invoice, so where a conversation happens is a budget decision.
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:
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.
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.
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.
If 30% of customers start on your website instead, volume drops to about 77,000 billable messages. Savings: about $660 a month.
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.
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.
Enter your numbers and move the sliders to see what each lever saves.
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.
Keep WhatsApp for what only WhatsApp can do. Pay for everything else once, on your site.
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.
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.
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.
For WhatsApp-specific flow tactics, see our guide to using WhatsApp for customer support. To compare platform fees with Meta's, check what a WhatsApp chatbot costs.
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.
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.