# Integrate WhatsApp with CRM without taking the app off reps' phones

> How to integrate WhatsApp with your CRM without losing chat history or the phone app: extensions, the official API and coexistence, what each path loses and how to move the team.

- **HTML version:** https://tolky.to/en/blog/integrate-whatsapp-with-crm-without-losing-the-app
- **Author:** [Marlos Carmo](https://tolky.to/en/author/marlos), Co-founder of Tolky
- **Published:** November 18, 2026
- **Reviewed:** November 18, 2026
- **Language:** en

## Summary

To **integrate WhatsApp with CRM** without taking the app off a sales rep's phone, the official path is **coexistence**: the same number stays on the WhatsApp Business app and also runs on the API, with new conversations recorded in the CRM. Past history comes over only in part (up to 180 days of one-on-one chats, once, without groups), and unofficial extensions put the number at risk of a ban.

Your sales team has been selling over WhatsApp on their phones for years. Customers know that number, reps know where every conversation lives, and "moving everything into the CRM" sounds like swapping something that works for a screen nobody asked for. When the integration goes wrong, history disappears, the number goes down and reps go back to their phones.

These problems have a known cause. They almost always come from the path chosen to **integrate WhatsApp with CRM**: an unofficial extension, a migration that takes the number off the app, or coexistence with no rule about who replies. Each path keeps and loses different things.

This guide compares the three paths, what happens to chat history in each one and how to migrate without taking the phone out of the rep's hand.

*Updated in November 2026.*

## What does it mean to integrate WhatsApp with CRM?

**Integrating WhatsApp with CRM means every conversation on the company's number reaches the customer record, with history, owner and next step, without manual copying.** The CRM knows who talked to whom, what was agreed and which pipeline stage the deal is in.

The integration is only stable when it runs on the [official WhatsApp Business API](https://tolky.to/en/glossary/whatsapp-business-platform), because the API is what delivers messages to another system in an authorized way. The [WhatsApp Business app](https://tolky.to/en/glossary/whatsapp-business-app) on a phone does not talk to any CRM on its own. That is why [WhatsApp is not a CRM](https://tolky.to/en/blog/whatsapp-is-not-crm): it is the channel, and the CRM is where the relationship is recorded.

## Why do sales teams lose chat history when integrating WhatsApp with a CRM?

**History gets lost because, before the integration, it lives on the device, and each integration path brings only part of it into the CRM.** Whatever is not brought over stays on the phone, or disappears with it.

The most common causes:

- **Full migration to the API.** The number leaves the app, and old conversations are not carried over to the API.
- **Time-limited coexistence.** Meta allows syncing up to 180 days of one-on-one chats, only once, and the platform has 24 hours after onboarding to do it.
- **Groups and media.** Groups are not synced, and older media arrives without the file, only as a placeholder.
- **Personal numbers.** Conversations a rep had on their personal WhatsApp do not enter any company integration.
- **Unofficial extensions.** History depends on the WhatsApp Web session; if the number is blocked or the session drops, the record is incomplete.

A lead that drops off along the way rarely says so: see how [lead loss on WhatsApp](https://tolky.to/en/blog/lead-loss-on-whatsapp) happens.

## What are the ways to integrate WhatsApp with CRM?

**There are three paths: an extension on WhatsApp Web, the official API with a full number migration, and coexistence between the app and the API.** Only the last two use Meta's official integration.

### Extension on WhatsApp Web

The extension runs in the browser on top of WhatsApp Web and copies conversations into the CRM. It is quick to install, but it depends on an open computer and, when it accesses WhatsApp in a way Meta does not approve, it puts the number at risk.

### Official API with a full migration

The number leaves the app and runs only on the API. Several reps and AI agents answer the same number and everything goes into the CRM. The cost is a change of routine: reps leave the app, and old conversations stay out. The steps are in [how to get the official WhatsApp API](https://tolky.to/en/blog/how-to-get-official-whatsapp-business-api).

### Coexistence: app and API on the same number

With [coexistence](https://tolky.to/en/glossary/coexistence), the number stays on the WhatsApp Business app on the phone and also runs on the API. Every message sent from the app is copied to the platform, which shows the copy in the contact's history. The rep keeps answering from the phone, and the CRM receives the conversation.

| Path | App stays on the phone? | Past history | New conversations in the CRM | Main risk |
| :--- | :--- | :--- | :--- | :--- |
| Extension on WhatsApp Web | Yes | Depends on the open session | While the browser is open | No official integration; number blocked |
| API with full migration | No | Not carried to the API | All of them | Change in the team's routine |
| Coexistence | Yes | Up to 180 days, once, no groups | All, including those answered in the app | Two replies to the same customer |

Requirements, setup and disconnection are covered in the guide to [coexistence between the app and the API](https://tolky.to/en/blog/whatsapp-coexistence-business-app-and-api).

## Why do sales teams resist integrating WhatsApp with a CRM?

**Teams resist because they fear losing three things: the phone as a work tool, their old conversations and the freedom to reply their own way.** Each fear has a concrete answer.

- **"I'll lose the app."** Not with coexistence. The number stays on the WhatsApp Business app, and reps keep replying from their phones.
- **"I'll lose my conversations."** Conversations stay in the app. The platform receives new conversations and, if the company authorizes it during onboarding, up to 180 days of one-on-one history.
- **"They'll watch me."** The CRM records the conversation so the customer does not depend on one person: when a rep is on vacation, whoever steps in has the context.
- **"It'll mean more work."** When AI fills in the opportunity and next activity from the conversation, reps type less.

In [sales](https://tolky.to/en/departments/sales), the rule that helps most is simple: reps do not switch tools in the first month.

## What happens to past chat history?

**With coexistence, all past history stays on the phone, and the platform can receive, only once, the one-on-one chats from the last 180 days.** Anything older stays only in the app.

Meta's rules for this sync, according to the [documentation on onboarding WhatsApp Business app users](https://developers.facebook.com/documentation/business-messaging/whatsapp/embedded-signup/onboarding-business-app-users), checked on November 18, 2026:

| Item | Rule |
| :--- | :--- |
| One-on-one chats | Up to 180 days before onboarding, synced once, if the company authorizes it |
| Deadline | 24 hours after onboarding; after that, the business must disconnect and repeat the flow |
| Contacts | Synced once; later changes in the app keep coming in |
| Older media | Arrives as a placeholder; the file only comes for media within 14 days of onboarding |
| Groups | Not synced |
| New messages sent from the app | Copied to the platform, which must show them in the contact's history |

Before connecting, agree on who authorizes the history on the phone and who checks the sync in the first 24 hours. Open deals older than six months deserve a manual note in the CRM.

## What are the risks of unofficial WhatsApp tools?

**Unofficial tools violate WhatsApp's Terms of Service and can lead to a temporary or permanent ban of the number.** WhatsApp's own Help Center says unofficial apps and sites are versions built by third parties without approval and may contain malware that steals data ([About unofficial WhatsApp apps](https://faq.whatsapp.com/1217634902127718), checked on November 18, 2026).

For a sales team, a ban is the worst case: the number customers know stops working, and the history is stuck on the device. Before installing any extension, ask the vendor whether it uses the official API.

## How to migrate without taking the phone away from reps, step by step

**The safest migration connects the number with coexistence, keeps reps on the app and puts the CRM and AI around them, in five steps.**

1. **Map the numbers.** List the company's numbers, who uses each one and who sells from a personal WhatsApp. Personal numbers need to move to a company number.
2. **Prepare the phone.** WhatsApp Business app 2.24.17 or later, a Meta business portfolio in the company's name and the primary phone in daily use: Meta disconnects the number from the API if the device is inactive for about 14 days.
3. **Connect and sync.** Connect through the platform's embedded signup, authorize the history on the phone and check the sync the same day.
4. **Decide who answers what.** Choose whether the platform only records conversations in the CRM or whether AI also replies, and on which topics. Automation must stop when the rep takes over.
5. **Review after 30 days.** Check what AI resolved and whether the pipeline matches reality. Only then decide between staying on coexistence or migrating fully.

Two cautions: WhatsApp for Windows and for WearOS are not supported as linked devices, and the app's broadcast lists become read-only, with bulk sends moving to campaigns using [approved templates](https://tolky.to/en/glossary/whatsapp-message-template).

## How to use WhatsApp and the CRM at the same time without losing data?

**Use WhatsApp and the CRM at the same time with one rule: the number belongs to the company, the conversation is recorded on the platform and only one side replies at a time, the person or the AI.** Data gets lost when that rule is loose.

- **One owner per conversation.** When a rep replies from the phone, AI stops in that conversation, or the customer gets two replies. See [handoff between AI and people](https://tolky.to/en/glossary/handoff).
- **A separate API window.** The API's [24-hour window](https://tolky.to/en/glossary/whatsapp-24-hour-window) only opens with messages the customer sends after onboarding. Messages exchanged in the app do not open or extend that window.
- **Contact identity.** With the [BSUID](https://tolky.to/en/glossary/bsuid), the phone number is no longer the only customer key; the CRM needs to store the identities Meta sends.
- **One CRM, not two.** If the company already uses another CRM, integrate the platform with it. See the example of [HubSpot with an AI agent on WhatsApp](https://tolky.to/en/blog/integrate-hubspot-whatsapp-ai-agent).

Turning conversation into sales data is what separates an inbox from a [conversational CRM](https://tolky.to/en/blog/what-is-conversational-crm-differences).

## Where does Tolky fit?

**Tolky is a conversational AI CRM that connects the number to the official WhatsApp API and offers coexistence when it is enabled for your account, so reps stay on the app while the CRM receives the conversations.** The connection is direct with Meta or through Gupshup, an official Meta partner.

- **Two coexistence modes.** Only record conversations in the CRM, or let AI reply alongside the number's owner. What the rep sends from the app enters the history, and AI pauses when they reply.
- **Sync at onboarding.** When linking in coexistence, Tolky makes the one-time contacts and history sync request that Meta allows.
- **A CRM that fills itself in.** AI suggests the opportunity, stage and next activity from the conversation, with review before saving. See [Tolky's CRM](https://tolky.to/en/solutions/crm) and the [WhatsApp CRM](https://tolky.to/en/features/whatsapp-crm).
- **Integrations.** Native integration with [HubSpot](https://tolky.to/en/integrations/hubspot), more than 1,000 apps in Flows, REST API, webhooks and MCP.

![Real screenshot of the Contacts screen in Tolky's CRM: a table with each contact's name, email, phone, creation date and last interaction, period filters and an Export button](https://tolky.to/screenshots/contatos-crm-en.png)

**What Tolky does not do:** it does not bring in conversations beyond what Meta syncs, it does not integrate personal numbers or WhatsApp Web extensions, and it has no native Salesforce or Pipefy integration. Coexistence availability depends on the account and the number, and Meta's limits (throughput of 20 messages per second, broadcast lists disabled, groups excluded) apply the same way. Connection details are on the [WhatsApp integration](https://tolky.to/en/integrations/whatsapp) page.

## Frequently asked questions

### Can I integrate WhatsApp with CRM without taking the app off the phone?

Yes, with Meta's coexistence. The number stays on the WhatsApp Business app and also runs on the official API, and messages sent from the app are copied to the platform connected to the CRM. Availability depends on the number, the country and the provider.

### Why did I lose chat history when integrating WhatsApp Business?

Because each path brings over only part of what is on the device. A full migration does not carry old conversations to the API, and coexistence syncs at most 180 days of one-on-one chats, once, within 24 hours of onboarding. Groups and conversations on personal numbers are left out.

### Is a CRM extension for WhatsApp Web safe?

Extensions that do not use the official API are outside the integration Meta authorizes. WhatsApp's Help Center says using unofficial apps violates the Terms of Service and can lead to a ban of the number.

### Can a rep keep replying from the phone with AI on the same number?

Yes, as long as the rule is clear. When the rep replies from the app, automation must stop in that conversation so the customer does not get two replies. In Tolky, AI pauses when the number's owner replies.

### Coexistence or full migration: which is better for sales?

Coexistence is better for getting started without changing the rep's routine. Full migration is better for large teams, high volume and anyone who does not want to depend on a phone, since coexistence has a fixed throughput of 20 messages per second.

### How much does it cost to integrate WhatsApp with a CRM?

There are two bills: the platform and Meta's messages. With coexistence, messages sent from the app remain free, and those sent through the API follow Meta's rate card. Estimate yours with the [WhatsApp API cost calculator](https://tolky.to/en/resources/whatsapp-api-cost-calculator).

---

## Conclusion

Integrating WhatsApp with CRM does not require taking the phone away from reps or accepting that history disappears. Coexistence keeps the app, records new conversations and brings over up to 180 days of old ones; the rest comes down to agreeing with the team on who replies and what becomes a note. To compare options, see the [best CRMs for WhatsApp](https://tolky.to/en/blog/best-whatsapp-crm-2026).

[See the plans](https://tolky.to/en/pricing), [explore Tolky's CRM](https://tolky.to/en/solutions/crm) or [talk to the team →](https://tolky.to/en/contact). Let's talk?

---

This is the Markdown version of the page. The full version, with images and navigation, is at https://tolky.to/en/blog/integrate-whatsapp-with-crm-without-losing-the-app

Tolky: https://tolky.to
