A lead who fills your form at 11:40 at night and hears back on WhatsApp the next afternoon has usually spoken to two other vendors by then. With WappBlaster, your CRM can fire a webhook the moment the lead is created and send an approved template within seconds. The hard part is deciding who owns the lead, and what happens when the data is wrong.
What the CRM webhook payload has to carry for WhatsApp
Most broken integrations fail on the payload. Agree on the minimum the CRM sends when a lead is created:
- Phone in E.164 format, for example +919812345678. Strip spaces, leading zeros and the "91-" prefixes people type into forms.
- Template name and language code, so the CRM picks the approved message instead of a hardcoded default.
- Variable values in template order: first name, the product they asked about, the branch.
- Your own lead or deal ID. It returns with delivery and reply events, so nothing downstream searches by phone number.
- The routing field: territory, pincode, product line or deal value band.
Teams skip the reference ID and regret it when a reply arrives from a number sitting on three old records.
Picking a lead routing key that uses what the CRM knows
Round-robin needs no data, which is why it is the default, and it throws away context. A lead from Pune asking about commercial fit-outs should not go to the person handling residential enquiries in Jaipur just because it was his turn.
| Routing key | Works well for | Watch out for |
|---|---|---|
| Territory or pincode | Field sales, dealers, multi-branch service businesses | Pincode missing on web forms; keep a fallback owner per state |
| Product interest | Specialist teams, such as loans versus insurance | Leads that tick several interests; pick a primary one |
| Deal value band | B2B teams where senior reps take large accounts | Self-reported budgets are often wrong; re-route after qualification |
Round-robin still works as the tie-breaker inside a pool of equally suitable people.
Lead routing from CRM form to first WhatsApp reply
- The lead is created in the CRM from a form, an ad or a logged call.
- A CRM workflow checks the phone format and calls WappBlaster's REST API with a scoped key.
- WappBlaster sends the approved template and returns a message ID.
- The owner is set from the routing field, and the conversation is assigned to that person in the shared team inbox.
- Delivered, read and replied events come back as signed webhooks, and the CRM stamps each timestamp on the lead.
- When the customer replies, the 24-hour service window opens, and the owner can answer in free text, with buttons or with a list.
Step five shows a sales manager, inside the CRM, which leads never read the message and need a call. Signature checks, retries and the full event list are on the webhooks and API page for developers.
Handling junk numbers and double webhook fires in lead routing
Every lead source carries junk: numbers without a country code, landlines, test entries from your own staff.
- Validate at the CRM end. A format check before the webhook fires stops most bad numbers.
- Read the failure reason. A failed send returns Meta's reason code. Write a "WhatsApp unreachable" flag to the lead so the owner phones instead.
- Do not retry permanent failures. Resending to a number not on WhatsApp only adds noise.
- Fire once. A workflow triggering on both "created" and "updated" sends two welcomes. Trigger on creation, or check a last-sent field.
Who owns the WhatsApp follow-up after CRM lead routing
The sequence should live in whichever system knows when to stop. If the deal stage flips to won or lost, that signal must end the follow-ups. WappBlaster's two-way sync writes the WhatsApp thread back to the CRM record and can start a drip from a stage change, so with Zoho, HubSpot, Salesforce or LeadSquared the stage can drive both the start and the stop. The Zoho CRM and WhatsApp integration guide walks through one field mapping end to end.
When CRM webhook lead routing is overkill
If you get a handful of leads a week and one person answers all of them, a shared WhatsApp inbox with saved replies will serve you better than an integration project. Automated routing also goes badly when:
- The CRM's owner field is stale, so leads get assigned to people who left months ago.
- Marketing templates go to leads who only asked for a callback. Consent to be contacted about an enquiry is not consent for promotions.
- No rule catches the leftovers. Every routing table needs a default owner for leads that match nothing.
On cost, WappBlaster charges a flat ₹7999 a year in India ($200 elsewhere), and Meta's per-message charge for each delivered template is passed through at cost and itemised on the invoice.