What does a Zoho CRM WhatsApp integration actually do?
It does two jobs: it records WhatsApp conversations on the right Zoho CRM record, and it lets Zoho send WhatsApp messages on its own when something happens in the CRM. Everything else, dashboards and routing included, is built on those two jobs.
Without an integration, WhatsApp lives on salespeople’s phones. A lead who writes on Monday and calls on Wednesday reaches a different person who has no idea what was promised. When a salesperson leaves, the chat history leaves with the phone. Managers can see calls and emails in Zoho but not the channel where most Indian buyers actually negotiate.
With a Zoho CRM WhatsApp integration in place, the inbound message from +91 98xxx lands on the lead with that mobile number. If no record exists, a new lead is created with source “WhatsApp”. When the lead moves to “Site visit booked”, a workflow sends the confirmation template with date, time and the owner’s name pulled from fields. When a deal sits in “Quotation sent” for three days, a reminder goes out automatically.
- Inbound: chats matched to leads, contacts or deals by phone number
- Outbound: approved templates sent from workflow rules or Blueprint steps
- Replies: agents answer from inside Zoho during the 24-hour window
- Routing: new chats assigned to an owner by your rules
- Reporting: response time and template results beside your pipeline
Three ways to set up Zoho CRM WhatsApp integration
You can use Zoho’s built-in Business Messaging channel, install an extension from Zoho Marketplace, or have a developer build a custom integration with Deluge and Meta’s Cloud API. Each one needs an official WhatsApp Business Platform number; none of them works with a personal WhatsApp or the free Business app.
The built-in route is the fastest and costs nothing extra on the Zoho side. Extensions add features such as shared inboxes and broadcast tools for a monthly fee. A custom build takes longer at the start but lets you decide exactly which module, stage and user each message belongs to.
A useful way to decide: list the five WhatsApp moments that matter in your sales process, for example “new enquiry”, “brochure sent”, “site visit confirmed”, “quote follow-up” and “won”. Then check which route handles all five without workarounds. If the built-in channel covers them, start there. If two of them need logic Zoho’s settings cannot express, custom usually wins.
Zoho CRM’s built-in WhatsApp Business Messaging: what it covers
Zoho CRM has its own WhatsApp channel under Setup › Channels › Business Messaging, and Zoho’s help documentation says it is available in the trial and all paid editions. Only an administrator can connect it, by logging in with the Meta business account that owns the WhatsApp Business Account.
According to Zoho’s help article, messages are sent to leads and contacts, templates can pull data from standard or custom modules, and approved templates can be added as actions in Workflow Rules, Blueprints, Journey Builder and Wizards. Customer-initiated conversations appear in a Messages module that stores conversations in order. During setup you assign WhatsApp profiles to users, groups or roles.
That is a solid base for many teams. Where people hit limits is usually the edges: sending from a deal-stage change when the deal’s contact is the recipient, applying custom routing when a lead writes in Tamil at 9 pm, logging chats into a custom module, or running several numbers for different branches with different rules. Test those edge cases in the trial before you decide.
Good fit
A single sales team, standard Leads and Contacts, a handful of templates and managers who mainly want visibility.
Weak fit
Complex deal pipelines, multi-branch routing, custom modules as the main record, or messages that depend on calculations across related records.
Zoho Marketplace WhatsApp extensions: when an extension makes sense
Choose an extension when you want a ready shared inbox, broadcast tools or chatbot features inside Zoho quickly and are comfortable paying a monthly fee to a third party.
Extensions are built by independent vendors and listed on Zoho Marketplace. Most connect to your WhatsApp Business Account through their own platform, which means messages pass through the vendor’s servers before reaching Zoho. That is normal, but you should know where chats are stored, for how long, and what happens to them if you cancel.
Before installing, ask each vendor the same questions and write down the answers. It saves arguments six months later when the bill or a limitation surprises you.
- Is the WABA created in my own Meta business portfolio or in yours?
- Do you add a charge per message, per user or both, on top of Meta’s rates?
- Which Zoho modules can send and log messages: deals, custom modules?
- Can workflow rules and Blueprint transitions trigger templates?
- Where is chat data stored, and can I export it if I leave?
- How are Zoho API credits consumed by your sync?
Custom Zoho CRM WhatsApp integration with Deluge and the Cloud API
A custom build uses Deluge, Zoho’s scripting language, to call Meta’s WhatsApp Cloud API directly from workflow rules, Blueprint transitions, buttons and scheduled functions, plus a small webhook receiver that writes incoming messages back into Zoho.
On the outbound side, a Deluge function reads the record, formats the phone number to international format, picks the template for the current stage and language, and sends it with the invokeurl task using a Zoho connection or a stored token. The Meta message ID returned by the API is saved on the record so later status updates can be matched.
Inbound is where custom builds earn their keep. Meta sends webhooks for new messages and delivery statuses. A receiver, hosted on your cloud account or on Zoho Catalyst, verifies Meta’s signature, looks up the phone number in Zoho, and writes the message to whichever place suits your team: a note, a related list, a custom “WhatsApp Messages” module or the deal timeline. Media such as photos of a site or a PDF of a quote are stored with a link.
Because the logic is plain Deluge and a short receiver script, your in-house Zoho admin or any Zoho developer can read and change it later. We document every function name and what triggers it.
How do you log WhatsApp chats against Zoho CRM leads correctly?
Match on a normalised phone number, decide in advance which record wins when several match, and store each message as its own entry, not as one growing text field. Those three rules prevent most of the mess teams see after a quick integration.
Phone numbers are the usual problem. Zoho may hold “98xxxxxxxx”, “+91 98xxx xxxxx” or “098xxxxxxxx”, while WhatsApp always sends the full international number. We add a hidden normalised field (for example 9198xxxxxxxx) populated by a workflow, and search on that. Without it, one buyer becomes three leads.
When the number matches both a lead and a contact, the usual rule is: open deal first, then contact, then lead. When nothing matches, create a lead with source “WhatsApp” and the first message in the description. When the same number belongs to two contacts, such as a husband and wife sharing a phone, log to the most recently active one and flag it for the owner.
- Normalise numbers to country code plus number, digits only
- Priority: open deal, then contact, then lead
- One record per message: direction, text, time, status, media link
- Keep Meta’s message ID to update sent, delivered, read and failed
- Never overwrite the lead owner from an inbound chat without a rule
Sending WhatsApp templates from Zoho lead and deal stages
Map each stage that deserves a message to one approved template, trigger it from a workflow rule or Blueprint transition, and fill the template variables from Zoho fields. Keep the list short; a message on every stage feels like spam.
Outside the 24-hour customer service window, WhatsApp only allows approved templates, so the wording is fixed at approval time and only the variables change. Plan variables around fields that are reliably filled: first name, owner name, appointment date, product, amount due. If a field can be empty, the Deluge function should either use a safe default or skip the send and alert the owner.
Blueprint is useful here because it enforces the order of stages. A transition such as “Visit done → Quotation sent” can require the quote PDF to be attached, then send the “your quotation” template with the file link. For deals, the recipient is the deal’s contact, so the function reads the related contact’s mobile number rather than the deal record. The table further down maps typical stages to templates and categories.
Owner assignment: who answers a new WhatsApp chat in Zoho CRM?
If the number belongs to an existing record, the record owner gets the chat. If it is new, apply one simple assignment rule and a fallback, and measure response time from the start.
Common rules we build: by territory using the pin code or city the lead mentions; by product line based on the ad or keyword that started the chat; by language, so a Marathi enquiry reaches a Marathi-speaking salesperson; and round robin among whoever is on shift. Zoho’s own assignment rules handle some of this for leads; custom Deluge handles the rest, such as time-based rules.
A fallback owner matters more than the clever rule. If the assigned person does not reply within, say, 15 minutes during working hours, the chat moves to a team lead and a task is created. Outside hours, an approved auto-reply sets expectations. Response time then becomes a field you can report on, which is often the most useful number a sales manager gets from the whole Zoho CRM WhatsApp integration.
The 24-hour window and template categories inside Zoho
When a customer messages you, a 24-hour window opens in which your team can reply freely; outside it, only approved templates can start the conversation. Zoho’s help docs describe the same rule inside the CRM.
Templates are categorised by Meta as marketing, utility or authentication. Zoho’s help article describes utility messages as related to an ongoing, suspended or completed transaction, such as an order confirmation or payment failure notice, and marketing messages as promotional, such as offers or reminders to continue. Meta’s pricing page states that utility templates delivered inside an open customer service window are free and that pricing is per delivered template message.
In practice that means timing matters. If a lead replies “yes, send details” at 11 am, send the brochure and quote as free-form replies before 11 am next day. After that, you need a template again, and it will be billed. We often add a Zoho field showing when the window closes, so salespeople can see it on the record.
Opt-in and opt-out rules for Zoho CRM WhatsApp messaging
Only send templates to people who have agreed to hear from your business, and stop when they ask you to. Meta’s opt-in guidance says the business must clearly state that the person is opting in to receive communication and must name the business, and that opt-out requests should be honoured.
In Zoho, that becomes two fields and one rule. A “WhatsApp opt-in” checkbox with a date and source (web form, click-to-WhatsApp ad, in-person) is set when consent is captured. A “WhatsApp opt-out” flag is set when someone replies STOP or asks not to be messaged. Every Deluge function that sends a template checks both fields first.
Imported leads from old spreadsheets or purchased lists are the risk. Do not bulk-message them from Zoho just because the numbers are there; poor feedback can hurt the number’s quality and messaging limit. For data-protection obligations in India, take your lawyer’s advice on wording and retention; we build the fields and checks, not the legal policy.
How much does Zoho CRM WhatsApp integration cost in India?
Expect three costs: Zoho CRM licences you probably already pay, Meta’s per-message charges for templates, and either an extension subscription or a one-time custom build. For custom work, BtechWaleTech starts at ₹40,000.
Meta charges for delivered marketing, utility and authentication templates at rates set per country, with volume tiers for utility and authentication. Service replies inside the 24-hour window are free, as are utility templates delivered in an open window. That is why a good Zoho CRM WhatsApp integration nudges salespeople to reply quickly: a conversation kept alive costs less than one restarted with templates.
Extension pricing varies widely by vendor, usually per user or per message volume, and it recurs. A custom build costs more in month one but has no per-user subscription; afterwards you pay Meta and, optionally, maintenance from ₹8,000/mo once the two free months end. Over a year, teams with many users often find custom cheaper; teams with two users often find an extension or the built-in channel cheaper. See the cost table below and our Meta pricing explainer.
Zoho API credits and limits a WhatsApp integration must respect
Every search, update and insert your integration makes uses Zoho CRM API credits, which are counted over a rolling 24-hour window. A chatty integration on a small edition can run out, so design the sync to use as few calls as possible.
Zoho’s developer documentation lists base credits of 50,000 plus a per-user amount that depends on edition: 250 per user on Standard, 500 on Professional and 1,000 on Enterprise, with caps of 100,000, 3,000,000 and 5,000,000 respectively. Most calls cost one credit; inserts and updates cost one credit per ten records. Zoho also limits concurrent calls: 10 on Standard, 15 on Professional and 20 on Enterprise.
We keep outbound sending in Deluge close to the record and batch inbound writes where we can. For a team receiving a few hundred chats a day, credits are rarely an issue; for thousands of messages plus delivery statuses, we log statuses in bulk rather than updating the record on every “delivered” and “read” event.
How long does a Zoho CRM WhatsApp integration take?
A built-in or extension setup can be running in days; a custom Zoho CRM WhatsApp integration usually takes two to four weeks, including template approval and a pilot with real salespeople.
Week one: map your stages, write template text, submit templates to Meta, add the normalised phone field and consent fields in Zoho. Week two: Deluge functions for outbound templates, the webhook receiver for inbound chats, and owner rules. Week three: pilot with two or three salespeople on live leads, fix edge cases like shared numbers and missing fields. Week four, when needed: reports, extra numbers or a data clean-up of duplicate leads.
The slowest step is often internal: agreeing what each stage means and who owns which leads. Settle that first and the build moves quickly.
Mistakes that break a Zoho CRM WhatsApp integration
Most failures come from data and process, not code. These are the ones we see most often when we are asked to fix an existing setup.
- Using a salesperson’s personal WhatsApp through unofficial tools, which risks a ban and loses history when they leave
- No phone normalisation, so every chat creates a duplicate lead
- Templates on every stage change, leading to blocks and a lower quality rating
- Access tokens pasted into client scripts visible to every user
- Delivery statuses written one call at a time, burning API credits
- No fallback owner, so night-time chats wait until someone notices
- No opt-out flag, so people who said STOP still get reminders
If your current setup shows several of these, a short audit before any new build usually saves money. We can review it as part of CRM development work and tell you which parts to keep.
Worked example: a hypothetical solar installer in Ahmedabad
Say a rooftop solar installer in Ahmedabad gets leads from click-to-WhatsApp ads, its website and phone calls, and uses Zoho CRM with stages from “New” to “Installed”. Chats sit on four salespeople’s phones, and follow-ups after site surveys slip. This is an illustration of the decisions, not a real client or result.
We would first test Zoho’s built-in channel against their five key moments. Suppose it handles lead follow-up well but cannot route Gujarati-speaking leads to the two Gujarati-speaking salespeople or send the quotation PDF from a deal stage. That tips it towards a custom build.
The custom Zoho CRM WhatsApp integration would add a normalised phone field and consent fields, a language field set from the first message, and Deluge functions for three templates: survey booked (with date and surveyor name), quotation ready (with the PDF link) and “installation date confirmed”. Incoming chats go to a custom WhatsApp Messages module linked to the lead or deal. New chats are routed by language, with a 15-minute fallback to the sales head.
After a month the installer’s own Zoho reports would show first-response times, how many surveys converted to quotes, and which templates were read. Those numbers, not guesses, decide what to add next.
Zoho CRM WhatsApp integration for teams across India
Zoho CRM is common among Indian SMEs and mid-sized companies, and WhatsApp is where their buyers reply. We work remotely with sales teams everywhere; the setup does not need anyone on site.
Manufacturers and exporters in Ahmedabad, Vadodara and Ludhiana use it for dealer and distributor follow-ups. IT services and SaaS firms in Chennai and Noida want demo reminders from deal stages. Real estate and education teams in Nagpur, Bhopal and Chandigarh need site-visit and counselling confirmations. Healthcare and travel businesses in Thiruvananthapuram and Guwahati often need templates in a regional language alongside English.
Talk to us in English or Hindi on WhatsApp; you get an itemised quote in about two working days.