Pre-written message formats Meta reviews and approves before you send them. They are required whenever a business starts a conversation, or replies more than 24 hours after the customer's last message — and they are the reason the 24-hour window matters so much.
A free-form message is anything you type inside the 24-hour window — text, media, interactive messages, whatever the conversation needs. A template is the pre-approved format you use outside it. One is a reply, the other is permission to reach out.
A header (text, image, video or document), a body of up to 1,024 characters, an optional footer, and an optional button row of quick replies, URL buttons or call buttons. Variables can appear in the header and body, never in the footer.
It opens the moment a customer messages you and resets with every new customer message. While it is open, reply however you like. Once it closes, only an approved template reaches that person again.
Only approved templates, in the category that matches the content: utility for transactional updates, marketing for promotions, authentication for codes. The moment the recipient taps or replies, the window reopens and free-form messaging resumes.
Templates exist only on the WhatsApp Business API. For the platform rules themselves, see Meta official WhatsApp message template guidelines.
Four failure modes we see in almost every team that comes to us with a stalled WhatsApp programme:
The template comes back "Rejected — INVALID_FORMAT" and that is the entire explanation. No line number, no highlighted field. You change something at random, resubmit, get rejected again, and Friday's campaign now goes out next Tuesday.
Copy is drafted in Docs, status is tracked by hand in a sheet, the real template lives in Business Manager and the sending happens in a third tool. Nobody knows which version is live, and offer_v2, offer_v2_final and offer_new are all approved.
You submitted an order update as Utility. Meta read the "check out our new arrivals" line and reclassified it as Marketing — priced differently, throttled differently. You find out weeks later when the invoice arrives or delivery quietly dips.
Blocks, reports and spam marks drag a template's quality rating down until Meta flags it, pauses it, then disables it — and your phone number's rating takes damage at the same time. Most teams discover it when a Monday broadcast silently fails.
👇 BetaXLab fixes all four — and your first approved template can be live within 48 hours.
Catch the errors before Meta sees them, keep one source of truth, and get told when something changes.
BetaXLab validates your template against Meta structural rules while you type — a body that opens with a variable, placeholders numbered out of sequence, missing sample values, over-length headers, footers containing variables, malformed dynamic URL parameters, and marketing copy inside a template labelled Utility. Every warning names the field and the rule behind it.
Every template sits in one searchable library with its live approval status, category, language, quality rating and last-edited date visible at a glance. The library is the source of truth, and the same record is what your broadcasts, drip campaigns, follow-ups and reminders send. Change the copy once and every automation using it sends the corrected version.
When you pick a category, BetaXLab explains what Meta actually allows inside it and scans your draft for the language that most commonly triggers reclassification — promotional phrasing in a utility template, an upsell line appended to an order update, a discount code in an authentication message. If Meta reclassifies later, the change appears on your dashboard with the date it happened.
Each template quality rating shows in the library, and you get alerted when a template is flagged or paused and when your phone number rating moves. You see which template triggered it, which broadcast it went out in, and which segment received it — so a mystery outage becomes a specific, fixable event.
Twelve capabilities that cover the entire template lifecycle — build, validate, submit, track, send and measure.
Build the header, body, footer and button row in a form-based editor with a live WhatsApp preview beside it. Character counters run against Meta actual limits — 60 for a text header, 1,024 for the body, 60 for the footer — so length problems never surface at submission time.
Insert variables with a click and map each one to a field on your contact record — first name, order ID, appointment time, agent name, invoice amount or any custom field. Meta requires sample values at submission, and BetaXLab prompts for them inline instead of letting an incomplete template through.
Add quick-reply buttons that trigger an automation when tapped, URL buttons with dynamic parameters that append a customer-specific path, and call buttons that dial your sales line. Quick-reply taps route straight into chatbot flows or assign the conversation to an agent.
Attach an image, video or PDF header — product shots for a catalogue drop, a property photo for a site-visit invite, an invoice or prescription as a document. Upload the sample asset Meta requires at submission, then swap in the per-recipient file at send time.
Meta treats each language as its own template version. BetaXLab groups them under one logical template so you manage the Hindi, English and Tamil versions as a single asset, and sends the right one based on the contact language field.
Every template, searchable and filterable by status, category, language, quality rating and tag. Version history records each edit and who made it. Meta caps how many edits an approved template can take per day and per month, so BetaXLab shows how many you have left before you burn one.
Send an approved template to your own number with real sample data before it goes to a list. Confirm the variables resolve, the media renders, the buttons work and the link lands where it should — the cheapest quality control step in the whole workflow.
Pending, Approved, Rejected and Paused states update in the library as Meta processes them. Approvals frequently land within minutes; Meta stated window is up to 24 hours. Rejections arrive with the reason code and a readable explanation attached to the draft.
Per-template sent, delivered, read and reply counts, plus button-tap breakdowns, so you can compare two variants of the same offer honestly. Filter by campaign, segment or date range.
The same approved template powers broadcast sends, drip campaigns, follow-up automation and reminder workflows. Pick a template from the library, map the variables once, and the automation handles the rest.
Decide who can create, edit, submit and send. Junior agents send approved templates without being able to edit them, a marketing lead can draft and submit, and only an admin can delete — backed by role-based access across the whole platform.
A quick-reply tap on a template can open a WhatsApp Flow — a structured in-chat form for booking a slot, choosing a plan or submitting details — so the template starts the conversation and the Flow captures the data.
The category you pick changes both what Meta charges and how the message is delivered. Get it right at draft time and reclassification never happens to you.
Order updates, shipping and delivery notifications, appointment reminders, payment confirmations and account alerts — always tied to an action the customer already took. Keep promotional lines out of them; that single appended sale sentence is the classic reason a utility template gets reclassified.
Offers, announcements, product launches, festive packages and re-engagement of quiet contacts. Priced differently to utility and subject to per-user delivery limits, so send them only to recently engaged, opted-in contacts to protect the quality rating.
OTPs, login codes and verification messages that must follow Meta fixed authentication format, including the copy-code button. No marketing language, no discount codes, no extra copy — the format is deliberately rigid so delivery stays reliable.
Six outcomes teams report once the template lifecycle stops being a bottleneck.
Templates are the only compliant way to restart a conversation that has gone quiet, and quiet is where most pipeline dies. A well-built template with a View Quote button reopens the 24-hour window the moment someone taps, and everything after that is a free-form conversation with a real agent. Teams that template their re-engagement moments recover deals that would otherwise go cold unnoticed.
Writing a template once and reusing it across forty campaigns is the obvious saving. The bigger one is approval time you stop losing: a template that passes the pre-submission check reaches Approved the same working day instead of consuming three rejection-and-edit rounds across a week. Multiply that by the twenty or thirty templates a real business runs and you recover days of calendar time per quarter.
Templates with buttons convert better than templates without, because the recipient never has to compose anything. A Confirm / Reschedule pair on an appointment reminder collects an answer in one tap, and a dynamic URL button drops the customer straight onto their own order page. Per-template analytics let you A/B the button labels and keep the version that wins — then scale it with WhatsApp broadcast.
Every button tap and template reply lands in the shared team inbox as an open conversation with an owner, not as an unread notification on somebody phone. Combined with lead management, a template reply automatically creates or updates a lead record with source, campaign and stage, so a hot response at 10pm is queued and assigned rather than lost overnight.
Customers do not want to hunt for their order status in an email folder. A utility template that arrives the moment the shipment moves, with the tracking link on a button, beats any status page. Because templates are pre-approved and structured, they arrive consistent every single time — same tone, same format, correct details, no agent typos in an invoice number.
Agents stop retyping the same twelve messages. Marketers stop waiting on a developer to add a variable. Managers stop chasing approval status in Business Manager. The whole lifecycle — draft, check, submit, track, send, measure — happens in one screen with clear permissions, alongside the rest of your WhatsApp CRM work.
No Business Manager login, no developer, no spreadsheet in the middle.
Pick a category (utility, marketing or authentication), choose your language, and compose the header, body, footer and buttons in the visual builder. Insert variables where you want personalisation and map each one to a contact field. The live preview shows exactly what the customer will see; the compliance checker flags anything Meta will reject.
Add sample values and submit to Meta directly from BetaXLab — no separate Business Manager login. The status updates in your library as it moves from Pending to Approved. If it is rejected, the reason code appears next to your draft with a plain-English fix so you can correct and resubmit in minutes.
Attach the approved template to a broadcast, a drip campaign, a follow-up sequence or a reminder workflow. Variables populate from your CRM at send time. Delivered, read, reply and button-tap numbers land in your analytics dashboard, and every reply opens a live conversation in your shared team inbox.
The template sets real businesses actually run — and the category discipline that keeps them delivering.
A broker keeps a small, deliberate set: a site-visit confirmation with Confirm and Reschedule buttons and variables for property, date, time and agent; a quote-ready template with a dynamic URL button opening the buyer own PDF; and a new-inventory marketing template with an image header of the project render — sent only to leads who engaged in the last 60 days.
A reminder 24 hours out with Confirm and Reschedule quick replies, a second two hours out carrying prep instructions, and a check-in three days after the visit. All utility, approved once, reused indefinitely, with variables for patient, doctor, time and branch. Prescriptions and reports go out as document-header templates.
A rebooking template triggered by days-since-last-visit, personalised with the client name, usual service and preferred stylist, with a Book Now button that opens a Flow for slot selection. A separate marketing template with an image header handles festive packages and new treatments for clients seen in the past six months.
Order confirmed, out for delivery with a tracking button, reservation confirmed with date, party size and a Cancel quick reply — expected messages, so quality ratings stay high. The promotional motion runs separately: weekend specials with a photo header, outlet launches and festival menus, capped in frequency and measured per template.
Application cut-off reminder, fee due notice with amount and a payment URL button, class rescheduled alert, admit-card release, result announcement — tight factual utility copy with no promotional language, which is exactly why they stay in the utility category. Admissions outreach runs as a separate marketing set with a Talk to a Counsellor quick reply.
Order confirmation, shipping update, delivery confirmation and return acknowledgement stay clean utility. Abandoned-cart recovery and campaign sends are honest marketing templates with image headers and a dynamic URL button reopening the exact cart. OTPs use authentication templates with the copy-code button.
Every platform here runs on Meta WhatsApp Business Platform, so the template rules, categories and per-message charges are identical. The difference is how much of that complexity the platform handles for you.
| Criteria | BetaXLab | WATI | Gallabox | Interakt | AiSensy | Zoko |
|---|---|---|---|---|---|---|
| Core Features | Full template lifecycle: visual builder, pre-submission compliance check, Meta submission, approval tracking, versioning, per-template analytics | Template builder and submission with campaign sending | Template builder with chatbot and campaign tooling | Template builder oriented around ecommerce order flows | Template builder focused on broadcast campaigns | Template builder built around catalogue and commerce use cases |
| Ease of Use | Live WhatsApp preview beside the editor, inline field-level rule warnings, plain-English rejection reasons | Established UI, template rules mostly learned by trial and error | Clean builder; approval troubleshooting largely handled outside the product | Straightforward for standard ecommerce templates | Fast for simple broadcast templates | Commerce-first UI; template management is secondary |
| Automation Depth | One approved template drives broadcasts, drip campaigns, follow-ups, reminders and Flow triggers from a single record | Strong campaign and chatbot automation | Good chatbot and workflow automation | Automation focused on order and cart events | Broadcast and basic sequence automation | Automation centred on commerce journeys |
| Built-in CRM | Native AI WhatsApp CRM — variables map directly to contact and lead fields, replies create and update lead records | CRM-lite contact management | Contact management with pipeline features | Contact management tied to store data | Contact lists with tagging | Customer profiles geared to purchase history |
| Pricing Transparency | Flat, published plan pricing with Meta per-message charges passed through as-is | Tiered plans plus add-ons | Tiered plans with usage components | Tiered plans with usage components | Plans with credit-based usage elements | Tiered plans with commerce add-ons |
| Team Collaboration | Shared multi-agent inbox, role-based create/edit/submit/send permissions, full edit history | Multi-agent inbox with roles | Multi-agent inbox with roles | Multi-agent support | Multi-agent support | Multi-agent support |
Comparison reflects publicly documented product positioning at time of writing. Meta's own template rules, categories and per-message charges apply identically across every provider.
One approved template record powers every sending surface on the platform.
Build your first compliant WhatsApp message template in under ten minutes, submit it to Meta without leaving the dashboard, and watch it go green. Free trial — no credit card, no setup fee, and our team walks you through your first three templates so they clear on the first submission.
Twenty questions we get asked about building, submitting and managing WhatsApp message templates.
Meta publishes its own rates — see the WhatsApp Business Platform pricing documentation — and our plans sit on top of it at BetaXLab pricing.
✅ Ready to get your WhatsApp templates approved first time?
Try Free →