In India, WhatsApp is not a marketing channel bolted onto sales — it is where the sale happens. Which means the leads, the negotiation and the follow-up live on somebody's personal phone, invisible to the business, and leave entirely when that person does. Integrating WhatsApp with your CRM is really about fixing that. Here is what the integration actually involves.
Pick the Right Door: App vs Cloud API
There are two WhatsApp products and choosing wrong costs you a phone number migration later.
- WhatsApp Business app — free, installed on a phone, one user. Quick replies and labels, no API, no CRM integration, broadcast limited. Correct for a solo founder, a dead end for a team.
- WhatsApp Cloud API — hosted by Meta, accessed over HTTPS. Webhooks for inbound messages, template sending, multiple agents on one number, and the only path to real CRM integration.
A number can be on one or the other, not both. If you plan to integrate at all, start on the API and never print the app number on anything.
The Four Message Categories (This Is Where Your Bill Comes From)
Meta charges per delivered message and prices by category. At current India list rates:
- Marketing — promotions, offers, re-engagement. Roughly Rs. 0.86 to Rs. 0.88 per delivered message. Requires opt-in and the strictest template review.
- Utility — order updates, payment reminders, appointment confirmations tied to an existing transaction. Roughly Rs. 0.11 to Rs. 0.13.
- Authentication — OTPs. Similar low rate to utility.
- Service — your free-form replies inside the 24-hour customer window. Free, with a monthly free-message allowance per business phone number.
The design implication is blunt: a payment reminder written as a utility message costs about one-seventh of the same reminder written as marketing. Category discipline is a cost lever, not paperwork. Rates and allowances do change — check Meta's current India pricing before you budget.
The 24-Hour Window Dictates Your Workflow
When a customer messages you, a 24-hour window opens in which your agents can reply freely at no cost. When it closes, reaching them requires a paid, pre-approved template. Every sensible WhatsApp workflow is built around that fact:
- Route inbound messages to an available agent fast — a reply at hour 23 costs nothing, a reply at hour 25 costs money and feels like a cold open.
- End conversations with a question when follow-up is expected; a customer reply reopens the window for free.
- Reserve templates for genuine re-engagement, not for conversations you simply let go cold.
Templates: Plan for Rejection
Any message outside the window is a template submitted for review. What gets rejected, repeatedly:
- Marketing content submitted under the utility category — the single most common rejection.
- Variables that carry whole sentences. Placeholders are for names, amounts and dates, not for smuggling arbitrary copy past review.
- Vague openers ("Hi, checking in") with no transactional anchor.
- URL shorteners, which look like cloaking.
Submit your core templates during build, not at launch. Approval is usually quick but not instant, and a rejected template on go-live day blocks the whole flow.
What the CRM Side Has to Do
Identity matching on phone number
Inbound webhooks carry an E.164 phone number. Your CRM must normalise stored numbers to the same format — Indian data is full of 9967561546, 09967561546 and +91 99675 61546 for one person — or every message creates a duplicate lead. Normalise on write, index on the normalised column.
One timeline per contact
WhatsApp messages belong on the same activity timeline as calls, emails and meetings. Separate inboxes recreate the problem you are solving.
Ownership and handover
A conversation needs an assigned agent, a visible handover action, and a rule for what happens when that agent is unavailable. Without it, either everyone answers or nobody does.
Idempotent webhook handling
Meta retries deliveries. Store the message ID and ignore duplicates, or your timelines will show the same message three times.
Media storage with retention
Customers send payment screenshots, PDFs and site photos, and media URLs from the API expire. Download and store on receipt against the contact record, with a documented retention period — these files contain personal data.
Two Mistakes That Cost Real Money
Buying a bulk-sender instead of an integration. Tools that only blast templates give you reach with no record. Six months later you have spent lakhs on marketing messages and still cannot tell which conversations produced revenue.
Ignoring quality rating. Blocks and reports lower your number's quality rating, and a low rating caps your daily sending limit. Teams discover this at the worst time — a campaign day that silently stops delivering. Send fewer, better-targeted marketing messages; keep utility flows clean.
Conclusion
WhatsApp integration is less an API project than a records project. The API part is a week of work. The valuable part is that every conversation lands on a contact record the business owns, so leads survive staff changes and follow-up stops depending on memory.
If your sales currently lives in your team's personal WhatsApp, that is the risk worth pricing. Tell us how your team handles enquiries today and we will map what the integration would look like.
Frequently Asked Questions
What does WhatsApp Business API cost in India?
You pay Meta per delivered message, and the price depends on the category. At current India list rates marketing messages run around Rs. 0.86 to Rs. 0.88, while utility and authentication messages are roughly Rs. 0.11 to Rs. 0.13. Service messages replying inside the 24-hour customer window are free, with a monthly free allowance per business phone number. A Business Solution Provider adds its own platform fee on top, so compare the all-in number, not the Meta rate.
Do I need the WhatsApp Business app or the API?
The free Business app is for one person answering a phone. It has no CRM integration, limited broadcast and no automation. The Cloud API is what you integrate — it gives you webhooks for inbound messages, template sending, and multiple agents on one number. You cannot use the same number on both, so pick before you publish it anywhere.
Can I send a WhatsApp message to any lead who filled my form?
Only with consent and only via an approved template. Outside the 24-hour window after the customer's last message, you must use a pre-approved template in the correct category, and marketing templates need opt-in. Sending unsolicited marketing is the fastest way to collect blocks, which lowers your quality rating and eventually caps your sending limit.
What is the 24-hour window?
When a customer messages you, a 24-hour service window opens in which you can reply with free-form messages. After it closes you can only reach them with an approved template, which is a paid message. This single rule shapes every WhatsApp workflow: you design around keeping conversations inside the window or paying to reopen them.
How does this connect to the CRM record?
Inbound messages arrive on a webhook carrying the sender's phone number. Your CRM matches that number to a lead or client and appends the message to that record's timeline; no match means a new lead with WhatsApp as the source. Done properly, every conversation is on the contact's history and any agent can pick up where the last one stopped.