Create Meta-approved templates without leaving the dashboard.
Visual editor for headers, bodies, footers, and all four button types. Variable insertion with one click. Send a test to your own number before you broadcast.
Visual editor
Real-time WhatsApp-style preview. See exactly what the delivered message will look like as you type.
All button types
Quick Reply, Website URL, Phone Number, and Copy Code — built with mix-rule validation per Meta spec.
Variable assistant
Click to insert. Auto-sequential numbering. Example values required by Meta surface inline as you add variables.
Send test to any number
Dispatches to your own WhatsApp before going live. The test message appears in inbox flagged, with delivery status tracked.
Live sync with Meta
Templates created, approved, paused, or disabled at Meta's end update in WapiSnap automatically. Your flow builder and broadcast composer always see the current list — no stale cache.
- Full approval-status badges in the template list
- Language variants tracked separately
- Failed submissions show Meta's rejection reason verbatim
Mix-rule validation built in
Meta's button rules are unintuitive — up to 10 Quick Reply, up to 2 URL, 1 Phone, 1 Copy Code. WapiSnap enforces them at the edit step so you find out now, not after a failed submission.
Template health, classified for you
WapiSnap watches the last 14 days of broadcasts per template and flags problems before you spam your audience again. Failure rate, frequency-cap dominance, audience overlap with the next scheduled send, Meta's own quality_score — all rolled into a single GREEN / YELLOW / RED indicator on the templates table. Click for the full breakdown and the recommended corrective action.
- Static thresholds: ≥25% failure rate → YELLOW, ≥50% → RED
- Trend detection — catches rates climbing 1.5× over 2 sends
- Meta quality_score override — RED on Meta = RED in WapiSnap
- Recommendation: pause N days, prune audience, or replace template
Archive stale templates locally
Old or replaced templates linger in Meta's list forever. Archive them in WapiSnap and they vanish from broadcast and CSV pickers — no risk of an operator picking the wrong one by mistake. Pure local state, fully reversible. Running flows that reference the template by name continue to send (we never silently break in-flight automations).
- Workspace-scoped — archive in one workspace, others unaffected
- Confirm dialog on archive · one-click unarchive
- Server-side guard rejects archived templates from broadcast creation
- Default-hidden in the table; toggle "Show N archived" to see them
Frequently asked questions
Can I create templates without going to Meta Business Manager?+
Yes. Build, preview, and submit templates directly in WapiSnap. We forward the submission to Meta; approval status is fetched live and shown in your dashboard.
What button types are supported?+
Quick Reply (up to 3), Website URL, Phone Number, and Copy Code. Create them visually — no JSON, no guessing at Meta's component structure.
How do variables work?+
Use {{1}}, {{2}} in headers, body, and URL buttons. The editor detects them automatically and asks for example values that Meta uses during review. One-click "Add variable" button inserts the next placeholder at your cursor.
Can I test a template before using it in a broadcast?+
Yes. Every template has a "Send Test" action — dispatches the template to any phone number with your chosen variable values. The test message lands in your inbox flagged as a test so you can see exactly what your customer will receive.
What if Meta rejects my template?+
The rejection reason surfaces in your dashboard with Meta's exact message. Edit, fix, and resubmit — no copy-pasting error codes from Meta's UI.
How does template health classification work?+
WapiSnap aggregates the last 14 days of completed broadcasts per template and applies static thresholds: ≥50% failure rate is RED, ≥25% is YELLOW. We also factor in Meta's own quality_score, the workspace circuit breaker, and frequency-cap dominance in the failure mix. Click the indicator on the templates table to see the failure breakdown, retry effectiveness, audience overlap with the next scheduled send, and the recommended action.
What does archiving a template do?+
Archiving hides the template from broadcast and CSV pickers in this workspace so it can't be selected by mistake. It's pure local state — Meta is unaware, no Meta-side change. Reversible from the same page. Running flows that already reference the template by name continue to send, so archiving doesn't break in-flight automations. The broadcast API also rejects archived templates server-side as a defense-in-depth check.
Your WhatsApp. Your AI. Your rules.
Join businesses automating WhatsApp without vendor lock-in.