What is the WhatsApp Business Messaging Policy?
Meta's WhatsApp Business Messaging Policy is the rulebook for the Business app and Cloud API. Recap of opt-in, the 24-hour window, prohibited goods, regulated verticals, and the commerce-features section that governs catalogs and payments — mapped to Ominiflow. It is Meta's public rulebook for WhatsApp Business Services (the Business app and the Business Platform). Together with the Messaging Guidelines and Business Terms of Service, it defines what is allowed. Violations can limit or remove access.
Last updated: 30 August 2026
The WhatsApp Business Messaging Policy is the rulebook for every business chat on WhatsApp — the Business app, the Business Platform (Cloud API), and future features Meta adds. If content or behaviour violates it, Meta can limit or remove access. This recap is not a substitute for the live policy. Meta may change it without notice unless the law requires otherwise.
The same page also holds the commerce-features section: catalogs, payments, and any other in-chat sale must follow the Meta Commerce Policy. Selling a SKU that is banned there can cost you catalog and messaging. Recovery playbook if you are already restricted: WhatsApp ban guide. Quality score that gates volume: quality rating.
Primary: WhatsApp Business Messaging Policy. Commerce section: Policy for WhatsApp Commerce Features. That page also binds you to the WhatsApp Messaging Guidelines and WhatsApp Business Terms of Service. This is an operator recap for Cloud API teams on Ominiflow, not legal advice. Country lists and exceptions change — re-read Meta before you ship a regulated category.
Phone + opt-in
you may contact someone only if you have their number and they confirmed they want messages or calls
24h
free-form replies after the last user message; outside that window, approved templates only
Catalog = Commerce Policy
in-chat sales follow Meta Commerce Policy; the seller owns taxes, terms, and fulfilment
Too long? Start here
- Who it covers: WhatsApp Business app, WhatsApp Business Platform, and later business features
- Contact rule: mobile number plus opt-in. Honor every opt-out, on or off WhatsApp. Do not impersonate another brand
- Platform: start with an approved template; reply free-form for 24 hours; bots need a real escalation path (human in chat, phone, email, web, store, or form)
- Do not collect full card numbers, bank accounts, or personal ID numbers in chat. Do not forward one customer's thread to another
- Regulated goods (alcohol, OTC drugs, online gambling, and the rest of Meta's list): default is no. Limited Platform-only messaging exists in named countries — never on the Business app, never as catalog commerce
- If you sell in chat: you own the transaction. WhatsApp does not process, pay for, or fulfil the order
1. Create a quality experience
Keep the business profile accurate: support contact plus at least one of email, website, or phone. Do not impersonate another business or speak in another brand's voice without permission. That is a policy violation even if your GST and Business Manager papers are clean.
You may only message people who (a) gave you their mobile number and (b) opted in to subsequent messages or calls. You own the opt-in method and must meet the laws that apply to those communications. Honor block, discontinue, and opt-out requests from anywhere — including removing the person from your list. Do not confuse, deceive, spam, or surprise people.
Category-level opt-in — Meta's best-practice block: cover order updates vs offers vs product recs separately; a separate opt-in for calls; clear opt-out per category. Unsolicited categories are how people block you
Escalation is mandatory if you automate — in-chat human, phone, email, website support, in-store, or a support form. A bot with no exit is not enough on Platform
A local licence does not override the list — firearms, adult, dating, MLM, payday loans, and the other Section 4 categories stay prohibited even if you are licensed at home
2. WhatsApp Business Platform terms
Business-initiated conversations use an approved message template, used only for its designated purpose. Meta can review, pause, or reject templates at any time. After a user messages you, you may reply without a template for 24 hours from the last user message. Outside that window, templates only. Standard conversation pricing applies to all categories. Template copy that actually gets approved: template library and template API guide.
3. Protect data
Publish a privacy policy. Get the notices and consents the law requires. Data you get from WhatsApp about a person (other than the thread itself) may only be used as reasonably necessary to support messaging with that person. Do not ask for or share full payment-card numbers, financial account numbers, or personal ID numbers in chat. Do not use WhatsApp for telemedicine or health data if the rules that apply to you forbid putting that data on systems that are not built for it. Never copy one customer's chat to another customer.
4. What you cannot promote — and the regulated exceptions
Section 4 bans criminal use, illegal products, and a long list of regulated or restricted goods: firearms; alcohol and tobacco; drugs (prescription, recreational, or otherwise); medical and healthcare products; endangered species; live animals (except livestock); hazardous materials; real, virtual, or fake currency including ICOs and binary options; body parts; fraudulent or exploitative models; real-money gambling and gaming; adult products and services; dating; multi-level marketing; payday loans, paycheck advances, P2P lending, debt collection, and bail bonds. Offensive or sexually explicit content is out. News publishers need a registered Facebook News Page. Discrimination based on personal characteristics is prohibited.
If a catalog or other commerce experience sells something banned by the Meta Commerce Policy, Meta may cut some or all WhatsApp Business Services — not only the catalog.
Section 5: messaging about regulated verticals (Platform only)
Limited exceptions exist for messaging about named regulated verticals on the WhatsApp Business Platform, in listed countries, under local law. They do not apply to the WhatsApp Business app. They do not allow commerce experiences (catalog, payments, in-chat checkout) for those goods. Messages must be gated by age (no one under 18), geography, and regulation. Licences must be current; if a licence lapses, stop immediately.
Meta currently publishes three exception charts on that page:
- Online gambling and gaming — Australia, Japan, Colombia, Mexico, Peru. Also requires a Meta permission application and proof of licence (Section 6). Promotions count even if nobody can bet inside the chat
- Over-the-counter drugs — a long country list that includes India as of this recap. Still 18+, still no catalog commerce for the vertical
- Alcohol — a long country list that, as of this recap, does not include India. Do not assume a liquor licence at home lets you run WhatsApp promos
Those lists move. Treat the live policy as source of truth. Physical casinos, state lotteries run by the official operator, ordinary retail prize promotions, and free-to-play games have separate notes in Section 6 — still subject to local law.
Policy for WhatsApp commerce features (catalogs, payments, selling in chat)
This is the section at #policy-for-whatsapp-commerce-features-including-offering-goods-or-services-for-sale. It governs whether you may sell with WhatsApp Business Services — catalog, payments, and any other commerce experience.
- You must comply with the Meta Commerce Policy plus applicable law
- You own the transaction: sales terms, privacy terms, and anything else the buyer sees
- WhatsApp is not responsible for processing, paying for, or fulfilling the sale
- You determine, collect, withhold, report, and remit taxes, duties, and fees
Practically: a Shopify catalog on Cloud API is still your shop. If a SKU is banned on Meta commerce, do not sync it to WhatsApp. Regulated verticals that may be messaged in a few countries still cannot be sold through WhatsApp commerce features. Store playbooks: WhatsApp API for e-commerce and Shopify integration.
Government and political use
Government entities may use the WhatsApp Business Platform only through a Solution Provider (the former BSP). Political parties, politicians, candidates, and campaigns are prohibited. So are law enforcement, military, national security and intelligence agencies. So are political consultancies, voting-system vendors, and exclusive government service providers. Ominiflow can onboard eligible government programmes as a Solution Provider; we cannot put a campaign on Cloud API because a client asked.
Enforcement, quality, and appeals
Meta may limit or remove access for negative feedback, harm, policy violations, or to keep quality high. People can block or report you; a low quality tier for a sustained period throttles how many messages or calls you can start. Unauthorized scale messaging can get the service cut. Termination for policy or terms can bar the organisation from future WhatsApp products. Detection uses both technology and human review of reported messages and unencrypted account, group, and profile data.
Business app suspension
Appeal via Meta's Business Help Center path linked from the policy page. Do not create a second number to dodge a ban.
Cloud API / WABA
Use WhatsApp Business Platform Policy Enforcement (linked from the same page). On Ominiflow we see template pauses and quality colour in WhatsApp Manager and help assemble the appeal pack — we cannot override Meta.
How this maps to Ominiflow
Official Cloud API, template submit/pause in-product, documented opt-in on checkout and forms, shared inbox as the in-chat human escalation, Shopify catalog sync that you must still filter for Commerce Policy, Meta conversation fees at cost. Typical go-live is 5-7 business days with complete Business Manager documents. We will not enable a prohibited vertical or a political campaign because a sales deck asked.
Operator checklist
- Display name, website, and support contacts match the real business
- Every Marketing send has recorded opt-in; STOP works
- Bots have talk-to-human (or phone/email/form) in the same flow
- No PAN, Aadhaar, full card, or account number collected in the thread — use a hosted payment page
- Catalog SKUs checked against Meta Commerce Policy; regulated verticals stay off commerce features
- If quality goes yellow, pause Marketing — rating playbook
Ban prevention and recovery · Order-status utility · Templates · Book a demo
FAQ
What is the WhatsApp Business Messaging Policy? expand_more
It is Meta's public rulebook for WhatsApp Business Services (Business app and Business Platform). Together with the Messaging Guidelines and Business Terms of Service, it defines what is allowed. Violations can limit or remove access.
Can I sell products in a WhatsApp catalog? expand_more
Yes if the goods and the experience comply with the Meta Commerce Policy and the WhatsApp commerce-features section. You own terms, taxes, and fulfilment. WhatsApp does not process or fulfil the sale. Regulated verticals cannot use commerce features even where limited messaging is allowed.
Do I need opt-in to message customers on WhatsApp? expand_more
Yes. You need the person's mobile number and opt-in confirming they want subsequent messages or calls. Honor opt-out everywhere. Meta also recommends separate opt-in by message category and a separate opt-in for calls.
Can Indian businesses promote alcohol or online gambling on WhatsApp? expand_more
Not under the exception charts on Meta's policy page as of this recap. India appears on the over-the-counter drugs messaging list (Platform, 18+, no commerce). Online gambling exceptions are only Australia, Japan, Colombia, Mexico, and Peru, plus a Meta permission form. Alcohol's allowed-country list does not include India. Re-check the live policy before you send.
How does Ominiflow help with WhatsApp policy compliance? expand_more
Ominiflow is official Cloud API: approved templates, opt-in logging, human handoff in the shared inbox, and catalog sync you still have to keep Commerce-Policy clean. Meta fees pass at cost. Typical go-live is 5-7 business days with complete documents. Policy enforcement stays with Meta.
