Google said 2 leads and WhatsApp said 0

Last week I put a Google ad up for PSFY. A few days in, the dashboard showed two conversions. Two people had filled in the site's form asking to be contacted.

I opened WhatsApp to reply and there was no message at all.

That is how I found out my own site was throwing leads in the bin.

Nothing had failed

That is the part that stings. No red screen, no warning, no error logged anywhere.

The person filled in name, company, email, phone and a message. Pressed send. The site thanked them. From where they stood, the request had been made.

On my side nothing arrived.

The hole was in the handover

The form did not store the data anywhere. It assembled a ready-made message and opened WhatsApp with that text already written.

Whoever pressed send inside WhatsApp became a conversation. Whoever closed the tab, lost signal halfway, was on a computer without WhatsApp Web logged in or simply gave up, became nothing. The data did not exist anywhere because it had never been saved.

The form worked. The delivery is what did not happen.

And that is the difference between a process with a bug and a process with a hole. A bug throws an error and somebody complains. A hole throws nothing, so nobody complains, and you spend months thinking everything is fine.

Why nobody sees it

To spot this kind of hole you need two things at once.

The first is somebody looking. A website form is the thing a company sets up once and never tests again.

The second is a second number to compare against. If all I had was WhatsApp, I would have seen zero messages and concluded that nobody was interested. Zero is a perfectly plausible number. It accuses nothing.

The ad is what created the second number. Google counted who filled the form in. WhatsApp counted who arrived. Two systems measuring the same event and giving different answers.

That gap was the alarm. And it was the only one there was.

The cheapest alarm an operation can have

This has nothing to do with websites. It has to do with any process.

Every time data moves from one place to another, it can be lost in the handover without raising an error. And the way to find out is always the same, take two sources that should be counting the same thing and compare them.

A few comparisons worth running in your company.

• The system recorded 40 orders this month and finance invoiced 37
• The CRM holds 120 leads and sales remembers talking to 80 people
• Inventory says the part is there and the shelf is empty
• HR approved 12 hires and payroll has 11 new people

None of these cases raises an error in any system. All of them are handover holes. And all of them show up the moment you put the two numbers in the same table.

You do not need a new tool for this. You need somebody asking the question.

How to test your own site in two minutes

If your site has a form that opens WhatsApp, run this test now.

1. Fill in the form with test data
2. When WhatsApp opens, close the tab without pressing send
3. Go wherever leads are supposed to land, email, spreadsheet or CRM
4. Look for the test you just ran

If you cannot find it, you have the same hole. Everyone who gave up halfway never existed for you.

Worth repeating on a phone and on a computer, because WhatsApp behaves differently on each.

What we did

The fix is simple to understand. The site now saves before it hands over.

Now, the moment somebody presses send, the data goes first to a flow that records the lead and emails me. Only then does WhatsApp open. If they carry on with the conversation, great. If they give up, I already have the name, the company, the phone number and what they wrote, and I reach out myself.

It is the same logic as any well-built process. Record at the point of entry, not at the point of exit. Anyone who only records when the flow completes never finds out about the people who dropped out halfway, and that is exactly the information you miss most.

What this teaches

I work on company processes and I had a process hole at my own front door. It was not carelessness. It was what it always is, a process nobody tested after building it.

A process does not break where you are looking. It breaks in the handover between two things, where nobody is the owner.