Key takeaways
- WhatsApp allows free-form messages only within 24 hours of the customer’s last message.
- Outside that window you may send only a Meta-approved template.
- If the channel lives on a personal phone, the history walks out when the rep leaves.
- A CRM should show open vs template-only state in the compose box, not after a silent failure.
Two things are true about WhatsApp in B2B sales. It is where your customers actually reply, and the WhatsApp 24 hour rule quietly decides whether your message arrives at all.
There is a gap between how B2B software assumes people communicate and how they actually do. Email open rates in most markets sit in the low twenties. WhatsApp message open rates sit around 98%, and the median reply arrives in minutes rather than hours.
Every sales leader in India, the Gulf, South-East Asia, Africa and Latin America already knows this, because their reps have been quietly running deals on WhatsApp for years. On their personal numbers, outside the CRM — and usually without anyone having explained the WhatsApp 24 hour rule to them, which is why so many of their messages silently fail.
What breaks when the channel lives outside the system
The history walks out the door. When a rep leaves, the entire relationship history for their accounts leaves with them, on their phone. You cannot offboard a personal WhatsApp.
Nobody knows what was promised. A discount agreed in a chat is as binding as one agreed in an email. If it isn't on the record, your next conversation with that customer starts from a worse position than theirs.
Your suppression list means nothing. A standalone WhatsApp broadcast tool doesn't know who unsubscribed, who is already a customer, or who asked not to be contacted. The CRM knows all three and isn't being asked.
You cannot measure it. Reply times, message volume, which rep actually responds — invisible.
The WhatsApp 24 hour rule, explained properly
This is the part most integration vendors gloss over, and it shapes everything.
WhatsApp — not your CRM — allows a business to send free-form messages only within 24 hours of the customer's last message. Outside that window, you may send only a pre-approved template. Meta documents this as the customer service window, and it is enforced at their API, so no vendor can opt out of it on your behalf.
The practical consequences:
- Every campaign is a template. A broadcast to people who haven't messaged you today is, by definition, outside the window. Templates need Meta approval, which takes hours to a day. Plan for it.
- Attachments are window-only. You cannot send a PDF to a cold conversation.
- The window is per-conversation. A rep can be inside it with one customer and outside it with the next.
A CRM that doesn't surface this state will let a rep type a message that silently fails. Qivity shows it directly: an open chat says so; a quiet one is marked Template only and the compose box switches to send your approved template instead.
Business API vs a personal number
Two different things, and the distinction matters commercially.
WhatsApp Business API (WABA) is the official route. You register a number, Meta approves your templates, and messages are billed per conversation at Meta's published rates. It is auditable, it scales, and it cannot be banned for doing what it is designed to do.
Linking a personal number by QR code — the mechanism WhatsApp Web uses — is unofficial. It works, and plenty of tools sell it. It also violates WhatsApp's terms, and Meta bans numbers for it. We support it where an organisation deliberately accepts that risk, and we say plainly in the product that a Business number is the right choice for anything that matters. Any vendor who sells you QR-linked automation without that warning is not being straight with you.
What "native" should actually mean
A checklist for evaluating any CRM's WhatsApp claim:
| Capability | Why it matters |
|---|---|
| Multiple Business numbers | One company number and a number per rep, mixed |
| Two-way inbox in the CRM | Not a link that opens WhatsApp Web in a new tab |
| Conversation ↔ record link | Matched even when the number was typed differently |
| Attachments stored | Incoming files kept in the CRM, not just on Meta's servers |
| Number screening before send | Missing, unreadable, duplicate, opted-out |
| Country code defaults | A number saved without one shouldn't silently fail |
| Window state visible | Open vs template-only, shown before you type |
| Reply-time analytics | Median reply time, replies per teammate |
The one that catches most products out is the second: a great many "WhatsApp integrations" are a button that opens wa.me in a new tab. That is a hyperlink, not an integration. The thread still isn't in your system.
Where it gets genuinely useful
Once the channel is inside the CRM, things become possible that are not integrations at all — they are just features:
- New-lead alerts to the rep's phone, from the number that lead will recognise.
- A daily reminder digest at 9am in each rep's own timezone, listing what is due and what is coming.
- Contract-expiry warnings to the account owner.
- Campaigns to mobile numbers with the same audience builder, suppression list and screening as email.
None of that is possible when WhatsApp is a browser tab.
Start where your customers already are
If your reps are running deals on WhatsApp today, that channel is already load-bearing in your revenue. The only open question is whether the company owns it or an individual does.
See how Qivity handles WhatsApp, or book a demo and we will connect a test number live.