WhatsApp CRM Integration: Integrate WhatsApp With Your CRM
Your reps close deals on WhatsApp, then that history dies on someone's phone. WaBulkSend connects WhatsApp to your CRM through the official Cloud API, so every message, reply, and delivery status lands on the right contact record and triggers the next step in your pipeline.
Free for your first 500 messages a month. No card required.
Conversation sync
Live webhookThe short answer: WhatsApp CRM integration connects a WhatsApp business number to your CRM through the WhatsApp Business Platform (Cloud API), so inbound messages, outbound replies, and delivery statuses are written automatically to the matching contact record. The free WhatsApp Business app has no public API and cannot do this. You need a WhatsApp Business Account, a dedicated phone number, a phone number ID, an access token, and an HTTPS webhook that receives message events. Once that webhook is live, your CRM can log the full conversation thread, create and update records, assign tasks, and fire follow-up automations without anyone copying and pasting a chat.
Last updated July 2026
Why WhatsApp needs to live inside your CRM
Sales teams already run on WhatsApp. A prospect asks a quick question, a rep answers from their phone, a price gets agreed, and none of it exists anywhere your business can see. When that rep leaves, the relationship leaves with them. When a manager asks why a deal stalled, nobody can reconstruct the conversation. The pipeline says one thing and the phone says another.
Integrating WhatsApp with your CRM fixes the record-keeping problem and then does something more useful: it makes WhatsApp a channel your automations can actually use. A message arrives, the CRM matches it to a contact by phone number, logs it on the timeline, moves the deal stage, and assigns a task to the owner. An outbound utility template goes out when an order ships, and the delivery receipt writes back to the record. Nobody retypes anything.
The technical requirement is straightforward. The WhatsApp Business app on a phone has no public API, so it cannot connect to a CRM. Integration runs on the WhatsApp Business Platform, Meta's Cloud API, which is what WaBulkSend uses. Meta retired the older On-Premises API in October 2025, so Cloud API is the only supported path today. You get a webhook that streams every message event and status callback, and an endpoint to send from. That is the whole foundation.
How to integrate WhatsApp with your CRM in six steps
From a bare Meta Business account to conversations syncing onto contact records.
Set up the WhatsApp Business Account
Create a Meta Business account and a WhatsApp Business Account, then verify the business. Verification is one of the ways you move past the starting messaging limit of 250 unique customers per rolling 24 hours.
Register a dedicated number
Use a phone number that can receive a voice call or SMS and is not already tied to another WhatsApp account. A Meta Business Account starts with 2 registered numbers and can be raised to 20, so departments can each have their own.
Get the credentials
Meta issues a phone number ID and an access token. Those two values authenticate every call your CRM makes to the Cloud API when it sends a message.
Point the webhook at your CRM
Subscribe an HTTPS endpoint to message and status events. Inbound texts, media, button replies, and sent, delivered, read, or failed receipts all arrive here in real time.
Map contacts and automate
Match the incoming wa_id to a CRM contact by phone number, create one if it is new, write the message to the timeline, then trigger the follow-up: assign an owner, move a stage, open a task.
Route the humans
Anything the automation cannot answer lands in a shared team inbox with an owner, so a real person picks up with the full history in front of them instead of asking the customer to repeat.
What actually syncs between WhatsApp and your CRM
The Cloud API webhook delivers these events. Everything below can be written to a contact, deal, or ticket.
| Event | What you get | Typical CRM action |
|---|---|---|
| Inbound message | Text, image, document, location, contact card, or interactive button reply | Log to the contact timeline, create the contact if new |
| Contact profile | WhatsApp display name and wa_id (the phone number) | Match or create the record, fill the phone field |
| Status callback | Sent, delivered, read, or failed, with a timestamp | Update the message record, retry or alert on failure |
| Outbound template | Confirmation the template was accepted and delivered | Mark the sequence step complete, advance the stage |
| Template quality | Quality rating changes and template status updates | Flag a template before Meta pauses it |
| Account alerts | Messaging limit tier and account quality changes | Warn ops before sending volume gets capped |
CRM integrations US teams ask for most
Connect through a native channel where one exists, or through the Cloud API and a webhook where it does not.
HubSpot
HubSpot ships a native WhatsApp channel for the Conversations inbox on Marketing Hub or Service Hub Professional and Enterprise. It logs chats to contacts and triggers workflows, with a shared cap of 1,000 template messages a month.
HubSpot WhatsApp integration →Zoho CRM
Zoho has first-party WhatsApp business messaging inside the CRM under Business Messaging, plus a WhatsApp channel in Zoho SalesIQ for a unified chat inbox. Both need a WhatsApp Business API account behind them.
Zoho WhatsApp setup guide →Pipedrive
No first-party WhatsApp channel. Connect through the Cloud API and a webhook that creates activities and notes on the deal, or through the marketplace apps that wrap the same API.
WhatsApp CRM →Salesforce
Service Cloud ships a native Enhanced WhatsApp Channel through the Messaging add-on, and Marketing Cloud sells WhatsApp separately. Large orgs often wire the Cloud API straight into Leads, Cases, and Opportunities instead, using Flow to route ownership.
Salesforce WhatsApp integration →Your own CRM
Anything that can accept an HTTPS POST can take the WhatsApp webhook. Receive the event, match the phone number, write the record, and send replies back through the Cloud API messages endpoint.
WhatsApp API integration →Spreadsheets and no CRM yet
If contacts still live in a sheet, start by sending from that list and capturing replies in a shared inbox. Move to a CRM once the conversation volume justifies it.
Send from Excel →Why the free app cannot integrate with a CRM
This is the single thing most teams get wrong before they start.
| Capability | WhatsApp Business app | WhatsApp Business Platform (Cloud API) |
|---|---|---|
| Public API to connect a CRM | None | Yes, REST endpoints plus webhooks |
| Conversation logged to a contact record | No | Yes, every inbound and outbound message |
| Users on one number | One phone plus up to four linked devices | Unlimited agent seats in a shared inbox |
| Assign a chat to an owner | No, every linked device sees every chat | Yes, with routing and roles |
| Trigger a CRM workflow from a message | No | Yes, from the webhook event |
| Send from an automation or a deal stage | No | Yes, via the messages endpoint |
| Cost | Free | Free to call, per delivered template message |
What teams do once WhatsApp is in the CRM
Capture the lead automatically
Someone messages the business number for the first time. The webhook fires, the CRM creates the contact with their WhatsApp name and number, tags the source, and assigns a rep.
Never lose the deal history
Every WhatsApp exchange sits on the deal timeline next to the emails and calls. A rep taking over a territory reads the thread instead of guessing.
Trigger from a stage change
A deal moves to Proposal and a utility template goes out with the quote. The delivery receipt writes back, so you know it landed and was read.
Follow up without a human
No reply in two days? The CRM fires the follow-up sequence, and stops it the moment the contact answers, because the inbound event cancels the step.
Order and delivery updates
Your store or ERP updates a record, the CRM sends the shipping notification on WhatsApp, and support sees it on the customer timeline when they call.
Give the whole team one number
Sales, support, and billing all work the same business number from a shared inbox, each seeing only the conversations assigned to them.
What US teams need to know before they wire it up
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. That does not block a CRM integration, and it does not stop the workflows most sales teams actually want. Utility templates, such as an order update, an appointment confirmation, or a quote, still deliver to US numbers. Authentication templates still deliver. Any reply you send inside the 24-hour customer service window, after a customer messages you first, is free and needs no template at all.
Practically, that means a US CRM integration should be built around conversations the customer starts, plus utility messages tied to a real transaction. Click-to-WhatsApp ads still work as a way to get people to message you first, which opens that free window. Design the automation so an inbound message opens the door and your templates carry transactional information, not promotions.
On billing, Meta moved from per-conversation to per-message pricing on July 1, 2025. You pay when a template message is delivered, priced by the template's category, and service messages inside the open 24-hour window are free. Calling the API itself costs nothing. See the full breakdown on our WhatsApp Business API pricing page.
Frequently asked questions
Can WhatsApp be integrated with CRM?
Yes. WhatsApp integrates with a CRM through the WhatsApp Business Platform, also called the Cloud API. You register a business phone number, get a phone number ID and an access token, and subscribe an HTTPS webhook to message events. Your CRM then logs every inbound and outbound message on the contact record and can send replies back through the API.
How do I integrate WhatsApp with my CRM?
Create a Meta Business account and a WhatsApp Business Account, verify the business, register a dedicated phone number, and collect the phone number ID and access token. Point a webhook at your CRM to receive messages and status callbacks, match the incoming phone number to a contact, and send outbound messages through the Cloud API messages endpoint. WaBulkSend handles this setup for you.
Does the WhatsApp Business app have an API for CRM integration?
No. The free WhatsApp Business app has no public API, so it cannot be connected to a CRM. It is built for a single business owner on a phone with up to four linked devices. Any real CRM integration, including conversation logging and automation, requires the WhatsApp Business Platform Cloud API.
Which CRM works best with WhatsApp?
HubSpot and Zoho CRM both ship first-party WhatsApp channels, so they are the fastest to connect. HubSpot requires Marketing Hub or Service Hub Professional or Enterprise. Salesforce, Pipedrive, and custom CRMs connect through the Cloud API and a webhook, which gives you more control over what gets logged and when automations fire.
Is WhatsApp CRM integration free?
Calling the WhatsApp Cloud API is free, and replies you send inside the 24-hour customer service window cost nothing. You pay per delivered template message, priced by category. Your CRM may also charge for its messaging add-on. HubSpot, for example, includes a shared allowance of 1,000 template messages a month across connected WhatsApp accounts.
Can I sync my old WhatsApp chats to a CRM?
Generally no. Integrations sync messages from the moment the connection goes live, not historical threads. HubSpot states plainly that existing WhatsApp conversations do not import. Plan the switch on a date, export anything critical beforehand, and treat the integration as the start of a clean record.
Will messages still show in the WhatsApp app after I connect a CRM?
Not on the same number. Once a phone number is registered to the Cloud API, it leaves the WhatsApp Business app and its messages route to your API endpoint instead. HubSpot warns about this too. Use a dedicated number for the integration and keep any personal or in-store number separate.
How many phone numbers can one WhatsApp Business Account have?
Meta Business Accounts are initially limited to 2 registered business phone numbers, and that limit can be raised to 20. A Meta Business Account is also initially limited to 20 WhatsApp Business Accounts, and each WhatsApp Business Account holds a maximum of 250 message templates. That is enough for sales, support, and separate brands to each run their own number under one CRM integration.
Put every WhatsApp conversation on the contact record
Connect your CRM to the official WhatsApp Cloud API and stop losing deal history to someone's phone. Free for your first 500 messages a month, no card required.
Start Free Today