Ask an Indian business owner where enquiries come from and WhatsApp is usually the first answer. Ask to see the pipeline report for that channel and there generally is not one. The conversations are on someone's personal phone.
That gap is the whole problem. The highest-volume channel is the least instrumented, the least shareable, and the most dependent on one person being available. When they go on leave, the channel stops.
Start with the API decision, because it constrains everything
There are three ways to run WhatsApp for a business, and only one of them supports automation at business scale.
- The consumer app. One device, no automation, no shared access. Fine for a sole trader, a dead end otherwise.
- The WhatsApp Business app. Adds labels, quick replies and a catalogue. Still fundamentally one device and no real automation surface.
- The WhatsApp Business Platform, commonly called the Business API. Supports verified sending, approved message templates, a shared team inbox, and programmatic automation.
The API route means going through a Business Solution Provider, verifying the business, and accepting that business-initiated messages use pre-approved templates. Those constraints feel like friction. They are also what makes the channel reliable enough to build on.
The rule that shapes every WhatsApp automation
WhatsApp draws a hard line between two situations, and almost every design decision follows from it.
The two messaging modes
Customer-initiated window
- Opens when the customer messages you
- Lasts 24 hours from their most recent message
- Free-form replies allowed
- This is where conversational automation belongs
- Each new customer message resets the window
Business-initiated messages
- Used when you contact the customer first
- Must use a pre-approved template
- Requires prior opt-in
- Charged per message
- Marketing templates face stricter approval and can be blocked
Practically: qualification, support and conversational flows run inside the 24-hour window and can be as natural as you like. Reminders, order updates and follow-ups reach outside it and must be templated. Designing a follow-up sequence that assumes free-form messaging is the most common mistake we see, and it surfaces only after build.
A qualification flow that does not feel like a form
The failure mode of WhatsApp automation is turning a conversation into an interrogation. Customers abandon a chat that fires six questions at them, and abandoning is one tap.
What works is asking one question per message, acknowledging the answer before moving on, and accepting unstructured replies instead of demanding a format.
New enquiry to qualified lead
- 01
Inbound message
Arrives on the business number. The 24-hour window opens.
- 02
Intent classification
New enquiry, existing customer, support issue, or booking change. Routing happens before any question is asked.
- 03
Acknowledge first
Confirm receipt and state what happens next, before asking anything. This single step measurably reduces drop-off.
- 04
One question at a time
Ask, acknowledge the answer, then ask the next. Never batch.
- 05
Accept messy input
'around 15 lakhs', '15L', 'about fifteen' all resolve to the same value. Rejecting input and asking again is where people leave.
- 06
Answer their questions too
A qualification flow that will not answer a customer's own question reads as extraction. Route routine questions to the knowledge base mid-flow.
- 07
Act
Book, quote, escalate or route based on the captured answers.
- 08
Write to CRM
Contact, captured fields and conversation summary. This is the step that makes the channel reportable.
- 09
Hand over cleanly
When a human takes the thread, automation steps aside and does not resume mid-conversation.
Getting off the personal phone
The operational change that matters most is often not the automation. It is that conversations move into a shared inbox the whole team can see.
- Any team member can pick up a thread, with the full history visible.
- Someone being on leave stops being a single point of failure.
- Unanswered conversations can be counted - you cannot manage what you cannot see.
- Conversation history belongs to the business rather than to a departing employee's device.
- Two staff members stop answering the same customer differently.
Several businesses we have worked with got most of their improvement from this alone, before a single automated flow went live. It is worth doing first for that reason.
Language, as it is actually used
Indian business WhatsApp is frequently code-mixed. A customer writes in English, switches to Hindi or Telugu mid-sentence, and uses Roman script for both. An agent configured for one language and one script will mishandle a large share of real messages.
Two things to get right: handle transliterated input, since 'kitna hoga' will not match a Devanagari pattern, and reply in the language the customer used rather than the one you configured as default.
What not to automate
The line is narrower than vendors suggest.
- Complaints. A frustrated customer receiving an automated reply escalates rather than settles.
- Final pricing on anything non-standard. Capture the requirement and route it.
- Negotiation of any kind.
- Medical, legal or financial advice. Route without exception.
- Anything irreversible without a human approval step - refunds, cancellations, payouts.
And one absolute rule: a customer who asks for a human gets one, immediately, without having to ask twice. Automation that resists this does more reputational damage than the efficiency is worth.
Sequencing an implementation
- 01Move to the Business API and get the number verified. Everything else depends on it.
- 02Set up the shared inbox and work manually for a fortnight. You will learn what the real questions are.
- 03Automate the acknowledgement and intent routing only. Measure the response-time change.
- 04Add the knowledge base for the repeated questions you now have evidence for.
- 05Add the qualification flow for new enquiries.
- 06Connect the CRM so the channel appears in reporting.
- 07Add templated reminders and follow-ups last, since they carry the approval overhead.
Step two is the one people skip and the one that most improves the result. Two weeks of manual handling in a shared inbox tells you what customers actually ask, which is reliably different from what the business assumes.
Related service
Want this mapped for your business?
Describe how the process runs today. We will come back with what can be automated, what should stay with your team, and what it would take to build.
Frequently asked
Can we automate our existing WhatsApp Business app number?
You can migrate that number to the Business API, which is the correct path and preserves it. What you should not do is drive the app programmatically with unofficial tooling - it risks a ban that takes the number and its history with it.
How much does the Business API cost to run?
There is a per-message charge on business-initiated conversations that varies by country and category, plus whatever your solution provider charges. Customer-initiated conversations are considerably cheaper. Cost scales with volume, so we model expected monthly spend during scoping rather than after launch.
Will automation make us look impersonal?
It can, if it answers questions it should not or refuses to hand over. Used on acknowledgement, routing, confirmations and reminders it usually reads as more responsive, because the alternative is a reply four hours later.
Do we still need a website if WhatsApp is our main channel?
Yes - they do different jobs. WhatsApp converts an enquiry that already exists; the website is how that enquiry gets created, and it is the only one of the two that search engines can index. Businesses that treat WhatsApp as a replacement tend to find their enquiry volume is capped by referral alone.
