WhatsApp CRM Integration: WhatsApp Leads Into Your CRM

View this page

How inbound WhatsApp messages become CRM leads with source, owner and history: the Cloud API webhook, field mapping, the 24-hour reply window, duplicates and ad attribution.

Organisation
WavX Solutions
Telephone
+919310079927

Description

Integration WhatsApp to CRM integration: every chat becomes a tracked lead

A WhatsApp to CRM integration receives every inbound WhatsApp message through Meta's Cloud API webhook, matches the sender to an existing contact or creates a lead, records the message and the ad it came from, assigns an owner, and lets that person reply from the CRM. It has to respect the 24-hour customer service window, verify Meta's signature and ignore the duplicate deliveries Meta's retries can cause.

Discuss an integration Last updated 2 October 2026

What this integration connects

In many Indian businesses, WhatsApp is where enquiries actually arrive, and the CRM is where the owner expects to see them. Between the two, leads are lost: a salesperson's phone holds the conversation, nobody logs the source, and a follow-up depends on memory.

The integration closes that gap. Each inbound WhatsApp message reaches your server through Meta's Cloud API, is matched to a contact or turned into a new lead, and appears in the CRM with the full thread, the owner assigned and the source recorded. Replies sent from the CRM go back out through the same API. The general API rules (templates, opt-in, messaging limits, pricing) are on WhatsApp Business API integration ; this page is about the join to the CRM.

Data flow: inbound message to CRM record

Customer sends WhatsApp message (or taps a click-to-WhatsApp ad)

Meta Cloud API ── POST webhook (X-Hub-Signature-256: sha256=…) ──▶ Your server

│ 1. verify signature with app secret

│ 2. reply 200 at once; queue the job

│ 3. skip if messages[].id already seen

look up contact by phone (wa_id)

├── found ──▶ add message to its timeline

└── new ────▶ upsert lead: name, phone,

source "WhatsApp", ad referral

──▶ assignment rule picks owner

CRM shows thread + "reply window open until 14:32"

Salesperson replies in CRM ──▶ your server ──▶ Cloud API send ──▶ customer

(free-form inside 24 h; approved template after)

Field mapping

WhatsApp webhook field

CRM field

Notes

contacts[].wa_id

Phone / mobile

The match key; store in one normalised format so existing contacts are found

contacts[].profile.name

Name (provisional)

It is the name the customer set in WhatsApp; mark it unverified

messages[].id

Message ID on the activity

De-duplication key

messages[].timestamp

Activity time

Unix time; convert to IST for staff

messages[].text.body

Activity or note text

Other message types have their own shapes

metadata.phone_number_id

Which business number received it

Routes to the right team when there are several numbers

referral (click-to-WhatsApp ads): source details and ctwa_clid

Lead source, campaign, click ID

What makes WhatsApp ad spend measurable in the CRM

Time of last customer message

Reply-window expiry

Drives the "window open" indicator and template choice

For Zoho CRM, the lead is written with the upsert API so a repeat sender updates the existing lead; see Zoho CRM integration . For HubSpot, contacts upsert on email, which WhatsApp does not provide, so the integration searches a normalised phone property instead; see HubSpot integration .

Limits and gotchas

Issue

What Meta documents

What the integration does

Duplicate deliveries

If your endpoint returns anything other than 200, Meta retries with decreasing frequency for up to 7 days, and retries can produce duplicates

Reply 200 first; de-duplicate on message ID

Forged requests

Payloads are signed with SHA256 in X-Hub-Signature-256 using your app secret

Verify every request before acting

Endpoint verification

Meta sends hub.mode , hub.challenge and hub.verify_token when the webhook is set up

Echo the challenge only if the token matches

Payload size

Webhook payloads can be up to 3 MB

Size the endpoint's body limit accordingly

Reply window

A customer message opens a 24-hour customer service window

Free-form replies inside it; a template after

Message charges

Charged when a template message is delivered; utility templates inside an open window are free; replying within 24 hours to a click-to-WhatsApp ad lead opens a 72-hour free entry point window

Show staff when a reply will be charged

Other common faults:

Phone formats that never match. The CRM holds "98000 00000", WhatsApp sends country code plus number. Without normalisation every repeat customer becomes a new lead.

One lead per message. Without a "find first" step, a ten-message conversation creates ten leads.

Slow handlers. Writing to the CRM before replying to Meta risks timeouts and retries. Queue, then write.

The thread lives only in the CRM's notes. Searchable history needs each message stored as its own activity, not appended to one long note.

