How to Integrate a CRM with WhatsApp

Almost every guide to this question skips the first decision and jumps straight to API setup. Do not. The integration you need depends entirely on which WhatsApp holds the conversations you want in the CRM.

• A brand number — a support line, an order-notification number, a sales line people message from your website. This is what the WhatsApp Business Platform exists for.
• An account you already use — the WhatsApp on your phone, or the WhatsApp Business app your team already runs, with years of threads and groups in it. The Platform has no view of this at all, no matter how it is configured.

Getting this wrong is the single most common wasted month in WhatsApp CRM projects: a team wires up the API, watches it work perfectly, and then realizes none of the relationships they cared about are in it — because those conversations never touched the API number.

This is the official, sanctioned route for businesses. Since the on-premises client was retired in late 2025, the Platform means Cloud API, hosted by Meta.

How you connect: you go through a Meta Solution Partner or Tech Provider, usually via Embedded Signup, which creates or attaches a WhatsApp Business Account (WABA) inside your Meta Business Portfolio and issues scoped API credentials. A Solution Partner extends a credit line and bills you for messaging; a Tech Provider supplies software while you pay Meta directly. Either way, a phone number is registered to the WABA and stops being usable in the consumer or Business app.

What it sees: conversations with that number, from the moment it went live.

What it never sees: every other account your team uses, every group chat, and every message that predates go-live.

The rules you design around: business-initiated messages must be pre-approved template messages in a category — marketing, utility, or authentication. Free-form replies are only allowed inside the 24-hour customer-service window that opens when the customer messages you. Billing attaches to delivered template messages, and messaging volume is tiered by business verification and quality rating.

When it is right: support queues, notifications, campaigns, and any multi-agent operation on a company number. For that job it is not just the best option, it is the only compliant one.

A second class of tool works with a WhatsApp account you already use — consumer WhatsApp or the WhatsApp Business app — and brings those threads into a shared inbox or a mainstream CRM.

What it sees: what that account holds, including group chats and one-to-one threads the API can never reach. Several of these tools support many numbers at once and push into HubSpot, Pipedrive, Zoho, or Salesforce.

What to weigh: this sits outside the Business Platform. That is a deliberate trade — you gain coverage the API does not offer and give up the guarantees of the sanctioned path. Read Meta’s terms, understand that unofficial integrations can put a number at risk, and make the decision explicitly rather than by accident.

When it is right: operations that genuinely run in groups, or teams who will not replace an existing CRM and just need WhatsApp threads to appear inside it.

The third approach is not an integration in the wiring sense at all. Instead of piping one number into a CRM you maintain, a messenger-native tool connects your messaging accounts once and the CRM assembles itself: contacts, conversation history, and the links between the same person on different apps.

What changes: there is no per-chat setup, no template to submit, and nothing for the other side to see or accept. There is also nothing to keep in sync, which matters more than it sounds — every bolt-on integration decays the moment someone forgets to route a conversation through it.

What it covers: the account you actually use, including the group chats and the history that predates the CRM decision.

This is the approach Pantheon takes. Connect your messaging and contacts and history build themselves, and because Pantheon is messenger-native rather than WhatsApp-only, the same connection covers Telegram and iMessage into the same record — so one person is one contact rather than three. Search runs across all of it at once.

One honesty note: Pantheon is in alpha. Telegram is live today; WhatsApp and iMessage run through the desktop app, with mobile incoming. Shared team inboxes and pipeline automation are not shipped.

There is no universally correct answer — there is a correct answer per job.

• Choose the Business Platform if the conversations belong to the company: a support line, notifications, campaigns, several agents on one number. Budget for template approval and design your outreach around the 24-hour window.
• Choose a third-party connector if the work happens in group chats or across many existing numbers and you are keeping your current CRM. Make the policy trade-off knowingly.
• Choose messenger-native capture if the relationships that matter are in an account you already use and you want the record to maintain itself across more than one messenger.

A useful test: if the integration only works when everyone remembers to use it, it will go stale. Bots, forwarding rules, and manual logging all fail that test. So does an API number that nobody outside marketing actually messages.

Many operators end up needing two of these — a Platform desk for the company number, and something covering the personal network. That is a legitimate outcome, and cheaper than discovering the gap after the fact.

WhatsApp anchors identity to a phone number, and phone numbers are less stable than CRMs assume. People change numbers when they change countries or jobs. Many carry two and use both with you. Display names are self-set. WhatsApp is now rolling out usernames so people can be reached without exposing a number at all — another handle attached to the same human.

If your integration keys on the phone number alone, you will accumulate duplicate records with the history split between them, and the split is invisible until someone searches and finds half a conversation. Before you commit, ask any vendor how they merge two numbers belonging to one person, and how they handle the same person appearing on a second channel. A CRM that cannot answer that is a message log, not a relationship record.