WhatsApp Message Template — The Pre-Approved Message, and the Approval-Time Gap in Our Own Reviews

Quick answer: A WhatsApp message template is the one kind of message a business can send outside the 24-hour customer service window, which is the window a user opens by writing to you. Meta's own documentation is unambiguous: template messages are "the only type of message that can be sent to WhatsApp users outside of a customer service window." You write the message once, with placeholders such as {{first_name}}, assign it to one of three categories (marketing, utility, authentication), submit it, and Meta reviews it through what its documentation calls "a combination of automated systems and manual reviews," with a decision in what the same page says "can take up to 24 hours." Approved templates are then priced by category per delivered message, rated for quality on customer feedback, and paused when that feedback turns bad. The part this entry adds is an audit of ourselves. Thirteen of our fifteen platform reviews describe a "BSP-expedited" approval path, and six of them put non-partner approval at "5-7 days." We could not find either claim in Meta's documentation, which describes one review process, automated with manual checks, with no partner variable in it, and the four approval times our reviews report as measured (26, 28, 56 and 58 hours) all sit above the 24-hour ceiling Meta publishes. Something is wrong on one side or the other. Our lean, argued below, is that the partner-lane claim is the weaker one, because it is cited nowhere and appears in no Meta page we read; our own timings are too few and too loosely bounded to settle what Meta's ceiling actually means.

What a template is, mechanically

A template is an asset of a WhatsApp Business Account, not of a phone number. It has a name (lowercase letters, numbers and underscores, up to 512 characters, and names are not unique, because the same name in a second language counts as a second template), a language code, a category, and a list of components: an optional header (text or media), a body, an optional footer, and optional buttons. Body text can contain variables in one of two formats. Positional parameters are numbered and must appear in order, {{1}} then {{2}}. Named parameters, {{first_name}}, {{order_number}}, can be supplied in any order and are easier to maintain; Meta documents both, and defaults to positional if you do not say. Every variable needs an example value at submission, because the reviewer is checking the rendered message, not the skeleton.

The reason the whole apparatus exists is the customer service window. When a user messages a business, a 24-hour window opens in which the business may send anything: free text, images, interactive buttons, lists, a WhatsApp Flow. When the window closes, the only thing the business can send is a template. Templates are therefore the mechanism behind every business-initiated message on the platform: order confirmations, delivery updates, appointment reminders, one-time passcodes, and every broadcast to an opted-in list. A confirmation message sent inside the window is just a message; the same words sent the next morning are a template or they are nothing.

Two structural limits are worth knowing before you design a catalog of templates. An unverified business portfolio can hold 250 templates per WhatsApp Business Account; a verified portfolio with at least one approved display name can hold 6,000. And a template nobody has sent for 12 months is archived and, 28 days later, deleted. Our guide to verifying a WhatsApp Business Account covers what verification requires; the point here is that verification, not partner status, is the variable Meta's documentation attaches to template capacity.

The three categories, and why the category is the price

Every template is marketing, utility or authentication, and since 1 July 2025 Meta charges per delivered template message at a rate set by that category and the recipient's country. Category is not a label you choose freely. Meta validates it against the content at creation and again, on a recurring basis, afterward.

Marketing is the default and the most expensive. It covers promotions, awareness, retargeting, app promotion and relationship messages, and it also absorbs two things people do not expect: any template that mixes utility and promotional content ("your order shipped, and here is 15% off your next one") and any template whose content is unclear (a body that is only {{1}}, or "Congratulations!").

Utility must satisfy two tests at once. It must be non-promotional, "not containing any promotional or persuasive intent," and it must also be either specific to or requested by the user, or essential to them. Meta's categorization page lists five utility objectives: opt-in management, order management, account alerts, feedback surveys tied to a specific transaction, and continuing a conversation that started on another channel. The pricing consequence is the whole reason the test matters: utility templates delivered inside an open customer service window are free, and utility rates outside it are a fraction of marketing rates in most markets.

Authentication is the narrowest. Only an authentication template may carry a one-time passcode, it must use a copy-code or one-tap button, and it may contain no URLs, no media, no emoji, and no parameter longer than 15 characters.

