Keep campaigns live even if Meta pauses a template
Never-Stuck Sends with Template Variants What's New! Create a Variant Group: Combine multiple Meta-approved versions of the same WhatsApp template into one group. Auto-fallback: If the primary template is paused/disabled by Meta, QuickReply automatically sends using the next available approved variant. Utility-first logic: Utility variants are prioritized. If none exist, Marketing variants are selected (in order of creation). Works everywhere: Supports Broadcasts, Journeys, and Conversations. Clear visibility: View group-level status, variant counts, individual Meta statuses, and see which variant will be used at send time. How It Works Pick any approved template → click Add Variant to create a Variant Group. Edit Body and Footer (structure stays the same as the parent). Submit the new variant for Meta approval. When sending, QuickReply checks statuses in real time and automatically picks the best approved variant (Utility first, then Marketing; oldest timestamp among equals). If a chosen variant fails, QuickReply automatically switches to the next approved variant. Why It Matters Eliminate send interruptions when Meta pauses a template. Protects campaign performance (reach, CTR, conversions) with always-available approved backups. Reduces manual operational work — no more last-minute template swaps. Allows fast creative iteration while maintaining compliance-friendly structure. Things to Know Before Using It Structure must match the parent template: same header type, button layout, and number of variables. You can change Body and Footer only (variables must not exceed the parent’s count). Categories: variants can be Utility or Marketing; groups can be Mixed (clearly labeled). Preview shows the exact variant that would send right now, based on statuses and rules. Carousel variants are Marketing only. If all variants are rejected, sending falls back to standard behavior and you’ll see an alert, keep 2–3 approved variants for critical flows. For more details check our documentation.
How do you feel about this update?
