Getting Approved by Meta to Send WhatsApp Messages

A retailer's reference guide to the paperwork, the people, and the process

The iVendNext WhatsApp App connects your store operations to WhatsApp. Before any of that wiring matters, Meta has to approve your business to use the WhatsApp Business Platform in the first place. That approval is not a single switch — it is a sequence of accounts, documents, reviews, and policy commitments that every business goes through. This guide walks you through it end to end, in the order it actually happens, with the trade-offs Meta does not always make obvious.

This is a neutral reference. It does not push you towards a particular provider or a particular path. It does point out, at each fork in the road, what most retailers choose and why.

All facts in this guide are drawn from Meta's primary documentation as of June 2026. Where pricing or policy is documented on a live page that Meta updates regularly, the article links to that page rather than reproducing numbers that will be out of date by next quarter.

Important — please read before relying on this guide

This document is provided by iVendNext (CitiXsys) for general informational and orientation purposes only. It is the product of internal research into Meta's published documentation as of the date noted above, and is intended solely to help retailers understand the broad shape of the onboarding journey before they begin.

This is not a substitute for Meta's own documentation, and it is not legal, financial, regulatory, or tax advice. Meta's WhatsApp Business Platform — including its account creation process, verification requirements, phone number rules, template categories, pricing model, policies, and approval timelines — is owned and operated by Meta, governed by Meta's terms, and changed by Meta at Meta's discretion. Meta may update any element of this process at any time without notice to iVendNext or to you.

iVendNext makes no representation, warranty, or guarantee that the contents of this guide are current, complete, accurate, or applicable to your specific business, jurisdiction, or commercial circumstance. Steps, requirements, document expectations, fees, review timelines, and policy enforcement described here may differ from what you encounter in practice. References to specific Meta features, products, programs, or behaviours are illustrative and may not be available in your market or to your business.

You are solely responsible for your own onboarding decisions, for ensuring compliance with Meta's then-current policies and terms, for satisfying applicable laws in every jurisdiction where you operate (including data protection, consumer protection, telecommunications, and sectoral regulations), and for any consequences arising from your use of the WhatsApp Business Platform. Before acting on anything described in this guide, verify the current position directly with Meta's official documentation and, where appropriate, take independent legal, regulatory, or tax advice.

iVendNext, CitiXsys, and their respective affiliates, officers, employees, and agents accept no liability whatsoever — whether in contract, tort, statute, or otherwise — for any loss, damage, cost, expense, missed opportunity, account restriction, account termination, or other consequence arising directly or indirectly from any reader's reliance on the contents of this guide.

The iVendNext WhatsApp App is a software application that connects to Meta's APIs once a retailer has independently completed Meta's onboarding process. iVendNext does not act as a Meta Business Solution Provider, does not sponsor or warrant any retailer's account on Meta's platform, and is not party to the contractual relationship between the retailer and Meta.

By continuing to read this guide, you acknowledge and accept the above.

The shape of what you are about to do

At the highest level, the onboarding process has four phases:

Phase 1 — Set up the corporate identity layer. This is the Meta Business Portfolio (still commonly called Meta Business Manager). It is the parent account that owns your ads, your Pages, your credit line, and your WhatsApp assets. You verify your business at this level.

Phase 2 — Set up the WhatsApp asset layer. Inside the Business Portfolio you create a WhatsApp Business Account (WABA). The WABA is the home for your phone numbers and your message templates.

Phase 3 — Get a phone number and a display name approved. You either bring your own number across from the WhatsApp consumer app, register a brand-new number, or use a Meta-supplied test number while you build. You also pick the display name customers will see in chat, and Meta reviews it.

Phase 4 — Get your templates approved and start sending. Every business-initiated message goes through one of Meta's approved templates. Templates are categorised, reviewed, and priced differently depending on what the message says.

Until all four phases are complete you cannot send a production message. A realistic retailer should plan for two to six weeks from "we want to use WhatsApp" to "first production message at meaningful volume." Verification delays are the single biggest variable.

Decision flowchart — read this first

Before you start clicking buttons in Business Manager, answer these five questions. The answers determine which path through the onboarding process you take.

Do you already have a Meta Business Portfolio? If yes (because you already advertise on Facebook or Instagram), you reuse it. If no, you create one in Phase 1. Either way, you must verify the business at the portfolio level to scale past the starter sending limit.
Will you use your existing WhatsApp number or a new one? If you already have a number on the WhatsApp consumer app or the free WhatsApp Business app and want to migrate it to the Platform, you must first delete the consumer account from that phone — which means losing your chat history unless you back it up first. If you do not want to lose history, you onboard via a Solution Partner that supports the "Coexistence" flow. If you would rather start fresh, buy a new mobile number from your telco and skip the migration entirely.
Are you in India or Brazil? If your portfolio's registered address is in India or Brazil, you currently cannot create a WhatsApp Business Account through the Meta Business Suite UI. You must use the App Dashboard route (more technical, requires creating a Meta developer app) or onboard via a Solution Partner. This is a Meta-imposed restriction, not a permanent one — it may lift, but as of June 2026 it is still in place.
Do you need a phone number ready immediately, or can you wait for OTP verification? A Meta test number (the +1 631 555-prefixed numbers) is generated instantly when you complete the Cloud API Get Started flow. It is for development and testing only — you cannot use it for production traffic. A real production number requires OTP verification by SMS or voice call, which usually completes in minutes but depends on your telco. A Solution Partner can supply a pre-verified production number that skips OTP entirely.
Do you have in-house or partner development resource? The iVendNext WhatsApp App is built for the direct Cloud API path — meaning your iVendNext implementation team handles the integration. If that team is in place, the direct path gives you maximum control and the cleanest billing (you pay Meta directly). If you do not have implementation resource and want a no-code campaign dashboard bundled, a Solution Partner (BSP) is an alternative path. Meta documents both paths as legitimate. The trade-offs are discussed at the end of this guide.

