# FAQs

### Best Practices

* **Create at least 2–3 variants** per high-impact message (e.g., COD-to-Prepaid nudges, promotions) to hedge against Meta status swings.
* Keep **variables identical** across variants; only refine **copy** (synonyms, phrasing, CTA).
* Maintain a **Utility version** where eligible to take advantage of the priority logic.
* Review the group **status badges** before big sends; aim for **≥1 Approved** variant at all times.
* Use **“Clone as New Template”** if you need a standalone asset outside the group.

### FAQs

**Q: My variant keeps hitting variable limits.**\
A: The number of variables is dictated by the parent template. You can use **up to** that count—no more. Consider rewording to fit existing placeholders.

**Q: The wrong variant preview is showing.**\
A: Previews show the **active** variant based on current statuses and rules (Utility first, then Marketing, newest first). If statuses change, the preview updates accordingly.

**Q: Can I change buttons or header type in a variant?**\
A: No. Structure (header type, buttons, variable count) must match the parent. Only **Body** and **Footer** can change.

**Q: What if every variant gets rejected?**\
A: The group shows **Rejected**, an **alert** is raised, and the system reverts to standard retry/fallback behavior until an **Approved** variant exists again.