How to connect WhatsApp, a CRM like Zoho or Kommo, and email
Many businesses use WhatsApp to sell, a CRM to stay organized and email for anything formal, but the three tools do not talk to each other. The result is familiar: data copied by hand, duplicate leads and follow-ups that depend on each person remembering.
Pick one source of truth
The first decision is not technical: where does the official record of each customer live? In most cases, in the CRM. WhatsApp and email are channels where the conversation comes in and goes out, but the contact, the deal stage and the tasks live in the CRM.
With that rule in place, every integration has a concrete job: bring into the CRM what happens in the channels, and trigger from the CRM what needs to happen next.
How the pieces connect
WhatsApp. Messages reach your own backend or an AI agent. There the person is identified, their record is looked up in the CRM and, if it does not exist, the contact is created with what they already said in the conversation.
The CRM. Zoho CRM and Kommo both have APIs, and that is what makes automation possible: creating and updating contacts, moving stages and assigning tasks. For Kommo I built my own MCP server, kommo-mcp, so AI agents can work directly on leads, pipelines and tasks.
Email. It works both ways: internal alerts when a lead comes in or a stage changes, and messages to the customer when the process calls for it. On this very site, the contact form first stores each message in a database and then sends it by email; if sending fails, the message is not lost. That order works for any integration: store first, notify second.
Between the pieces you can use a workflow tool like n8n or custom code. It depends on the volume, how much logic the process has and who is going to maintain it.
A real case: Nexus and Zoho CRM
Nexus is the clinical operations platform I built for OmniStem on Microsoft Azure. It follows the patient journey from quote through care plan, medical approval, billing and follow-up, and it syncs with Zoho CRM.
The sync keeps the team from maintaining two records side by side: what happens in operations is reflected in the CRM, with role-based access at every step. It also includes Connect, a passwordless patient portal that works with one-time codes.
The project was a full rewrite of a legacy PHP/MySQL application, and the CRM integration was designed as part of the platform from the start, not bolted on at the end.
Common mistakes
Connecting everything to everything without a source of truth, which creates duplicate contacts. Not keeping a record of what was sent and when. And trusting that an automation will never fail: you always need a way to spot what did not go out and try again.
If your data is spread across a phone, the CRM and an inbox today, start by drawing one customer journey from beginning to end. That drawing shows which connection saves the most work and where to begin.
Do you have a similar case?
Tell me how you work today and what you want to solve. Native Spanish; English (B2).