Build every WhatsApp template type, with a real preview and a test harness.
A template builder that mirrors the WhatsApp schema exactly. Utility, marketing and authentication categories. Headers in text, image, video or document, positional and named variables, and every button type WhatsApp supports, including OTP, voice call and Flow.
A builder at full parity with WhatsApp: every category, sub-category, header, variable and button type it accepts.
Full schema parity
Build OTP, Flow, voice-call and interactive templates.
Pick a category (utility, marketing or authentication) and a sub-category. Add a header in text, image, video or document. Compose the body with positional `{{1}}` or named `{{name}}` variables. Attach any button type WhatsApp supports.
- Categories: utility, marketing, authentication
- Every sub-category WhatsApp exposes
- Buttons: quick reply, URL, phone number, copy code, OTP, voice call and 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 for approval.
A built-in test harness fires the template at a test number with sample variables, so you see exactly what lands on the device before you submit it. Once submitted, approval and rejection status syncs back in the background.
- Send a sample to your own number before submitting
- Status sync that surfaces the approval or rejection reason
- 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 the API.
Templates are the canonical asset. The inbox sends them inline, campaigns pick them as a broadcast asset, automations fire them as a send action, and the public REST API exposes them via /v1/messages/template. Build once, reuse everywhere.
- Used by the inbox composer, campaigns, automations and REST API
- Status filter: pending, approved, rejected
- Submit and update audit log retained per template
- The same builder for every button and 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 supported
0
Button types, including OTP and Flow
0
Header types: text, image, video, document
Every approval audited. Every send accountable.
Templates are the most regulated surface on WhatsApp. WBIZ keeps an audit-log entry on every submit and update, status syncs keep approval state fresh, and a test harness catches mistakes before review does. Multi-language variants and Flow button types are first-class.
Test harness
Send the draft template to a test number with sample variables before submitting it.
Multi-language
A template family can carry variants in any supported language, and status syncs per language.
Status sync
Approval and rejection state, plus the rejection reason, mirror back into WBIZ in the background.
Submit and update audit
Every submit and update writes an audit entry: who, when and with which payload.
Plays nicely with
Connected to every WBIZ surface that sends.
Templates are not a silo. They power campaigns, automations, the inbox composer and the public REST API. Build once, reuse everywhere.
Campaigns
Pick approved templates as a broadcast asset
Automations
Send a template from any trigger
Inbox
One-click send from the composer
REST API
POST /v1/messages/template
Status sync
Approval state pulled in the background
Flows
The Flow button type opens a Flow inline
FAQ
Templates, answered.
All three WhatsApp categories, utility, marketing and authentication, plus the sub-categories WhatsApp exposes for each of them.
WBIZ surfaces the 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 sends the draft template to a test number with sample variables, so you see exactly what lands on the device before submitting it for approval.
Every button type WhatsApp accepts: quick reply, URL, phone number, copy code, OTP, voice call and Flow.
Yes. Every submit and update writes an audit-log entry with the actor, timestamp and payload, so a compliance review is a query away.