Decision matrix: WhatsApp Business app, official API, or intermediary platform
The three ways to use WhatsApp in a business (and when each one is best)
If your business receives messages on WhatsApp, at some point you will face this decision: stick with the WhatsApp Business app, migrate to Meta's official API, or hire an intermediary platform that uses that API. There is no universal answer, but there are measurable criteria that allow you to decide without relying on what a salesperson tells you.
This page is a decision matrix: a table with the criteria that matter, a method to score them according to your case, and the edge cases where the answer changes. It does not replace consulting with a provider, but it gives you the framework to do so with numbers, not feelings.
What each option is (in 30 seconds)
- WhatsApp Business app: Meta's free application for mobile phones. It serves small businesses with a single device, few messages, and no need to integrate systems.
- Official WhatsApp API (WhatsApp Cloud API): the interface Meta offers for a business to send and receive messages programmatically. It requires technical development or a platform that wraps it.
- Intermediary platform (like Wando): software that connects to the official API and adds a shared inbox, AI suggestions, templates, campaigns, and statistics. The business does not need to program anything.
The key difference is not technical: it is about scale. The app is a manual tool for low volume. The API is the technical foundation. Platforms are the layer that makes that foundation usable for a team that does not live in code.
The 6 criteria that determine the choice
After working with dozens of businesses that went through this decision, the criteria that truly separate one option from another are these six. Each one has a different weight depending on your case, and at the end of the page we give you the method to score them.
| Criterion | WhatsApp Business App | Official API (direct) | Intermediary platform |
|---|---|---|---|
| Daily message volume | Up to ~50-100 messages. More than that, the phone becomes unmanageable. | No practical limit, but requires development to manage the flow. | No practical limit. The shared inbox absorbs the volume without programming. |
| Monthly budget | Free (only equipment and data costs). | Initial development cost (US$2,000-10,000+ depending on complexity) + Meta per-conversation fees. | Fixed subscription (e.g., US$9.99-49.99 depending on plan) + Meta per-conversation fees. |
| Integrations with your own systems | None. Only manual contact export. | Full: you can connect your CRM, ERP, or database with webhooks and custom code. | Partial: platforms offer native integrations (Google Sheets, Zapier, Make, n8n, Slack, Mercado Pago). For very specific integrations, webhooks may be required. |
| Team that handles it | 1 person with the phone. No roles or shared history. | Requires a developer to implement and maintain. The team works from a custom system. | Multiple people with roles and a shared inbox. No development needed. |
| Marketing features (templates, campaigns) | Limited to templates offered by the app. No scheduled campaigns. | Requires building template and campaign logic from scratch. | Templates (HSM) and campaigns included, with Meta approval managed by the platform. |
| Maintenance and support | No maintenance, but no real technical support. | Continuous maintenance: Meta API changes, errors, monitoring. | The platform handles maintenance and API changes. |
How to use the matrix: weighted scoring method
- 1Assign a weight from 1 to 5 to each criterion based on your situation. Weight 5 is for what hurts you today: if you receive 300 messages per day and lose them, volume weighs 5. If your budget is tight, budget weighs 5.
- 2Score each option from 1 to 5 on each criterion (1 = does not meet, 5 = meets perfectly). Use the table above as a guide.
- 3Multiply weight by score for each option and add them up. The option with the highest total is the one that suits you in principle.
- 4Review the edge cases in the next section before making the final decision.
Example: a food place that receives 120 messages per day, has 2 people handling them, and a tight budget. Weights: volume 5, budget 4, integrations 1, team 4, marketing 2, maintenance 2. The app loses on volume and team; the direct API loses on budget and maintenance; the platform wins on almost everything except budget (which weighs less than volume anyway). Result: platform.
Edge cases: when the answer changes
- Fewer than 30 messages per day and a single owner: the WhatsApp Business app is enough. Don't pay for a platform if the problem doesn't hurt you.
- You have an internal development team and a very specific use case (e.g., integrating WhatsApp with your own appointment system): the direct API may make sense, but only if the development cost is amortized in less than a year against a platform subscription.
- You need very specific integrations that no platform offers natively: check if the platform has webhooks (Wando has them for Make, Zapier, n8n, and Slack). If not, the direct API is the only way.
- Your volume is seasonal (e.g., year-end campaigns): a platform with a monthly plan lets you scale up and down without committing to development.
What should NOT influence the decision
There are arguments that are heard a lot but are not valid criteria: "the app is free and the platform is not," when the cost of the app is your team's time; "the API is the most professional," when without development the API is unusable; "this platform has AI," when AI is a feature, not a reason to buy. The decision is made with volume, budget, integrations, and team, not with marketing features.
Questions you should ask any provider
- Do they use Meta's official API or an unofficial one? (Unofficial ones can go down and violate WhatsApp's terms.)
- How long does template approval take? (Meta's timeframe is up to 48 hours.)
- How do they handle volume spikes? Are there daily message limits?
- What native integrations do they have, and which ones require webhooks?
- Does the price include Meta's fees or are they separate?
Meta's per-conversation fees vary by country and conversation type. Check Meta's official documentation for your market before budgeting.
Conclusion: the decision in one sentence
If you handle fewer than 50 messages per day with a single person, the app is enough. If your volume grows and you need the team to work together, an intermediary platform is the shortest path. The direct API is for cases with in-house development and integration needs that no platform covers. With the matrix above, the answer comes out with numbers.
What to do when the decision is already made (and it goes wrong)
The matrix gives you the right answer 80% of the time, but sometimes reality corrects you. If you already chose an option and it's not working, the problem isn't that you chose poorly: it's that you didn't set a rollback threshold before starting. Before signing any contract, set a simple rule: if after 60 days the cost per handled message exceeds X, or if the team is still losing messages, go back to the matrix and switch. Without that threshold, you'll stick with a solution that doesn't work out of fear of 'losing what you invested'.
| Warning sign | What it means | Recommended action |
|---|---|---|
| The team goes back to using personal phones | The tool isn't more convenient than what came before | Review the shared inbox and the provider's mobile app |
| Meta's fees double the subscription | Actual volume is much higher than estimated | Renegotiate the plan or evaluate a plan with more features to reduce cost per message |
| Template approval takes more than 48 hours | The provider doesn't manage the process well with Meta | Demand a written SLA or switch providers |
| Nobody uses the statistics | The team doesn't understand them or doesn't care | Request training; if it continues, remove them from focus and keep only the inbox |
The uncomfortable question: what if my business is too small for all this?
There is a case that nobody in the industry wants to name: the business that doesn't need any of this. If you handle 15 messages per day, you answer them yourself on the spot, and you have no employees, the WhatsApp Business app is enough. The problem is that the salesperson of the moment will tell you that 'you need to grow' and that 'without API you'll fall behind.' Don't believe them. The intermediary platform makes sense when there is pain: lost messages, multiple people handling chats, high response time. If there's no pain, there's no purchase. And that's fine.
How to try a platform without committing (or dying trying)
Most platforms, including Wando, offer a free trial without a credit card (Wando: 14 days). That's not enough to evaluate everything, but it's enough for what matters: connect your WhatsApp, upload 3 real contacts, message your own business, and see if the AI suggestions work for you or if you prefer to write manually. If in 14 days you couldn't integrate your main use case, it's not that you're slow: it's that the platform isn't for you. Trials are also useful for quickly ruling things out.
Frequently asked questions
How many messages per day justify moving from the app to a platform?+
There's no magic number, but in practice, when you exceed 50-100 daily messages or have more than one person handling the same number, the app becomes unmanageable: no shared inbox, no per-contact history, and messages get lost. That's when a platform with the official API starts paying for itself.
Is the official WhatsApp API free?+
The API itself has no subscription cost, but Meta charges per conversation depending on the country and conversation type. Additionally, implementing it requires technical development (or a platform that wraps it). The real cost is the sum of Meta's fees plus development or subscription.
What happens if I use an unofficial WhatsApp API?+
Unofficial APIs (like those based on whatsapp-web.js) may work for a while, but they violate WhatsApp's terms of service and the number can be blocked without notice. Also, they don't have access to official features like approved templates. If your business depends on WhatsApp, the official API is the only safe option.
Does Wando use Meta's official API?+
Yes, Wando connects to Meta's official WhatsApp API (WhatsApp Cloud API). That means messages go through Meta's official infrastructure, with approved templates and no risk of blocking for unauthorized use.
What do I do if the platform I chose doesn't deliver what it promised?+
First, check the contract: most platforms have a trial period or monthly cancellation clauses. If you're within the 14-day trial, cancel without hesitation. If you've already paid, raise the issue in writing with evidence (screenshots, metrics). Serious platforms respond quickly because they depend on monthly renewal. If they don't respond, that tells you something about the platform.
Can I use the WhatsApp Business app and a platform at the same time?+
Technically, it's not recommended: Meta's official API doesn't coexist well with the app on the same number, and you can have session conflicts. If you want to try a platform, use a new number or wait until you're clear you're going to migrate. Wando, for example, uses the official API, so the number stays linked to the platform.
Does the client or the platform pay Meta's per-conversation fees?+
It depends on the provider. Some platforms include the fees in the plan (and charge extra if you exceed a certain volume), others bill them separately. In Wando's case, Meta's conversation prices vary by country and refer to Meta's official documentation. Always ask this before signing: it's a variable cost that can surprise you.