Key takeaways
- A WhatsApp CRM integration partner should show you a working flow on a real phone number before you sign. A slide deck does not count.
- Only the official WhatsApp Business API supports verified business messaging at scale. Unofficial wrappers put your number at risk of suspension.
- Get fixed scope and a fixed price in writing before work starts. Hourly billing turns a small automation into a growing invoice.
- Automation and marketing retainers should run month-to-month and never as a percentage of ad spend.
- Ask who owns the Make or n8n workflow and the code after launch. A black-box platform you can't touch has the same handover gap as a dev shop that disappears.
What a WhatsApp CRM Integration Partner Actually Does
At Meant, we treat a WhatsApp CRM integration partner as the team that connects four things and keeps them working together. Those four are your WhatsApp number, your CRM, the rules that move data between them, and the AI that handles conversations a fixed rule can't. Hire for all four. A partner who only does one leaves you to stitch the rest together yourself.
The scope, in plain terms:
- WhatsApp Business API connection. Your business number is registered on Meta's official API, verified, and set up with approved message templates for things like order updates and reminders.
- CRM sync. Every conversation, contact and status change is written to your CRM automatically, so nobody copies chat logs into a spreadsheet at six o'clock. The sync runs both ways: when a deal moves stage in the CRM, the right WhatsApp message goes out.
- Lead capture. Website forms, click-to-WhatsApp ads and inbound messages arrive in the CRM tagged with their source, so you can see which channel produces customers rather than chats.
- AI WhatsApp automation for judgment calls. An AI agent answers routine questions, qualifies a lead, books a slot or hands the thread to a person when the conversation needs one.
Underneath sits a workflow layer. That might be Make, n8n or custom code against the CRM's API. Which one fits depends on volume, how much logic is involved and who will maintain it. We cover each of these pieces on our page about AI agents, WhatsApp and CRM sync.
Good work starts before anything is connected. A sensible first step is to spend twenty minutes mapping where your team currently logs WhatsApp conversations. A partner who skips that map will automate a process you don't actually run.
Ask to See a Live Flow, Not a Slide Deck
Anyone can draw arrows between logos. The first test of a WhatsApp CRM integration partner is whether they can show you the arrows working.
Ask for a live demo on a real phone number, before you sign anything. If they can't run one, they haven't built one.
What a real demo should show
A genuine demo is something you take part in. You send a message from your own phone and watch what happens next. At a minimum:
- You message a business number and get a reply within seconds, from the official API rather than someone's personal phone.
- A contact record appears or updates in the CRM, with the message, the source and a timestamp.
- A rule fires. The lead gets tagged, assigned to a person or moved to a pipeline stage.
- The AI agent answers a question it was trained on, then hands over cleanly when you ask something outside its brief.
- A template message goes out from the CRM side, such as a booking confirmation, and lands on your phone.
A mockup looks different. It shows screenshots or a recorded video, or the presenter runs everything from their own device and you never touch it. Recordings are fine for a portfolio. They tell you nothing about whether the system copes when you type something unexpected.
Questions to ask about the demo
- Is this number on the official WhatsApp Business API, and whose Meta account is it under?
- What is running underneath: Make, n8n, or custom code? Why that choice for this flow?
- What happens if the CRM is down when a message arrives? Is the message queued, retried or lost?
- Where are the logs, and can I see them?
- If I want to change the AI agent's answers next month, do I need you to do it?
The choice between Make and n8n matters more than it seems. Make is quick to build and easy to read. n8n can be self-hosted and suits heavier logic. Custom code costs more upfront and gives you the most control. A partner should explain why they picked one for your case, not default to whatever they always use.
Check Whether They Build on the Official WhatsApp Business API
There are two ways to automate WhatsApp. Only one of them keeps your number safe.
The official WhatsApp Business API is Meta's sanctioned route for businesses messaging customers at scale. It supports verified business profiles, approved templates, opt-in rules and proper integrations with CRMs. Unofficial tools work differently. They script the consumer app or WhatsApp Web, imitating a person tapping a phone. They are cheap and quick to set up, and they break Meta's terms.
Why the official API matters
Your WhatsApp number becomes part of how customers reach you. If it gets suspended, every saved contact, every thread and every ad pointing to it stops working at once. Unofficial automation is the fastest way to lose a number, because it looks to Meta like exactly the behaviour its policies forbid.
The rules are also moving. Meta has tightened its usage policies on automation and message templates in 2026, and some AI chatbots that used to run through WhatsApp APIs are no longer allowed. For AI-driven WhatsApp automation, the agent has to be built for your business and your customers' questions, inside current policy. A general-purpose chatbot bolted onto a number won't qualify. A partner who isn't tracking policy changes will build you something that works until the day it doesn't.
Eligibility takes more than owning a phone number. A business needs the correct Meta assets in place before it can be approved. Partners who skip the documentation checks are the ones who stall halfway through a launch. If you want the whole build in order, we've written up building a WhatsApp chatbot in six steps.
How to confirm it's official
- Ask whether the integration uses Meta's Cloud API directly or goes through a Business Solution Provider, and which one.
- Ask to see the number inside WhatsApp Manager in a Meta Business account. It should be your account, not the agency's.
- Ask to see the approved message templates and their status.
- Be wary if setup needs a phone left on in an office, a QR code scanned on WhatsApp Web, or a SIM card posted to the agency.
Decide Who Owns the Code After Launch
The usual complaint: the dev shop builds and disappears, and the marketing agency can't change the site. WhatsApp automation has its own version. The agency builds the flows inside a platform it controls, charges a licence to keep them running, and you can't move without starting again.
Custom code vs black-box platforms
A black-box platform is fine until you need something it doesn't do. You might need to sync a field your CRM added, send a different message to wholesale customers, or swap CRMs. Then you are waiting on the agency's roadmap.
Custom code, or a Make or n8n workspace in your own name, works the other way. Any competent developer can open it, read it and change it. That matters for CRM integration in ecommerce, where order, refund and delivery events change as the store grows. It matters just as much for CRM automation in SaaS, where trial sign-ups, onboarding nudges and renewal reminders depend on product data that shifts with every release.
The principle applies beyond WhatsApp. For Lava Space, we built the Next.js site on a completely bespoke CMS that puts the studio in control. Projects, galleries, categories and client logos are uploaded and organised without calling a developer. Automation should leave you in the same position: able to run and adjust it without asking permission.
If you're deciding what to build first, start with your first five CRM automation flows. Get those right and owned before adding more.
What 'ownership' should mean in the contract
Put these in writing:
- The code repository sits in your account, or is transferred to it at launch.
- The Make or n8n workspace, scenarios and credentials are in your name.
- The WhatsApp number, Meta Business account and templates belong to your business.
- CRM API keys are issued by your account and can be revoked by you.
- Documentation explains what each flow does, what triggers it and where it fails.
- No ongoing licence fee is needed to keep what was built running.
If a partner resists any of these, you are renting your own customer conversations.
Compare How They Price the Work
You'll meet four pricing models when choosing a WhatsApp CRM integration partner. Each one changes who carries the risk.
| Pricing model | How it works | Works for you when | The catch |
|---|---|---|---|
| Fixed project fee | Scope and price agreed in writing before work starts | You know which flows you need and want a firm number | Scope has to be defined properly upfront |
| Monthly retainer | A set monthly fee for running, improving and extending flows | You want ongoing changes, monitoring and new automations | Watch for minimum terms and notice periods |
| Percentage of ad spend | Fee rises with your advertising budget | Rarely, if ever | The agency earns more when you spend more, not when you sell more |
| Hourly billing | Every hour is logged and invoiced | Very small, genuinely unknown tasks | A small automation becomes an open-ended invoice |
The setup is a project. Running it is a retainer. Keep the two separate and you can see what you're paying for. Meta's own messaging charges sit outside any agency fee and are billed to whoever owns the account, which should be you.
At Meant, builds are fixed scope and fixed price, agreed after a free 30-minute call. Automation and marketing run as monthly retainers you can stop, never a percentage of ad spend, and ad accounts are opened in the client's name. You can see how projects are quoted as a fixed price before you talk to us. For CRM automation in SaaS, where flows grow alongside the product, a stoppable retainer means you pay for the months you need, not the months a contract says you owe.
Signs You're Talking to the Right Partner (and the Wrong One)
Use this on the call. Most of it you can check in thirty minutes.
Green flags
- They ask how your team handles WhatsApp today before suggesting any tool.
- They show a live flow on a real number and let you message it.
- They build on the official API and set it up under your Meta Business account.
- They explain why Make, n8n or custom code suits your volume and logic.
- Price and scope are in writing before anyone starts.
- Retainers are month-to-month and can be stopped.
- You own the code, the workspace, the number and the templates at launch.
- The person you speak to is the person who builds it.
- Their case studies name clients and explain what was actually built, not just list logos.
Red flags
- A slide deck instead of a demo.
- Setup needs a QR code, a spare phone or your SIM card.
- Hourly billing with no cap, or a fee tied to ad spend.
- The flows live on their platform and leaving means rebuilding.
- No mention of Meta's policies or template approval.
- Vague answers about who maintains the AI agent's responses.
- A long minimum contract for work that should be stoppable.
A good WhatsApp CRM integration partner gives you clear, boring answers to every one of these. The wrong one will say "it depends" and change the subject.
Frequently asked questions
What is the difference between the WhatsApp Business API and the WhatsApp Business App?
The Business App is a phone app for small teams messaging customers by hand from one device. The Business API has no interface of its own. It connects your number to software, so a CRM, an AI agent and several staff can work from the same conversations. CRM integration and automation at scale need the API.
How long does it take to connect WhatsApp to a CRM?
It depends on two things: how quickly your business clears Meta's verification, and how many flows you need on day one. A single lead-capture flow is a much smaller job than a full sales pipeline with an AI agent and template messages. A good partner should give you the timeline in writing alongside the fixed scope.
Can WhatsApp automation integrate with Shopify or a custom-built CRM?
Yes, as long as the system has an API, and Shopify and most modern CRMs do. Order confirmations, delivery updates, abandoned-cart reminders and support threads can all flow between Shopify, the CRM and WhatsApp. A custom-built CRM usually needs custom code or an n8n workflow rather than an off-the-shelf connector.
What does WhatsApp CRM automation cost per month?
There are two parts. The agency retainer covers running and improving the flows, and Meta's messaging charges are billed separately to the account owner. At Meant, the retainer is quoted after the free call, runs month-to-month and can be stopped. It is never tied to ad spend.
Do I need my own WhatsApp Business API account, or can an agency provide one?
You should own it. The number, the Meta Business account and the templates are part of how customers reach you, so they belong under your business, with the agency given access. If an agency puts your number under its own account, leaving it later gets much harder.
If you want to see a live flow on a real number before deciding anything, book the free 30-minute call and Meant will show you how we build your WhatsApp CRM integration, end to end, and hand you the keys.
