> ## Documentation Index > Fetch the complete documentation index at: https://docs.ycloud.com/llms.txt > Use this file to discover all available pages before exploring further. # Template review and lifecycle > Follow template review, approval, category changes, quality controls, and retirement before sending. 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. | State or event | Meaning for your workflow | | - | - | | Draft in your editor | Work is not yet approved for sending. | | Pending or in review | Wait for a review outcome. | | Approved or active | The template can be eligible for sending; recipient and account checks still apply. | | Rejected | Review the reason and correct the issue, or use the available review route if you disagree. | | Paused | Stop new sends using the template until its status permits them. | | Disabled | Do not continue scheduling it as an available template. | | Archived or deleted | Check availability before reuse; an old saved reference is not sufficient. | 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. ## 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 | Review issue | A useful correction | An ineffective response | | - | - | - | | Utility template contains a promotion | Remove the promotional purpose entirely, or submit as marketing. | Replace “discount” with “benefit” while keeping the same offer. | | Review examples are missing | Add realistic sample values for every required variable or media field. | Submit empty or meaningless placeholders again. | | Purpose is hidden in variables | Put the stable business event and context in the fixed text. | Replace most of the body with one large variable. | | Authentication submitted under another category | Use an authentication template and its required format. | Rename the template “notification” while still sending login codes. | | Invalid button configuration | Correct the count, grouping, subtype, or destination. | Keep the same components and change only the visible label. | 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](/en/documentation/whatsapp-business-platform/pricing-limits-and-quality/quality-and-delivery-controls) for pacing, pausing, and recipient-level controls. Meta's [template fundamentals](https://developers.facebook.com/docs/whatsapp/business-management-api/message-templates/) 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](/en/documentation/channels/whatsapp-accounts-management/template-management/create-template/index) for console tasks or [Manage templates with the API](/en/api-reference/guides/whatsapp-platform/manage-whatsapp-templates) 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. This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.