A WhatsApp CRM built around the conversation
Keep every contact, custom field, segment, lead stage and consent decision in one place instead of three spreadsheets and somebody's phone. Create your account and import your contacts to get started.
The problem
Your customer list lives in five places at once
Most businesses that sell on WhatsApp do not have a contact problem so much as a scattering problem. Names sit in a Google Sheet, phone numbers sit in a phone, order history sits in accounting software, and the actual context — what this person asked last month, whether they said they were not interested — sits only in the chat thread of whoever handled it.
That works until you need to do something at scale. You want to message everyone in Pune who bought last quarter, and you cannot, because nothing joins those two facts together. You want to know why a customer is annoyed, and the agent who spoke to them left in March. Someone asks to stop receiving offers, it gets noted in a WhatsApp reply, and they get the next broadcast anyway.
That last one is not just embarrassing. On WhatsApp, people who did not want your message block and report you, and Meta scores your number on exactly that behaviour. Bad contact hygiene eventually shows up as a lower quality rating and a restricted ability to send.
Setting expectations
What a WhatsApp CRM is, and what it is not
A WhatsApp CRM is a contact and conversation database. It answers questions like: who is this number, what do we know about them, which segment are they in, what stage of our process are they at, who on our team owns them, and are we allowed to message them. It earns its place because all of that sits next to the chat, so an agent never has to alt-tab to know who they are talking to.
It is not a replacement for a full enterprise CRM. If you need deal forecasting, quote generation, territory management and a multi-channel account timeline, keep the platform that does that. Anyone who tells you a chat tool replaces Salesforce is selling you something. The realistic setup for a growing team is a WhatsApp CRM as the working surface for chat, and a general CRM as the system of record behind it.
If you are new to the category, our explainer on what a WhatsApp CRM is covers the ground in more detail.
WhatsApp contact management
What sits on a contact record
A contact is more than a phone number and a name. These are the pieces that make a list usable instead of merely long.
Custom fields
Add the fields your business actually runs on — city, plan, dealer code, class section, policy number, preferred language. They sit on the contact record and can be used to filter lists and personalise messages.
Contact groups
Group contacts into segments you can reuse: a city, a product line, a cohort, a webinar's attendees. Groups are the unit you point a broadcast at, so a clean segment is worth more than a big list.
Lead statuses
Define your own pipeline stages — new, contacted, quoted, negotiating, closed, lost — and move contacts through them. Status is a filter, so you can pull up everyone stuck at one stage and follow up.
Contact ownership
Assign a contact to a specific user so there is a named person responsible for it. Filtering by owner gives each agent their own book of contacts without splitting the database into silos.
Filtered lists
Search by name or number, then narrow by status, group, owner, favourite, or whether the contact has opted out. Every filter combination is a working list you can act on immediately.
Favourites
Flag the accounts that matter — the reseller who orders monthly, the parent who escalates, the client mid-renewal — so they surface without hunting through the full list.
Birthdays and anniversaries
Date of birth and anniversary are first-class fields on the contact, not something you have to bolt on as a custom field. Retail, wellness and education businesses ask for these constantly, so they are built in.
Ad-click attribution
When someone reaches you from a click-to-WhatsApp ad, the click identifier is stored on their contact record. You can trace which campaign brought a customer in rather than guessing.
Import and export
Bring an existing list in from a file, and export contacts back out whenever you need them elsewhere. Your contact data stays yours and stays portable.
Leads arrive on their own
A public contact webhook lets outside systems push new contacts straight into the database — a landing page form, an event registration, an internal tool. The lead exists as a proper record from the moment it is created, so the follow-up can start immediately rather than after somebody copies a row across on Monday morning.
Consent controls
Opt-outs are a database problem, not a good-intentions problem
Meta's WhatsApp Business Platform requires you to have opt-in before you message someone and to honour it when they ask you to stop. Most teams genuinely intend to comply and still get it wrong, because the request arrives as a message in one agent's chat window and never becomes a fact about the contact. If consent is not stored on the record, it does not exist as far as your next broadcast is concerned.
Opt out and resubscribe
Mark a contact as opted out and they drop out of your campaign audiences. If they later ask to hear from you again, resubscribe them — the record keeps the change rather than you re-adding a deleted row.
Block and unblock
Block a number when someone is abusive or a nuisance, and unblock it if the situation changes. Blocking is separate from opting out, because "stop marketing to me" and "stop contacting me at all" are different requests.
Opted-out as a filter
Opt-out state is a filter on the contact list, so you can audit who has withdrawn consent before a send instead of finding out from a complaint afterwards.
Treating consent as structured data rather than tribal knowledge is the single cheapest thing you can do to protect your sending reputation. It also happens to make your campaign numbers more honest, because you stop counting people who were never going to read you.
Typical setup
How teams get their contact database in order
A sensible order of operations, roughly a week's work for a small team with an existing list.
Decide what a contact record needs to hold
Before importing anything, write down the handful of fields your team asks about every day. Those become your custom fields. Resist adding twenty — a field nobody fills in is worse than no field.
Define your lead statuses
Map your real sales or support process into a short list of statuses. Four to six stages is usually enough. If two stages always get updated together, they are one stage.
Import your existing list
Bring in the spreadsheet you have been living with, mapping its columns onto your fields. Import first, tidy second — it is far easier to fix data once it is queryable.
Build the groups you will actually message
Create contact groups around the messages you plan to send, not around abstract categories. If you cannot name the message a segment would receive, you do not need the segment yet.
Assign owners
Give every active contact an owner. Unowned contacts are the ones that go quiet for three weeks and then churn.
Wire up lead capture
Point your website forms or lead sources at the contact webhook endpoint so new enquiries land in the database automatically, already tagged and ready for follow-up.
Set your consent rules and stick to them
Agree internally what counts as opt-in, honour opt-out requests immediately, and check the opted-out filter before every broadcast. This step is boring and it is the one that protects your number.
Where it connects
The contact database is the layer everything else stands on
Segments and statuses are only useful if something acts on them. The groups you build here are the audiences that template broadcasts go out to, and a lead status change is a natural trigger for a follow-up sequence so nothing stalls silently.
On the human side, contact ownership pairs with the shared team inbox, where several agents work the same WhatsApp number without tripping over each other. And if your reporting still happens in a spreadsheet, the Google Sheets integration keeps contacts flowing to where your analysts already live.
None of this works without official platform access first. If you are still deciding how to get on the API, start with the WhatsApp Business API and our primer on what the WhatsApp Business API actually is.
FAQ
Frequently asked questions
What is a WhatsApp CRM?
A WhatsApp CRM is a contact database built around the chat rather than around a sales pipeline. It stores who each person is, the fields you care about, which segment and lead stage they sit in, who owns them, and their consent state — all attached to the WhatsApp conversation your team is already having with them.
Does a WhatsApp CRM replace Salesforce or HubSpot?
No, and it is worth being honest about that. A general-purpose CRM handles deals, forecasting, quotes and multi-channel account history. A WhatsApp CRM handles the contact and conversation layer for one channel very well. Larger teams typically run both and keep the general CRM as the system of record.
Can I import my existing contact list?
Yes. Contacts can be imported from a file and mapped onto your fields, and exported again whenever you need the data elsewhere. Importing before you tidy is usually faster, because you can then filter and correct records in bulk instead of editing a spreadsheet by hand.
How does opting out work on WhatsApp?
Meta's WhatsApp Business Platform requires businesses to have opt-in before messaging people and to honour opt-out requests. In ChatSetu AI you mark a contact as opted out and they are excluded from campaign audiences; you can resubscribe them later if they ask. Ignoring opt-outs damages your quality rating and can restrict your ability to send.
What is the difference between blocking a contact and opting them out?
Opting out means the person no longer wants promotional or broadcast messages from you, but you may still handle a support conversation they start. Blocking is stronger — you are cutting the contact off entirely, usually because of abuse or spam. They are separate controls because they answer different requests.
Can I see which ad a contact came from?
If someone arrives through a click-to-WhatsApp ad, the click identifier is recorded on their contact record. That gives you a trail from ad click to conversation to outcome, so campaign attribution is based on stored data rather than assumption.
Get your contact data in one place
Create your account, or message us on WhatsApp and we'll help you import and organise your contacts at onboarding.