What WavX builds

WavX builds the receiver (signature check, de-duplication, queue), contact matching on normalised phone numbers, lead creation with source and ad referral, assignment rules, a reply box inside the CRM that knows whether the window is open and offers the right templates, and a daily report of WhatsApp leads by source and owner. Where an AI assistant should answer first and hand over to a person, that is a WhatsApp AI chatbot feeding the same CRM.

For a team whose sales process does not fit Zoho or HubSpot, custom CRM development builds WhatsApp into the lead screen itself; that page also carries WavX's planning ranges for a CRM build.

Effort band

Quoted after scoping. For planning, the software cost estimator carries third-party integrations as a ₹60,000 line item inside a larger build. Meta's message charges, any WhatsApp provider's fees and CRM licences are paid to those vendors.

When not to build one

If one or two people answer every chat and leads are few, the WhatsApp Business app on a phone, plus a shared sheet for leads, may be enough. If your CRM vendor or WhatsApp provider already offers a maintained connector that matches contacts properly and records the source, try it first. Build custom when several people share one number, when you need to know which ads produce which sales, or when the CRM is your own.

Frequently asked questions

Can this work with the WhatsApp Business app on a phone?

Not for an automatic integration. The WhatsApp Business app is for people chatting on a phone or desktop; software reads and sends messages through Meta's WhatsApp Business Platform (Cloud API). Moving a sales number to the API is the first decision in this project, so it is made with the sales team, not around them.

Which CRMs can it connect to?

Any CRM with an API. Zoho CRM and HubSpot are the common ones, and a custom CRM is the most flexible, because the WhatsApp thread can be a native part of the lead screen rather than a note attached to it.

Can we reply to WhatsApp leads from inside the CRM?

Yes, within Meta's rules. A free-form reply is allowed while the 24-hour customer service window is open, which starts when the customer messages you. After it closes, the first message must be an approved template. The integration shows the salesperson whether the window is open.

Can we tell which ad a WhatsApp lead came from?

For click-to-WhatsApp ads, Meta's messages webhook includes a referral object with the ad's source details and, since September 2023, a click ID (ctwa_clid). We store those on the lead, so ad spend can be compared with leads and sales in the CRM.

Sources

Meta for Developers: Set up WhatsApp webhooks · read 2 October 2026

Meta for Developers: WhatsApp webhooks overview · read 2 October 2026

Meta for Developers: Webhook payload examples · read 2 October 2026

Meta for Developers: Graph API webhooks, getting started · read 2 October 2026

Meta for Developers: WhatsApp Business Platform pricing · read 2 October 2026

Meta for Developers: WhatsApp changelog · read 2 October 2026

Zoho CRM API v8: Upsert records · read 2 October 2026

HubSpot developer docs: Contacts API guide · read 2 October 2026

Related

WhatsApp Business API integration

Custom CRM development

Zoho CRM integration

HubSpot integration

How to send automated WhatsApp messages

Build your own software — your way, your pricing.

WavX Solutions is here to create your own software in a fully custom way, built exactly how you work — with a pricing model that fits your business. Connect now and let's build it.

Contact Now helpwavx@gmail.com

Reference material from WavX Solutions

Related questions WavX has answered

I run a facilities services company in Dubai with 15 sales and support staff. Most customers message us on WhatsApp, about half of them in Arabic. I want a CRM where the team can work in English or Arabic and every WhatsApp chat is logged. Is that buildable, and what should I ask a developer?

It is buildable. Ask for three things in the scope: a full right-to-left Arabic interface that each user can switch to, not just translated labels; the official WhatsApp Business API with chats stored against each customer; and Arabic-capable search, templates and PDF quotations. Also ask where data will be hosted and how the build would be designed around the UAE's data protection law, with your own advisers signing off. WavX names WhatsApp Business API among its integrations and works 8:30 AM to 5:30 PM UAE time. Source

Whatsapp business api crm integration india?

A custom CRM connects to WhatsApp through the official WhatsApp Business API, not through a personal number or an unofficial tool. Incoming messages attach to the right lead, salespeople reply from inside the CRM, and approved templates send quotations, payment reminders or follow-ups automatically. Message charges from Meta are billed separately from the software, and templates need its approval. For Indian businesses whose buyers enquire on WhatsApp first, this keeps every chat on company record instead of in an employee's phone. Source

Same buyer entered twice by different agents in crm duplicate leads?

