Zoho CRM WhatsApp Integration: How to Connect WhatsApp to Zoho CRM
Zoho gives you two first-party ways to put WhatsApp inside the CRM: Business Messaging in Zoho CRM itself, and the WhatsApp channel in Zoho SalesIQ. Here is what each one does, what you need before you start, and which to pick.
Short answer: Zoho offers two native paths. You can enable WhatsApp Business messaging directly inside Zoho CRM under Business Messaging, which lets reps send and receive WhatsApp from a contact or lead record and logs the thread there. Or you can connect a WhatsApp channel in Zoho SalesIQ, which gives you a unified inbox across website chat and WhatsApp with routing and bots. Both require a WhatsApp Business API account behind them, meaning a WhatsApp Business Account and a dedicated phone number. The free WhatsApp Business app cannot be connected to Zoho, because it has no public API.
That last sentence is where most setups stall. People download the WhatsApp Business app, look for a Zoho connector, and find nothing. The app was never designed to integrate with anything.
The two Zoho paths, side by side
| Business Messaging in Zoho CRM | WhatsApp channel in Zoho SalesIQ | |
|---|---|---|
| Where you work | Inside the CRM, on the lead or contact record | In the SalesIQ operator console |
| Best for | Sales reps messaging known contacts | Support and inbound chat at volume |
| Unified with website chat | No | Yes, one inbox for both |
| Chatbots | No | Yes, via the SalesIQ bot builder |
| Routing to operators | Owner-based | Rules and queues |
| Conversation on the CRM record | Yes, natively | Yes, when SalesIQ is linked to CRM |
| Needs WhatsApp Business API | Yes | Yes |
If your team lives in the CRM and messages people they already know, use Business Messaging. If strangers arrive from your website and you need bots, queues, and one inbox for chat plus WhatsApp, use SalesIQ. Plenty of companies run both.
What you need before you start
The prerequisites are the same as any WhatsApp integration, because they come from Meta rather than Zoho.
You need a Meta Business account with business verification completed. Without verification you are capped at 250 unique customers per rolling 24 hours. You need a WhatsApp Business Account to hold the number, and a dedicated phone number that can receive a voice call or SMS, is not sitting behind an IVR, and is not already registered to another WhatsApp account. Use a number nobody answers by hand.
Then you need that number provisioned on the WhatsApp Business Platform, Meta's Cloud API. Meta retired the older On-Premises API in October 2025, so Cloud API is the only supported route now. Some Zoho flows also consume Zoho's own messaging credits on top of what Meta charges, so check your plan before you assume the integration is free.
How to connect WhatsApp to Zoho CRM
Working inside Zoho CRM, the flow is roughly this. Open Setup, find Channels, and go to Business Messaging. Choose WhatsApp as the channel. Zoho will ask you to authenticate with Meta and select the WhatsApp Business Account and phone number you want to connect. Assign the channel so reps can see it, and map the number to the right users.
Once connected, a WhatsApp tab appears on lead and contact records. Reps send from there, replies come back into the record, and the thread is stored against that contact. Workflow rules can fire a template message when a stage changes, which is where the automation value starts.
For SalesIQ, you add WhatsApp as a channel in the SalesIQ settings, authenticate with Meta the same way, and then decide routing: which operators or departments receive WhatsApp conversations, and whether a bot handles the first response. If SalesIQ is already linked to Zoho CRM, conversations and visitor records tie back to the CRM contact automatically.
What actually syncs
Underneath both options is the same Cloud API webhook, so the data available is identical. Inbound messages arrive with the sender's WhatsApp display name and phone number, along with the message body, media, or interactive button reply. Status callbacks report whether each outbound message was sent, delivered, read, or failed. Template status and account quality events tell you when Meta is unhappy with a template before it gets paused.
Zoho matches the incoming phone number to an existing lead or contact and creates one if it does not exist. That matching is the whole point: without it, you have a chat app, not a CRM integration. It is worth cleaning your phone number formatting before you switch the channel on, because a contact stored as 555-0142 and a WhatsApp ID of 15555550142 will not match themselves.
One thing to plan for: history does not come with you
Integrations sync forward, not backward. Conversations that happened in the WhatsApp Business app before you connected the number stay in the app. And once the number moves to the Cloud API, its messages stop appearing in the app at all. Pick a cutover date, tell the team, export anything you genuinely need, and treat the integration as the start of a clean record.
What it costs in the United States
Calling the Cloud API is free. Since July 1, 2025, Meta bills per delivered template message, priced by the template's category rather than by conversation. Any reply you send inside the 24-hour customer service window, after the customer messaged you first, is free and does not use a template.
US teams need to know one more thing. Meta paused delivery of marketing category template messages to US phone numbers on April 1, 2025, and as of July 2026 there is no announced resume date. This is a platform-level restriction, so it applies through Zoho exactly as it applies everywhere else. Utility templates such as order updates, appointment confirmations, and quotes still deliver to US numbers. Authentication templates still deliver. Inbound conversations are untouched.
Practically, a US Zoho playbook is built around conversations the customer starts. Use click-to-WhatsApp ads or a website widget to get that first inbound message, answer free inside the window, and reserve templates for transactional moments. Where WhatsApp cannot open the conversation, email still can, so most Zoho teams pair the channel with a personalized email sequence for first touch and switch to WhatsApp once the prospect replies. Our WhatsApp Business API pricing page explains the per-message model in detail.
Common problems and what causes them
If the number will not register, it is almost always because it is still active in the WhatsApp Business app or attached to another WhatsApp Business Account. Delete it from the app first, wait, then register.
If messages send but never arrive, check the template status. A template pending review does not deliver, and a template that got rejected silently fails. If US recipients specifically are not receiving anything while other countries are, check the template category, because marketing templates to US numbers are paused.
If conversations are not attaching to the right record, the problem is phone formatting. Store numbers in E.164, meaning a plus sign, the country code, and the number with no spaces or dashes.
If you hit a daily wall around 250 unique customers per 24 hours, your Meta business verification is incomplete. Finish it.
Where to go next
Zoho's native channels are the fastest way to get WhatsApp onto a contact record, and for a sales team messaging known contacts they are usually enough. The limits show up when you want to send at campaign volume, segment a list, throttle delivery to protect your number's quality rating, or compare reply rates across template variants. That is a different job from a CRM inbox.
If you are weighing platforms generally, our guide to WhatsApp CRM integration covers the credentials, the webhook, and what syncs regardless of which CRM you use. HubSpot users should read the HubSpot WhatsApp integration page, since HubSpot's channel carries a 1,000 template per month allowance that Zoho does not impose the same way. And if the real question is how several people share one number without stepping on each other, start with WhatsApp Business multiple users.