WhatsApp is where the deal actually happens
Customers moved to messaging years ago. What that means for a CRM, and the compliance details teams find out the hard way.
In most Indian sales teams, the phone call opens the conversation and WhatsApp carries it. Prices, brochures, site photos, "sir, is this still available", payment screenshots — all of it happens in a thread on a phone that belongs to the caller, not to the company.
That has two consequences most teams only notice at the worst moment.
The two problems
The record is on someone's personal phone. When a caller leaves, the history of every relationship they owned walks out with them. The customer remembers the conversation. Nobody else can see it.
Nothing about it is measurable. You cannot tell which leads were followed up, what was promised, or how long a reply took, because none of it is anywhere the business can see.
What good looks like
Messaging should be one more channel on the lead record, threaded next to calls and notes. Not a separate app someone alt-tabs to — the same timeline, so the person picking up the account tomorrow reads one story instead of three.
Practically that means:
- Inbound and outbound messages land on the lead, automatically.
- Templates for the things you send fifty times a day, so nobody retypes a price list.
- Replies visible to the manager without asking anyone to forward a screenshot.
- An inbound reply counting as engagement in your reporting, because it is the single strongest signal you get.
The compliance parts teams learn late
If you use the WhatsApp Business API rather than a phone in someone's hand:
- Business-initiated messages must use an approved template. You cannot open a conversation with free text, no matter how reasonable it sounds.
- There is a 24-hour window. After a customer's last message, free-form replies are allowed for 24 hours. After that it is templates again.
- Opt-out has to work. Not as a policy on a page — as a thing the system respects on the next send.
- Template approval takes time. Write and submit them before the campaign, not the morning of it.
None of this is difficult. It is just the kind of detail that turns a launch date into a two-week delay when it is discovered on launch day.
In Nexus
WhatsApp threads onto the lead like any other activity, templates live with the channel configuration, and an inbound message marks the lead as having replied — which is why "no reply" is a filter you can trust rather than a column nothing ever writes.
Want this running in your team? Everything above is how atomcrm.ai works out of the box — try it for ₹5 or book a walkthrough.