Start your Zoho CRM WhatsApp integration with one business number, one test sender, and a named person responsible for replies. A connected account is only the first check. You also need to prove that an inquiry reaches the right record and produces a next step.
Use the native route below as your starting point. Keep a worksheet of the settings you choose and the results you observe before opening it to the wider team.
Choose native WhatsApp or a provider route
Zoho documents a native WhatsApp Business integration. This walkthrough follows that route. A provider extension is a separate choice with its own configuration and support.
For either route, verify these requirements:
- The CRM modules you need for new and existing senders.
- Who can see conversations and send messages.
- How templates, replies, and failures become visible.
- How the route identifies an existing customer.
- Who owns external account administration and CRM follow-up.
Do not assume a provider's bot features are included in the native integration. If you need a WhatsApp bot, document its input, its handoff to a person, and the CRM fields it must populate. Verify the bot separately before relying on it.
For another messaging channel, compare the Twilio SMS setup checklist. Passing an SMS test does not establish WhatsApp behavior.
Check prerequisites and connect the business account
An administrator must initiate native setup. Zoho lists a verified business, a WhatsApp Business account, and an eligible registered number as prerequisites.
- Identify the administrator and the business account owner.
- Confirm the business, account, and number meet the current requirements.
- Open Setup > Channels > Business Messaging.
- Follow the current authorization screens for the intended business.
- Review the connected account and number before proceeding.
- Record who can maintain the connection if the original administrator leaves.
The business account owner should complete any external verification or authorization. Never send account passwords or tokens through a shared setup worksheet.
Check module availability in your live account. The help page contains both broader module coverage and an older lead/contact-only note. That conflict is a reason to verify your destination rather than publish a universal module limit.
If you need several WhatsApp numbers, check the current help docs and your account's setup options. Do not assume that proving one number works proves that another number can be added under the same configuration.
Map incoming senders and assign an owner
Zoho's documented setup allows incoming senders to map to CRM fields and be assigned to users, groups, roles, or an assignment rule.
Write down the intended destination and the fields you require. Include the incoming number, sender name if available, inquiry source, and the evidence your team uses for qualification. Treat missing information as a review case.
Test a sender whose number already belongs to a CRM record. Confirm which record receives the conversation. Then test an unknown sender and inspect the resulting destination. Do not infer matching behavior from the appearance of a phone field.
Use a routing worksheet:
| Case | Intended result |
|---|---|
| Existing customer | Correct existing record and responsible owner |
| New qualified inquiry | Agreed destination and territory owner |
| Missing routing information | Fallback person who will review it |
| Ambiguous number | Review before linking or creating another record |
Use assign new leads to prepare the CRM ownership work. Check contacts without email or phone for records that need attention before testing.
Create and test an approved message template
Saving a native message template submits it for Meta review. Zoho documents that approved templates can be used in CRM automations.
Draft a narrow message for your pilot, such as a response to an agreed inquiry. Review its text and any merge values using a test record. Confirm that missing names or other empty fields will not produce confusing text.
Check approval status before using the template. A saved draft is not evidence that it is ready for automated use.
Send to a consenting test recipient through the documented route. Record the sending user, destination record, template, and test time. Ask the recipient to confirm what arrived.
Locate the resulting conversation or message history in your account and note the exact CRM location. The pilot should establish where your team can inspect it; do not assume every route uses the same related list.
Reply from the test phone and verify that the assigned person can find the response.
Let the AI Assistant configure follow-ups
The Zoho CRM AI Assistant can set up the CRM routing, fields, layouts, views, and follow-up rules you request. It can inspect CRM message evidence and identify inquiries that still need attention. It waits for approval before changing the CRM messaging configuration and records.
Give it a bounded request:
Review our WhatsApp pilot records. Propose sender mappings, a fallback owner, and a view of qualified inquiries awaiting a reply. After approval, configure the CRM rules and create an owned follow-up task for each eligible unanswered inquiry. Show which records were included and why.
Define “unanswered” before creating tasks. Specify what counts as a response, where the evidence lives, and when an inquiry should leave the list. If the chosen route does not expose the required evidence, use a reviewed manual status until that gap is resolved.
Use leads without a first response to review the CRM backlog. The assistant can also build reports or Deluge functions inside CRM when your design needs them. It does not operate the external business account or a third-party bot.
For audience preparation across channels, see the Mailchimp integration guide. Keep subscription and reply rules specific to each channel.
Run the launch checklist and troubleshoot
Repeat the pilot as a normal salesperson, not only as the administrator. If some users cannot access chats, compare their intended access with the working test user's configuration before changing permissions.
Test a known number, an unmatched number, a reply, a missing routing value, and a record that should not trigger a task. Confirm that repeating an event does not create unwanted follow-ups.
If automation fails, inspect the source record and rule evidence with why a workflow did not run. Separate a missing message from a message that arrived but never received an owner.
How much will messages cost? Check current charges, available credit, and the applicable billing terms in the live account before launch. The help page includes potentially dated conversation-pricing language, so an old rate is not a reliable budget.
Widen usage only when the team can find messages, answer them, and explain each follow-up task. Assign someone to review exceptions and recheck the connection after configuration changes.