Once you have these five answers, you can proceed.

Phase 1 — The Meta Business Portfolio

What it is

The Meta Business Portfolio (often still called Meta Business Manager, accessed at business.facebook.com) is the umbrella account that owns every Meta asset your business uses. Your Facebook Page, your Instagram account, your ad accounts, your catalogue, and — critically — your WhatsApp Business Account all live inside one portfolio.

You can have more than one portfolio (a holding company with multiple brands, for example), but each WhatsApp Business Account can belong to exactly one portfolio. Meta is explicit on this: "A WABA must belong to only one business portfolio. You cannot have two or more portfolios owning one WABA." Migration of a WABA between portfolios is not supported.

How to create one

Go to https://business.facebook.com/. If you are signed in to a personal Facebook account, you will be offered the option to create a business portfolio. Provide your business legal name (this matters later — it must match your registration documents exactly), the primary admin's name, and a business email address that is not a personal address.

The whole creation step takes minutes. The verification step that follows takes considerably longer.

Business verification — the bottleneck

You can use a Meta Business Portfolio without verification for a limited set of features. To do meaningful WhatsApp business messaging — specifically, to scale past Meta's starter sending limit of 250 unique recipients per 24 hours — you must complete business verification. This is the gating step most retailers underestimate.

What documents Meta wants

Meta does not publish one universal document list. Requirements vary by jurisdiction and entity type. In broad terms, what is consistently required is:

A business formation document showing the entity name and beneficial owners — a certificate of incorporation, a company registration form, or your local equivalent. The document must show an official signature or seal. Self-filled or self-prepared documents are not accepted.
A utility bill or equivalent showing the business name and address. A utility bill that shows only an address but not the business name is not sufficient to confirm a phone number.
Optional but accelerating: domain ownership proof. Meta lets you verify your business by updating a DNS TXT record at your domain registrar. Meta describes this as the "easiest and fastest method, about a minute" — but it only works if the business has its own internet domain.

The single most important rule across all of these: the legal name on every document must match the legal name in your Business settings exactly. Punctuation, abbreviations, "Ltd" vs "Limited" — any mismatch is a top rejection reason.

How the review actually works

You submit documents through Business Settings → Business Info → Verification, and Meta places the request in a queue. Meta does not publish a verification SLA. In practice the review can complete in hours, days, or weeks depending on jurisdiction, document quality, and current queue depth. There is no way to expedite it.

If verification is rejected, Meta tells you the reason and lets you resubmit. Common rejection reasons Meta documents:

Self-filled legal documents without an official signature or seal.
Small, blurry, or low-resolution scans.
A website that does not load, is not on HTTPS, or has broken links.
Submission of false or misleading information.
Trying to claim a business the submitter does not own or legally represent.
Legal name mismatch between document and Business settings.

Appeals run through the Business Support Home (business.facebook.com/business-support-home/). Each resubmission triggers a fresh review.

What if you cannot verify directly?

If your business cannot complete its own verification — typically because it is too small to have formal incorporation documents, or because the verification process keeps failing for reasons outside your control — a Solution Partner (BSP) can complete Partner-led business verification on your behalf. This is a documented Meta flow, not a workaround. It is one of the reasons retailers choose the BSP path even when they otherwise prefer direct Cloud API.

Phase 2 — The WhatsApp Business Account (WABA)

What it is, in Meta's own words

"WhatsApp Business Accounts ('WABAs') represent a business on the WhatsApp Business Platform. You must have a WABA to send and receive messages to and from WhatsApp users, and to create and manage templates."

A WABA is a child asset that sits inside your Meta Business Portfolio. It is the home for your business phone numbers and your message templates. You can have more than one WABA in a single portfolio (up to 20 initially, expandable), and you can register up to two business phone numbers per portfolio initially (expandable to 20). Each WABA can hold up to 250 message templates.

The asset hierarchy

Stack it up and the picture is:

Meta Business Portfolio (up to 20 WABAs)

└── WhatsApp Business Account (up to 250 templates)

├── Business phone number 1

├── Business phone number 2

└── ...

A Meta App ID is a separate concept — it represents the application that calls Meta's APIs. The App ID is created in the App Dashboard, configured with the WhatsApp use case, and connected to the WABA. The iVendNext WhatsApp App becomes the application that uses this App ID to authenticate API calls to Meta.

Three paths to creating a WABA

Meta documents three ways to create a WABA. Pick one based on your situation.

