Why was my WhatsApp message template rejected by Meta? Explained
Discover the common reasons Meta rejects WhatsApp message templates and how to fix them for seamless omnichannel support.
When you set up a WhatsApp Business Account, the first step is often creating message templates that can be sent outside the 24‑hour customer‑care window. If Meta rejects a template, it can stall your omnichannel support flow and frustrate both agents and customers. Below is a concise guide to help you understand the policy framework and avoid common pitfalls.
Understanding Meta’s WhatsApp Template Policy
Meta requires every outbound template to comply with a set of clear, safety‑first rules. The policy is designed to protect users from spam, misinformation and unwanted commercial content. Templates are evaluated on three core criteria: relevance, format and compliance with legal standards.
Relevance means the template must be directly linked to a prior user‑initiated interaction. For example, a shipping update is acceptable after a purchase, but a generic promotional offer sent without a recent conversation is not. Meta’s system checks the context by matching the template’s purpose with the most recent inbound message from the same user.
Format refers to the structural elements of the template. Each template must contain a clear header, body and optional footer, and placeholders (e.g., {{1}}, {{2}}) must be used consistently. The body cannot exceed 1024 characters, and the total number of placeholders is limited to ten. Meta also enforces language‑specific rules; a template written in English must be submitted in English, and any mixed‑language content will be flagged.
Compliance covers legal and regulatory requirements. Templates must not contain any of the following:
Prohibited content such as hate speech, adult material or illegal services.
Misleading claims, including unverified health advice or financial promises.
Requests for personal data that are not essential to the service (e.g., asking for a passport number in a delivery confirmation).
The table below summarises the key policy dimensions and the typical outcomes of a review.
Policy Dimension
What Meta Checks
Typical Reason for Rejection
Relevance
Link to prior user message
Template sent without recent user interaction
Format
Header, body, footer, placeholder count
Exceeds character limit or mismatched placeholders
Compliance
Prohibited content, legal claims, data requests
Contains promotional language or disallowed data fields
Understanding these pillars helps you craft templates that pass the automated review and, if needed, the manual audit performed by Meta’s compliance team.
Common Reasons for Template Rejection
Even with a solid grasp of the policy, many users encounter rejections because of subtle oversights. Below are the most frequently observed issues, illustrated with practical examples you can avoid.
1. Vague or Generic Messaging
Templates that read like mass marketing – for instance, “Hello! Check out our latest offers now!” – are rejected for lacking a specific transactional or service‑related purpose. Instead, tie the message to a concrete event: “Your order #{{1}} has been dispatched and will arrive on {{2}}.”
2. Improper Placeholder Usage
Placeholders must be numbered sequentially and used consistently throughout the template. A common mistake is mixing numbered and named placeholders or leaving a placeholder empty. Meta’s system flags any mismatch, resulting in a “Placeholder error” rejection.
3. Exceeding Character Limits
The body of a template is limited to 1024 characters. Long legal disclosures or extensive product descriptions often push the limit. Trim non‑essential text or move detailed information to a linked web page, keeping the WhatsApp message concise.
4. Inclusion of Unapproved Media
While images, PDFs and videos can be attached to templates, they must be pre‑approved and hosted on a secure URL. Using copyrighted material without permission or embedding promotional graphics will trigger a rejection.
5. Requesting Sensitive Personal Data
Templates that ask for data such as credit card numbers, social security identifiers or passport details are automatically blocked unless the request is part of a verified financial service and complies with local regulations. Re‑phrase to request the data via a secure web form instead.
6. Language and Spelling Errors
Meta’s review includes a basic language check. Templates riddled with spelling mistakes or mixed‑language fragments are often rejected for poor quality. Proofread carefully and use the language settings that match your target audience.
By auditing your templates against these points before submission, you can dramatically reduce the turnaround time for approval and keep your omnichannel support running smoothly.
How to Craft a compliant Message Template
WhatsApp message templates must adhere strictly to Meta’s policy framework. The first step is to understand the core categories that are permitted: customer support, notifications, and marketing, each with its own set of rules. Templates are written in a plain‑text format that includes placeholders for dynamic variables, surrounded by curly braces. For example: “Hello {{1}}, your order {{2}} is ready for collection.”
When drafting, keep the following principles in mind:
Relevance and Necessity – The template must provide genuine value to the recipient and cannot be purely promotional.
Clarity and Brevity – Use straightforward language; avoid ambiguous or sensational phrasing.
User Consent – The recipient must have opted in to receive messages from your business via the official opt‑in flow.
Accurate Placeholders – Each placeholder must correspond to a valid field supplied at send‑time, and the data should not reveal sensitive information unless absolutely required.
Formatting Rules – Do not include URLs, phone numbers, or non‑alphabetic characters outside of placeholders.
Meta’s template review also evaluates the business’s compliance record. If previous templates were rejected, the new submission is scrutinised more closely. Maintaining a clean history of compliant templates helps streamline future approvals. Finally, test your template in the WhatsApp Business Manager’s “Template Preview” tool; any flagged content will be highlighted for correction before you hit submit.
The Review Process: What Happens After Submission
Once a template is submitted, Meta initiates an automated pre‑screening to catch obvious violations such as prohibited content or formatting errors. If the pre‑screen passes, the template enters the human review queue, where a Meta policy officer checks for adherence to the full policy set.
The review process typically takes anywhere from a few hours to several business days. During this window, the officer verifies:
The template’s category matches the intended use (e.g., support vs. marketing).
All placeholders are legitimate and will not expose private data.
No prohibited language or imagery is present.
The business’s opt‑in status and data handling practices are compliant.
If the template is approved, you will receive a status update in the Business Manager and the template will become available for scheduling. If rejected, Meta will provide a brief explanation, often citing the specific policy section violated. Common rejection reasons include “template contains promotional content” or “template references a URL.”
After a rejection, you can amend the template and resubmit. Meta advises that resubmissions should address all flagged issues; otherwise, repeated failures may lead to a longer review cycle or, in extreme cases, suspension of the business’s WhatsApp access. Staying transparent with your team about the exact rejection rationale and documenting the changes you make helps ensure that the next submission aligns with Meta’s expectations.
Steps to Appeal a Rejected Template
When Meta’s WhatsApp Business API rejects a message template, it usually points to a single compliance issue. Follow these systematic steps to submit a clean appeal:
Identify the exact reason. Log in to your WhatsApp Business Manager, open the Templates section and click the rejected template. Meta lists the violation – whether it’s prohibited content, incorrect formatting, or an outdated tag.
Correct the violation. If the template contains non‑business language, remove slang or promotional phrases. Replace any <quick_reply> tags that exceed the character limit with shorter options, or swap them for <button> elements that fit the policy.
Re‑upload the corrected version. In the template editor, click “Add a new template”, paste the revised text and choose the appropriate category. Meta’s UI will automatically flag remaining issues before submission.
Submit for review. Once the editor reports “Ready for review”, click the review button. Meta typically processes the request within 24–48 hours. Keep the original name and category to preserve the template’s context.
Track the status. The template’s status will change from “Under Review” to either “Approved” or “Rejected” again. If it’s rejected again, review the new feedback, make further adjustments, and repeat the cycle.
Document the changes. Store a copy of the final approved template in your internal knowledge base, noting the approval date and any policy references. This audit trail is useful for future onboarding and troubleshooting.
Remember, each appeal must be a genuine improvement. Meta’s algorithm detects repeated attempts that simply rename or slightly tweak a template; these will be fast‑tracked as violations and may result in a permanent block.
Word count: 354
Best Practices to Avoid Future Rejections
Preventing template rejection starts with a clear understanding of Meta’s content policy and a disciplined development workflow. Implement the following practices to keep your templates compliant and reduce the need for appeals.
Use approved template categories. Meta limits templates to predefined categories (e.g., Order Updates, Appointment Reminders). Stick to one category per template to avoid category‑mixing penalties.
Limit character count and placeholders. Each line may contain a maximum of 1,200 characters and only one placeholder per line. Over‑loading a line with variables can trigger rejection.
Avoid promotional language. Templates must be purely transactional or informational. Phrases like “Buy now” or “Limited time offer” are disallowed.
Validate quick replies. Quick replies can have a maximum of 20 characters and must not exceed five per template. Use the “quick_reply” tag only for user‑directed actions, not for marketing.
Test locally before submission. Use OmniDesk’s built‑in template validator to flag syntax errors, missing tags, or disallowed characters. This step catches errors that Meta’s system might miss.
Maintain version control. Keep a versioned log of every template change. If Meta rejects a version, you can roll back to the last approved copy without re‑creating from scratch.
Keep an up‑to‑date policy reference. Meta periodically updates its content guidelines. Subscribe to the WhatsApp Business API changelog or community forums to stay ahead of policy shifts.
Request pre‑approval for high‑risk content. If your business requires a unique template that borders on policy limits, contact Meta’s support for a provisional approval before publishing.
Educate your team. Run quarterly workshops on WhatsApp policy for marketers, developers, and customer support agents. The fewer misconceptions, the fewer rejections.
By integrating these practices into your template lifecycle, you can minimise rejection risk, reduce support overhead, and deliver consistent, compliant communication to your customers.
Word count: 388
Verdict: Ensuring Your Templates Get Approved
WhatsApp template approval is not a gamble – it is a carefully regulated process designed to keep the platform safe, professional and useful for all users. A rejected template usually signals that one or more of Meta’s guidelines have not been fully satisfied. By following a systematic approach, you can avoid common pitfalls, streamline your submissions and significantly increase the likelihood of approval.
Meta’s template review policy emphasises three key pillars: relevance, clarity and compliance. Relevance ensures the content speaks directly to the user’s intent, clarity guarantees that the message is concise and unambiguous, while compliance checks that no disallowed content or promotional language is used. When you map your template against these pillars, you create a safety net against rejection.
The first step is to analyse your audience. Your template must be tailored to the user’s journey – for example, a support ticket update, a delivery notification or a loyalty reward. Avoid generic copy that could be perceived as spam. Next, craft precise language; use plain English, keep sentences short, and eliminate unnecessary qualifiers. Meta favours direct, actionable statements such as “Your order #1234 has shipped” over vague wording.
Compliance is the final gatekeeper. Ensure that the template does not contain any prohibited topics such as political content, financial advice or adult material. Additionally, use only the placeholders that WhatsApp explicitly supports (for example, {{1}}, {{2}}) and confirm that they are correctly positioned. Avoid using placeholders that could result in ambiguous or misleading information.
Before you submit, run a quick self‑audit using the checklist below. It captures the most common reasons for rejection and helps you verify that each element is in order. Completing this checklist will give you confidence that your template meets Meta’s high standards and is ready for a smooth approval process.
✔ The template’s intent matches the user’s request or interaction.
✔ All sentences are clear, concise and free of promotional content.
✔ The template uses only allowed placeholders and they are correctly formatted.
✔ No disallowed topics (politics, finance, adult content) are present.
✔ The language is fully in English (or the language specified for the audience).
✔ The template includes a single, actionable call‑to‑action and no more than two short paragraphs.
By adhering to these principles, you transform your template creation process from a trial‑and‑error endeavour into a predictable, repeatable workflow that consistently gains Meta’s approval. Remember: every rejected template is a learning opportunity – use the feedback, refine your approach, and iterate. With a disciplined, compliance‑driven strategy, you can minimise rejections and maximise the impact of your omnichannel support on WhatsApp.
Frequently Asked Questions
What are the main criteria Meta uses to approve WhatsApp templates?
Meta checks that templates are clear, non‑promotional, and respect user privacy. They must follow the prescribed structure and avoid prohibited content.
Can I use emojis or special characters in a WhatsApp template?
Emojis are allowed only if they add meaning and are not used excessively. Overuse or decorative symbols often trigger rejection.
How long does the review of a WhatsApp template usually take?
Review typically completes within 24 hours, but complex templates may take up to 48 hours.
What should I do if my template is rejected for “policy violation”?
Review the rejection reason, adjust the wording to remove the flagged content, and resubmit. If unclear, use Meta’s appeal form for clarification.
Is it possible to reuse a previously approved template after making minor edits?
Minor edits still require a fresh review. Even small changes can affect compliance, so submit the revised version for approval.
Frequently Asked Questions
What are the main criteria Meta uses to approve WhatsApp templates?
Meta checks that templates are clear, non‑promotional, and respect user privacy. They must follow the prescribed structure and avoid prohibited content.
Can I use emojis or special characters in a WhatsApp template?
Emojis are allowed only if they add meaning and are not used excessively. Overuse or decorative symbols often trigger rejection.
How long does the review of a WhatsApp template usually take?
Review typically completes within 24 hours, but complex templates may take up to 48 hours.
What should I do if my template is rejected for “policy violation”?
Review the rejection reason, adjust the wording to remove the flagged content, and resubmit. If unclear, use Meta’s appeal form for clarification.
Is it possible to reuse a previously approved template after making minor edits?
Minor edits still require a fresh review. Even small changes can affect compliance, so submit the revised version for approval.
The page_welcome_message payload takes a fixed envelope — type of "VISUAL_EDITOR", version of 2, landing_screen_type of "welcome_message" and media_type of "text" — with the interesting part nested inside text_format:
Meta also exposes welcome message sequences as reusable objects. You POST a sequence to the welcome_message_sequences endpoint, get an ID back, and reference that ID from the creative in either the Marketing API or Ads Manager. A sequence bundles an introductory text message, an autofill message and ice breakers. Creating them requires the whatsapp_business_management permission.
One constraint to design around: a sequence linked to an active ad cannot be deleted or modified. You have to disconnect it from every ad first. In practice that means versioning sequences rather than editing them — create consultation-v2, point new ads at it, retire consultation-v1 once its ads stop.
The Welcome Message Is the Highest-Leverage Field
The value you pass in customer_action_type decides how much structured intent reaches your inbox before a human reads anything. Meta supports four:
autofill_message — pre-fills the user's input box with a fixed string; they just tap send. Every lead from that ad arrives with identical text, which makes exact-match routing trivial. It captures nothing beyond "this person tapped this ad".
ice_breakers — renders tappable prompts such as "Book a viewing", "Request pricing" or "Talk to sales". Meta caps these at three quick-reply options. Each sends its own payload, so the first inbound message already tells you which branch the prospect chose.
whatsapp_flow — opens an interactive multi-step form inside WhatsApp before the first message is sent. This is how you collect an email, a budget band or a preferred slot without an agent having to ask.
ctwa_call_prompt — surfaces a call prompt alongside messaging. Remember the objective constraint: this one requires OUTCOME_ENGAGEMENT.
The trade-off is friction against context. An autofill message maximises how many people send something and minimises what you learn about them. A Flow does the reverse. Our default for a sales-led desk is ice breakers: three options is enough to branch on, and tapping a button costs the prospect nothing. Whichever you pick, the payload it produces is what lets you assign WhatsApp chats to the right agent automatically instead of letting the fastest agent cherry-pick the queue.
The 72-Hour Free Window Nobody Prices In
This is the part of click-to-chat ads that changes the maths, and it is routinely misunderstood. There are two windows, they run on independent timers, and one of them is free.
When a user messages you via a click-to-WhatsApp ad, a 24-hour customer service window opens, exactly as it would for any inbound message. Facebook Page call-to-action buttons behave the same way, though Meta notes that entry point applies to the Android and iOS apps only.
Here is the part that matters. If you respond inside that window with any message type, a separate free entry point window opens, and it lasts 72 hours from your response. Meta's wording on what you can send during it is unambiguous: while open, you can send any type of message to the user at no charge. Any category. Marketing templates included.
The two windows do not move together. Once the 24-hour customer service window closes, you are back to templates only — but if the free entry point window is still running, those templates are still free. So a prospect who taps your ad on Monday morning and gets a reply within the hour can be re-engaged with a marketing template on Wednesday morning at no Meta charge, long after free-form replies have stopped being available.
Two consequences follow for anyone budgeting click-to-chat ads. First, response speed is not only a conversion lever, it is a cost lever: replying inside 24 hours is what buys the 72 free hours. A campaign that runs while nobody is watching the inbox pays full rate for every follow-up. Second, your follow-up cadence should be built around the 72-hour boundary rather than around a generic day-one, day-three, day-seven schedule. This is where SLA timers stop being a support-quality metric and start showing up in the media budget, which is why we wire them into routing rules in OmniDesk rather than leaving them to agent discipline.
Two related pricing facts are worth stating plainly, because both are widely misreported:
Utility templates sent inside an open customer service window are free. Meta's documentation says so directly, and the webhook confirms it — those messages come back with type of free_customer_service, category of utility and billable set to false.
There is no change on 1 October 2026 that makes service messages billable. You will find this claim on a lot of comparison pages. Meta's updates-to-pricing documentation lists only rate-card moves for that date — lower rates for Bangladesh, Iraq, Nepal and Sri Lanka, higher rates for Kazakhstan, Kuwait, Morocco, Oman and Ukraine, plus billing localisation in Brazil. Service conversations have been free for all businesses since 1 November 2024 and remain so.
For context on the surrounding model: on 1 July 2025 Meta replaced conversation-based pricing with per-message pricing, so marketing, utility and authentication templates sent outside a free window are billed individually by delivery, destination country calling code and volume tier. Our breakdown of WhatsApp Business API pricing goes through how those layers stack.
The Referral Object: What Arrives With the First Message
When someone taps your ad and sends their first message, the WhatsApp Cloud API attaches a referral object to that inbound message on your webhook. This is the attribution data for click-to-chat ads, and it is the raw material for every routing rule in the next section.
Two properties of it drive the engineering. It arrives only on the first message. Meta generates ctwa_clid at the moment of the tap and attaches it to the referral object of that first inbound message; subsequent messages in the same thread carry nothing. If you do not persist it on arrival, it is gone. And users may elect to remove their referral data, so referral can be absent entirely. Any handler that assumes the key exists will throw on a real, legitimate message.
The object carries source_url, source_id, source_type, headline, body, media_type, image_url, video_url, thumbnail_url and ctwa_clid. What each is worth operationally:
Referral field
What it holds
Routing decision it enables
source_id
The ad ID
The primary routing key. Map ad IDs to teams, queues or owners so a lead is assigned before anyone opens the thread.
source_type
"ad" or "post"
Separate paid traffic from organic post traffic and apply a tighter SLA to the traffic you are paying for.
source_url
The ad or post URL on Facebook
Give the agent a one-click link to the exact creative the prospect saw.
headline
The ad headline you set as name
Keyword routing without maintaining an ad-ID table — match on the words you already wrote into the creative.
body
The ad's primary copy
Secondary tagging: offer, promotion or product line mentioned in the ad.
media_type
The creative's media type
Creative-format performance analysis once you join it to conversion outcomes.
image_url / video_url / thumbnail_url
The creative asset
Render the ad the prospect tapped inside the agent's conversation view, so the first reply can reference it accurately.
ctwa_clid
An opaque click identifier
The attribution key. Store it on the contact and send it back through the Conversions API when the lead converts.
Automated Lead Routing Built on Referral Data
Referral metadata is only worth capturing if something acts on it within seconds. Four patterns cover most of what click-to-chat ads demand of a growth or support team.
Route by source_id
The cleanest rule: match the inbound ad ID against a table of active campaigns and assign the thread accordingly. Enterprise campaign to the enterprise pod, consumer promotion to tier-one support, high-budget campaigns to your closers. Teams running one campaign per property or per product line use this to bind a lead to its owner before an agent has read a word — the pattern behind WhatsApp lead follow-ups for real estate.
Route on headline and body text
Maintaining an ad-ID table gets painful when you are testing dozens of creatives a week. The cheaper approach is to match on strings you already control: put a token in the headline and route on it. Headlines containing "Enterprise" or "Commercial" get a high-priority tag and a tight response SLA; headlines containing "Clearance" go to the promotions queue. It is the same mechanism that lets a small team manage 500 WhatsApp prospects without losing a lead during a spike, because the queue sorts itself.
Bot-first triage with a clean handoff
When volume outruns headcount, an automation should acknowledge every ad-sourced thread immediately, referencing the specific headline so the reply does not read as generic. It asks the two or three qualifying questions your team would ask anyway, then hands over with an internal summary note attached. The failure mode to design against is a bot that will not let go; our notes on chatbot-to-human handoff cover the escape hatches that matter. Remember that the bot's reply is also what opens the 72-hour free window, so this pattern pays for itself twice.
Persist ctwa_clid on the contact record
Write it to a dedicated field on first contact, and make it read-only. It is the only bridge between a WhatsApp conversation and the ad that produced it, and it arrives exactly once. A deal that closes forty-five days later is still attributable if the field survived; it is unattributable if an agent overwrote it. Locking system fields against manual editing is one of the less glamorous shared inbox best practices, and one of the few that has a directly measurable cost when skipped.
Closing the Loop With the Conversions API
Without conversion signal, Meta optimises click-to-chat ads for conversations started. You will get cheaper conversations and, frequently, worse ones. Sending qualification and purchase events back through the Conversions API is what moves the auction from volume to value.
Meta runs a specific variant for this, Conversions API for Business Messaging, and its requirements are narrow enough to get wrong:
action_source is "business_messaging" — a fixed value across all messaging channels. Not "chat", not "other".
messaging_channel is "whatsapp" (the same field takes "messenger" or "instagram" for the other surfaces).
For WhatsApp, user_data must carry whatsapp_business_account_id and ctwa_clid.
ctwa_clid must not be hashed. Meta's parameter reference marks it "Do not hash" explicitly. Email and phone still require SHA-256; this field is the exception, and a pipeline that hashes everything in user_data by default will silently break attribution.
Non-web events require only action_source — you do not need client_user_agent or event_source_url, which web events do require.
Supported event_name values include Purchase, LeadSubmitted, QualifiedLead, InitiateCheckout, AddToCart, ViewContent, OrderCreated, OrderShipped, OrderDelivered, OrderCanceled, OrderReturned, CartAbandoned, RatingProvided and ReviewProvided. For a sales desk, QualifiedLead fired when an agent marks a thread qualified is usually the highest-signal event you can send early enough to be useful.
One operational warning from Meta's own guidance: Meta does not deduplicate these events for you, and explicitly encourages advertisers to deduplicate before sending. If both your inbox automation and your CRM can mark a deal won, decide now which one owns the event, or you will train the auction on inflated conversion counts.
A Pre-Launch Checklist for Click-to-Chat Ads
Objective matches the creative. One of the four permitted values, and strictly OUTCOME_ENGAGEMENT if the creative uses ctwa_call_prompt.
Destination is set and live.destination_type of "WHATSAPP", pointed at a number someone is actually watching.
Welcome message matches your intent-capture goal. Autofill for volume, ice breakers for branching, Flow for structured data. Sequences versioned rather than edited, since a sequence attached to a live ad cannot be changed.
Webhook handles a missing referral key. Users can strip it. Test that path deliberately rather than discovering it in production.
ctwa_clid is persisted on first message, unhashed, and write-protected. It never arrives twice.
Someone replies inside 24 hours, always. That reply opens the 72-hour free entry point window. Set the SLA timer to something well short of it and alert on breach.
Follow-up cadence is built around the 72-hour boundary, not around a generic drip schedule.
Templates for post-window re-engagement are approved before launch. Approval is Meta's decision and takes as long as it takes — see WhatsApp message template approval. A WhatsApp Business Account holds a maximum of 250 templates, so prune before you add.
Conversions API events fire with business_messaging, whatsapp and an unhashed ctwa_clid — and exactly one system owns each event.
None of this is exotic. Click-to-chat ads come down to a handful of fields, two windows and one identifier. But the gap between a click-to-chat campaign that reports well and one that quietly loses its attribution is almost entirely in this list, and most of it has to be right before the first impression is served rather than after.
Want every ad-sourced lead routed, tagged and timed before an agent opens it?
WhatsApp click-to-chat ads are Meta ad units whose call-to-action opens a WhatsApp thread with your business instead of loading a landing page. Meta calls the format ads that click to WhatsApp, usually shortened to CTWA. The prospect taps the ad, WhatsApp opens with a welcome message you configured, and their first message arrives on your webhook carrying a referral object that identifies the exact ad, headline and click. That referral payload is what makes click-to-chat ads routable: you can assign the conversation to the right team before an agent has read it.
Which campaign objectives can I use for click-to-chat ads?
Meta permits four objectives for WhatsApp-destination campaigns: OUTCOME_ENGAGEMENT, OUTCOME_LEADS, OUTCOME_SALES and OUTCOME_TRAFFIC. One rule is absolute rather than advisory: if your creative uses a call prompt, the objective must be OUTCOME_ENGAGEMENT. Decide whether you want call prompts before you build the campaign structure, because that choice constrains everything above it. Beyond that constraint Meta does not publish a decision matrix, so which of the four suits your click-to-chat ads is a question to test rather than to look up.
Are messages free after someone clicks a WhatsApp ad?
Partly, and the mechanism is worth learning because it is where click-to-chat ads stop behaving like ordinary paid traffic. A user messaging you from a click-to-WhatsApp ad opens the usual 24-hour customer service window. If you respond inside that window with any message type, a separate free entry point window opens and runs for 72 hours from your response. Meta states that while it is open you can send any type of message to that user at no charge, marketing templates included. The two windows run on independent timers, so once the 24-hour window closes you are limited to templates, but those templates stay free while the 72-hour window is still open.
Is it true that WhatsApp service messages stop being free in October 2026?
No. This claim circulates widely and Meta's own documentation contradicts it. Service conversations became free for all businesses on 1 November 2024 and remain free, and Meta's pricing documentation still states that utility templates delivered inside an open customer service window are free. What Meta actually documents for 1 October 2026 is a set of rate-card moves: lower rates for Bangladesh, Iraq, Nepal and Sri Lanka, higher rates for Kazakhstan, Kuwait, Morocco, Oman and Ukraine, plus billing localisation in Brazil. That is a change to what things cost, not to what is billable.
What is ctwa_clid and how do I use it?
ctwa_clid is the Click to WhatsApp ID. Meta generates it at the moment a prospect taps your ad and attaches it to the referral object on that prospect's first inbound message only, so if you do not persist it on arrival it is gone. Store it on the contact record as a write-protected field, then send it back through the Conversions API when the lead converts. Two rules trip people up: it must never be hashed, even though email and phone in the same user_data object must be SHA-256 hashed, and for WhatsApp you must send whatsapp_business_account_id alongside it.
How do I route leads from click-to-chat ads automatically?
Route click-to-chat ads on the referral object that arrives with the first message. The cleanest key is source_id, the ad ID, matched against a table of active campaigns so each ad assigns to a specific team or owner. When you are testing many creatives, matching on the headline or body text is cheaper to maintain, because you control those strings when you write the ad. source_type tells you whether the traffic was an ad or an organic post, which lets you apply a tighter SLA to traffic you are paying for. Build the rules so they fire on message arrival, not on agent pickup, or click-to-chat ads will keep arriving faster than anyone can triage them.
What Conversions API settings do click-to-chat ads need?
Meta runs a specific variant called Conversions API for Business Messaging. Set action_source to business_messaging, a fixed value across all messaging channels, and messaging_channel to whatsapp. For WhatsApp, user_data must carry whatsapp_business_account_id and an unhashed ctwa_clid. Non-web events require only action_source, unlike web events which also need client_user_agent and event_source_url. Supported event names include Purchase, LeadSubmitted and QualifiedLead. Meta does not deduplicate these events for you and asks advertisers to deduplicate before sending, so decide which single system owns each event.
Can I change a welcome message sequence after the ad is live?
No. Meta states that a sequence linked to an active ad cannot be deleted or modified, and you must disconnect it from every ad before making changes. The practical answer is to version sequences rather than edit them: create a new sequence, point new ads at it, and retire the old one when its ads stop running. Sequences themselves are reusable objects you POST to the welcome_message_sequences endpoint, which returns an ID you reference from the creative in either Ads Manager or the Marketing API. Creating them requires the whatsapp_business_management permission.
One inbox. Every channel. No per-message platform fee.
Join 500+ businesses using OmniDesk to manage WhatsApp, Instagram, Telegram and live chat — with live translation, routing and SLA tracking included on every plan.
