WhatsApp Business Terms and Conditions: Read the Contract Behind the Number
WhatsApp business terms and conditions are a contract between Meta and your business that sets what your number may send, to whom, at what price, and on what clock, and the enforcement clause is the one that decides whether your number survives the quarter. Most teams treat the document as a click-through during setup. We read it as the operating manual for the account.
The distinction matters because the terms govern three separate things at once: the commercial side (what a message costs and when it is free), the consent side (who you are allowed to message and how you prove it), and the content side (what gets your number restricted). Only the first appears on a pricing page. The other two are what actually end businesses on the platform, which is why a compliant number is a more valuable asset than a cheaper message rate.
What the Terms Actually Bind You To
The terms are the legal contract between Meta and your business, and they determine everything from whether you can send a broadcast to whether your phone number survives the week. They are not the consumer terms that govern your personal messages, and they are not the pricing sheet alone.
Three things sit inside the same document. Commercial terms set the message categories and the billing window. Consent terms define opt-in, the proof you must be able to produce, and what happens when you cannot. Content and conduct terms cover what a template or a broadcast may say, plus the restrictions Meta applies when it detects bulk behavior that looks like spam.
A useful way to hold the distinction: the commercial terms decide how much you spend, consent terms decide who you may contact, and conduct terms decide whether the account continues to exist. Those are different failure modes with different recovery paths.
For a fuller walk through the document as it applies to teams running automation, our guide to the terms as they apply to API runners covers the enforcement side in more depth than the signup flow will ever show you.
The Clauses Worth Reading Twice
Read for the clauses that carry an enforcement mechanism behind them. Four are worth your time, and the criteria differ sharply.
| Clause group | What to check | What evidence you can produce |
|---|---|---|
| Consent and opt-in | How opt-in was captured and whether it names your business | Timestamped source, form copy, ad creative |
| Billing window | Which messages fall inside a free window and which are billed | Per-conversation logs with entry point |
| Template content | Whether the copy names a category or makes a claim you cannot substantiate | Approved template history |
| Number hygiene | Who controls the number and what happens to it if a provider relationship ends | Account ownership records |
The billing clause has an unusual shape. When customers send you a message from an ad that clicks to WhatsApp or a Facebook Page call-to-action button, for the following 3 days (72 hours) your messages are not charged (WhatsApp Business). That window is generous for a support thread and short for a sales cycle. Read it as a design constraint on your follow-up sequence, not as a discount.
The consent clause earns the second read because of what it does not say. It does not describe a format. It describes a standard: you must be able to show that the person asked to hear from you. A spreadsheet with a date and a source column satisfies that. A database entry that says "imported" does not.
How to Audit a Number Before You Build on It
Before you build, run the audit against your own records. It takes an afternoon and it surfaces the problems that a support ticket takes weeks to resolve.
- Pull every opt-in source you have, including forms, ads, and chat entry points, and confirm each one names your business rather than a partner or a generic signup page.
- Reconstruct the last ninety days of outbound traffic and tag each message by whether it fell inside a free entry window or a billed template.
- List every template you have ever submitted and mark the ones whose copy would read differently to a stranger than to the customer who opted in.
- Confirm in writing who owns the number: your business entity, or the provider account it currently sits under.
- Map which system holds the consent record and whether it survives if you change messaging platforms.
Step four is the one teams skip. If the number lives inside a provider account you do not control, a provider dispute or a forced migration takes your conversation history with it. Ownership belongs to your entity, and the operational relationship with a platform is a separate layer. If you are still deciding which layer your team needs, our comparison of API versus Web for a team explains where the account structure diverges.
How Enforcement Machinery Reads Your Account
The platform does not read your terms. It reads signals, and the terms describe how those signals get interpreted. This is where most compliance advice goes wrong: it treats a policy as a rule a human applies, when the enforcement layer is statistical.
Recipients block. Templates get rejected. Delivery rates drop. Those three signals feed a risk model, and the risk model decides whether a review happens.
The consequence is that the enforcement threshold is not published, and it does not need to be. What you can control is your reply rate. A list with high block rates gets you restricted regardless of how compliant your consent record is. A list with strong engagement gives you room on everything else.
Meta's own fraud enforcement gives a sense of the scale the platform operates at. Meta banned more than 6.8 million WhatsApp accounts linked to scam operations between January and June 2025 (The Spokesman-Review). Your account sits inside a system tuned against that volume, and it is tuned automatically.
Where Compliance Programs Break Down
Treating opt-in as a checkbox produces a list you cannot defend. Import a spreadsheet from a trade show and every row looks like a contact. Apply the standard in the terms and most rows fail, because the person did not ask to hear from your business specifically. The fix is not a bigger disclaimer on the form. It is capturing source and intent at the point of contact and refusing to import anything you cannot trace.
Sharing a number across a team without a shared inbox record is the second predictable failure. Two agents reply to the same customer, one sends an offer, the other sends a resolution, and neither can prove who said what. When a dispute arrives, you have a phone and no thread. Our explanation of why a shared inbox needs the Business API covers the mechanism, and the compliance point is simpler: an unlogged conversation is an unprovable one.
Skipping template review is a third. A template rejected for promotional phrasing during a launch week costs you the campaign, not the account. Submit the copy you intend to use in the category you intend to use it, and treat a rejection as information about how the platform will read your messaging.
Assuming the account sees audience behavior is a fourth, and a costly one to plan around. A business account does not show profile viewers, so any program built on tracking who looked at your profile is built on a feature that does not exist. Growth has to come from replies, saved contacts, and threads you can measure. That is also the safer direction, since replies are the signal the platform rewards.
Where WhatsBox Sits in That Contract
A provider cannot renegotiate Meta's terms for you. What it can do is carry the operational record the terms require, which is where most compliance programs fail in practice rather than in principle.
WhatsBox runs on the official WhatsApp Business API as a messaging platform with a shared team inbox that carries session timers and assignment. A session timer is the compliance-relevant part: it shows an agent how much of a billing or service window remains, so a reply lands in the right window rather than being reconstructed from a spreadsheet later. Assignment means each thread has a named owner and a timestamped history.
Broadcast campaigns run through the same API, so a template you submit is a template you can trace back to its audience. Custom-trained AI chatbots with a knowledge base handle the first reply, and human-in-the-loop escalation passes a complex query to a person with the thread intact. Workflow automations run through the embedded Zapier integration, and Google Sheets and Google Forms are connected, which matters if your consent captures live in a form and your records live in a sheet.
Pay-Per-Use is the single tier, currently free during beta, with no monthly seat fees, no user limits and no contracts. We would rather you read the contract behind the API number before you commit to any provider, including us. When you are ready, our contact page and the pricing page are the two places to start.
Frequently Asked Questions
What is the 24 hour rule for WhatsApp Business?
Outside that window you must use an approved template, which is billed. The rule does not reset on your schedule, only on a new inbound message from the customer. Teams that treat it as a daily limit rather than a per-conversation clock send templates they did not need and pay for messages that could have been free.
What are the disadvantages of a WhatsApp Business account?
The constraints are real: template approval adds lead time to campaigns, the free-form window closes quickly, and a single number carries shared risk so one bad campaign affects every conversation on it. Content policy limits what you can say in outbound copy. The account also depends on consent records you must maintain yourself. None of these make the platform unusable. They make it a channel that rewards planning, which is why pre-launch copy review and consent capture belong in your process rather than in a cleanup exercise after a warning.
Can WhatsApp Business account see who viewed your profile?
No. A business account does not have a viewer list, and neither does a personal account. Any tool or page promising profile viewer tracking is not reading a real signal. What you can see is behavioral: who replies, who saves your number, who clicks a link, and what the thread shows. Build reporting on conversations because that is the data the platform produces. Businesses planning a campaign around viewer data are planning around a metric that does not exist.
What are the rules for WhatsApp Business account?
The rules fall into three buckets: consent, content, and conduct. You must be able to show that a person agreed to receive messages from your business, outbound content must fit an approved template and category, and account conduct must avoid the bulk patterns that trigger restrictions. Opt-out requests must be honored. Pricing terms sit alongside these but are the least consequential when broken, since a billing error costs money while a conduct violation costs the account. ➀