The rule that changed how miscategorization fails is dated 9 April 2025. Before it, a template submitted as utility that Meta judged to be marketing was rejected, which was loud. Since then it is approved as marketing, which is quiet. Your reminder sends, at the higher rate, and nothing in the send path tells you. Meta also runs a recurring sweep of approved templates: a utility template that should be marketing is re-categorized with one day's notice, and a business that has already been warned for categorization misuse gets no notice at all. A marketing or utility template found to be carrying an OTP is not re-categorized but rejected on the first of the following month. The correct_category field on the template API shows what is coming, and a template_category_update webhook fires when it lands.

Review, quality rating, pacing and pausing

Templates are "automatically reviewed upon creation or after editing," in the words of the Template fundamentals page; the Template review page is more precise, saying content "undergoes validation through a combination of automated systems and manual reviews," and that "it can take up to 24 hours for an approval decision to be made." A template that passes is APPROVED and can be sent; a template with any other status cannot. A rejection can be appealed with a sample attached, and Meta commits to deciding the appeal within 24 hours as well. Infobip's partner documentation adds that approval "is usually immediate if your business is verified, but may take up to 24 hours otherwise," which again names business verification, not partner status, as the variable.

Approval is where most write-ups stop and where Meta's lifecycle is only beginning. Every approved template carries a quality rating: UNKNOWN (quality pending) at creation, then GREEN, YELLOW or RED as customers block, report, or simply fail to read the messages. All four ratings can still be sent. Rating matters because of the two processes it feeds.

Pacing applies to marketing templates, and to utility templates only for seven days after a utility template of yours has been paused. A paced template sends normally up to an undisclosed threshold, after which further sends are held with a held_for_quality_assessment status while Meta waits for early feedback. Good feedback releases the held messages; bad feedback drops them, with a failed status and error code 132015 on each, and pauses the template. Meta's stated guardrail is that even a paced campaign's highest-throughput messages should be delivered within an hour at the 99th percentile.

Pausing is the sanction. A template whose quality falls to RED is paused, and it cannot be sent while paused. The schedule, as published in partner documentation that mirrors Meta's pausing page: three hours the first time, six hours the second, and permanently disabled the third. The same partner documentation says an edit made during a pause goes live within minutes, which is the intended escape hatch, and that Meta keeps tracking the block rate on the edited version.

Alongside all of this sit two limits that are not about any one template, both named on Meta's Template fundamentals page and neither re-derived here. Messaging limits cap how many template messages a phone number may send outside customer service windows in a rolling day, and they rise with quality; our WhatsApp channel guide covers the tiers. And a per-user marketing limit caps how many marketing templates one WhatsApp user can receive from all businesses combined, which means a marketing template can be silently undelivered for reasons that have nothing to do with you. Our WhatsApp broadcast campaign guide covers the ramp that these limits impose on a new number.

What our fifteen reviews say about approval time, and what Meta says

This is the section we would rather not have needed. Thirteen of our fifteen platform reviews use the phrase "BSP-expedited" or "expedited template" to describe the approval path available through a Meta Business Solution Provider. Six of them put the alternative, non-partner path at "5-7 days." Our own WhatsApp channel guide states the split as "24–48 hour template review versus 5–7 days for non-BSP" and lists direct BSP status as the first selection criterion partly on that basis.

We read six of Meta's template pages looking for the source of that split and did not find one. The Template fundamentals page says templates are "automatically reviewed upon creation"; the Template review page adds that validation runs through "a combination of automated systems and manual reviews" and repeats the 24-hour figure for a decision. Neither page mentions partner status anywhere in the review process, and the categorization page, which describes how category is validated, does not mention it either. The one variable Meta's documentation does attach to templates is business verification, which governs how many templates you may hold (250 against 6,000), and which Infobip's documentation, not Meta's, associates with faster approval. None of the six Meta pages we read promises partners a faster template queue, we are not aware of one that does, and we would rather say that plainly than keep repeating a figure we cannot trace.

The measured figures in our corpus make the same point from the other side. Four reviews report approval times as things we timed: Manychat at 26 hours, Wati at 28 hours, Botpenguin at 56 hours and Typebot at 58 hours, the last two presented as slower than the BSP pair. All four are above Meta's published 24-hour ceiling, and Manychat and Wati both describe themselves as BSPs. Read literally, our own measurements say that the partner lane is slower than the queue Meta describes for everyone, which is not a finding anyone intended. The likelier readings are that the timings include steps other than template review (display-name approval, a first-time WhatsApp Business Account connection, or simply the gap between submission and someone checking), or that Meta's "up to 24 hours" is a typical figure rather than a ceiling. Our reviews do not record which, and this entry cannot settle it.

