How to Integrate a CRM with WhatsApp

Write down the phone number the customer actually messages, who owns it, and which account currently receives the thread. This prevents a common implementation error: a marketing manager connects a fresh Platform number to a CRM while all the useful founder and BD conversations remain on other phones. WhatsApp describes the Business app and Platform as distinct products. HubSpot’s channel documentation adds a useful reality check: its WhatsApp integration rejects a personal account and syncs only new messages after connection. A successful onboarding screen therefore proves that a number is connected, not that the CRM contains the relationships you meant to record.

Pick four test conversations before creating an account: a new customer inquiry, an old one-to-one deal chat, a group where a partner made an introduction, and a customer who has changed numbers. For each, say what the CRM must do: display the message, attach a contact, assign an owner, trigger a reply, or preserve a source link. An agency may only need a client approval logged; a retailer may need a team queue and order update; a crypto BD lead may need the group introduction. This small inventory will tell you whether the official API, a provider, a linked account, or a manual export can answer the actual question.

The Business Platform is the official API route for company-number messaging, with templates and opted-in outreach. A Business Messaging Partner or CRM vendor can package that API with an inbox and onboarding. Linked-account software works from an account already in use, subject to that vendor’s capabilities and WhatsApp’s terms. Export chat produces a text file for a selected thread, useful when a live integration is unnecessary. These are different data paths. The official API does not turn a personal account into a company help desk; an export does not update as new messages arrive.

As of November 2026, ask every provider for its exact connection type and the permissions it receives. Do not classify it from a logo on a marketplace card. A vendor may say “WhatsApp integration” while meaning only a Platform number registered to a WhatsApp Business Account. Another may offer coexistence with an existing Business app number but no historical sync; respond.io documents precisely that combination. The choice should follow the conversation and the action you need, not the impression that one route is universally more mature.

A team with developers can connect a company number to the WhatsApp Business Platform, receive inbound events, and write the resulting contact or message to its CRM. WhatsApp’s Platform feature page describes customer-initiated replies, template-based outreach after opt-in, media messages, and interactive responses. The technical build must still decide which phone number maps to which CRM contact, how duplicate inbound events are handled, and which agent owns a case. For example, a bike shop’s order number and customer number can attach an inbound “where is my repair?” to the right service record. The API connection itself does not know the repair status.

The practical setup starts with the company’s Meta business assets and a registered number. If the company already uses Salesforce, its Unified WhatsApp setup shows the account and number connection, including a Business Portfolio selection and number verification. If it builds directly, it needs developer resources for API calls and webhook handling; WhatsApp’s business FAQ distinguishes the app from the Platform, while its current Platform pages describe the API’s purpose. Test one inbound message from a separate customer phone, inspect the event and CRM contact, send a permitted reply, and verify the customer sees the expected business name and number. Only then add automation.

A provider can shorten the work by supplying a team inbox, embedded onboarding, billing support, and CRM mapping. This is attractive to a small service team without an API engineer. It also introduces a second set of rules: the vendor’s plan, history limits, permissions, and exit path. For instance, HubSpot’s setup says to open Settings → WhatsApp → Connect a WhatsApp phone number → Continue with WhatsApp, then choose business assets in Meta’s window. It specifically warns that old conversations do not sync and that connected messages will no longer appear in the WhatsApp mobile or web app for its documented route. A support lead should know that before moving the public service number.

Zoho CRM puts WhatsApp Business messages beside Leads and Contacts and can enable selected custom modules; its template workflow starts at Setup → Automation → Actions → WhatsApp Notification. Salesforce’s Unified WhatsApp instructions use Setup → Your Numbers → Add Number and a WhatsApp Business Account connection. These are examples, not interchangeable menu paths. Make the buyer test a real customer request, a handoff from one agent to another, and a reply after a shift change. Ask how the provider preserves message context if you change CRM vendors later and whether the company owns its WhatsApp Business Account.

A founder may need the conversations on a phone they already use, rather than a new service line. A linked-account product may capture messages from that account and build a record, but its scope depends on the vendor, device, and account type. Ask for an explicit demonstration of old one-to-one history, new messages, a group, media, and replies using the actual number. A tool that shows a new test DM but no past group does not solve a BD lead’s relationship history. Check what happens when the linked host is asleep, a phone is replaced, or the account is reauthorized.

The WhatsApp Business app has a distinct coexistence route with some API providers. Trengo describes keeping the Business app active while its API inbox handles team workflows; it cautions that group messages and some message types may not appear there. Respond.io’s October 2026 guide says its setup does not sync previous contacts or messages. Those are provider-specific descriptions; require a live test for the provider you choose. For a personal account, do not assume coexistence applies. Read WhatsApp’s consumer terms and ask the linked-account vendor to explain its access method and how it handles policy changes before relying on a valuable number.

