WhatsApp CRM with your own AI key
For many Indian businesses, WhatsApp is where enquiries actually arrive. A buyer sees a reel, taps the WhatsApp button and asks "price?". If that chat sits in one person's phone, it never reaches the CRM, nobody follows up, and nobody knows it was lost.
This post covers how to bring chats into a CRM properly, where automation helps and where it does not, and how an AI assistant can work on your own key. It describes WhatsApp CRM in TaskSync, which is included with the Sales CRM add-on.
Step 1: one inbox, not five phones
The first win is simply putting every chat in one place. TaskSync's Conversations inbox holds WhatsApp, Instagram Direct and Facebook Messenger chats together, with Mine, Unassigned and All, filters by status, channel and tag, internal notes, snooze and delivery ticks.
Connecting does not need your own Meta developer app. Continue with Facebook uses TaskSync's Meta app; the person connecting must be an admin of your Meta business, and you need a WhatsApp Business account. Each company connects one WhatsApp number. Each WhatsApp number and each Facebook Page with Messenger or Instagram is charged as a connection, and you see the price before connecting.
You also decide who sees what: all chats, the team's own chats, the team's plus unassigned, or only chats assigned to the person. Each number or Page can belong to a team.
Step 2: route chats to the right record
A chat on its own is not a CRM. The useful part is what happens to it. Routing rules look at the channel, whether the person has an open ticket or an open lead, whether they are a known customer, words in the message and office hours. Then they:
- add the message to the open ticket,
- create or update a lead,
- create a ticket,
- assign the chat to a person or a team, or
- add tags.
So a known customer asking about a delivery goes to support, while a new number asking for a price becomes a lead with an owner and a first-response target, like any lead from IndiaMART or a web form. See respond to IndiaMART leads in 15 minutes for how those targets work.
Step 3: chatbot flows for the first questions
Before any AI, a simple flow does a lot. TaskSync's chatbot flows start from templates such as Lead capture, Support triage and an office-hours away message. They use buttons, lists, questions with checked answers, branches and hand-over to a person. You can test the chat, publish it, keep versions and see analytics.
A good first flow asks two or three things: what the person wants, their city or pincode, and for B2B, the quantity. That is enough for routing and for the salesperson to reply with something useful.
Step 4: an AI assistant, on your key
Some questions repeat endlessly: "do you ship to Pune?", "what is the return policy?", "is the blue one in stock?". An AI assistant can answer these at night and on Sundays. TaskSync has no platform AI of its own. The optional assistant runs on Claude through your own Anthropic API key:
- You create the key in your Anthropic account and paste it into TaskSync.
- Anthropic bills you directly for what it uses. TaskSync charges nothing for AI.
- Your chats go to Anthropic only if you connect your key, and they are never used for training.
The assistant answers only from what you give it: your published help articles, your own questions and answers, products (with the price your customer would see and stock shown only as in stock, low or out of stock, never cost or exact quantities) and the policies you type in. It can look up the customer's own order, save a lead, open a ticket or hand the chat over. When it does not know, it says so and hands over with a short summary for the team. It never makes up prices, stock, delivery dates or policies.
Keeping cost and quality under control
Two worries come up with AI on customer chats: cost and wrong answers. Both have controls.
Cost. You set a monthly token limit, a monthly spend limit in US dollars and a cap on AI replies per chat. Managers are warned at 80% and 100%. At the limit, the AI stops and chats go to the team. A spend limit in your Anthropic account is a second safety net.
Quality. Questions the AI could not answer go to a review queue, where someone writes the answer, links an article or marks it for hand-over. Team ratings, a weekly report and your own test questions show whether it is getting better.
Rules that come from WhatsApp itself
WhatsApp has its own rules, and any honest setup works within them:
- Outside the 24-hour window after the customer's last message, you can only send a template approved by Meta. Templates are made in Meta and read into TaskSync.
- The AI never sends templates and only answers inside the 24-hour window.
A catalogue link instead of a PDF
Instead of sending a 20 MB PDF catalogue, put a private catalogue link with your prices and stock into a reply. The customer can request a quote, which makes a lead and a draft quote, or send an order request.
A sensible order to roll it out
- Connect WhatsApp and move the team into the shared inbox.
- Add two routing rules: known customers to support, new numbers to leads.
- Publish a short lead capture flow and an away message.
- Write ten good answers and your policies, then switch the AI on for one channel with tight limits.
- Review the queue every week.
For the sales side, see the Sales CRM and sales commission; for privacy, the Trust centre.