WhatsApp CRM: how to pick one for your team

A WhatsApp CRM is not a spreadsheet of phone numbers, and it is not the WhatsApp Business app with coloured labels. It is the system where the team handles, qualifies and closes on the same channel the customer already writes on. If chat lives on a phone and the CRM lives in another tab, you do not have a WhatsApp CRM: you have two tools that do not talk.

This guide is for choosing without getting dazzled by an integrations count.

What problem it solves

Almost every sales team in Spain already closes on WhatsApp. The problem is not “being on WhatsApp”. The problem is:

• Each salesperson has their number or their session.
• When they leave, they take the conversation.
• The manager does not know who replied or how long it took.
• The CRM (HubSpot, Pipedrive, Walcu…) is updated by hand, if it is updated.

A WhatsApp CRM puts the channel in the centre: one company number, one inbox, one pipeline and a history that belongs to the company. That is what we ask for in sales teams.

The 7 pieces you actually need

If one is missing, you end up patching with Zapier and screenshots.

1. Shared inbox. Several agents, assignment, internal notes, no stepping on each other. Detail in shared WhatsApp inbox.
2. WhatsApp Business API. Without the API there is no real multi-agent and no campaigns. Start with what the API is.
3. Pipeline (kanban). New, contacted, meeting, closed. Drag. Not a “status” field nobody fills in.
4. Official templates. To leave the 24-hour window and to run campaigns.
5. AI that qualifies. Not a “press 1” menu bot. An agent that asks budget, timing and hands over the lead. See WhatsApp AI agents.
6. Native integrations. HubSpot, Pipedrive, Holded, Odoo, Walcu. Chat should create or update the contact, not the other way around.
7. Permissions and visibility. The salesperson sees theirs. Management sees everything. Without that, the “CRM” is a shared chat.

Generic CRM + connector vs native WhatsApp CRM

Two architectures.

A. Your usual CRM + a bridge to WhatsApp. Useful if the team already lives in HubSpot and only wants to send a message from the record. The risk: the bridge is thin, history splits, and the AI agent does not exist or is an expensive add-on.

B. A CRM born for WhatsApp that then syncs to HubSpot or Pipedrive. Chat is the source of truth. The usual CRM gets activity and stage.

For teams that close in the chat, B wins. For teams that close on calls and use WhatsApp as a ping, A can be enough.

ManyContacts is B: a WhatsApp panel (and Instagram and email) with kanban and AI, and connectors to HubSpot, Pipedrive, Odoo or Walcu.

How to evaluate a vendor in 30 minutes

Ask for a demo with your number or a test number and look at this, not the “+3,000 integrations” slide.

• Can two people write in the same chat without duplicating? If the answer is a QR on two phones, walk away.
• What happens if I delete a user? Does the history stay?
• Can I see average time to first response per agent?
• Does the AI use my data (stock, intakes, prices) or only a generic FAQ?
• Are templates managed in the same place as the inbox?
• Does the price include real users, or do they bill the “WhatsApp agent” on the side?

If the salesperson has to copy the chat into the CRM at the end of the day, it is not a WhatsApp CRM.

Pricing: what to compare for real

Compare three figures, not one:

• Subscription (users + channels).
• Meta conversations (the same across serious partners).
• AI (per conversation or per bot).

Be wary of “unlimited” that then caps templates or contacts. ManyContacts includes unlimited contacts, messages and history; extra users at €18; AI at €0.20/conversation.

The cost of not having a CRM is higher: a salesperson who leaves with 400 chats, or a weekend with no reply to a €20,000 lead.

Industries where a WhatsApp CRM is not optional

• Training and academies: enrolments, intakes, many advisors. See training centres.
• Dealerships: stock, test drive, finance. Guide in WhatsApp for car dealerships.
• eCommerce: carts and after-sales. Recover abandoned carts on WhatsApp.
• Real estate, insurance brokers, clinics: appointments and follow-up that today live on a phone.

If your industry already has a landing, use it as a process checklist. The CRM has to map that flow, not “a pretty chat”.

Signs your current CRM does not work for WhatsApp

• Salespeople still reply from a personal iPhone.
• The manager asks for screenshots to know how a deal is going.
• Campaigns run from a burned number or a spreadsheet plus copy/paste.
• The AI is a button tree customers hate.
• Nobody trusts the pipeline because it is not connected to the chat.

You do not need to “train the team more”. You need to change the tool.

Example: an academy with 12 advisors

Before: each advisor captured enrolments on their WhatsApp. The director asked for a weekly spreadsheet nobody filled in well. Two advisors left in the same quarter and conversations with 90 leads vanished.

After: one number, inbox, enrolment kanban and templates per intake. AI asks the first three questions at night. The advisor steps in when there is a payment date or a finance question. The director filters by intake and sees response times. It is not magic: it is the same work, with an owner.

If your case looks like this, the training centres landing describes the flow. The CRM is the layer that makes it repeatable.

What is not a deal-breaker (and distracts you)

• Having 8,000 integrations in a directory. You use five.
• A flow builder with 200 nodes. If the team does not maintain it, it dies.
• White-label inbox for your clients (unless you are a real agency).
• “Generative AI” with no access to your data. It is a friendly chatbot.

Prioritise inbox, API, pipeline, templates, AI with handoff, and integration to the CRM you already pay for.

Next step

Choose on your team’s real flow, not on a marketplace logo. Try ManyContacts for 7 days or book a demo and look at the inbox with two users at once. That tells you more than any comparison.