What survives the audit is narrower and more useful. Template review is automated with manual checks and, per Meta, decided within 24 hours. The things that reliably turn one cycle into two are the rejection reasons Meta's own Template review page lists: a body that starts or ends with a parameter ("dangling parameters are not allowed"), parameters that are not sequential, "too many variable parameters relative to the message length," special characters inside a parameter, a body and footer that duplicate an existing template's, content that asks for full card or ID numbers, and, from the categorization page, utility submissions with persuasive wording. Every one of those is checkable before submission, which is what our template approval predictor does, and a clean submission on a verified account is the fastest path we can document from Meta's own pages.

How to check a template's health yourself

Three requests, in order of how often you should make them.

1. Status and quality, daily on anything you send at volume. GET /<TEMPLATE_ID>?fields=status,quality_score returns the current status and a score of GREEN, YELLOW, RED or UNKNOWN with the date it last changed. A template that moved from GREEN to YELLOW this week is a template to edit before it is paused, not after.
2. Category drift, weekly. GET /<WHATSAPP_BUSINESS_ID>/message_templates?fields=category,correct_category lists every template with the category it has and the category Meta has decided it should have. A mismatch is a scheduled reprice.
3. Webhooks, always. Subscribe to message_template_status_update, message_template_quality_update and template_category_update. A one-day notice window is useless to a monthly poll.

If you are on a platform rather than the raw API, the question to ask the vendor is whether their template manager surfaces correct_category and quality changes, or only the approved/rejected state. Our WhatsApp channel guide tabulates the template managers of the platforms we cover and rates Wati's as the most extensive native authoring surface in that shortlist; none of those reviews recorded whether quality ratings and category drift are visible in the vendor UI, which is a gap our next refresh of each review should close.

Related terms

• WhatsApp Business API — the platform templates live on, the BSP model, and the history of conversation-based pricing.
• WhatsApp Flows — the in-chat form a template button can open, with its own publish-and-never-delete rule.
• Chatbot broadcast — the use case that consumes most marketing templates, and the opt-in rules around it.
• Confirmation message — the classic utility template when sent outside the window, and a plain message inside it.
• WhatsApp green tick — the verified-business badge; business verification is the variable that raises the template limit from 250 to 6,000.
• Webhook — the delivery mechanism for status, quality and category-change notifications.
• Click-to-WhatsApp ads — the ad format that can earn a 72-hour window in which templates of every category are free to deliver.

FAQ

What is a WhatsApp message template?

A pre-written, Meta-reviewed message with fixed text and variable placeholders that a business can send to a WhatsApp user at any time, including outside the 24-hour customer service window a user opens by messaging first. It is the only message type permitted outside that window, which makes it the mechanism behind every business-initiated WhatsApp message.

How long does WhatsApp template approval take?

Meta's documentation says review combines automated systems with manual checks and that a decision "can take up to 24 hours"; a partner's documentation adds that it is usually immediate for verified businesses. The four approval times our own reviews report as measured were 26, 28, 56 and 58 hours, all above that figure, and we discuss the discrepancy above rather than pick a side. Rejections, commonly for placeholder formatting and utility copy that reads as promotional, add a full resubmission cycle.

What are the three WhatsApp template categories?

