Is it worth building your own app because of WhatsApp's new charges?
Almost always, no. If your volume is small, the charge barely shows up on your bill, and switching channels to save a few cents costs more than the problem itself. Your customers are already on WhatsApp. Asking them to download another app is the fastest way to lose them.
Your own app pays off when WhatsApp was already falling short for what you do: tracking orders, viewing history, paying, scheduling, opening support tickets. In that case, the new charge is just the nudge toward a decision that was already on the table.
The rule I would follow: first streamline your customer support, then run the numbers, and only then decide whether an app belongs in the picture.
What changed in the WhatsApp Business API in October 2026
The change applies to companies that use the official API, the one connected to a CRM, chatbot, or customer support system. Before, when a customer sent a message, the company had 24 hours to reply at no cost. You only paid when you started the conversation with an approved template for marketing, utility, or authentication.
Now, support replies are charged after an allowance. According to press coverage, each number gets 1,000 free support messages per month, and that allowance does not roll over to the following month. The prices reported vary by source and taxes, at a few cents per message.
The free WhatsApp Business app, the one you use directly on your phone, is not subject to this charge. And here's the point that catches a lot of people off guard: without a payment method on file, Meta stops delivering the messages that would be charged.
Run the numbers: what WhatsApp will really cost you
Take the number of support messages your company sends per month, per phone number. Subtract the 1,000 free ones. Multiply the rest by the per-message price on your rate card, which you can check in the Meta dashboard or with the provider that handles your integration.
A hypothetical example, just to illustrate: 20,000 support messages in a month, at a price around R$ 0.04, comes to roughly R$ 800 after the allowance. For a business with healthy revenue, that's a routine cost. For one with tight margins and long conversations, it already hurts.
What tends to scare people is the shape of the conversation, not the unit price. Support that used 12 messages to say where an order is now has a visible cost. And a customer who comes back because the issue wasn't solved the first time multiplies the bill.
Before leaving WhatsApp, cut the waste in your customer support
In practice, a good part of the savings comes from fixing your support, not from switching channels. The most common mistake I see is the bot that greets the customer, asks five questions, never checks the system, and hands off to a human with no history. The customer repeats everything, and every repetition costs a message and team time.
What I would review first:
When your own app makes sense
An app pays off when a large share of your message volume is information customers could look up on their own. Delivery status, statements, purchase history, schedules, documents, tickets. If 60% of your WhatsApp traffic is people asking "where's my order?", that's a screen waiting to be built.
It also makes sense when you already have repeat customers. A customer who comes back every week will download the app. A customer who buys once a year won't, and pushing the issue is a waste of time.
Before thinking about app stores, consider a PWA or a logged-in web area. It opens from a link, needs no installation, and handles most lookup cases. Save the native app for when you need strong push notifications, camera access, offline operation, or an experience the browser can't deliver.
The classic mistake is building the app to escape the fee and forgetting to give customers a reason to open it. If the app just repeats what WhatsApp already did, nobody will switch.
How to migrate without losing customers
It's not a switch, it's a division of labor. WhatsApp remains the front door and the channel for real conversation: complex questions, negotiation, consultative sales. The app or logged-in area takes over lookups and self-service.
Do it in stages. Pick the most frequent type of question, solve only that one outside WhatsApp, and measure how much of the volume moved. If it works, pick the next one. If nobody uses it, you found that out while spending very little.
This is the kind of decision where seeing the screen before you code helps a lot. At SKAD, you can generate a free, clickable prototype of your app, with a ballpark estimate, and test with real customers whether lookups outside WhatsApp make sense for your business.
Frequently asked questions
Did the regular WhatsApp Business app also start charging for messages?
No. The October charge applies to those who use the official WhatsApp Business API, integrated with a CRM, chatbot, or customer support system. The free app used directly on your phone is not affected by this change.
How many support messages are still free?
According to press coverage, each phone number has an allowance of 1,000 support messages per month, which does not roll over to the following month. After that, messages are charged.
Do I need to build an app to avoid the charge?
In most cases, no. First reduce unnecessary messages and connect your customer support to your system. An app only pays off if it moves lookups that customers can handle on their own out of WhatsApp.
What happens if I don't add a payment method with Meta?
According to what has been announced, Meta stops delivering the support messages that would be charged. It's worth checking your account and talking to your integration provider.
PWA or native app to take support out of WhatsApp?
For order lookups, history, and duplicate invoices, a PWA or logged-in area is usually enough and avoids the installation barrier. A native app comes in when you need stronger notifications, camera access, or offline use.
Conclusion
Do this week: open the message report from your API, sort support messages by topic, and see which questions repeat the most. If the top three are lookups that a system can answer on its own, you already know what to build first, whether it's a page, a logged-in area, or an app. If they're sales conversations and questions, stay on WhatsApp, pay the few cents, and invest your time in providing better support.