Build every Meta template type — with a real preview and a test harness.
A template builder that mirrors Meta's schema 1:1. UTILITY, MARKETING and AUTHENTICATION categories. Headers (text, image, video, document), positional and named variables, and every button type Meta supports — including catalog, single / multi-product, OTP, voice call and Flow.
Meta-parity builder: every category, sub-category, header, variable and button type Meta accepts.
Meta-parity builder
Build catalog, MPM, SPM, OTP, Flow and voice-call templates.
Pick a category (UTILITY / MARKETING / AUTHENTICATION) and sub-category (DEFAULT, CATALOGUE, FLOWS, ORDER_STATUS, ORDER_DETAILS, CALLING_PERMISSIONS, OTP). Add a header — text, image, video or document. Compose the body with positional `{{1}}` or named `{{name}}` variables. Attach any button type Meta supports.
- Categories: UTILITY, MARKETING, AUTHENTICATION
- Sub-categories incl. CATALOGUE, FLOWS, ORDER_STATUS, OTP
- Buttons: QUICK_REPLY, URL, PHONE_NUMBER, COPY_CODE, OTP, CATALOG, MPM, SPM, VOICE_CALL, FLOW
- Headers: text, image, video, document
Template builder
MarketingHeader
Body
Hey {{1}}, your order #{{2}} is on the way! Track it here:
Buttons
Hey Priya,
your order #4421 is on the way! Track it here:
Approved by Meta
Test harness
Verify the template before you submit it to Meta.
A built-in test-harness endpoint lets you fire the template at a test number with sample variables — see exactly what lands on the device before you submit it for Meta approval. Once submitted, status sync from Meta updates approval / rejection in the background.
- Test-harness endpoint to send a sample to your own number
- Status sync from Meta — approval / rejection reason surfaced
- Multi-language variants under one template family
- Audit log on every submit and update
Templates
48 active- Approved
order_dispatched_v3
Utility
- Approved
diwali_sale_2025
Marketing
- In review
cart_abandon_v2
Marketing
- Approved
otp_login
Authentication
- Rejected
shipment_delay
Utility
Library across every WBIZ surface
One template library — used by Inbox, Campaigns, Automations and API.
Templates are the canonical asset. Inbox sends them inline, Campaigns picks them as a broadcast asset, Automations fires them as send_template actions, and the public REST API exposes them via /v1/messages/template. Build once, reuse everywhere.
- Used by Inbox composer, Campaigns, Automations and REST API
- Status filter: pending / approved / rejected
- Submit + update audit log retained per template
- Same builder for every Meta button + header type
Templates
48 active- Approved
order_dispatched_v3
Utility
- Approved
diwali_sale_2025
Marketing
- In review
cart_abandon_v2
Marketing
- Approved
otp_login
Authentication
- Rejected
shipment_delay
Utility
By the numbers
What teams ship on WBIZ.
0
Categories: UTILITY / MARKETING / AUTH
0
Sub-categories incl. CATALOGUE, FLOWS, OTP
0
Button types incl. CATALOG, MPM, SPM, FLOW
0
Header types: text / image / video / document
Every approval audited. Every send accountable.
Templates are the most regulated surface area on WhatsApp. WBIZ keeps an audit-log entry on every submit and update, status syncs from Meta keep approval state fresh, and a test-harness endpoint catches mistakes before Meta does. Multi-language variants and Flow / catalog button types are first-class.
Test harness
Fire the draft template at a test number with sample variables before submitting to Meta.
Multi-language
A template family can carry variants in any Meta-supported language; status syncs per language.
Status sync from Meta
Approval / rejection state and rejection reason mirrored back into WBIZ in the background.
Submit + update audit
Every submit and update writes an audit entry — who, when, with which payload.
Plays nicely with
Connected to every WBIZ surface that sends.
Templates aren't a silo — they power Campaigns, Automations, the Inbox composer and the public REST API. Build once, reuse everywhere.
Campaigns
Pick approved templates as broadcast asset
Automations
send_template action from any trigger
Inbox
One-click send from the composer
REST API
POST /v1/messages/template
Meta sync
Status pulled from Meta in the background
Flows
FLOW button type opens a Flow inline
FAQ
Templates, answered.
All three Meta categories — UTILITY, MARKETING and AUTHENTICATION — plus the sub-categories Meta exposes (DEFAULT, CATALOGUE, FLOWS, ORDER_STATUS, ORDER_DETAILS, CALLING_PERMISSIONS, OTP).
WBIZ surfaces Meta's rejection reason on the template once status sync runs. Fix it in the builder, save a new version and resubmit.
Yes — the built-in test-harness endpoint sends the draft template to a test number with sample variables, so you can see exactly what lands on the device before kicking off Meta approval.
Every button type Meta accepts: QUICK_REPLY, URL, PHONE_NUMBER, COPY_CODE, OTP, CATALOG, MPM (multi-product message), SPM (single product), VOICE_CALL and FLOW.
Yes — every submit and update writes an audit-log entry with the actor, timestamp and payload, so compliance reviews are a query away.