How to connect WhatsApp to your CRM without losing leads

In Mexico, Colombia and most of Latin America, customers ask, negotiate and buy on WhatsApp. If those chats live on salespeople’s phones, the company does not own its pipeline. Connecting WhatsApp to the CRM fixes that, but only if you pick the right connection and apply two rules from day one. This is how we do it.

Two ways in: the official API and QR connectors

The WhatsApp Business Platform is Meta’s official API. You register a number through Meta or a Business Solution Provider, and the CRM receives every message through webhooks. It supports many agents on one number, bots and approved message templates. Outside the 24-hour window after the customer’s last message, you can only start a conversation with an approved template, and Meta charges for templates by category and country. Check Meta’s current rate card before you budget.

QR connectors link a phone the way WhatsApp Web does. Setup takes minutes and you keep the number your customers already know. The trade-off: they depend on a phone session and sit outside Meta’s official API, so bulk sending or unusual volume can get a number restricted. Use them for person-to-person conversations, never for campaigns. Our WaConsole works this way inside Bitrix24: each number connects with a QR code, every chat is logged and follow-ups can be scheduled.

Between the two sit platforms that put the API behind a shared inbox, such as Bitrix24 Open Lines or Biky.ai. They save you from building the integration yourself.

How to choose

• Many agents on one number, bots or outbound campaigns: the official API.
• A few salespeople whose numbers customers already save: a QR connector can be enough to start.
• Moving an existing number to the API: Meta now lets some numbers run the WhatsApp Business app and the API at the same time, with limits. Check what applies to your country and provider before you migrate.

The ownership rule

Every conversation belongs to one person in the CRM. A message from an unknown number creates a contact and a lead, assigned by a rule: by source, by product, by load. A message from an existing contact goes to the current owner of the open deal. If the owner does not reply within the time limit, the CRM alerts a manager and reassigns. Without this rule you get the worst of both worlds: everyone sees the chat and nobody answers.

The next-step rule

No conversation ends without a next step and a date in the CRM: a call, a visit, a quote, a test drive. A chat that closes with "I will think about it" and no task is a lead you already lost. Every morning, the sales manager gets a list of open conversations without a next step. That list is the most useful report we build, and the shortest to set up.

Let an agent take the first minutes

Leads write at night and on weekends. An AI agent can answer right away, ask the qualifying questions, read your stock and prices, and book the next step. Then it hands the conversation to a person with a written summary. Write the handoff rule before you build: the agent passes the lead when the customer asks for a person, starts negotiating price or shows buying intent. Closing stays human.

Pitfalls we see in real deployments

• Chats on personal phones: when the salesperson leaves, the customers leave too.
• One shared phone passed around the team: every lead has five owners, so none.
• Duplicate contacts because the same number is stored as +57 300…, 300… and 57300…: normalize numbers to international format before matching.
• Templates rejected because a promotional message was filed as a utility message.
• Automations that send a welcome message to a customer already in the middle of a deal.
• Migrating a number without checking what happens to its chat history.

Start small

One number, one pipeline, the two rules, one week. Measure two things: leads without an owner and conversations without a next step. When both are near zero, add the agent. Then connect the next number.