Your salesperson sends a quote on WhatsApp. The client replies with three follow-up questions. A price is agreed in voice notes. The deal closes. And none of it ever reaches the CRM.
This is the default state for most Hong Kong SMEs. The conversations that matter most — the ones that actually move money — happen on WhatsApp, and the CRM ends up as a tidy graveyard of form submissions and business cards. The two systems do not talk to each other, so nobody has the full picture.
Connecting WhatsApp to your CRM fixes that. This guide covers what the integration actually means, the three real options you have, and what it honestly costs if you are running a business in Hong Kong.
Why this matters in Hong Kong
Roughly 83% of Hong Kong adults use WhatsApp daily (DataReportal, Digital HK 2024). For business, that number is effectively 100%. Clients expect a reply on WhatsApp. Quotes, shipment updates, meeting confirmations, last-minute changes — they all land in the same green chat bubble.
When those conversations never reach the CRM, three things go wrong, and they go wrong quietly.
First, handovers break. A colleague covering for you while you are on leave has no way to pick up the thread. They do not know what was promised, what was objected to, or what was discounted. They walk into the next call blind.
Second, you lose pipeline visibility. Your CRM dashboard says you have fifteen active deals. Your team’s WhatsApp has forty ongoing conversations that are genuinely close to closing. The number on the dashboard is fiction, so any forecast built from it is fiction too.
Third, when someone leaves, the relationship leaves with them. The client’s phone number is not the problem — the client has your company’s number in their phone too. The problem is the history: every exchange, every concession, every reference to the decision-maker’s preferences. It is all on one person’s device. When they walk out, that institutional memory walks out with them.
What “connecting WhatsApp to a CRM” actually means
The phrase gets used loosely, so let’s be precise.
A proper integration is bidirectional. Incoming messages from a customer appear on that customer’s contact record in the CRM — same timeline as their emails, calls, and notes — matched automatically by phone number. Outgoing messages sent from the CRM are delivered to the customer’s WhatsApp as if you had sent them from the app. Both participants see the same conversation thread, and your team sees it from within the CRM regardless of which phone originally sent or received it.
This is not the same as importing your phone’s contact list into the CRM once. That is a separate, useful task — covered in detail in How to Import Your WhatsApp Contacts into a CRM — but it moves a snapshot of contacts, not a live channel. This guide is about making the channel live.
Your three options
There are three genuine paths, and only one of them is legitimate at scale. It is worth understanding all three before you decide.
Option A: WhatsApp Business API (the official path)
This is Meta’s sanctioned integration. You connect a dedicated business phone number (which cannot simultaneously be on the regular WhatsApp or WhatsApp Business app) to Meta’s cloud or on-premise API, then your CRM sends and receives messages through that API.
You reach the API either through a BSP — a Business Solution Provider licensed by Meta — or directly as a registered Tech Provider. For a typical HK SME, the BSP route is the realistic choice; becoming a Tech Provider is a significant commitment meant for platforms serving many customers.
Meta charges per conversation, not per message, and the rate depends on the conversation category and country. For Hong Kong in 2026, ballpark figures are roughly HK$0.15 to HK$0.40 for a marketing or utility template conversation, and roughly HK$0.03 to HK$0.10 for a service conversation started by the customer. These rates change — always check Meta’s current pricing before budgeting.
What you get in return is real: official support, unlimited scale, opt-in compliance, template approval workflows, and a business account that will not be banned for using the wrong tool.
The catch is onboarding. You need a business verification with Meta (documents, a verified domain, a Facebook Business Manager account), a dedicated sending number, and either a BSP contract or a direct Tech Provider registration. End-to-end, expect one to three weeks before your first message flows.
Option B: Unofficial or reverse-engineered integrations
A cheaper category of tools bypasses the official API. They either scrape WhatsApp Web in a headless browser or emulate the mobile client at the protocol level. You install them, scan a QR code with your regular WhatsApp Business app, and messages start flowing.
On paper it looks appealing — no Meta verification, no per-conversation fees, and usually a flat monthly subscription. In practice it is a ticking clock for three reasons.
It violates WhatsApp’s terms of service. That is not a nitpick: if Meta detects automated traffic on your number, the number gets banned. Not rate-limited — banned. You lose the business account, the client chats, and the number itself.
It breaks whenever Meta ships an update. WhatsApp Web changes every few weeks. When it does, the scraping tool stops working until the vendor patches it, which can take days. During those days your team has no WhatsApp at all.
It cannot scale. These tools work until you have a meaningful volume of traffic, and then the detection heuristics catch up. People who try this usually do it because the official path seemed expensive or slow, then learn the hard way that the cost of a banned number is much higher than a BSP subscription would have been.
This is not recommended. The section exists so you can recognise tools in this category when a vendor pitches them and understand the actual tradeoff.
Option C: Keep WhatsApp separate and log manually
This is what most HK SMEs are doing today, whether they admit it or not. The team uses WhatsApp normally on their phones. Important conversations get summarised into the CRM by hand — a pasted quote, a few notes about what was agreed, a reminder for next week.
It works, up to a point. Below roughly 200 meaningful messages a week and with a team of one or two people, the discipline is manageable. Everyone knows what they are responsible for logging, and the overhead is tolerable.
It breaks when volume grows or the team grows. With five salespeople, the logging simply does not happen consistently. Some log everything, some log nothing, the CRM becomes a lottery of how diligent each person feels this week. This is also the option most vulnerable to the “when someone leaves” problem — because the source of truth stays on personal phones, not in a shared system.
If you are here, it is not because the manual option is wrong. It is because you have outgrown it.
What to look for in a CRM
Independent of which option you pick, the CRM side of the integration needs four things. If any is missing, the integration will feel worse than no integration.
Contact auto-matching by phone number. When a WhatsApp message arrives from +852 9123 4567, the CRM should match it to the existing contact with that number and attach the message to their record automatically. If it cannot, every incoming message becomes a manual filing task — worse than before.
Unified timeline. The WhatsApp message should appear in the same feed as emails, calls, and notes for that contact, in chronological order. Not in a separate “WhatsApp” tab. One timeline per contact, all channels visible together — that is what makes a handover possible.
Team inbox. Any teammate with the right permission should be able to reply from the CRM, even if they were not the original sender. WhatsApp’s own apps are bound to a single device; the CRM is where you escape that constraint.
Template management. Meta requires pre-approved templates for any business-initiated message outside the 24-hour service window. The CRM should help you submit templates, track approval status, and use approved templates when composing outbound campaigns. Without this you will be pasting raw text into Meta Business Suite and wondering why your outbound never sends.
What it costs honestly
For a ten-person HK SME choosing the official WhatsApp Business API route, here is a realistic monthly breakdown.
Your BSP will charge a platform fee. Depending on the tier and the BSP, this typically sits in the HK$800 to HK$2,000 per month range for a setup that includes a reasonable message volume and usable analytics. The higher end buys you better support, template assistance, and sometimes a dedicated account manager.
On top of that, Meta’s per-conversation fees. At moderate HK SME volume — say a few hundred outbound template conversations and a few hundred inbound service conversations per month — expect another HK$200 to HK$500 from Meta itself.
Then your CRM. HARi, for example, is HK$1,990 per month flat for your whole team, no per-seat fees.
All-in, a real official setup lands in the HK$1,500 to HK$3,000 per month range for a ten-person team, on top of your CRM subscription. Option C (manual logging) saves all of that, at the cost of the problems described earlier.
Where HARi is today
It is worth being direct about this, because the alternative is marketing copy that lets you down after purchase.
HARi’s data model already treats WhatsApp as a first-class channel. The _mailbox and _inbox_message tables support any channel — email, WhatsApp, SMS, in-app chat — without schema changes. Inbound phone-number matching works today: if you forward or log an inbound WhatsApp message with a known phone number, HARi attaches it to the correct contact automatically.
The outbound side — native sending through a Meta BSP, template submission, template management, and the team inbox reply experience — is the next piece on the roadmap. It is not shipped yet. When we say “coming soon” for this feature, we mean the data model is ready and the integration is actively being built on top, not that we hope to get to it someday.
If you would benefit from WhatsApp integration as soon as it ships, early access is the fastest way in.
FAQ
Can I use my personal WhatsApp number? No. The WhatsApp Business API requires a dedicated business number that is not simultaneously on the regular WhatsApp app or the WhatsApp Business app. If you want to keep using your personal number for personal chats, use a second number for business.
Does WhatsApp Business (the free app) work with a CRM? Barely. The free WhatsApp Business app has no public API. Some unofficial tools pair it with phone-based automation (Option B above), but the approach is fragile, violates terms of service, and risks bans. If you are serious about integrating with a CRM, the Business API is the path.
How long does WhatsApp Business API setup take? Plan for one to three weeks end-to-end. That covers picking a BSP, completing Meta’s business verification, provisioning a dedicated number, approving your first templates, and connecting the CRM. Much of the clock is Meta’s verification queue, which you cannot speed up.
What if I sell into Chinese-majority markets? The process is identical. Meta’s infrastructure is global, and the rules are the same. What differs is whether your BSP has mature Chinese-language template libraries and support staff — worth asking up front if most of your outbound will be in traditional or simplified Chinese.
If you are thinking about WhatsApp as a real sales channel in HK and don’t know where to start, we’re opening early access to HARi’s WhatsApp integration. Sign up for early access here.
For related reading: CRM for Hong Kong SMEs in 2026 covers the broader stack decision, and HARi pricing has the full breakdown of what’s included at HK$1,990/month flat.