Skip to main content
Submit your template for review, check its approval status before sending, and monitor later changes to its availability.

​
From draft to usable template

Prepare the category, language, components, and variable examples before submitting. Meta reviews the content and can approve or reject it. While a template is in review, do not schedule a send that assumes it will become available by a fixed time. Check the result first.
English demonstration template listed with In review status.

A submitted template can appear as In review. Wait for its result before sending.

Dashboard labels and API values can differ. Use the documented status returned by the interface you integrate with, rather than matching a translated UI label.
Demonstration template with Active-Quality pending status after review.

After review, this demo shows Active-Quality pending. Review status and quality are separate.

​
If the template is rejected

Review the exact issue before changing the text:
  • Is the category consistent with the full message?
  • Are sample values present and understandable?
  • Are variables used in a supported way?
  • Does the message contain prohibited or misleading content?
  • Are button actions and destinations appropriate?
  • Does an authentication use case use an authentication template?
If you disagree with the decision, use the review or appeal option available for that template. Do not assume that an account-restriction appeal is the same workflow.

​
Correct the reason, not just the wording

Save the rejection reason with the template’s WABA, name, language, and revision. A decision for one language or revision should not be assumed to cover another.

​
Separate review state from runtime availability

A campaign can fail after template approval because of a recipient restriction, number state, missing send parameter, or later template pause. Diagnose the level involved:
  • Template review problem: the reusable content is not approved.
  • Template quality problem: feedback affects availability after sending starts.
  • Individual delivery problem: a particular recipient’s message fails.
  • Account problem: restrictions affect the sender or broader business assets.
Duplicating the template is not a general solution to the last three cases.

​
Category changes

Meta can categorize a template differently from the category you requested. Check the actual category before launching a campaign or estimating cost. If a transactional message includes a promotion, removing a few obvious sales words may not change its purpose. Rewrite the use case clearly or select marketing. After a category change, check pricing, segmentation, and any automation that selects templates by category.

​
Quality after approval

Approval and quality are separate. Customer feedback and engagement can affect a template after it begins sending. A quality-pending template is not the same as a template awaiting initial review. An active template with deteriorating quality may still be usable but needs attention before further rollout. See Quality and delivery controls for pacing, pausing, and recipient-level controls. Meta’s template fundamentals describe current lifecycle and archival behavior.

​
Edit and retire safely

Before editing, replacing, or deleting a template:
  1. Find campaigns, journeys, AI Agents, and API callers that reference it.
  2. Check whether the proposed edit requires another review.
  3. Confirm the new language, category, and required parameters.
  4. Test the replacement before changing scheduled workflows.
  5. Remove obsolete references only after the replacement is ready.
Keep a small internal register of template purpose, owner, triggering event, language, and dependent workflows. This makes it easier to retire unused templates without breaking a customer notification.

​
Manage in YCloud

Use Template management for console tasks or Manage templates with the API for integration work. When troubleshooting, include the WABA, template name, language, current status, and review reason. Never include customer verification codes or API keys in a support request.

​
Frequently asked questions

First inspect the send error. The campaign may reference a different language or WABA, an unavailable template, invalid variables, or a recipient/account restriction. Check the template’s current state at dispatch; a previous approval screenshot is not proof of current sendability. Review is relevant only if the error or current status requires it.
Do not use a replacement to evade quality enforcement. Identify the customer feedback and content or audience problem first. If you legitimately replace a template, wait for approval, test it, and update dependent references in Campaigns, Journeys, AI Agents, and APIs before retiring the old one.
No. Keep the platform’s actual category and the message-level pricing result. Review affected automations and budgets, and use Meta’s category-review route if you believe the classification is wrong. Changing an internal label does not change the upstream category or charge.