WhatsApp to CRM integration: every chat becomes a tracked lead

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

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

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.