WhatsApp Troubleshooting
WhatsApp Template Rejected or Reclassified as Marketing? What to Check
A rejection and a category change are different problems. Start with the actual status and message purpose before rewriting the copy.
You submit a reminder template and expect to use it tomorrow. Instead, the status changes to rejected—or the category is different from the one you selected. Editing random words and submitting again can turn a small problem into a confusing collection of almost identical templates.
When a WhatsApp template is rejected, start by recording the exact status, reason and version. The useful question is what the message actually does for its recipient, not which label would make it cheaper or easier to send.
Separate rejection from reclassification
A rejected template is not approved for use. A category change means the platform has classified its purpose differently. A paused or disabled template is another state again. Keep those distinctions in your troubleshooting note.
Capture the template name, language, submitted category, current category, body, header, footer, buttons and the feedback shown in WhatsApp Manager or your provider interface. Remove customer data from screenshots shared for support.
Read the whole message as the recipient
Ask why the recipient would receive it. Does it refer to a specific existing request or transaction? Does it introduce a promotion, recommendation or invitation? Does the button lead somewhere consistent with that purpose?
Mixed intent is a common reason to reconsider the category. A message that begins with an order update and ends with a promotional offer is no longer simply an order update. Removing one enthusiastic adjective does not change the underlying purpose.
| Draft pattern | What to review |
|---|---|
| Specific order information | Whether the reference and action are genuinely tied to that order. |
| Reminder plus discount | Whether the promotional content changes the message purpose. |
| Generic “important update” | Whether the recipient can understand what the message concerns. |
| Mostly variable placeholders | Whether the reviewer has enough fixed context and realistic samples. |
| Button with unrelated destination | Whether the link matches the stated action. |
Inspect structure as well as wording
Check that variables appear in the expected format and that sample values make sense. Read the message with realistic values inserted. A template can appear clear in the editor but become confusing when a missing product name or malformed date is substituted.
Check language, punctuation, button labels and destination URLs. If you include media, verify that the supplied sample matches the intended use. Avoid putting private customer information into review examples; fictional but realistic samples are sufficient for an internal review.
Choose a deliberate next action
- If there is a clear content or structure issue, correct it and record what changed.
- If the message’s purpose fits a different category, use the appropriate category rather than disguising the intent.
- If you believe the decision is mistaken, use the available review or support route with the exact template details.
- Wait for the actual status before scheduling a dependent workflow.
No wording formula can guarantee approval. Do not create a workflow that depends on a template merely because it was submitted successfully.
Approval is only one part of delivery
An approved template still needs the correct recipient, permission, variables and a working send path. If a message fails after approval, use our WhatsApp delivery troubleshooting guide. If you are unsure why a template is required, read the 24-hour window explanation.
Check Meta’s current messaging policy and the category guidance available in your template manager before submission. Platform rules and review outcomes can change.
Review the workflow that depends on the template
Discuss your template workflow with SHVYA. Bring a redacted draft, the visible status and the intended recipient event. The aim is to align the message, category and automation trigger—not to promise a particular review decision.