Duplicate buyers appear when the CRM accepts a new lead without checking phone and email against existing records. The fix has three parts: normalise phone numbers on entry so country codes and spaces do not hide a match; block or merge on a match and show the agent who already owns the lead; and set a written ownership rule, such as first valid contact within a set number of days, that the system enforces. Then run a one-time clean-up to merge existing duplicates and their histories. Source

Can an AI chatbot reply in Arabic, and does the chat window support right-to-left text?

Language models can converse in Arabic, and a custom chat window can be built to display right-to-left text properly, including mixed Arabic and English lines, numbers and punctuation. The two are separate pieces of work: the model handles the language, while the interface needs right-to-left layout, Arabic fonts and mirrored alignment. For Gulf customers, both should be checked on real messages before launch. WavX names English, Hindi and Hinglish for its bots; Arabic quality depends on the model chosen. Source

Can leads from my website, Facebook ads, WhatsApp and IndiaMART go straight into my CRM without anyone typing them in?

Leads from all of these can land in a custom CRM automatically. Website forms post directly to the CRM; Facebook and Instagram lead forms come in through Meta's API; WhatsApp enquiries arrive through the WhatsApp Business API, which WavX names among its integrations; and B2B portals are connected where they offer an API or a lead email that can be parsed. Each lead is tagged with its source, checked against existing phone numbers for duplicates, and assigned by your rules. Source

I run a 25-person trading firm in Delhi. Billing and accounts are in Tally, orders and stock are in Excel, and leads come on WhatsApp. Should I get an ERP, a CRM, or both, and what should come first?

Start with the order-to-stock side, where a trading firm loses money: sales orders, purchase and stock as one system, with Tally kept for accounts and synced by integration. In WavX's published cost model a focused internal tool starts at ₹2,00,000 and a full ERP/CRM system at ₹9,00,000 before add-ons, so a first phase can begin well below the full figure. Add a light CRM for WhatsApp leads in phase two, on the same database. The price is negotiable, and a consultation at /contact will size your first phase. Source

I'm planning a WhatsApp bot for my D2C snack brand in India. We get around 8,000 customer chats a month, mostly order tracking and return requests. Apart from the build, what will I be paying every month, and to whom?

Expect four recurring payments on top of the build, which in WavX's published cost model starts at ₹1.5 lakh for a chatbot and more if it reads live order data. The model provider bills usage for the 8,000 chats; WhatsApp charges for business messaging through the Business API; your cloud host bills for server and database; and maintenance is 15–25% of the build cost per year. Order-tracking answers are short, so usage per chat stays low. WavX does not quote provider rates. The build price itself is negotiable, so state your budget up front. Source

Our support chatbot's monthly model bill has roughly tripled since we started sending the full conversation history and ten retrieved passages with every message. Answer quality did improve. How do we bring the cost down without losing that?

Keep the quality gains and cut the waste around them. Summarise older turns into a short running summary and send only the last few messages in full. Retrieve ten passages but re-rank them and pass the best three or four to the model. Cache the fixed parts of the prompt if your provider supports it, and cache answers to common questions. Route simple messages to a smaller model. Measure cost per conversation and accuracy on your test set after each change, so savings never come from worse answers. Source

WavX starting prices (base scope, before add-on features)

From the cost model behind the WavX calculators. A quote follows a scoping call; features, integrations and scale move these figures. Annual maintenance is typically 15–25% of the build cost.

BuildStarting priceTypical timeline
Landing pagefrom ₹40,0003–6 weeks
Business websitefrom ₹50,0003–6 weeks
E-commerce storefrom ₹1,50,0003–6 weeks
Internal tool / dashboardfrom ₹2,00,0003–6 weeks
Custom web applicationfrom ₹4,50,0006–10 weeks
SaaS productfrom ₹7,00,00010–16 weeks
ERP / CRM systemfrom ₹9,00,00010–16 weeks
AI chatbotfrom ₹1,50,0003–6 weeks
RAG assistant (your data)from ₹3,50,0006–10 weeks
AI agent / automationfrom ₹5,00,0006–10 weeks
AI feature in an appfrom ₹2,50,0003–6 weeks

Calculators: website, software, AI, mobile app. Pricing explained: https://www.wavxsolutions.in/pricing.

About WavX Solutions

WavX Solutions (WAVX — Web Application & Venture Exchange) is a remote-first, 100% custom software development company founded in 2022 in Gurgaon, Delhi NCR, India. WAVX designs, builds, scales and maintains custom websites, web applications, iOS and Android apps, Shopify stores, ERP/CRM software, loyalty systems, AI integrations and performance marketing for startups, businesses, brands and institutions across India.