Path A — App Dashboard (the direct Cloud API path). Go to the Meta App Dashboard, create a new app with the WhatsApp use case selected, and complete the Cloud API Get Started flow. Meta automatically provisions a test WABA and a test business phone number on the spot. You then add a production phone number through the App Dashboard's WhatsApp section, which generates the production WABA. This is the path the iVendNext WhatsApp App is built for.

Path B — Embedded Signup via a Solution Partner. The partner provides a signup link. The flow gathers business details and creates the WABA for you. This path is required if you are using a BSP.

Path C — Meta Business Suite. Settings → Accounts → WhatsApp accounts → +Add → Create a new WhatsApp Business account. The simplest UI path, but as noted above, not available to portfolios with a registered address in Brazil or India.

Two things to know about WABAs before you create one

Time zone and currency are locked. Once you attach a credit line to a WABA, the time zone and currency cannot be changed. Pick carefully.

WABA migration between portfolios is not supported. If you create a WABA under the wrong portfolio, you have to delete it and create a new one — losing any associated templates and history. Choose the right portfolio the first time.

Phase 3 — Phone numbers and display names

The four phone number options

Option A — Bring your own existing number

If you already have a number on the regular WhatsApp app or the free WhatsApp Business app and want to use it on the Platform, you have to delete the consumer account first. Meta's documentation is explicit: "To use an existing WhatsApp Messenger phone number with Cloud API, you must first delete your WhatsApp Messenger account."

Deletion is straightforward — open WhatsApp on the phone, go to Settings → Account → Delete my account. Meta notes it can take up to three minutes for the freed number to become available again to the Platform.

The catch is chat history. Deleting the consumer account deletes the chats on that number. If you have customer conversations on a WhatsApp Business app number that you want to keep, two options exist:

Back up the chats first using the platform-specific backup guides (Android, iOS), then accept that the backup is offline-only — it cannot be restored to the Platform.
Onboard via a Solution Partner that supports business app number onboarding (Coexistence). This flow preserves history and allows the Business app and the Platform to run on the same number concurrently. It is the only way to avoid the data loss.

Once the number is freed, registration on the Platform requires verifying ownership via SMS or voice OTP. The number must:

Be owned by you.
Have a country and area code (short codes are not supported).
Be able to receive voice calls or SMS.
Not currently be registered to a personal WhatsApp account anywhere in the world.

A two-step verification PIN (six digits) is mandatory at registration. You will need this PIN later to change settings or delete the number. The PIN cannot be disabled through the API — only through WhatsApp Manager.

Option B — Buy a new number from a telco

If you do not have a WhatsApp-suitable number, buy a new mobile SIM from a telco for the business. The same eligibility rules apply. A mobile number is Meta's recommended choice — it supports both SMS OTP and voice OTP for verification, and behaves reliably across the Platform.

Landline, toll-free, and VoIP numbers are usable for voice OTP only (SMS to these number types is unreliable or not supported), and Meta marks them as "Not Recommended" for SMS OTP. If you must use a 1-800 or toll-free number sitting behind an IVR, Meta will share the 1–2 originating phone numbers that the registration call will come from, so you can allow-list them and route to a human or mailbox during verification.

Numbers Meta does not support: pager numbers, machine-to-machine / IoT numbers, shared-cost numbers, and personal premium-rate numbers.

Option C — Meta test numbers (the "555" numbers)

When you complete the Cloud API Get Started flow in the App Dashboard, Meta automatically issues you a test business phone number in the format +1 631-555-1111. This number:

Can send template messages to a small allow-list of phone numbers you specify (typically your own and your developer team's).
Can receive incoming messages for webhook testing.
Cannot be used for production customer traffic.
Cannot be promoted to a production number — it is forever a test number.

The test number's role is integration validation. Once you have proven the iVendNext WhatsApp App is wired up correctly and your templates send and webhooks fire, you move to a production number. The test number can stay around for ongoing development.

Option D — BSP-supplied pre-verified numbers

A Solution Partner can supply a number that arrives pre-verified — no OTP step, no waiting for SMS, instant production capability. This is one of the headline benefits of the BSP path. Meta documents this through the Embedded Signup pre-verified phone numbers flow. It is a legitimate option; whether the trade-offs make sense for you is covered in Phase 4 and the closing section of this guide.

Display name approval

The display name is the name customers see in WhatsApp when they receive a message from your business. You supply it at the time of phone number registration, and Meta reviews it. The review status moves through values like PENDING_REVIEW, APPROVED, AVAILABLE_WITHOUT_REVIEW, DECLINED, and EXPIRED.

Meta's published guidelines require the display name to:

Match your established brand.
Avoid generic terms ("Best Shoes," "Pharmacy") that could apply to many businesses.
Avoid deceptive or misleading language.
Avoid most special characters (emojis, decorative symbols).

Common rejections come from generic names, names that don't match the verified business name, and names with promotional language ("ABC Store — 50% off!").

You can change the display name later through WhatsApp Manager. Each change triggers a fresh review.

The green checkmark and the blue checkmark

Two badges exist, and the distinction matters.

Green checkmark — Verified Name. This is what nearly every legitimate retailer gets. It indicates the display name has been approved and matches a verified business. The badge appears in smaller contexts on WhatsApp; the customer still sees the business name as the sender, but the prominent visual treatment is reserved for the next badge.

Blue checkmark — Official Business Account (OBA). This is the elevated badge most businesses want but few qualify for. Meta's eligibility list is:

Comply with the WhatsApp Business Messaging Policy.
Have been on the Platform for at least 30 days.
Have two-step verification enabled on the phone number.
Have an approved display name.
And critically: "the business must be considered a notable business — a well-known business that has a substantial presence in news articles from publications with sizable audiences."

That last criterion is the gatekeeper. The OBA badge is reserved for businesses with genuine press coverage in reputable publications. A typical regional retailer will get the green-check Verified Name and not the blue OBA. This is normal. Plan around it.

Phase 4 — Templates, categories, and policy

What a template is

Outside the 24-hour customer service window — meaning more than 24 hours after the customer's last message to you — you can only send a customer a message using an approved template. Templates are pre-written message structures with named variables that you fill in at send time. They have headers, bodies, footers, and optional interactive buttons.

Templates are approved by Meta, not by you. Submission is automated (the iVendNext WhatsApp App pushes templates to Meta's API on save), but the review is performed by Meta against published guidelines. Status moves from PENDING to APPROVED or REJECTED, typically within minutes to a day. Meta does not publish a review SLA.

The three template categories

Every template must be classified as one of:

Marketing — for awareness, sales, retargeting, customer relationship-building. Promo codes, new-product announcements, abandoned cart messages, birthday wishes, "thank you for your last order, here's 15% off" — all Marketing.
Utility — for following up on user actions or requests. Order confirmations, shipping updates, delivery notifications, payment reminders, balance alerts, feedback surveys tied to a specific transaction.
Authentication — for one-time passwords and identity verification. Authentication templates have their own rules: no URLs, no media, no emojis, parameters capped at 15 characters, and must use Meta's Template Library authentication template format with a copy-code or one-tap button.

The legacy "Transactional" category was retired in mid-2023 when this three-category system launched. There is no separate "Service" category — what some materials call "service messages" are the freeform non-template messages you can send within the 24-hour customer service window.

What makes a template Utility (and not Marketing)

Meta's rule has two parts, both of which must be true. The template must be:

Non-promotional, containing no promotional or persuasive intent.
Either specific to or requested by the user (clearly related to their order, account, services, or transactions) OR essential or critical to the user (such as for safety).

The most common pitfall: writing a template that does the right thing (e.g., confirms an order) but adds a promotional line at the end ("…and here's 10% off your next purchase"). The presence of the promo turns a Utility candidate into Marketing. Meta categorises mixed-content templates as Marketing automatically.

Another common pitfall: a template that is too generic to verify ("Hi {{1}}, see you soon!" or just "{{1}}"). Meta categorises generic templates as Marketing because there is no specific transaction to anchor them to.

What happens when Meta disagrees with your category choice

Until early 2025, choosing the wrong category meant your template got rejected and you had to resubmit. As of 9 April 2025, Meta changed the behaviour:

If you submit as Utility but Meta determines the template is actually Marketing, the template is automatically approved as Marketing (no rejection). You have 60 days to appeal in Business Support if you disagree.
If you submit as Marketing but Meta determines it should be Authentication, Meta gives you a notice period and then flips the status to REJECTED on the first of the following month.

The previous opt-in setting that allowed automatic recategorisation is now the default behaviour. You cannot turn it off.

Don't try to game the categories

Meta added enforcement against deliberate miscategorisation effective 16 April 2025. The cadence:

First offence — Warning.
Continued misuse — Rate limiting (a cap on utility templates in any 24-hour window).
Further misuse — Utility restriction: all your approved utility templates are recategorised as Marketing for 7 days (30 days for repeat offenders).
Repeated abuse across multiple WABAs in your portfolio — Portfolio-wide restriction: every WABA in the portfolio is affected for 30 days.

The financial incentive to mislabel exists because Marketing templates are priced higher than Utility. Meta's enforcement is designed to remove that incentive.

Why category matters beyond compliance

Two practical reasons to get the category right at submission:

Pricing. Marketing > Utility > Authentication. Marketing templates cost the most per delivery; Authentication the least. A retailer mislabelling Marketing as Utility will save money — for a while — and then pay it back with interest under enforcement.

Frequency and user controls. Users can stop receiving Marketing messages from individual businesses without blocking the number entirely. Utility and Authentication templates are not subject to the same user-toggleable opt-out. Sending what should be Marketing as Utility doesn't just save money — it bypasses the user's ability to mute promotional traffic. Meta treats this as a serious abuse.

Messaging limits, quality, and how you scale up

The tiers

Every newly-created Meta Business Portfolio starts at the same place: 250 unique recipients in any 24-hour period. From there, you can scale to:

2,000 unique recipients per 24 hours
10,000 unique recipients per 24 hours
100,000 unique recipients per 24 hours
Unlimited

The limit is the maximum number of unique WhatsApp phone numbers you can deliver messages to outside of an open customer service window in any moving 24-hour period. Replies sent inside an open customer service window do not count against the limit. The limit applies at the portfolio level, shared across all phone numbers in all WABAs in that portfolio.

How to get to 2,000

Meta gives you three ways to move from 250 to 2,000, and you only need to complete one:

Verify your business. Once Phase 1 business verification is complete, your portfolio is eligible for the 2,000 tier.
Have your Solution Partner verify your business, if you were onboarded via a BSP using Partner-led business verification.
Send 2,000 delivered messages outside of customer service windows to unique WhatsApp phone numbers within a 30-day moving period, using templates with a high quality rating. This is the "earn your way up" path for unverified businesses.

The first two routes are typically faster than the third.

How automatic scaling works

Once you are at 2,000, Meta will continue to scale you up automatically — to 10,000, then 100,000, then Unlimited — provided you meet two criteria simultaneously:

You are sending high-quality messages across all your business phone numbers and templates.
In the last 7 days, your business has utilised at least half of your current messaging limit.

If both criteria are met, Meta will increase the limit by one tier within six hours. You do not have to apply; the system does it on your behalf.

The "utilisation ≥ 50%" rule means you cannot leapfrog tiers — you have to use your current allowance enough to justify the next one. A retailer sending 800 messages a day will sit at the 2,000 tier indefinitely, regardless of quality.

Quality rating — green, yellow, red

Each business phone number has a quality rating tracked separately from the messaging limit. The rating reflects user behaviour: blocks, reports, "I didn't sign up for this" feedback, and read-rate signals.

The rating is colour-coded:

Green — High. Healthy. Continue sending.
Yellow — Medium. Mixed signals. Pay attention.
Red — Low. Sustained negative feedback.

If the quality rating drops to Low, the phone number's status flips from Connected to Flagged. At that point you have a seven-day recovery window. Meta documents the recovery rules as follows:

"If the quality rating improves to a high or medium quality by the 7th day from when your status was changed to Flagged, the status will return to Connected and your messaging limit tier will remain unaffected. However, if quality does not improve to a high or medium quality by the 7th day from when your status was changed to Flagged, your status will return to Connected but the messaging limit will decrease to the next level."

A downgrade is recoverable — quality must climb back up, and then your tier can grow again through the same automatic scaling rules — but it is painful. Avoiding the downgrade in the first place comes down to opt-in discipline, template content, and respecting customer signals.

Opt-in — the rule that sits behind everything

Meta's WhatsApp Business Messaging Policy is unusually direct on this point. Quoted verbatim:

"You may only contact people on WhatsApp if: (a) they have given you their mobile phone number; and (b) you have received opt-in permission from the recipient confirming that they wish to receive subsequent messages or calls from you."

"You are solely responsible for determining the method of opt-in, that you have obtained opt-in in a manner that complies with laws applicable to your communications, and that you have otherwise provided notices and obtained permissions that are required under applicable law."

The responsibility is yours. Meta does not collect opt-in on your behalf, and "the customer gave me their phone number when they bought something" is not enough by itself — you need explicit permission to message them on WhatsApp.

What Meta requires

Three things, in Meta's words:

Clearly state that the person is opting in to receive communication from the business.
Clearly state the business name they are opting in to receive messages from.
Comply with applicable law (GDPR in the EU, sectoral regulations in financial services and healthcare, etc.).

Valid opt-in methods

Meta lists four valid channels:

SMS — the customer texts a keyword to a number to opt in.
Website — a checkbox or form on your site.
By phone via an IVR flow.
In person or on paper — a physical document the customer signs at the till or registration desk.

The method matters less than the substance. A poorly-worded website checkbox can be invalid; a well-worded paper form at the till can be perfectly compliant.

Best practice — beyond the minimum

Meta makes specific recommendations beyond the policy minimum:

Either get one broad opt-in covering all message categories (order updates, offers, recommendations), or get separate opt-in per category. The per-category approach gives better signal — customers who opt in to "promotions" really did mean it, and your block rate drops accordingly.
Provide a clear opt-out path on and off WhatsApp. Honour opt-outs immediately.
Communicate the value of opting in ("we'll send your order updates to WhatsApp") rather than asking for permission in the abstract ("can we contact you on WhatsApp?").

What happens if you don't comply

The mechanics are blunt. Customers who do not remember opting in either block your number or report it. Either action contributes to negative quality signal. Negative signal accumulates into a quality downgrade. A sustained downgrade triggers Flagged status. If quality doesn't recover within seven days, your tier drops. If the violations are severe or repeated:

"We may limit or remove your access to or use of the WhatsApp Business Services if you receive significant amounts of negative feedback, cause harm to WhatsApp or our users, violate or encourage others to violate our terms or policies."

"If we terminate your account … we may prohibit you and your organization from all future use of WhatsApp products and services."

Termination is permanent. There is no good reason to skimp on opt-in discipline.

The 24-hour customer service window

WhatsApp Business is built around an idea that does not exist in email: a conversation window that opens when a customer messages you and closes 24 hours later.

Within that window, you can send freeform messages — plain text, images, documents, voice notes, whatever — without using a template. Meta calls these "service messages." They are free.

Outside the window, you can only send approved templates. Templates are not free (with some exceptions covered in the next section).

Two specific obligations Meta places on businesses operating within the 24-hour window:

You may use automation to reply during the window — chatbots, automated responses, FAQ matching — but you must also provide prompt, clear, direct escalation paths to a human. Meta lists the acceptable escalation paths: in-chat human agent transfer, phone number, email, web support, in-store visits, or a support form. At least one must be available.
The 24-hour window opens the moment the customer's message reaches you. It closes 24 hours later regardless of how many messages were exchanged in between.

A useful rule of thumb: design every conversation flow so that even fully-automated interactions can escalate to a person within 24 hours.

Pricing — the model changed in 2025

How Meta charges you now

The pricing model in effect since 1 July 2025 is per-message, not per-conversation. Meta's wording:

"You are only charged when a template message is delivered (type:template). Rates vary based on the template's category and the recipient WhatsApp phone number's country calling code."

"All non-template messages are free (type:text, type:image, and so on). These can only be sent within an open customer service window."

"Utility templates delivered within an open customer service window are free."

"You can unlock lower rates for utility and authentication template messages, based on messaging volume."

"All messages are free for 72 hours, including template messages, if sent within an open free entry point window."

Translated: every template delivery is a billable event. The rate depends on (1) the template's category and (2) the country code of the recipient. Non-template messages within an open customer service window cost nothing. Utility templates inside an open service window also cost nothing. And conversations that start when a customer clicks a Click-to-WhatsApp ad or a Facebook Page call-to-action have a special 72-hour free entry point window where everything sent is free, templates included.

How a real billing day looks

Meta walks through a worked example. Imagine a single conversation over 30 hours:

Hour 0 — You send a Marketing template (a promotional message). Marketing charge.
Hour 2 — Customer replies. The customer service window opens. No charge.
Hour 3 — You send a freeform reply within the window. Free.
Hour 4 — You send a Utility template (order confirmation) within the open window. Free.
Hour 26 — The 24-hour service window closes.
Hour 30 — You send a Utility template (delivery update). The window is closed. Utility charge.

Four messages sent, two billed.

What rates actually are

Meta does not publish narrative dollar figures on the developer documentation page. Instead, Meta publishes a live, downloadable rate card per currency at business.whatsapp.com/products/platform-pricing. Rate cards exist for USD, GBP, EUR, INR, BRL, IDR, and many other currencies, and Meta updates them quarterly with one month's notice.

Two facts hold consistently across markets:

India has higher Marketing template rates than most other markets.
North America has lower Utility and Authentication rates than most other markets.

Beyond that, the rate card is the source of truth. The article you are reading would mislead you within a quarter if it tried to quote per-message figures here. Link to the live rate card and price your campaigns against it.

Localised billing currency

Meta has been progressively rolling out billing in local currencies beyond USD. Where local-currency billing is available, it materially reduces FX exposure for high-volume campaigns. Check the live pricing page for the current list of supported billing currencies in your market.

Pricing-change governance

Meta committed to two governance rules that are worth knowing:

Pricing-model changes (e.g., the conversation-to-message shift in 2025) come with at least six months' notice.
Rate-card updates come with at least one month's notice and only happen on the first day of a quarter: 1 January, 1 April, 1 July, or 1 October.

This makes budgeting predictable. There will be no surprise mid-quarter rate hikes.

What you cannot send

Some content is off-limits on the WhatsApp Business Platform regardless of opt-in, regardless of templates, regardless of whether you have a license to sell it in your jurisdiction. Meta is direct on this:

"We prohibit use of the WhatsApp Business Services for buying, selling, promoting, or otherwise facilitating the exchange of certain regulated or restricted goods and services listed below, as determined in our sole discretion … These prohibitions apply irrespective of the global or local licenses, registrations, or other approvals your business may hold."

The full prohibited list includes firearms, drugs (prescription or otherwise), medical and healthcare products, endangered species, hazardous materials, real or virtual currencies (including ICOs and binary options), body parts or fluids, fraudulent business models, real-money gambling, adult products, dating services, multi-level marketing, payday loans, debt collection, and bail bonds.

A retailer running a normal mainstream business will not bump into most of these. The exceptions worth flagging:

Alcohol and tobacco are prohibited by default, with regional carve-outs. Alcohol messaging is permitted (with age gating and license proof) in a published allow-list of countries including Australia, Brazil, Mexico, Singapore, Japan, and several others. India is not on the alcohol allow-list. A liquor retailer in India cannot use WhatsApp Business for product promotion.
Healthcare is restricted by default; over-the-counter drugs are permitted in a longer allow-list that does include India, Indonesia, Brazil, and the Philippines, subject to local law.
Government, political parties, candidates, law enforcement, military, and intelligence are prohibited from using the WhatsApp Business Platform directly. Government entities can use it only via a Solution Partner, not direct.
Online gambling and gaming are permitted in only five countries (Australia, Japan, Colombia, Mexico, Peru), and only with Meta's written prior permission via an application form.

Other content rules that apply universally:

Do not impersonate another business.
Do not share full payment card numbers, full bank account numbers, government ID numbers, or other sensitive identifiers in messages. This is a hard rule. Use last-four-digit references instead.
Do not forward one customer's chat data to another customer.
News publishers must be registered as a Facebook News Page to message on the Platform.

Appeals

Template-level appeals (disputing a category change or a rejection) go through Business Support Home, with a 60-day window from the decision.

Account-level enforcement appeals (a phone number flagged, a WABA restricted, a portfolio limited) also go through Business Support Home. Meta does not publish appeal SLAs; some resolve in hours, others in weeks.

If your account is terminated for a severe policy breach, the documented position is that Meta may prohibit you and your organisation from future use of WhatsApp products and services permanently. There is no formal appeal path against permanent termination.

Direct Cloud API or a Solution Partner — choosing the path

Meta supports two onboarding paths, and both are legitimate. The iVendNext WhatsApp App is built for the direct Cloud API path, but the BSP path is real and many retailers choose it. Here is what each provides, with the trade-offs.

What direct Cloud API gives you

You create the Meta app, you own the WABA, you register the phone numbers, you submit and manage your own templates.
You attach your own credit line and Meta bills you directly.
Full control over webhook configuration and template lifecycle.
The iVendNext WhatsApp App handles the integration on your side. Your iVendNext implementation team does the setup.
No third-party markup on Meta's rates.

What a Solution Partner gives you

Embedded Signup — a Meta-supplied flow the partner runs that creates your WABA with less manual configuration.
Pre-verified phone numbers — skip the OTP step, get to production faster.
Partner-led business verification — useful if your business cannot complete its own verification.
A shared credit line — you can avoid attaching your own credit card and pay the partner instead.
Template approval shortcuts — some BSPs maintain a library of pre-approved templates for common retail use cases.
A no-code dashboard for sending campaigns and managing contacts, layered over Meta's API.
Billing aggregation — a single invoice from the BSP rather than multiple Stripe charges from Meta.

The trade-offs

Vendor lock-in. Migrating a WABA from one Solution Partner to another, or from a partner to direct, is possible (Meta documents the Embedded Signup migration flows) but takes effort and can break some assets along the way.
Markup on Meta's rates. BSPs typically add a per-message margin or a platform fee on top of Meta's rate card. Meta does not police this; the markup is between you and the partner.
Less direct control. When you operate through a partner's dashboard, you trade webhook-level control for ease of use. For most retailers this is the right trade; for some it is not.
Faster time to first message. Pre-verified numbers and pre-approved template libraries can mean production traffic in days rather than weeks.

Which path makes sense

There is no universal answer. Three honest patterns hold:

If your iVendNext implementation team is in place and you want maximum control with no markup, the direct Cloud API path is the natural fit. The iVendNext WhatsApp App is built for it.
If you do not have technical resource and you want a no-code campaign tool bundled with your WhatsApp access, a Solution Partner is a sensible choice. You pay a markup; you get a managed experience.
If your business cannot pass Meta's business verification on its own — typical for early-stage retailers without formal incorporation documents — a Solution Partner with Partner-led business verification may be the only viable route.

A note on terminology: the Meta documentation uses "Solution Partner," "Solution Provider," and "BSP" (Business Solution Provider) interchangeably. They mean the same thing.

Realistic timeline

A retailer doing this from scratch, on the direct Cloud API path, with iVendNext's implementation team handling the technical work, should expect roughly this shape:

Step	Realistic duration	What gates it
Create Meta Business Portfolio, fill profile	Minutes (Day 0)	Just admin time
Create WABA via the App Dashboard	Minutes (Day 0)	Meta App setup
Add and verify production phone number (OTP)	Up to 3 minutes for consumer-app deletion + OTP delivery (Day 0–1)	Telco SMS/voice reliability
Submit display name for review	Same day to 1–2 days	Meta review (no SLA)
Submit business verification documents	Days to several weeks	Meta review queue, document quality
Submit first templates	1–3 days	Meta auto-review (usually minutes to a day)
First production message at 250-tier limit	Day 1–7 (after verification approval)	Templates approved
Reach 2,000-tier (via business verification path)	Concurrent with verification (Week 1–2)	Business verification complete
Automatic scale to 10,000-tier	Week 3–4 minimum	Sustained ≥50% utilisation of 2,000 tier over 7 days, high quality

End to end: 2–6 weeks. The single biggest variable is business verification. Submit clean, exactly-matching documents on the first attempt, and you reduce that variable substantially.

What to gather before you start

A prerequisite checklist that, if completed in advance, will keep the process moving:

Business legal name as it appears on your registration documents. This must match exactly across Business settings, verification documents, and your WhatsApp display name application.
Certificate of incorporation or business registration document with an official signature or seal. Self-filled forms will not pass.
Tax / VAT / GST registration document appropriate to your jurisdiction.
A recent utility bill or equivalent that shows the business name and address (not just an address).
A business website on HTTPS that loads cleanly and has no broken links. Meta inspects the site as part of verification.
Ability to add a DNS TXT record at your domain registrar, for the fastest domain verification path.
A business phone number that is mobile (recommended), can receive international SMS and voice, and is not currently registered to a personal WhatsApp account anywhere.
A backup of any existing WhatsApp Business app chats on a number you plan to migrate (chats are lost on deletion unless backed up).
A six-digit two-step verification PIN to set during phone number registration. Choose something you will remember; you will need it later.
A display name candidate that matches your brand and avoids generic terms.
A payment method for the WABA credit line (a corporate card, ideally), or a Solution Partner's credit line if you go that route.
A documented opt-in flow that shows customers the business name they are opting in to and the type of messages they will receive.
Draft templates classified by category (Marketing / Utility / Authentication) ready to submit once the WABA is live.
A webhook endpoint on HTTPS if you are integrating directly via Cloud API (the iVendNext implementation team handles this for you).

The pitfalls that catch most retailers

Drawn from Meta's published troubleshooting documentation and the failure modes that recur in retail onboarding:

Trying to register a number that is still on the consumer WhatsApp app. Delete the consumer account first; wait three minutes.
Legal name mismatch between verification documents and Business settings. The most common single rejection reason. Punctuation matters.
Submitting a utility bill that does not show the business name. Has to show both name and address.
A website that fails to load or is not on HTTPS. Fix the site before submitting verification.
Mixing promotional language into utility templates. Auto-recategorises to Marketing as of April 2025; you will pay Marketing rates without realising why.
Deliberately mislabelling Marketing as Utility. Triggers Meta's enforcement ladder. The pricing differential is not worth a portfolio-wide restriction.
Letting opt-in be ambiguous. Customers who don't remember signing up block the number; block rate destroys quality rating; quality rating destroys your tier.
Running automated 24-hour-window conversations with no human escalation path. Policy violation even if customers are happy.
Sending alcohol, healthcare, financial, or gambling content in non-allowed countries. Hard policy violation; can lead to permanent termination.
Trying to create a WABA via Meta Business Suite when your portfolio is registered in India or Brazil. Currently blocked. Use the App Dashboard or a Solution Partner.
Expecting the blue OBA badge. Most retailers get the green Verified Name badge. The blue badge is reserved for "notable" businesses with significant press coverage.

A pragmatic order of operations

For most retailers, the order that works in practice is:

Create or claim the Meta Business Portfolio. Confirm your business legal name matches your registration documents exactly.
Start business verification. Submit clean documents on the first attempt. Add domain verification via DNS TXT for speed. This is the long pole — start it on day one and let it run in the background.
Decide on direct Cloud API vs Solution Partner. If direct (the iVendNext default), proceed to step 4. If BSP, switch to your partner's Embedded Signup flow.
Create the Meta App in the App Dashboard, enable the WhatsApp use case, and take the test number to validate the iVendNext WhatsApp App integration end to end.
Decide on your production phone number. Bring across an existing number (delete consumer account first, back up chats if needed) or use a new mobile SIM.
Register the production phone number in the App Dashboard. Set the two-step verification PIN. Submit your display name for review.
Draft your first templates. Categorise each one carefully — Marketing, Utility, or Authentication. Avoid mixed content. Submit for approval.
Build your opt-in flow. Update your website, your point-of-sale checkout, your in-store sign-up sheets. State the business name clearly. State what messages the customer is agreeing to.
Wait for business verification to complete. Once approved, your portfolio is eligible for the 2,000-tier sending limit.
Send your first production message. Start small. Watch your quality rating. Scale up only as Meta's automatic scaling promotes you.

This is the sequence. Each step has a defined output, and the steps run partly in parallel. The whole thing fits in two to six weeks with disciplined execution.

Where to verify and what to consult

This guide is current as of 2026-06-09. Pricing and policy on the WhatsApp Business Platform change. Before committing to a budget or a rollout plan, check Meta's primary sources for any changes:

WhatsApp Business Accounts overview — https://developers.facebook.com/docs/whatsapp/overview/business-accounts/
Pricing on the WhatsApp Business Platform — https://developers.facebook.com/docs/whatsapp/pricing
Live rate card (per-currency) — https://business.whatsapp.com/products/platform-pricing
Messaging Limits — https://developers.facebook.com/docs/whatsapp/messaging-limits/
Template categorisation — https://developers.facebook.com/documentation/business-messaging/whatsapp/templates/template-categorization
WhatsApp Business Messaging Policy — https://business.whatsapp.com/policy
Getting opt-in for WhatsApp — https://developers.facebook.com/docs/whatsapp/overview/getting-opt-in/
Business phone numbers — https://developers.facebook.com/documentation/business-messaging/whatsapp/business-phone-numbers/phone-numbers
Migrate an existing WhatsApp number — https://developers.facebook.com/docs/whatsapp/cloud-api/get-started/migrate-existing-whatsapp-number-to-a-business-account/
Verify Your Business in Meta Business Suite — https://www.facebook.com/business/help/2058515294227817
About Business Verification — https://www.facebook.com/business/help/1095661473946872
About WhatsApp Business Display Name — https://www.facebook.com/business/help/338047025165344
About Quality Rating — https://www.facebook.com/business/help/896873687365001

Meta updates these pages frequently. If the procedure you read here does not match what you see in Business Manager on the day you do this, the live Meta page is the authoritative source.

This guide accompanies the iVendNext WhatsApp App. Once your Meta-side onboarding is complete, the iVendNext implementation team configures the App in iVendNext Desk and connects it to your approved WABA. From there, every order confirmation, payment reminder, and promotional campaign you send through iVendNext flows through the approved templates, phone numbers, and policies you have just set up.

Docs