Articles
WhatsApp CRM: how to connect WhatsApp to your CRM the right way
A practical guide for small businesses: what a WhatsApp CRM is for, the two ways to connect a number, what each one costs and risks, and how to set it up without losing messages.
What a WhatsApp CRM is for
For many small businesses, WhatsApp is where customers actually write — and where requests get lost. The chat lives on one employee's phone; when that person is busy or leaves, the conversation and the customer go with them. A WhatsApp CRM adds structure around the chat:
- Shared inbox. Several people answer from one number, and every conversation has an owner and a status.
- Contact card next to the chat. Orders, notes and deals are visible while you reply.
- Pipeline. An inquiry becomes a deal with a stage, an amount and a next step.
- Follow-ups. Tasks and automatic messages such as appointment reminders.
- Visibility for the owner. Who answered, how fast, and where customers drop off.
The WhatsApp Business app is fine for one person. Once several people share the work or you need automatic reminders, you need WhatsApp connected to a CRM — and there are two very different ways to do it.
Option 1: the official WhatsApp Business Platform (Cloud API)
Your number is registered on the platform under a Meta business portfolio; the CRM receives incoming messages through a webhook and sends replies through the API.
The 24-hour rule. You can send free-form messages — text, images, documents — only inside a 24-hour customer service window, which opens and resets every time the customer writes to you. Outside that window, and whenever you write first, you can only send a template message. Templates fall into three categories: marketing, utility (order updates, reminders, confirmations) and authentication (one-time codes).
What Meta charges. Since July 1, 2025, Meta charges per delivered message, by message category and by the recipient's country code. Messages customers send you are free. Changes that took effect on October 1, 2026:
- Service messages (your free-form replies inside the window) are charged again, after a free tier of 1,000 per business phone number per month that resets monthly.
- Utility templates sent inside an open window, free since July 2025, are charged again.
- Without a payment method in Meta's Billing Hub, service messages stop being delivered once the free tier is used up.
There is one notable free case: when a customer messages you from a Click-to-WhatsApp ad on the mobile app and you reply within the service window, a free entry point window opens for up to 7 days, and marketing, utility, authentication and service messages in it aren't charged.
Meta's USD rate card effective October 1, 2026 lists these rates for recipients in North America (the US and Canada):
| Message category | Typical use | Rate per delivered message |
|---|---|---|
| Marketing | Promotions, win-back offers | $0.025 |
| Utility | Reminders, confirmations, status updates | $0.0034 |
| Authentication | One-time passcodes | $0.0034 |
| Service | Replies inside the 24-hour window, after the 1,000 free | $0.0034 |
Utility and authentication rates drop with volume tiers; other countries have their own rates. At list rates, 500 utility messages a month to US numbers come to about $1.70, and a 1,000-message promotion about $25.
Option 2: unofficial QR-code gateways
A gateway is a third-party service that connects to your number the way a linked device does. With GREEN-API, for example, you open WhatsApp on your phone, go to Linked devices and scan a QR code shown in the gateway's console.
Why people choose it: it takes minutes, the number stays on your phone with its history, there are no templates or 24-hour window, and Meta doesn't bill per message.
What you take on:
- It isn't an official Meta product. WhatsApp's Terms of Service prohibit "bulk messaging, auto-messaging, auto-dialing, and the like" and say WhatsApp may disable or suspend accounts.
- The gateway can't protect your number. GREEN-API's own documentation states that blocking is decided by WhatsApp and doesn't depend on the gateway. It advises warming up a new number for at least 10 days and messaging only customers who have saved your number.
- The phone has to stay online. GREEN-API asks that the phone stay charged and connected to the internet, unless you pay for its hosted-phone option.
The lower-risk way to use a gateway is to answer customers who write to you first. Cold outreach or mass mailings through it put the number — often your main business number — at risk.
The two options side by side
| Official Cloud API | QR-code gateway | |
|---|---|---|
| Status | Meta's platform under its business terms | Unofficial |
| Setup | Business portfolio, app, access token, webhook | Scan a QR code in the WhatsApp app |
| Your number | Registered on the platform; a number in use with WhatsApp must be deleted first, unless a Meta partner onboards it via coexistence | Stays on your phone as is |
| Writing first or after 24 hours | Approved templates only | Any text, at your own risk |
| Running costs | Meta's per-message rates plus the CRM | The gateway's plan plus the CRM |
| Risk of losing the number | Meta's messaging policies apply | WhatsApp may block it; the gateway can't prevent that |
| Best for | Templates, campaigns, several agents, growth | Light inbound replies and testing |
How NeuroCRM connects WhatsApp
NeuroCRM supports both routes; either way, messages land in the same inbox as Telegram, Instagram, email and website chat.
Official Cloud API. Under Integrations you enter the Phone Number ID, a permanent system-user access token, the App Secret (used to verify incoming webhooks) and the WhatsApp Business Account ID from your Meta Business settings, then paste NeuroCRM's callback URL and verify token into your Meta app's webhook settings. You can connect several numbers. The setup is manual, so coexistence onboarding (see the FAQ) isn't available on this route. Meta's message charges go to the WhatsApp Business account you connect; NeuroCRM itself is priced per user ($13 a month, or $10.40 billed yearly).
The 24-hour window, handled for you. NeuroCRM tracks the window for every chat from the customer's last real WhatsApp message, with a five-minute safety margin. Inside the window you type as usual. When the window is closed, only an approved template of that number can go out — one you pick from the list, or a default: the template your company set, or else a plain-text approved template, utility ones first. The chat history shows exactly what the customer received, and your typed draft stays in the reply field. If the number has no suitable approved template, NeuroCRM tells you to create one in WhatsApp Manager instead of showing "sent" for a message that would never arrive.
GREEN-API gateway. You create an instance in GREEN-API, link your number by QR code in their console and paste the instance ID and API token into NeuroCRM. Everything said above about gateway risks applies. Other gateways, such as Wazzup, aren't supported.
Around the chat:
- Every WhatsApp conversation gets a contact card, an owner and a status, and can be turned into a deal.
- Online booking (included in the seat price) sends booking reminders over WhatsApp too; confirmations and changes can go out through an automation rule on the booking event. If both connections are set up, reminders go through the Cloud API. Through GREEN-API they arrive as ordinary messages; through the Cloud API they go out as plain text, so they reach only customers who wrote within the last 24 hours — they aren't switched to templates automatically. For the rest, use SMS, email or Telegram.
- Automations can write into a customer's existing chat — for example, when a deal moves to a new stage. On the Cloud API, automations and the AI send only inside the 24-hour window; outside it, an automation step is marked as not sent. Automations don't pick a template on their own; a sales-sequence step sends the approved template you set.
- AI replies are optional: the AI Contact Center module costs $200 a month plus $0.50 per successful dialog and runs on your own AI key with no markup (or through us with a 20% markup). The AI qualifies the request, creates tasks and hands the chat to a person; it doesn't book appointments by itself.
Which option should a small business choose?
- You send confirmations or promotions, or several people answer: the official Cloud API. Templates take preparation, but the number is on Meta's own platform and costs are predictable.
- You only reply to people who write first, at low volume, and the number must stay on your phone: a gateway is acceptable if you accept the risk and keep another way to reach customers.
- You want to message cold lists: not through a gateway; use marketing templates on the official API, only for people who agreed to hear from you.
- Not sure: connect a test number during a free trial before moving your main number.
Checklist before you connect WhatsApp to a CRM
- Pick the number. A new number for the API, or your existing one — and what happens to it in the WhatsApp app.
- Get access to your Meta business portfolio with admin rights, and add a payment method in Billing Hub.
- Prepare templates in advance: a utility template to restart a conversation after 24 hours ("Can we continue with your request?") and one for order or booking updates.
- Agree on ownership: who answers new chats, who covers, and how fast the first reply should be.
- Collect consent before sending promotional messages, and give people an easy way to opt out.
- Test on your own phone: an incoming message, a reply and a template after 24 hours.
- If you use a gateway: warm up a new number, message only people who saved it, and keep the phone charged and online.
- Check practical constraints: data location, mobile access for staff, the cost of AI replies at your volume.
Popular WhatsApp CRM options at a glance
Entry prices from vendors' pricing pages, before WhatsApp message charges; details in our Kommo alternatives comparison.
| Tool | Entry price | WhatsApp detail |
|---|---|---|
| Wati | $59/mo billed annually, 3 users | Template messages charged per Wati's rate card |
| respond.io | $79/mo billed yearly, 5 users | Meta's fees paid through WhatsApp credit you top up |
| Kommo | $25/user/mo on a 6-month term, $20.84 yearly | One WhatsApp number on Base, plus one channel per extra user |
| Bigin by Zoho CRM | $7/user/mo billed annually | WhatsApp integration from the Express plan |
| NeuroCRM | $13/user/mo, or $10.40 billed yearly | Cloud API (Meta bills your account) or GREEN-API |
FAQ
Is the WhatsApp Business app a CRM?
No. It's a messaging app for one business number; assigning chats to owners, tracking deals by stage and team reporting are what a CRM adds.
Do I need a separate phone number for the WhatsApp API?
Not necessarily. Meta's documentation says a number already in use with WhatsApp must be deleted from WhatsApp before it can be registered on the platform. The exception is "coexistence": Meta Solution Partners and Tech Providers can onboard an existing WhatsApp Business app number through Embedded Signup, and it keeps working in the app and through the API. A QR-code gateway works with your existing number as is.
Will a QR-code gateway get my number banned?
Not automatically, but the risk is real and the gateway can't remove it: WhatsApp decides on blocks, and cold outreach, identical messages and new numbers raise the risk.
Can several employees answer one WhatsApp number?
Yes — chats from one number go to a shared inbox and each is assigned to an owner. In NeuroCRM this works with both connections.
Sources
Checked Nov 16, 2026:
- Meta: WhatsApp Business Platform pricing and USD rate card
- Meta: phone numbers on the Cloud API and onboarding WhatsApp Business app users (coexistence)
- WhatsApp Terms of Service
- GREEN-API: protecting a number from a ban and before you start
- Pricing pages: Wati, respond.io, Kommo, Bigin by Zoho CRM, NeuroCRM
- NeuroCRM feature comparisons
How this article was made: written by the NeuroCRM team with AI assistance; product claims were checked against NeuroCRM code and help docs; prices are from the published pricing as of the update date.