What Happens to a Lead After It Sends You a WhatsApp Message?

For many businesses WhatsApp is the front door. A message arrives at 9:40 in the evening: a price question, a photo, a “is this available?”. What happens next is rarely designed. It just happens, or it doesn’t.

The path most businesses have

1. The message lands on one person’s phone, or a shared number.
2. Whoever sees it replies, when they can.
3. Details are typed into a spreadsheet later, or not at all.
4. A follow-up is meant to happen in a few days. It depends on memory.
5. If the person who took the message is away, the lead waits.

None of these steps is careless. The path is just implicit, so it fails at the handoffs: between the chat and the record, between the person and the calendar, between the first reply and the follow-up.

The same path, designed

Designing it means deciding each of these on purpose:

• Capture: the message becomes a record, with the contact, the channel, the time and what was asked.
• Understand: is this a new lead, an existing customer, or something else? What are they asking for?
• Decide: who owns it? What is the target for a first reply?
• Act: the first response goes out, and the next action is scheduled, not remembered.
• Remember: every step is recorded so anyone can pick it up.

What should stay human

Not all of this should be automated. Reading a customer’s tone, negotiating a price, deciding whether an odd request is worth taking: those stay with a person. The design goal is that the person’s time goes there, and the routine parts (recording, reminding, routing) don’t depend on them.

How fast should the first reply be?

Pick a target you can actually meet, and write it down. A target of “within a few minutes during working hours” that is met is worth more than “instantly, always” that is not. Many businesses split it in two: an immediate acknowledgment that confirms the message was received and says when a person will reply, and a considered reply from a person during working hours.

The acknowledgment is a good candidate for automation because it is routine. The considered reply often needs judgment, so the system can draft it and a person can approve it.

What should a message become in your records?

Decide the few fields that matter before you automate anything. For most small businesses a useful lead record holds:

• Who: name, phone number, and which channel they used.
• What: the request in their own words, plus what you understood it to be.
• When: the time of the first message and any timeframe they gave.
• Owner: the one person responsible for the next step.
• Next step: what happens next and by what date.

Keep the list short. Every extra field is something a person must fill in or a system must guess.

How do you test the path?

Send yourself a test message from a phone that is not on your contact list, outside working hours, and follow it. Did it become a record? Did it get an owner? Did anyone reply, and when? Was a follow-up scheduled? Then send a second message from the same phone and see whether it joined the first conversation or created a duplicate. Ten minutes of this shows you more than any diagram.

Who covers the number out of hours?

Decide this on purpose. Options include a rota, a shared inbox that one person checks first thing, or an automatic acknowledgment that sets expectations until someone is back. What matters is that every message has an owner by the next working morning, and that nobody has to wonder whether someone else already replied.

What about customers who write on more than one channel?

People move between WhatsApp, email, and phone calls without thinking about it. If each channel creates its own record, one customer becomes three leads and nobody sees the whole history. Match on something stable, such as the phone number or email address, so a new message joins the existing record. When the match is uncertain, flag it for a person instead of guessing.

Where it usually breaks

• Nobody owns the message outside working hours.
• The record is created but the next action is not.
• The lead goes quiet and nothing notices.
• The customer contacts again on another channel and is treated as new.

Write your own version of this path. Where does the trail go cold? That step is where a system would help first. You can try it with the System Brief, which structures a workflow you describe and runs it once as a fictional case, or show us your workflow and we will map it with you. The wider picture is on workflow automation.