What should founders check before using the WhatsApp Business Platform?
The WhatsApp Business Platform supports business messaging through software, with rules governing customer permission, templates and account use. Check account ownership, opt-outs, current pricing and the handover to a person before adopting an integration. Confirm its actual access scope rather than assuming it can read every existing personal or business conversation.
Keep these in mind
- Check customer permission and message eligibility before sending.
- Keep account ownership and human handover under business control.
- Estimate delivered-message costs with current official rates.
Distinguish the app from the platform
A business using the WhatsApp Business app may already have labels, quick replies and a familiar phone workflow. The Platform is a different integration arrangement for software-driven messaging. Moving a workflow into it involves account setup, access and message handling, not merely turning on an AI switch.
Ask a prospective provider what happens to the number, staff access and existing workflows. Get a written explanation of supported history access and migration. Avoid assuming that an API connection supplies every old conversation or authorizes an application to monitor employees’ personal accounts.
Permission is a business process
The official WhatsApp Business Messaging Policy sets opt-in and opt-out requirements. It also describes the customer-service window and the use of approved templates outside that window. Check the live policy when designing a workflow because platform rules can change.
For a fictional furniture store, a customer asking about a sofa does not automatically justify unrelated messages forever. Record why the customer may be contacted and provide a straightforward way to stop. Staff should be able to recognize a stopped contact before preparing another campaign or reminder.
Map each message to a job
A delivery update and a promotion have different purposes. Define the intended message before choosing automation.
| Message | Business check | Operating owner |
|---|---|---|
| Reply to an enquiry | Current conversation and permitted reply | Sales person handling the enquiry |
| Delivery update | Correct order, recipient and eligible message | Dispatch coordinator |
| Promotion | Appropriate permission and category | Marketing owner |
| Unclear complaint | Escalation to a person | Support owner |
| Opt-out request | Stop further eligible campaigns promptly | Account administrator |
Estimate cost from the actual traffic
The official Platform pricing page describes delivered-message pricing and market/category differences. Use the current rate card for your recipient markets. Do not rely on an old “per conversation” estimate or a blanket claim that automated replies are free.
Build an illustrative monthly worksheet with the number of recipients, messages per recipient, relevant categories and provider charges. Then add staff review and support time.
A useful message reaches the right person and makes a commitment the business can fulfill. Include those checks when comparing costs.
Plan the human handover before launch
When a customer asks about a damaged delivery, a person needs the order, the latest messages and any draft response. An automation should say when it has handed the issue over and who is responsible. A queue with no named owner can leave the customer waiting despite technically successful message delivery.
Test a customer who changes the order, asks to stop messages and sends two similar enquiries. Check that the process avoids duplicate replies and that staff can correct the underlying record. Keep operational facts distinct from the conversation thread so another employee can understand the current situation.
Check what the integration actually accesses
Ask the provider to show which accounts, messages and history the connection can access. Test with the permissions a normal employee will use. Document how relevant information reaches the shared business record and who checks the result.
Assign a response owner, escalation route and account-recovery responsibility. The process should remain usable during absences and access changes.
- List the precise messaging jobs you want to support.
- Confirm account ownership, access and migration behavior.
- Check policy eligibility and current costs for each job.
- Test stop requests, duplicates and human escalation.
- Keep one accountable owner for the whole messaging process.
Common questions
What should we check before connecting business messaging to software?
Confirm account ownership, accessible messages, customer permissions, applicable message rules and the route to a human. Test with ordinary employee access and realistic exceptions. Document what happens during an outage, a staff departure or a request to stop messages.
How should we budget for business messaging?
Use the current official rate card for the relevant recipient markets and message categories. Add provider charges and staff effort, and keep the estimate dated. Recheck it when traffic, product configuration or platform pricing changes instead of relying on an old general figure.
Sources & further reading
Primary references for the facts and frameworks discussed. Worked examples and recommendations are Daltn’s own analysis.
- WhatsApp Business Messaging Policy ↗
Provides the current official messaging, permission and escalation rules.
- WhatsApp Business Platform Pricing ↗
Explains the official pricing structure and rate-card access.
Published by the team building Daltn. Comparisons are first-party analysis, not independent reviews. Our editorial approach.