Platform details last reviewed on 5 October 2026. Platform rules and prices change often. This is general information, not legal advice, so confirm specifics with Meta's current documentation and your own counsel.
Many Indian businesses already chase invoices, confirm approvals and update customers on WhatsApp, by hand. Automating that makes sense, because the message arrives where people look. It also goes wrong predictably: messages to people who never agreed, and no record of what was received.
This guide covers WhatsApp automation for business: what the WhatsApp Business Platform requires, how to design an event, recipient, template and proof loop, which events suit WhatsApp or email, and what OpsGrids does today. If you also use email automation for business events, treat the two as one routing decision.
The event loop: event, recipient, template, proof
Design around the event, not the message. Five events cover most needs: invoice sent, payment received, payment reminder, approval decided and delivery update. For each, decide who must know, on which channel, with what wording, and how you will prove it arrived.
Keep rules explicit and few. The final step matters most for money: "we sent a reminder on the 3rd" is defensible only if the receipt is attached to the invoice, as part of sound accounting workflows.
What the WhatsApp Business Platform requires
Opt-in
Meta's Business Messaging Policy requires that you have received opt-in permission from the recipient confirming they want to receive later messages or calls from you. It recommends opt-ins that cover each message category and give clear opt-out instructions. You may use automation when responding inside the 24-hour window, but must offer prompt, clear and direct escalation to a person.
Templates and the 24-hour window
Each message template must be categorised as authentication, marketing or utility, and must have status APPROVED before you can send it. Template messages are the only type you can send to a user outside a customer service window, so an invoice notice or reminder is a template with placeholders for amount, number and due date.
A 24-hour timer starts when a user messages or calls you, and resets to 24 hours if they message again. Inside it you can send any message type (text, media, interactive, documents). After it closes, only pre-approved templates. Most automated events happen when the customer has not just written, so design for templates.
Pricing and limits
From 1 July 2025, Meta charges per delivered template message, by category. Free: service messages inside an open window, utility templates delivered inside an open window, and messages inside the 72-hour free entry point window from Click-to-WhatsApp ads. Charged: marketing templates, utility templates outside the window, and authentication templates.
Rates vary by recipient country calling code, volume tiers can lower utility and authentication rates, and Meta publishes a downloadable rate card. For India, Meta started billing localisation on 1 January 2026 with India-specific rates, and eligible Indian customers are to migrate to INR billing by 31 December 2026, per Meta's pricing documentation, so check your own account.
Messaging limits cap the unique users you can deliver to outside a customer service window in a moving 24 hours: 250, then 2,000, 10,000, 100,000, then unlimited. They apply at the business portfolio level across phone numbers, and can scale up automatically when you send high-quality messages and use at least 50% of the current limit within 7 days.
Rules at a glance
| Topic | What Meta's documentation says |
|---|---|
| Opt-in | Recipient permission required; cover each category; give opt-out instructions |
| Templates | Authentication, marketing or utility; APPROVED before sending |
| Customer service window | 24 hours from the user's message; resets on each new one |
| Outside the window | Pre-approved templates only |
| Pricing | Per delivered template, by category, from 1 July 2025 |
| Messaging limits | 250, 2,000, 10,000, 100,000, then unlimited users per moving 24 hours |
If you build on the WhatsApp Cloud API, Meta now requires support for business-scoped user IDs (BSUIDs) for businesses integrating directly. Usernames roll out gradually through 2026 and are optional for users, and phone numbers can be omitted from webhooks in some cases. Do not key records only on phone numbers, and check Meta's current documentation.
Which events suit WhatsApp and which suit email
| Event | Who receives it | Suggested channel | What the message must contain |
|---|---|---|---|
| Invoice sent | Customer's billing contact | Email with the PDF; WhatsApp as a nudge | Invoice number, amount, due date, how to pay |
| Payment received | Customer's billing contact | Amount, invoice number, date received | |
| Payment reminder | Customer's billing contact | WhatsApp, email as backup | Invoice number, amount outstanding, due date, who to contact |
| Approval decided | Whoever raised the request | What was decided, by whom, what happens next | |
| Delivery update | Customer or site contact | Order reference, status, expected date | |
| Escalated approval | Manager above the one who did not answer | Request, who is waiting, since when |
Short, time-sensitive messages suit WhatsApp; formal or attachment-heavy items suit email. Keep the invoice as your record and use WhatsApp to say it exists; for invoice rules see the e-invoicing guide. For purchase approvals, see procure-to-pay.
Writing templates and reminders
Write each template for one event and one action, with variable data in placeholders and factual wording. For payment reminders, set a cadence (before the due date, on it, then at fixed intervals after) and stop automatically once the payment is allocated.
Consent is where design meets law. India's Digital Personal Data Protection Rules were notified on 13 November 2025, and the main consent and notice obligations are reported to take effect around mid-May 2027, 18 months later; confirm with counsel.
That is not in force today, but building consent capture to that standard now, recording when and how each person agreed, avoids a rebuild. See our privacy approach. SMS has its own regime; WhatsApp is governed by Meta's policy.
Pre-launch checklist
- Opt-in stored per contact with date, source and category
- Every template categorised and showing APPROVED
- Largest expected batch checked against your messaging limit
- Each event has a recipient rule and a fallback channel
- Delivery receipts stored against the source record
- A person reachable from any automated conversation
- Reminders stop when payment is allocated
Common mistakes
- Sending without opt-in. A phone number on an invoice is not permission.
- Marketing wording in utility templates. Keep payment and approval messages factual.
- No receipt trail. Without stored status you cannot show what happened.
- Reminding after payment. Tie the cadence to allocation.
What OpsGrids has today
This article is a guide to doing WhatsApp automation well. OpsGrids today covers the event-notification part only. Notification rules route events from the products to people on WhatsApp or email, with a delivery receipt coming back. Sending on WhatsApp needs each organisation's WhatsApp Business account to be connected through Meta first.
Examples shown on the rules screen: an invoice being finalised (Finance) goes to the customer's billing contact on WhatsApp; an approval step escalated (HRMS) goes by email to the manager above the one who did not answer; an approval decided (HRMS) goes on WhatsApp to the employee who asked for the attendance correction; a storefront postal-code import (Storefront) goes by email to the operations team.
CRM plus Notification is live: a contact's sealed phone number can be messaged without anyone decrypting it. The send resolves the target through an audited path, and the number never leaves the vault. HRMS plus Approvals is live for attendance corrections only: it routes up the employee's reporting line, escalates to the manager's manager when unanswered, and applies on approval.
OpsGrids has no WhatsApp inbox or shared team inbox, template-management screen, broadcast or campaign sending, chatbots, Meta account onboarding flows, SMS or email builder. Marketing has no send path; messaging runs through Notification. The full list, with every gap, is on the products page; see also how automations work.
| Product | What it does today | Not yet |
|---|---|---|
| Finance | Invoices, payments and allocations; GST registration, returns and a diff against your books; TDS withholding; a full ledger; e-invoice-ready IRN, e-way bill and IMS workflows | Not connected to the government portals yet (simulated portal); online payments in test mode |
| HRMS | Employee records, reporting lines, PII masked with an audited unmask; check-in and check-out, shifts, geo-fences, attendance regularisation with an approval chain | No leave ledger, no payroll |
| Support & IT | Tickets with SLA policies; incidents, service requests, service catalogue, asset register | Nothing declared |
| Operations & Inventory | Inventory with reorder points, warehouses, suppliers scored on lead time, on-time % and spend; purchase orders down to the line; goods receipt | No automation rules; receiving and warehouse screens still marked coming soon |
| Storefront | Store identity and a publish step; delivery zones by postal code; bulk import; a tester; a demand report | Builder is a preview; no cart, checkout or orders; fees shown, not charged |
| CRM | Leads that convert to a company, contact and deal; deal board; companies and contacts with owners; audited phone reveal; messaging-target resolution; activity log | No quotes; pipeline stages are fixed; no dated follow-up tasks |
| Projects | Projects, milestones and tasks, on a board or a timeline | Nothing declared |
| PulseBoard | Projects and tasks against a people roster, timesheets, daily standups | Nothing declared |
| Marketing | Campaigns and performance, audiences, channels, revenue-versus-spend per campaign | Revenue is entered by hand; no send path |
FAQ
Do I need opt-in before sending an invoice notification? Per Meta's Business Messaging Policy, yes: you need the recipient's opt-in permission. Capture it per category, with opt-out instructions.
Can I send a payment reminder if the customer has not messaged me lately? Only as an approved template. Once the 24-hour window closes, templates are the only message type allowed, and utility templates outside the window are charged.
Are WhatsApp messages free? Not always. Service messages and utility templates inside an open window are free; other delivered templates are charged by category. Check your account's rate card.
Should invoices go on WhatsApp or email? Email as the formal delivery, WhatsApp as the short, timely nudge.
Talk to us about notifications
If you want event notifications wired to your invoices and approvals, Talk to our team.
Sources (checked 5 October 2026)
- Meta, WhatsApp Business Platform documentation: templates, messages and customer service window, pricing, messaging limits (developers.facebook.com)
- Meta, WhatsApp Business Messaging Policy (whatsappbusiness.com/policy)
- Meta, WhatsApp Business Platform pricing and rate card (business.whatsapp.com/products/platform-pricing)
- Digital Personal Data Protection Rules, 2025: dates are from secondary reports; confirm on meity.gov.in before relying on them