· By the AgentSDR team
The short answer
You connect WhatsApp to a CRM in one of four ways: the CRM’s own integration, a WhatsApp inbox tool that links to the CRM, Zapier or webhooks, or a CRM that has WhatsApp built in. Pick by testing that a reply lands on the right contact, then check limits, opt-out and call recording.
This guide is written by the AgentSDR team, and AgentSDR is of the fourth type, so weigh our view accordingly. For tools compared side by side, see best WhatsApp CRMs. For pacing a new number safely, see WhatsApp for B2B outreach.
What are the ways to integrate WhatsApp with a CRM?
| Route | How it works | Watch for |
|---|---|---|
| 1. The CRM’s own integration | The CRM vendor connects to WhatsApp and shows conversations on the contact | Which connection type it needs, what it logs, and which plans include it |
| 2. A WhatsApp inbox tool with CRM links | The inbox tool owns the conversation and syncs contacts or notes to your CRM | Two places to work, and what exactly syncs back |
| 3. Zapier or webhooks | Events such as a new message trigger a record update elsewhere | Gaps and delays when a step fails, and matching a phone number to the right contact |
| 4. A CRM with WhatsApp built in | The same product holds the CRM and the WhatsApp connection | You adopt that CRM, so migration of your existing records matters |
Underneath all four sits a connection to WhatsApp. It is either Meta’s WhatsApp Business Platform, with its templates, opt-in rules and 24-hour customer service window, or a linked number connected by QR code, with no templates and a ban risk if you start too many chats. The two behave differently inside any CRM. Our best WhatsApp CRM guide compares them.
What about HubSpot and Zoho?
Many searches for a WhatsApp integration name one of these two CRMs. We do not describe either vendor’s own WhatsApp feature here, because we could not confirm one from their own pages on the day we wrote this. Check HubSpot’s and Zoho’s current documentation, and ask which connection type it requires.
What we can say from other vendors’ own sites is that route 2 exists for both. WATI’s homepage lists integrations with Salesforce, Zoho CRM and HubSpot, and respond.io’s homepage lists HubSpot, Salesforce, Zoho, Odoo, Pipedrive and Zapier. Ask any such vendor what a sync writes to your CRM: a contact, a note per conversation, or each message.
What should you check before you integrate?
| Check | Ask |
|---|---|
| Inbound replies | Does each reply appear on the contact record, with time and sender, without a rep copying it? |
| Outbound from a phone | If a rep answers on the phone or in WhatsApp Web, is that logged too? |
| Contact matching | How is a phone number matched to a person, and what happens with duplicates or numbers in different formats? |
| Sending limits | Are warm-up, daily new-chat caps and gaps between sends enforced on the server, or only suggested? |
| Opt-out | Does a stop request mark the person Do Not Contact, and does every send check it? |
| Calls | Can you place calls, are they recorded, and do the recording and transcript sit on the record? |
| Connection type | Official API with templates, or a linked number? What does that mean for first messages? |
| Ownership | Where is the data stored, and can you export it? |
Do replies land on the contact record?
This is the check that matters most. A sales team works from the CRM, so a reply that stays in a separate inbox is a reply that gets answered late. Send a test message from a second phone and watch where it appears. Then reply from the CRM, then reply from your own phone, and see whether both are logged and labelled by sender. An integration that logs only the first message or a daily digest will lose context.
Does the integration enforce sending limits?
On a linked number, WhatsApp can ban a number that starts many chats with people who do not have it saved, so limits are a safety feature. Ask whether the tool enforces them where it cannot be bypassed, and whether they apply to every route a message can take: manual replies, automated sequences and call follow-ups. If you use Meta’s official API instead, the equivalent controls are Meta’s own templates and window rules, described in Meta’s send messages documentation.
How does opt-out reach WhatsApp?
Meta’s documentation says businesses are required to obtain opt-in before messaging people on WhatsApp, and that users can stop marketing messages from a business. Whatever tool you use, a person who says stop has to become unmessageable everywhere. If your CRM holds the opt-out flag but the WhatsApp tool does not read it, the next sequence step will go out anyway. Test this directly: mark a test contact as opted out and try to send.
What about recording calls?
Many places require every party to consent before a call is recorded, so tell people. Check that a recording is stored in a place you control, that a transcript is attached to the same contact, and that access is not public. If the integration cannot call at all, decide whether your reps will call from a phone and log by hand.
How does AgentSDR connect WhatsApp to the CRM?
AgentSDR avoids the integration by keeping WhatsApp inside the CRM. It is an open-source (MIT) AI CRM you host yourself, and it uses linked numbers, not Meta’s official API. Here is how it answers the checklist.
- Numbers. You link a number in Unipile by scanning a QR code, then sync it into AgentSDR (see the Unipile integration). The alternative is a cloud calling station, which is one WhatsApp number kept open in a browser profile on a worker, and which sends and receives messages on its own.
- Replies.A reply from a lead you know by phone lands in the CRM on a WhatsApp conversation, like LinkedIn replies do. Each message has an origin: the lead, AgentSDR, or the phone, meaning something a rep typed on their phone or in WhatsApp Web. A phone message counts as answering the lead. The reply is classified into your stages, and the stage’s sequence drafts the answer. A person sends it by default.
- Limits. Every WhatsApp send passes the same server-side checks under a per-number lock. The defaults are 24 hours without new chats after linking a number, 25 new chats a day per number, and 10 seconds between sends. They are Sending rules you can change.
- Opt-out.A message to a Do Not Contact lead is always refused, and marking someone Do Not Contact stops every channel for that person. A reply on any channel stops that person’s open WhatsApp campaign enrolments.
- Calls. AgentSDR places WhatsApp calls through WhatsApp Web, records them to your own Cloudflare R2 bucket, transcribes them with the model you choose and keeps the result on the lead. Recordings play through short-lived links only.
- Other systems. A public API and an MCP server let other applications and AI assistants work the CRM. We do not claim ready-made connectors to other CRMs.


