It is not an app

The most common misunderstanding: people expect to download something.

There is no app. The WhatsApp Business Platform is an interface your systems talk to. Messages are sent and received by software, not by a person opening a phone.

Which means you need one of two things:

A provider’s interface. Most businesses use this — a web application where agents see conversations, plus tools to manage templates and contacts.

Your own integration. You connect it to your ERP, CRM or helpdesk directly.

Most companies use both: a provider interface for agents, and an integration for automated messages from their systems.

The pieces

Five things you need. Getting them in the right order saves weeks.

A Meta Business account. The container for everything.

Business verification. Meta confirms your business is real, using documents. This is the long pole — days to weeks depending on your paperwork.

A phone number. Not already registered on WhatsApp. Once used here, it cannot be used in the normal app.

A Business Solution Provider. Your route in, plus interface, support and billing.

Approved templates. Before you can message anyone outside an open conversation.

Choosing a provider

They differ more than the marketing suggests. Six questions.

What does the agent interface look like? Your team will live in it. Ask for a demonstration with real conversations, not a slide.

Does it integrate with your systems? Ready-made connectors for your ERP or helpdesk, or an API you would build against.

How is pricing structured? Meta charges per conversation or message. Providers add their own fee — per user, per month, per message, or a mix. Model the total on your expected volume, not the headline number.

How do templates get managed? Some providers make submission and tracking easy. Some do not.

What happens when something breaks? Support hours, response times, and whether you reach a person.

Can you export your data? Conversation history and contacts. Ask before you commit, not when you are leaving.

The service window, again

It governs the whole design, so it is worth stating precisely.

A customer messages you. A service window opens — commonly 24 hours. Inside it, you reply freely with any content.

The window closes. Now you can only send an approved template.

Two design consequences:

Support works naturally. The customer starts it, so you are always inside a window.

Proactive messaging needs templates. Every notification you initiate is a template, approved in advance.

A pattern worth knowing: a template can reopen the conversation. Send an approved order update, the customer replies, and now you have a service window for a normal exchange.

Templates in practice

Three things worth knowing before you write any.

Variables are positional. The template has placeholders filled at send time — a name, an order number, a date. The surrounding text is fixed.

Categories matter. Utility, marketing and authentication have different rules and different costs. Submitting a promotional message as utility gets it rejected, and that is the most common rejection reason.

Changes need re-approval. Editing a template means submitting it again. Design them to last — put anything variable in a variable rather than in the fixed text.

Quality rating

Meta scores your number based on how recipients react — blocks, reports, and whether messages get read.

Why it matters: a falling rating reduces your messaging limits. Keep falling and the number can be restricted.

What damages it:

• Messaging people who did not opt in
• Too much marketing, not enough usefulness
• Sending too often
• Content that does not match what people expected

What protects it:

• Real opt-in, recorded
• Mostly utility messaging that people actually want
• Immediate opt-out handling
• Somebody watching the rating

Check it regularly. It falls before you lose access, which makes it a warning you can act on.

Connecting it to your systems

The point of the platform, and where the value is.

Outbound. Your ERP sends an order confirmation. Your booking system sends a reminder. Your accounting system sends an invoice link.

Inbound. A customer’s reply creates or updates a support ticket, with their history attached.

What makes this work well: the customer record in your system and the WhatsApp contact need to be linked. Match on phone number, and store it in a consistent format — country code included, no spaces or punctuation.

Inconsistent phone number formatting is the single most common cause of messages not matching to the right customer.

What it costs

Three layers, and companies routinely budget for only one.

Meta’s charges, per conversation or message, varying by category and country.

Your provider’s fee, structured differently by provider.

Your integration work, if you connect it to your systems.

Check current Meta pricing with your provider. It has changed more than once and any article’s figures go stale.

What usually goes wrong

Verification started too late. The project waits on paperwork.

A number already on WhatsApp. It has to be freed first, or you use a different one.

Templates written as marketing. Rejected, rewritten, delayed.

Inconsistent phone formats. Messages not matching customer records.

No opt-out process. Legal and reputation risk together.

Nobody watching the quality rating. The warning goes unheard.

The short version

The Business Platform is an interface, not an app. You need a Meta account, business verification, a clean phone number, a provider, and approved templates.

Start verification first — everything waits on it.

The service window governs the design. Inside it, talk freely. Outside it, use a template.

Store phone numbers consistently, protect your quality rating, and check current pricing rather than trusting any article.