transactional utility messages
WhatsApp Utility Messages: Transactional Templates and Conditions
A useful transactional message tells the customer what changed in a specific order, payment, appointment or service they use. Start with that record and its purpose; adding an offer can change how the whole message is classified.
Confirm the transaction source, enabled messaging tools, sender/template eligibility and plan scope. The task examples and request below are illustrative; they do not establish template approval, priority delivery or a connected integration.
An enquiry asks the team to confirm the scope, availability and commercial terms. It does not book an appointment, activate an integration, create a trial or send a WhatsApp message.
Illustrative workflow
Select a transaction event
Choose the specific order, receipt, appointment or service update and its authorized source.
Map the template
Match recipient, language and variable positions; include only the fields needed for the transaction.
Check eligibility and dispatch
Confirm permission, category, format/window conditions and sender limits before an eligible request.
Handle status and questions
Distinguish acceptance from delivery. Reconcile failures, duplicate events and customer replies with the source owner.
Transactional tasks to discuss
These are examples of message purposes, not provider approval of a category. Review the full content and actual template classification.
Orders and logistics
Confirmation, cancellation or modification for a specific order; shipment, delivery or exception updates tied to a mapped reference.
Finance
A receipt, invoice notice or refund update tied to the actual transaction. A message is not proof that funds settled.
Appointments
A confirmation, reminder or rescheduling notice for the selected booking.
Account and service
An eligible subscription/service update, maintenance or restoration notice. Security or authentication content needs its own classification and permitted format review.
Check the source and mapping contract
For a webhook, scheduled process or supported file import, agree who supplies the event, which fields are required and when the data is current. Confirm validation, duplicate handling and any retry/preview tools; no automatic connector or instant dispatch is assumed.
Review the whole message purpose
A specific transaction reference helps the reader, but does not guarantee utility classification. A friendly greeting alone does not establish a marketing category either. Review offers, promotional links, vague context and the complete text against current provider guidance.
On a narrow screen, scroll the table horizontally to read every column.
| Draft choice | Question to resolve |
|---|---|
| Order update plus an upsell | Does the offer make the whole message promotional? |
| “Shop more” or generic promotional link | Does the action serve the transaction or another campaign? |
| No identifiable record | Can the customer understand which transaction changed? |
| Neutral template wording | Does the provider approve this exact content and category? |
Approval and reclassification need account evidence
Confirm the exact template category, language, variables and status in the actual account. If rejected or reclassified, inspect the reason and revise the content as appropriate. No word list, pre-approved sample or guaranteed review time establishes approval.
Keep format permission separate from pricing
Effective 1 October 2026; original INR billing card, per delivered message. This schedule is not the price for messages delivered before 1 October 2026. Whats91 passes through Meta messaging charges without markup. Whats91 platform subscriptions, setup, integrations and applicable taxes are separate. From 1 October 2026, delivered Utility templates are charged even inside the 24-hour customer-service window, unless an eligible free-entry window exempts the delivery. The customer-service window controls messaging permission; it does not make all replies free.
On a narrow screen, scroll the table horizontally to read every column.
| Situation | What to verify | Budgeting basis |
|---|---|---|
| Inside a reply window | Category and effective allowance conditions | Dated recipient-market/category rates and confirmed exclusions at /pricing |
| Outside a reply window | Eligible approved template and effective tariff | Dated recipient-market/category rates and confirmed exclusions at /pricing |
| Qualifying entry event | Actual eligibility, response/delivery timing and policy | Dated recipient-market/category rates and confirmed exclusions at /pricing |
| Changed classification | Actual category and applicable rate period | Dated recipient-market/category rates and confirmed exclusions at /pricing |
Time-sensitive does not mean unrestricted
Throughput, recipient limits, template pacing and quality restrictions need account-specific checks. Confirm any specialized API/flag and its permitted purpose before using it. This page does not establish a queue bypass, frequency-cap exemption or instant delivery.
Choose an action the customer can use
Scope a tracking link, invoice document, appointment confirmation or support reply around the transaction. Confirm the template supports that button type and how an event is recorded. A link click or button display alone is not proof that a customer message opened a reply window.
Contact permission still needs review
Document the intended transactional purpose, how the recipient chose it and how withdrawal is handled. Check applicable policy and law for your setup; a previous order alone does not establish permission for unrelated promotions. Keep promotional additions out of a transactional draft unless deliberately reviewed.
Sample utility template request
Illustrative request only. Replace placeholders using the current API version, authorized sender, eligible recipient and the exact approved template, language and parameter order. The code panel only expands or scrolls text; it cannot send, authenticate or validate an account.
Scroll the code panel to read the full example.
curl -X POST "https://graph.facebook.com/YOUR_API_VERSION/YOUR_PHONE_ID/messages" \
-H "Authorization: Bearer YOUR_ACCESS_TOKEN" \
-H "Content-Type: application/json" \
-d '{
"messaging_product": "whatsapp",
"to": "YOUR_ELIGIBLE_RECIPIENT",
"type": "template",
"template": {
"name": "YOUR_APPROVED_TEMPLATE",
"language": { "code": "YOUR_APPROVED_LANGUAGE" },
"components": [{
"type": "body",
"parameters": [
{ "type": "text", "text": "YOUR_ORDER_REFERENCE" },
{ "type": "text", "text": "YOUR_TRANSACTION_AMOUNT" },
{ "type": "text", "text": "YOUR_TRANSACTION_DATE" }
]
}]
}
}'Handle ambiguous and failed states
Validate the record and missing fields before requesting a message. Record actual provider statuses and stop inappropriate repeated requests. A phone being offline or a visual tick in a chat is not a billing reconciliation rule. Confirm final charges against provider billing and delivery records.
Prepare a small transactional scope
Bring the source event/schema, template draft, mapping, permission process and expected volume. Agree failure handling, duplicate suppression, account limits, any document attachment and a permitted test plan. Confirm platform fees separately from message charges.
Messaging and setup conditions
A customer message opens or resets the 24-hour reply window. Outside it, an approved template is needed. Permission to use a message format does not determine its price; confirm the effective category, allowance and account conditions separately.
Eligible Click-to-WhatsApp ad entry on Android or iOS can open a free-entry window when the business replies within the customer-service window. The window starts with that response and can last up to 7 days, subject to Meta’s actual eligibility and expiry. During that window, Marketing, Utility, Authentication and Service deliveries are free for that business phone number/customer pair across messaging accounts. An ad click alone or desktop/web entry does not establish this exemption. Confirm the actual window before excluding deliveries.
Onboarding, verification, template review and integration timing depend on the account, provider, workflow and outstanding approvals. Confirm the scope and schedule with the team; no instant approval, fixed waiting period or go-live deadline is promised.
Questions about transactional utility messages
What separates utility from marketing?
A transactional update concerns a specific transaction or service context. An offer or promotional purpose may change classification; confirm the whole template with current provider guidance and the account status.
Are these pre-approved templates?
No. The examples explain possible tasks. Confirm the exact template, category, language and approved status for your actual sender.
Does a service window mean the message is free?
From 1 October 2026, delivered Service replies are charged at the recipient market’s Service rate after the monthly 1,000 free Service deliveries per business phone number. This allowance is shared across recipient markets and 1:1/group deliveries, counts each delivered group recipient, resets monthly and does not roll over. Service messages require an open 24-hour customer-service window, opened or reset by a customer message. Incoming customer messages are not charged. From 1 October 2026, delivered Utility templates are charged even inside the 24-hour customer-service window, unless an eligible free-entry window exempts the delivery. The customer-service window controls messaging permission; it does not make all replies free. Eligible Click-to-WhatsApp ad entry on Android or iOS can open a free-entry window when the business replies within the customer-service window. The window starts with that response and can last up to 7 days, subject to Meta’s actual eligibility and expiry. During that window, Marketing, Utility, Authentication and Service deliveries are free for that business phone number/customer pair across messaging accounts. An ad click alone or desktop/web entry does not establish this exemption. Confirm the actual window before excluding deliveries.
Can a time-sensitive flag bypass queues?
No bypass or priority-delivery capability is established here. Obtain the current API contract and eligibility before relying on any specialized sending feature.
Does an accepted request prove delivery or billing?
No. Track actual delivery events and reconcile billing records. Missing status is unknown; a device tick or phone condition is not enough to establish a charge.
Choose the next workflow
Review privacy terms and the Legal Center. Confirm support in your signed service agreement.
Discuss your transactional utility messages setup
An enquiry asks the team to confirm the scope, availability and commercial terms. It does not book an appointment, activate an integration, create a trial or send a WhatsApp message.
Send an enquiry