Marketing (promotions, awareness, retargeting, and anything mixed or unclear), utility (non-promotional and either specific to the user's order, account or request, or essential to them), and authentication (one-time passcodes only, with a code button and no links, media or emoji). The category sets the per-message price.

What happens if I submit a marketing template as utility?

Since 9 April 2025, it is approved as marketing rather than rejected, and it sends at the marketing rate. Approved templates are also re-checked on a recurring basis, and a utility template later judged to be marketing is re-categorized with one day's notice, or none if the account has already been warned. The correct_category field shows the change before it lands.

Why was my WhatsApp template paused?

Its quality rating fell to RED on customer feedback: blocks, spam reports, or low read rates. The first pause is three hours, the second six, and the third disables the template permanently. Editing the content during a pause puts the edited version live within minutes, but Meta keeps tracking the block rate on it.

Are utility templates free on WhatsApp?

As of Meta's pricing page on 1 September 2026, a utility template delivered inside an open customer service window is free and one delivered outside it is charged at the market's utility rate. Partner write-ups report that from 1 October 2026 in-window utility templates become chargeable as well; we could not read Meta's own page on that change without a login and have flagged it for re-verification.

Do I need a Business Solution Provider to get templates approved faster?

We can find no Meta documentation that says so, and thirteen of our own reviews use the phrase anyway. Meta describes one review process, automated with manual checks and a 24-hour ceiling, and ties template capacity to business verification, not partner status. The reasons to use a BSP are onboarding, hosting, a template manager and support, which are real; a faster approval queue is not one we can document.

Sources

• Meta for Developers, WhatsApp Business Platform documentation, read 1 September 2026: Template fundamentals (page stamp 5 May 2026; names, categories, components, parameter formats, the "automatically reviewed upon creation" statement, the "can take up to 24 hours" ceiling, the 250 and 6,000 template limits, the 12-month archival rule and the 100-templates-per-hour creation limit); Template review (17 June 2026; "a combination of automated systems and manual reviews," "it can take up to 24 hours for an approval decision to be made," the 24-hour appeal decision, and the common rejection reasons quoted in the body: dangling and non-sequential parameters, too many parameters relative to length, special characters in parameters, duplicate body and footer, sensitive identifiers); Template categorization (30 January 2025; the two-part utility test, the five utility objectives, the 9 April 2025 approve-as-marketing rule, the 16 April 2025 no-notice rule for warned accounts, the recurring re-categorization process and the correct_category field); Template quality rating (17 June 2026; the GREEN/YELLOW/RED/UNKNOWN scale and the quality_score request); Template pacing (21 May 2026; the held-message mechanism, held_for_quality_assessment, error code 132015, the seven-day utility rule and the one-hour 99th-percentile guardrail); Pricing on the WhatsApp Business Platform (30 March 2026; per-message pricing effective 1 July 2025, free in-window utility templates, the 72-hour free entry point, the quarterly pricing calendar). Meta's Template pausing page and its page on non-template message pricing (the 1 October 2026 change) could not be rendered without a login and are not cited as read.
• Infobip, "Keep message templates compliant" (republished 18 March 2026), read 1 September 2026, for the pause schedule (3 hours, 6 hours, permanent) and the statement that approval "is usually immediate if your business is verified, but may take up to 24 hours otherwise." Used where Meta's pausing page could not be read, and marked as partner documentation in the body.
• ChakraHQ, "New WhatsApp API Pricing Update: Non-Template (Service) Messages Will Now Be Charged From October 2026" (2 July 2026), read 1 September 2026, for the partner-reported 1 October 2026 change to service and in-window utility pricing. Printed as partner-reported, not as Meta-verified.
• Chatbotscape review corpus (the fifteen platform reviews listed at /reviews), searched 1 September 2026 from the repository root. Denominator: ls sample-reviews/*-review.md | wc -l returns 15. The expedited-lane count is grep -liE 'BSP-expedited|expedited template' sample-reviews/*-review.md | wc -l, returning 13. The "5-7 days" count is grep -liE '5[-–]7 day' sample-reviews/*-review.md, returning six files: aisensy-review.md, botpress-review.md, manychat-review.md, tars-review.md, voiceflow-review.md, wati-review.md. The measured figures are quoted from manychat-review.md ("template approval completed in 26 hours versus 5-7 days reported by non-BSP integrators", with no source for the second figure), botpenguin-review.md ("56 hours versus BSP-certified platforms like Wati (28 hours measured) and Manychat (26 hours measured)", and in its body "template approval times typically run 48-72 hours versus BSP-expedited 24-48 hours"), typebot-review.md ("template approval completed in 58 hours — slower than Wati BSP 28h, Manychat 26h, Blip 22h") and wati-review.md (test-summary row "34 min setup; 28 hours BSP template approval"). The Blip projection is from blip-review.md ("~22 hours BSP template approval | Anchored vs Wati 28h + Manychat 26h"). The Chatfuel projection is quoted from chatfuel-review.md ("Anchored editorial assessment — pending 2026-06 measurement. WhatsApp BSP template approval completes in 28 hours"). The channel-guide phrasing is quoted from sample-reviews/channels/whatsapp-chatbot-guide.md ("24–48 hour template review versus 5–7 days for non-BSP"). The claim that Meta's documentation contains no partner variable in template review is an argument from absence across the six pages named above, and is stated that way in the body.
• Ahrefs Keywords Explorer, US overview and volume-by-country, queried 1 September 2026 — the demand, difficulty, CPC, global-volume, parent-topic and country-split figures in this entry's keyword note.
• Chatbotscape evaluation methodology, including the six-scenario protocol under which the Scenario C template timings were recorded. /methodology (continuously updated).