When WhatsApp enquiries start getting lost

Most established businesses we look at can tell you roughly how many enquiries they get. Very few can tell you what happened to the ones from last month. The messages are all still there, scattered across three phones — and that is exactly the problem.

Where the enquiry actually goes

A customer messages the number on your website, or the one a friend gave them. It lands on a phone. Someone answers, asks a few questions, promises a price, and gets pulled into something else. Nothing has failed yet — nothing has been recorded either.

The enquiry now exists in one place only: a chat thread on one device, in one person's memory. Everything that happens next depends on that person remembering to look at it again. That is not a process. It is a habit, and habits break under load — which is to say they break exactly when business is good.

Six ways an enquiry disappears

The failures are boringly consistent. Almost every one we see is a version of these:

• There is no single record. The enquiry lives in a chat, so nothing outside that chat knows it exists.
• Ownership is unclear. Two people saw the message, each assumed the other replied, and neither did.
• The quote went out and the follow-up did not. Sending a price feels like completing the task, so the thread goes quiet and stays quiet.
• The customer's history is scattered. A returning buyer has to explain the last order again, because the previous conversation is on a different phone.
• Nobody can see the pipeline. Management can describe the busy weeks but cannot list the open opportunities.
• The relationship depends on one person's memory. When they take leave, change roles or leave the company, the customer relationship leaves with them.

Notice that none of these is a communication failure. The messages were received and read. What failed was everything after the message.

WhatsApp is not the problem

It is worth being clear about this, because the usual advice is to move customers onto a form or a portal. In this region that advice mostly loses you the enquiry. Customers message on WhatsApp because it is instant, because they can send a photo of the part they need, and because they can see that you read it.

Keep the channel. The fix is not to move the conversation somewhere the customer does not want to be — it is to add structure behind the conversation, so that what happens in the chat also exists somewhere the business can see.

A process that holds

The structure that fixes this is small. Seven stages, each with one thing that has to be true before the enquiry moves on:

1. 1EnquirySomething arrives — a WhatsApp message, a call, a website form, a walk-in. The channel does not matter; being captured does.
2. 2RecordIt is written down once, in one place, with the customer, what they asked for and when. This is the step almost everyone skips, and the one everything else depends on.
3. 3OwnerOne named person is responsible for it. Not a team, not a group chat — a person, so that 'someone will handle it' is never the answer.
4. 4QuoteThe price goes out, and the record notes what was quoted, on what date, and against which specification.
5. 5Follow-upA date is set at the moment the quote is sent, not left to memory. If that date arrives and nothing has happened, it should be visible to someone other than the owner.
6. 6OutcomeWon, lost or dormant — and, when lost, one word on why. Price, lead time, specification, no reply. This is the cheapest market research a business can do.
7. 7ReportingOnce a month: how many enquiries, how many quoted, how many won, and what the common reasons for losing were.

That is the whole thing. It does not require software to exist — plenty of businesses run it in a shared sheet for a year before they need anything more. What it requires is that the steps are agreed, that one of them is 'write it down', and that someone looks at the result once a month.

Fitting it around WhatsApp rather than against it

In practice the shape that works looks like this. Enquiries keep arriving on WhatsApp. The person who picks one up logs it — customer, request, date, owner — before they answer, or immediately after. Conversation continues in the chat. Quotes are produced from a template so they look the same whoever sends them, and the record notes when one went out and when to chase it.

Two details make the difference between this holding and quietly collapsing. The first is that logging has to take seconds, not minutes: if the record is a long form, nobody will fill it in during a busy morning. The second is that the follow-up date has to be visible to more than one person, because the entire failure mode of the old way was that it was visible to exactly one.

A business number rather than a personal one is usually the next step, because it makes the account portable between staff. That is a change worth making deliberately, with the history exported first, rather than in a hurry when someone resigns.

Where to start

Start with the record, not the software. Pick the enquiries from the last two weeks, put them in one list with an owner and a next action against each, and see how many of them nobody could account for. That number is usually the argument for doing the rest of it.

Then agree the seven stages with the people who actually handle enquiries — the ones taking the messages, not only the ones reading the reports. A process designed around how the work already happens survives. One designed against it gets bypassed within a month.