> For the complete documentation index, see [llms.txt](https://docs.quickreply.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.quickreply.ai/product-modules/templates/whatsapp-templates/template-variants/faqs.md).

# 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.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.quickreply.ai/product-modules/templates/whatsapp-templates/template-variants/faqs.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.