WhatsApp CRM: what it is, what it needs, and how to pick one

What is a WhatsApp CRM?

A WhatsApp CRM is customer-relationship software built around WhatsApp as the main channel. It connects to your WhatsApp number through Meta’s Cloud API and gives your team a shared inbox, a contact record for every chat, a sales pipeline, templates for outbound messages, and usually AI replies.

The idea is simple. In most of the markets we serve, such as Pakistan, India, the UAE, Mexico and Brazil, a lead does not email you. They message you. The chat is where the question, the price, the objection and the “send me the location” all happen. A CRM that makes your agent copy that into a form after the fact is a record-keeping tool. A WhatsApp CRM treats the chat itself as the record.

In practice that means four things sit next to each other on one screen: the conversation, the person’s details (name, phone, tags, custom fields, notes), the deal they are part of (stage, value, owner), and the next task. When the customer replies, the card moves or a task appears, and nobody retypes anything.

This is a different product from a chatbot builder and from a bulk-sender. A chatbot builder automates replies. A bulk-sender blasts templates. A CRM remembers who the customer is and what happens next. The better platforms do all three, but when you evaluate one, ask the CRM question first: if I open a contact, can I see everything that happened with them across WhatsApp, and who owns the follow-up?

Which features does a WhatsApp CRM need?

Nine things matter: a shared inbox with assignment, per-chat contact records with custom fields, a pipeline, approved-template campaigns with opt-in tracking, automation flows, AI replies with human handoff, tasks, a way to take payment, and an export or API so your data is never trapped. Everything else is polish.

Use this as a pass/fail list when you trial a tool. Each line says what to test, not just what to tick.

1. Shared inbox with assignment. Assign a chat to an agent, add an internal note, resolve it. Check that two agents cannot reply to the same customer at once without seeing each other. See how our inbox works.
2. Contact record with custom fields. Budget, property type, car model, preferred time: whatever your team asks every customer should be a field, not a sentence buried in a thread. Labels or tags alone are not enough.
3. Pipeline. A Kanban board whose cards are the conversations. Test moving a deal both by hand and automatically. If the board is a separate tab nobody opens, the pipeline will rot.
4. Template campaigns. Outside the 24-hour window you can only send Meta-approved templates. You need template submission inside the tool, audience filters, scheduling and delivery and read numbers. See WhatsApp campaigns.
5. Opt-in tracking. Every imported contact should carry an opt-in status, and a campaign should respect it. This protects your quality rating, and with it your sending limits.
6. Automation flows. Welcome messages, out-of-hours replies, lead routing, reminders. A visual builder is fine; what matters is conditions on fields and tags. See WhatsApp automation.
7. AI with handoff. An AI agent should answer from your own knowledge base, update the contact’s fields, and hand the chat to a human on request. Ask to see a transcript where it says “I don’t know”. See the AI agent.
8. Tasks and reminders. Follow-up is where CRMs earn their keep. Every deal needs a next action with a date.
9. Payments, calling and escape hatches. Payment links inside the chat close deals faster, and calling matters in markets where customers prefer a voice call. Equally important: CSV export and an API with webhooks. If you cannot leave, you are renting your own customer list.

Nice to have, not essential: a mobile app, WhatsApp group support, multi-language interface, agency white-label. Each becomes essential for a specific kind of team, and the next section is about finding out which kind you are.

How do you set up a WhatsApp CRM on the official Cloud API?

You need a Meta business account, a phone number not already registered in a WhatsApp app, an approved display name and a payment method on your WhatsApp Business Account. Connect them through the CRM’s embedded signup, submit templates, import contacts with opt-in status, then configure routing, pipeline and AI.

1. Create or find your Meta Business portfolio. You need admin rights. Business verification is optional to start but it raises your messaging limits, and a verified business is easier to trust. See green tick and verification.
2. Choose the number. Use a number that can receive a verification call or SMS and is not registered on the WhatsApp or WhatsApp Business app. If it is, either remove it from the app first or, where Meta allows it, link it through coexistence so the app keeps working. Do not pick a personal number you cannot lose.
3. Connect through embedded signup. In WhatsGrow AI this is a button in Settings, Channels: you log in with Facebook, pick the business account and number, and the connection is created. No developer work and no manual API tokens.
4. Add a payment method in Meta. Meta bills you directly for conversation fees. Meta needs a payment method on the account to deliver paid messages, and since 1 October 2026 it stops delivering service messages once the 1,000 free ones are used up if none is on file. More on this under costs.
5. Submit your first five templates. Start with a welcome or follow-up (marketing), an appointment or order confirmation (utility), and a re-engagement message. Submit them from inside the CRM and give each a plain, specific name. Approval can be fast or take longer; do this before you need them.
6. Import contacts with their opt-in status. Upload a CSV or Excel file, map columns to name, phone and your custom fields, choose how duplicates are handled, and set the default opt-in. Only message people who agreed to hear from you.
7. Set up the team. Add agents, decide who gets new leads, create labels and the pipeline stages that match how you actually sell, not a generic template.
8. Turn on the AI agent last. Upload your price list, FAQs and policies as the knowledge base, set the languages, and decide the handoff rule. Test with your twenty real messages. Start in a mode where a human approves replies if the tool offers it.

The step-by-step version with screenshots is in our WhatsApp Business API setup guide. Budget a day of effort and a few days of calendar time, because Meta verification and template approval run on their clock, not yours.

What does a WhatsApp CRM cost, including Meta’s fees?

Two separate bills. The CRM subscription is a flat or per-seat fee set by the vendor. Meta’s message fees are charged per delivered message by category (marketing, utility, authentication, service) and by the customer’s country. Since 1 October 2026 service replies are free only for the first 1,000 per business number each month.

For our own plans, see the pricing page; prices are shown in your currency and the plans list no setup fee. Meta’s fees are billed by Meta to your own Meta account, and we add no markup on them. Not every vendor can say that, so ask for the underlying Meta rate beside any per-message price you are quoted.

Meta’s list rates on 1 October 2026 for a marketing template are, in US dollars per delivered message: India 0.0118, North America 0.0250, Mexico 0.0397, Pakistan 0.0473, and the UAE and Saudi Arabia 0.0576. Utility templates cost a fraction of that in most of these countries. Rates change only on 1 January, 1 April, 1 July and 1 October. We keep the full table, worked examples and ways to cut the bill on one page: WhatsApp Business API pricing, and you can plug in your own volumes in the pricing calculator.