Your customers already have the app open
Ask a small business in India how it talks to customers, and the answer is almost always WhatsApp. Orders arrive there, photos of products go out there, and payment reminders are typed there by hand, one at a time, late in the evening.
That makes WhatsApp the most important channel many businesses have, and also one of the least organized. Messages live on one person's phone, nothing is linked to the order book, and when that person is busy, customers wait.
Software can help a great deal here, but only if it is designed around how WhatsApp actually works, including its rules.
Two very different products
There are two ways for a business to use WhatsApp, and they suit different needs:
| WhatsApp Business app | WhatsApp Business Platform | |
|---|---|---|
| Who uses it | A person, on a phone | Your software, through an API |
| Best for | Personal conversations with a small number of customers | Invoices, reminders, confirmations and updates sent automatically |
| Messages you start | Typed by hand | Pre-approved templates |
| Cost | Free app | Charged by Meta per message, by category |
| Connects to your systems | No | Yes |
Most businesses that outgrow typing by hand move their routine messages to the platform and keep personal conversations in the app or a shared inbox.
Rules that protect your number
WhatsApp works hard to keep spam off its network, and businesses that ignore the rules can find their messaging limited. Designing for the rules from the start avoids that:
- Get clear opt-in. Ask customers whether they want updates on WhatsApp, record their answer and make it easy to stop.
- Use templates for messages you start. Invoices, reminders and delivery updates are sent as templates approved in advance. Write them clearly, in each language you need, with the details filled in by your software.
- Respect the conversation window. When a customer messages you, you can reply freely for a limited time. Outside it, you need a template.
- Watch your quality rating. If customers block or report your messages, Meta lowers your rating and can restrict sending. Send fewer, more useful messages.
Pricing and category rules change from time to time, so check Meta's current documentation before you budget.
What to automate first
The best candidates are messages that are repetitive, predictable and genuinely useful to the customer:
- Order and booking confirmations, with the key details in one message.
- Invoices and statements, as a PDF or a short summary with a payment link.
- Payment reminders that are polite, specific and spaced out, never daily.
- Delivery and dispatch updates, ideally with a photo of what's on its way.
- Appointment reminders with a simple way to confirm or reschedule.
In MurtiTrack, built jointly by Univolute and Unitary Tech, idol workshops send Marathi invoices, reminders, statements and dispatch photos on WhatsApp, and every message is tracked against the order. A clear statement on WhatsApp turned an awkward phone call about money into a simple, professional follow-up.
Design notes from building it
- Log every message against a customer and an order, so anyone in the business can see what was sent and when.
- Handle replies. Customers will answer your automated reminder with a question. Route replies to a person, quickly.
- Plan for failures. Messages can fail when a number is invalid or a template is paused. Retry sensibly and tell someone when a message didn't go.
- Keep payment links secure. Generate them on your server, tie them to the order and confirm payment with the provider, not from what the customer's phone reports.
- Collect only what you need. Phone numbers are personal data. Store them carefully, and delete them when they're no longer needed.
The bigger picture
WhatsApp isn't a replacement for your business software. It's the front door to it. The businesses that use it best treat it as one channel connected to their orders, payments and customer records, rather than a separate world on someone's phone.
Want to connect WhatsApp to your order book or billing? See how we approach integrations.
