Integrations · WhatsApp
Your customers already message you. Make it reach the CRM.
We connect the WhatsApp Business Platform to monday.com, HubSpot, Salesforce and your ERP, so an enquiry becomes a tracked record with an owner, a stage and an SLA — instead of a thread on one salesperson’s phone.
WhatsApp is not a CRM. It has no pipeline, no reporting and no handover, and every conversation that stays inside it is revenue your system of record cannot see.
The work is the plumbing between the two, and the platform rules that constrain it: a 24-hour messaging window, template categories that are priced and policed differently, and consent you have to be able to evidence to a regulator rather than to Meta.
Clients who have used our messaging integration services
Where it matters
For most of the world, WhatsApp is the channel.
Every figure below comes from Meta’s own disclosures or a national regulator. We leave out the country numbers that circulate on comparison blogs, because none of them trace back to a source that publishes them.
Global
2bn daily actives
Over 3 billion monthly. More online adults name WhatsApp their single favourite platform than any other app.
United Kingdom
90% of online adults
Ofcom puts daily use at 76%, up from 67%. Your UK customers are not waiting on email.
United States
100m users
Large, and a special case: Meta does not deliver marketing templates to US numbers at all.
Southeast Asia
Top-10 revenue markets
Thailand and Vietnam rank top-10 for Meta business messaging despite sitting in the 30s by GDP, because commerce runs through chat.
The pipe
From a message to a record with an owner
Meta’s Cloud API posts every inbound message to a webhook. What happens in the moment after that is the integration.
- WhatsAppCloud API webhook
- Routing layerIdentity match · dedupe · consent
- monday.com / HubSpotSingle source of truth
- ERP & billingOrders · delivery · invoices
Outbound runs the same path in reverse, with template approval and the messaging window enforced before send.
Your stack
What your CRM does on its own, and what we build.
Nobody sells you an honest version of this table. Three of these five shipped or withdrew something in the last twelve months.
PlatformSupportOut of the boxWhat we build
HubSpot
Native
Out of the boxA first-party WhatsApp channel in the Conversations inbox, connected direct to Meta. Needs Marketing Hub or Service Hub Professional.
What we buildBroadcast, which HubSpot has no native tool for, and headroom past the 1,000 template messages a month shared across every connected WhatsApp account.
Salesforce
Native
Out of the boxThe enhanced Messaging channel connects straight to Meta. The legacy one routes through Twilio and needs the Digital Engagement add-on.
What we buildMigration off the legacy Twilio channel, the lead and opportunity flows the service product does not cover, and consent as a field you can audit.
Zoho CRM
Native
Out of the boxSupported on the trial and every paid edition against your own WhatsApp account — the most permissive gate of the five.
What we buildEverything outside Zoho. The moment WhatsApp has to reach an ERP, a warehouse or a finance system, the native channel stops.
Microsoft Dynamics 365
Deprecated
Out of the boxMicrosoft deprecated the Azure Communication Services WhatsApp channel on 23 September 2026, with removal set for 30 September 2028. New deployments go through Twilio.
What we buildThe migration to the supported path before removal, plus the Power Platform flows that connect it to the rest of the estate.
monday.com
Not native
Out of the boxNo first-party WhatsApp integration and no native channel in monday CRM. Third-party marketplace apps only, each with its own provider relationship and per-seat pricing.
What we buildA Cloud API webhook into monday’s GraphQL: message becomes an item, thread becomes an update, status drives the automation. No per-seat ceiling on the rollout.
Your ERP
Not native
Out of the boxNothing. ERPs do not ship messaging channels.
What we buildOrder, dispatch and invoice events as approved utility templates, throttled, and logged against the record that triggered them.
Verified against each vendor’s own documentation in September 2026. We re-check this table each quarter and date it, because a stale answer here costs you a licence you did not need — or a migration you did not see coming.
What we build
Six pieces,every one of them yours to keep.
Documented, owned by a named maintainer, and handed over with the architecture written down.
🔌
Channel setup
Business verification, display-name approval and the number strategy — one number per market, or one per team.
🧭
Identity resolution
Matching a phone number to the right existing contact, so one customer does not become three records by Friday.
🧾
Template governance
Templates written, categorised correctly and submitted for approval, with a rejection path that does not block the release.
🔀
Routing & SLAs
Assignment by language, region, product or deal value, with escalation before the messaging window closes.
🛡️
Consent & retention
Opt-in captured and stored as a field you can audit, with retention rules that satisfy your regulator, not just Meta.
📈
Cost reporting
Per-message spend attributed to the campaign, team or deal that caused it, read from the pricing object on every delivery receipt.
Platform rules
The constraints that decide what you can actually build.
This is why WhatsApp is engineering work rather than a connector toggle. Every row below changes the design of the system.
- Messaging window
- 24 hours from the customer’s last message or call
- What it meansIt resets on every inbound message. Outside it you may send only a pre-approved template, so your routing has to know how much window is left.
- Pricing
- From 1 October 2026, service messages and in-window utility templates become billable
- What it meansBoth have been free since November 2024. Any quote built on the old model understates what the channel costs to run.
- Template categories
- Marketing, utility and authentication, priced and policed differently
- What it meansSince April 2025 a utility template Meta judges to be marketing is approved as marketing rather than rejected, so you are billed at the higher rate with no error to catch.
- Messaging limits
- 250 → 2,000 → 10,000 → 100,000 → unlimited unique recipients per rolling 24 hours
- What it meansShared across your whole business portfolio, not per number. Multi-brand groups hit the ceiling far earlier than they expect.
- Access model
- Cloud API direct, or through a Solution Partner
- What it meansDirect means Meta bills you and the operational burden is yours. A Solution Partner holds the credit line and invoices you. We model both against your real volume.
- Data residency
- Pin data at rest to one country, or store nothing at rest at all
- What it meansLocal storage covers Australia, India, Singapore, Japan, the UK and Germany among others. This is the answer to the residency objection most teams do not know exists.
- Opt-in
- Required, and yours to evidence
- What it meansMeta relaxed the prescribed method, not the requirement. Your own regulator — GDPR, PDPA, India’s DPDP — sits on top, and it is usually the stricter one.
- On-Premises API
- Expired 23 October 2025
- What it meansIf anything in your estate still points at it, those messages are not being delivered. Cloud API is the only remaining path.
Verified against Meta’s WhatsApp Business Platform documentation in September 2026. Meta may change rates on 1 January, 1 April, 1 July or 1 October with one to six months’ notice depending on the change, so we date this panel and re-check it quarterly.
What this looks like in your industry
Enquiry to inspection without a spreadsheet in the middle
A buyer messages about a listing. The listing reference is parsed out of the message, the enquiry lands on the agent who owns that property, and the inspection booking writes straight back to the CRM — while the buyer stays in the app they started in.
Benefits
Listing reference parsed from the first inbound message
Routed to the agent who owns the property, not a shared queue
Inspection reminders as approved utility templates
Full thread on the contact record for whoever picks it up next
Why WhatsApp projects stall
Four failure modes we are usually called in to undo, and what we do instead.
01
It lives on someone’s personal phone When they leave, the pipeline leaves with them. There is no reporting, no handover, and no record that a conversation ever happened.
02
Templates written the night before launch Submitted late, miscategorised as marketing, and suddenly the launch date belongs to Meta’s review queue rather than yours.
03
Consent captured nowhere in particular A checkbox on a form that never reached the CRM. The first regulator question is “show me”, and there is nothing to show.
04
Per-seat app licences that cap the rollout The marketplace app works for the pilot team, then the price to extend it to everyone else exceeds the cost of building it properly.
How the engagementactually runs
Fixed phases, defined outcomes, published fees. You always know what is being delivered, by when, and at what cost.
01
Channel & consent audit
Where conversations happen today, who owns them, what consent you can actually prove, and which access tier your volume justifies.
02
Data model & routing design
How a message becomes a record, which object it attaches to, who it routes to, and what happens when nobody answers in time.
03
Build, with error handling first
Rate limits, retries, dead-letter queues and alerting designed in, because integrations that fail silently corrupt trust in every connected system.
04
Handover you can maintain
Architecture documentation, a named maintenance path, and your team trained on the parts they will change. No mystery middleware.
Book a time
Talk to a consultant who has shipped this
Thirty minutes. We will tell you whether WhatsApp is the right channel for your market before we quote you anything.
contact@fruitionservices.ioSydney · New York · London · Singapore · New Delhi · Manila
Platinum monday.com partner · 900+ implementations
Frequently asked questions
Either works, and the difference is mostly about who invoices you. As a Tech Provider the platform bills you directly through Meta and charges separately for its software; a Solution Partner holds the credit line and invoices you for messaging itself. Direct is cheaper per message and puts number provisioning, template submission and support on your team. We model both against your real volume and tell you which one your traffic justifies.
Get WhatsApp out of the group chat
Book a 30-minute discovery call. We will give you a frank read on scope, fit and cost.