Sometimes the job is narrow. An account manager may need to put an approved scope change into a client file, not launch a permanent messaging integration. On Android, WhatsApp’s Export chat guide gives More options → More → Export chat, then a choice with or without media. Save the output securely, check that the approval and date are present, and attach it to the CRM record only if your organization’s data rules permit it. On iPhone, use the chat’s Export Chat action and inspect the result. The export is not a backup and WhatsApp says it cannot be imported back into the app.

A snapshot demands maintenance. If the client changes the scope again on Tuesday, Monday’s export does not update. Write the latest decision and next step in the CRM, then repeat the export only where preservation is needed. This route is honest for a handful of relationships but becomes laborious when dozens of new conversations arrive daily. It also means the CRM will not automatically answer “who replied overnight?” The backup guide covers phone recovery; export is for a readable record of a chosen conversation.

On the Platform, free-form service replies are allowed inside the 24-hour customer service window, which opens and resets with a user message. Outside it, the Business Messaging Policy requires an approved Message Template. The same policy says you may contact people only after they supplied a mobile number or username and opted in to subsequent messages or calls; stop requests must be honored. A visitor who sends “is my order ready?” can receive a service reply. A store that wants to send a promotion next month needs a suitable approved marketing template and a valid opt-in. One customer question is not blanket consent to every later campaign.

Create templates for actual use cases: a nonpromotional order update, a scheduled appointment reminder, or a marketing offer. WhatsApp’s pricing page explains marketing, utility, authentication, and service categories. Zoho’s template instructions show that it submits templates to Meta for review and only lets approved messages be sent. Store the consent source and category in the CRM so an agent can explain why a person was contacted. If the business has automated replies, provide a clear route to a human as the policy requires during the service window. Test a template after the window closes; a reply that works at hour two does not prove the hour-thirty flow.

Meta’s current Platform pricing says charges are based on delivered messages, recipient market, and message category. Service messages are free, and utility messages in response to users are free under the conditions shown. It lists volume tiers for utility and authentication messages and a 72-hour free entry point when a person writes through a qualifying ad or Facebook Page call-to-action button. The rate selector is market-specific. As of November 2026, build a budget from your countries, category mix, and delivered volume rather than quoting an old “per conversation” price or a universal dollar amount.

Then add the CRM or partner’s own charges. A vendor may bill by seat, active contact, connected number, or subscription tier. Respond.io’s coexistence documentation, for example, says app-sent messages do not incur WhatsApp fees but echoed messages can affect its Monthly Active Contacts usage. Request an invoice example for 500 support replies, 200 utility updates, and 50 marketing templates, using your target market. Confirm who pays Meta, whether the business owns the account and templates, and what happens if message categories are reclassified. A cheap per-message quote is not useful if old chats are absent or agents cannot find the right customer.

A CRM integration should turn an incoming sender into the right person without silently joining unrelated histories. Two customers can share a family phone; one buyer may write from a work and a personal number. Establish a matching rule: keep source number and account visible, suggest likely duplicates, and require a human review when the evidence is weak. For a BD lead’s supplier, the company and next action matter more than a display name. Test your rule by sending from two known numbers and checking both records.

Next assign access. A shared service line belongs in a workspace with agents who need it; a founder’s personal account can include private relationships outside company work. The Business Messaging Policy puts responsibility on businesses to secure the notices and permissions needed to collect and share message content. Finally, simulate a failure: disconnect the provider, send one customer message, reconnect, and check whether it backfills or needs manual reconciliation. Vendor documentation may say what happens; your exact account test tells you whether the CRM has a gap. Keep WhatsApp itself available while you validate the connection.

Pantheon is an invite-only alpha for relationship-led operators who want supported WhatsApp messages to build a contact record beside notes, companies, and deals. Its WhatsApp connection currently needs the Mac app. If a founder’s WhatsApp contact is also known through Telegram or iMessage, Pantheon suggests the cross-channel match for the operator to approve; it does not silently combine private threads. A useful test is a known partner whose introduction was in Telegram and whose current request is on WhatsApp. For a company support line with many agents and template campaigns, use the Platform workflow and test the provider’s desk.

Connecting the wrong number. Draw the sender-to-CRM path before onboarding. Expecting history by default. HubSpot only syncs new messages, and coexistence implementations vary. Sending outside the service window without a template. Meta’s policy requires an approved template after 24 hours. Treating a contact list as opt-in. Record permission for the message category, then honor stop requests. Using old pricing. Meta’s live rate page is delivered-message and market-specific. Calling a text export a live integration. WhatsApp’s export help says it is a non-importable text file. Each mistake is observable in a small trial before a team depends on the connection.