A WhatsApp message lands as a lead and a ticket, not in someone’s phone
WhatsApp helpdesk and lead capture for Indian service businesses — each inbound message is matched to a contact, logged on a lead and opened as a ticket, and your team replies from that ticket.
The challenge
For many Indian businesses, WhatsApp is where customers actually ask for things: a quote, a site visit, a fix for equipment that stopped working this morning. Those messages arrive on one phone, or a WhatsApp Business app shared by a few people, and the only record of them is the chat itself. Whether anyone follows up depends on who happened to read it.
That breaks both sales and support. A pricing enquiry never becomes a lead, so it never shows up in the pipeline or the source report. A fault report never becomes a ticket, so there is no assignee, no SLA clock and no thread anyone else can pick up. The photo of the faulty unit lives in a chat that the engineer, the account manager and the person who will eventually raise the invoice cannot see.
Forwarding messages into a CRM by hand doesn’t fix this; it just adds a step that gets skipped on a busy day. What works is a system that receives the message directly, recognises an existing customer by phone number, and creates the lead and the ticket itself, so the conversation is on the record from the first message.
How DexVee helps
One inbound message, four linked records
DexVee receives WhatsApp through Twilio, acting as the WhatsApp Business Solution Provider for your business number. A message that opens a new enquiry is matched to a contact and fans out into a lead, an activity and a helpdesk ticket, all linked to each other and to the customer’s account.
Matched to the right contact
The sender’s number is compared on its last ten digits against the phone and mobile fields of your existing contacts, so a customer saved as “98765 43210” months ago is recognised. A new contact is created only when nobody matches.
A lead with WhatsApp as its source
A new enquiry opens a lead with source WHATSAPP and an owner, and logs a WhatsApp activity on its timeline. If the contact already has an open lead, the message is appended to that lead instead of opening a duplicate.
A helpdesk ticket, threaded by conversation
The enquiry opens a WhatsApp-channel ticket linked to the contact, lead and account, assigned to the lead’s owner. Follow-up messages while that ticket is open are added to its thread, so five messages in a row stay one ticket.
Photos and documents saved
Media is downloaded from Twilio as it arrives and stored in DexVee’s own document storage, then attached to the ticket (and to the lead for a new enquiry). It doesn’t depend on a provider link that expires later.
Ticket email with one-click assign
A new WhatsApp ticket emails your configured internal recipients with the message and an Assign link per team member. Each link is signed, single-use and expires after seven days, and it opens a confirmation page before anything changes.
Replies from the ticket, with rules
Replies go out from the number the customer messaged. A super administrator can send freely; everyone else replies only on a ticket they can access, and only to a number already on that ticket. Every message is kept under Helpdesk > Messages.
What this looks like in practice
- An existing customer’s WhatsApp fault report opens a ticket on their own contact and account, with an owner, instead of sitting unread on a shared phone.
- A WhatsApp pricing enquiry appears in the sales pipeline as a lead you can report on by source, not as a chat someone meant to forward.
- The engineer, account manager and support lead all see the same thread and the same photos, on the ticket, without anyone forwarding screenshots.
Frequently asked questions
The business number has to be connected through Twilio as the WhatsApp Business Solution Provider, because Twilio is what delivers each message to DexVee. Messages sent to a phone running the WhatsApp Business app never reach DexVee. Each delivery is checked against Twilio’s signature, and a request that fails the check is rejected before it touches your CRM.
Nothing new is created. Every message is recorded with Twilio’s unique message ID, and a repeat delivery with an ID already on file returns the existing ticket. The same ID is stored on the lead, so a replay can’t open a second lead either.
WhatsApp only allows free-form replies within 24 hours of the customer’s last message. DexVee doesn’t block a late reply in advance: if WhatsApp rejects it, the agent sees a plain-language reason and can send the pre-approved message template instead. Delivery status for every reply is tracked.
No, not today. The customer’s message opens a ticket and alerts your team, and the first WhatsApp reply comes from a person. If the contact has an email address on file, the helpdesk’s “ticket received” email can go out, subject to your outbound email settings.
From our Insights
From WhatsApp Message to CRM Lead and Helpdesk Ticket
How DexVee turns one inbound WhatsApp message into a deduplicated contact, a WHATSAPP-source lead, an activity and a helpdesk ticket, with media stored.
CRM for IT MSPs: What to Look For
Most CRM guides target one-shot sales teams. Here's what matters when you're an IT MSP running support contracts, tickets and dispatch.
Why SLA Reports Don't Match Reality
SLA dashboards that look green while customers are frustrated usually have one of a handful of specific measurement problems. Here's how to find them.
Ready to see WhatsApp Ticket Intake in action?
Talk to our team about your specific workflow — no generic demo script, just a conversation about what you actually need.