Contact form or WhatsApp: what actually happens to each lead

A contact form can go months without delivering a single notification and nobody notices. WhatsApp tells you whether the message landed. Here is the plumbing of both channels, and the checks you can run yourself this week.

It is Tuesday afternoon and the phone goes. Whoever it is sounds annoyed: "I messaged you through your website three weeks ago and nobody got back to me."

You search your inbox. Nothing. You check junk. Nothing. You log into the website admin and there it is: 9 July, 21:14, name, phone number, four lines of message. The form did its job. The notification email never got out of the building.

The uncomfortable bit is not that customer. It is the question behind them: how many others.

"Contact form emails not being received" is an entire genre on the WordPress support forums, and it is nearly always answered the same way — install an SMTP plugin. Sometimes that works. It explains nothing. And the real difference between the two channels is not a matter of style: the form's failures are silent, and WhatsApp's almost never are.

A form has seven steps and only the last one leaves a mark

For an enquiry typed on your website to become a reply from you, seven things have to go right:

  1. Someone starts filling it in.
  2. They finish.
  3. The captcha or spam filter doesn't wrongly reject them.
  4. The submission gets stored somewhere.
  5. The notification email goes out.
  6. It lands in your inbox rather than junk.
  7. Somebody reads it and replies.

Step 4 is not obvious. Contact Form 7, the most-installed form plugin on WordPress, does not store submissions by default — you need its companion plugin, Flamingo. Without it, if the email fails, the message exists nowhere. There is no admin screen to check.

Of the seven steps, six fail without telling you. You only ever find out about the seventh.

Why the notification lands in junk: the "From" field mistake

The commonest failure has a very specific cause and almost nobody explains it.

Plenty of forms put the visitor's email address in the notification's From: header, so you can just hit reply. It sounds sensible. But your server is now sending a message claiming to come from customer@btinternet.com, and BT has not authorised your server to speak for it.

That is what DMARC checks: whether the domain in From: lines up with the domain authenticated by SPF or signed by DKIM. If it doesn't, the receiving server applies whatever policy that domain publishes. You can look it up yourself in ten seconds:

dig +short TXT _dmarc.btinternet.com

As of 1 August 2026, btinternet.com, sky.com, virginmedia.com and yahoo.co.uk all publish p=reject, and icloud.com publishes p=quarantine. In plain terms: a lead with a BT, Sky, Virgin or Yahoo address gets refused outright, and an iCloud one goes to junk. Not because of what it says. Because of the header. Contact Form 7's own documentation is blunt: put an address on your own domain in From, and the visitor's in Reply-To.

There is also a floor that does apply to you. Since 1 February 2024, Google has required every sender — not just bulk ones — to have SPF or DKIM, valid reverse DNS, a TLS connection and a spam rate below 0.3% in Postmaster Tools. The hard requirements (SPF and DKIM and DMARC, aligned) start above 5,000 messages a day, and Microsoft has applied the same since May 2025. Your form is nowhere near that. The alignment failure breaks you at any volume.

What WhatsApp shows you that email doesn't

Next to that, WhatsApp's plumbing is boring, which is exactly what you want.

When you reply through the WhatsApp API, Meta returns a status for every message you send: sent, delivered, read or failed. You know whether it landed. Email has no equivalent — a message that drops into junk has been delivered perfectly well as far as the protocol is concerned, and nobody tells you.

Two more differences. The number they message from is verified by definition, because they are messaging from it; on a form, the phone and email are just text somebody typed, and one wrong character is a lead lost silently. And replying currently costs nothing: Meta's pricing documentation has made service conversations — the ones the customer opens — free since 1 November 2024. Note that a rate card update is announced for 1 October 2026, so check the source before you build a budget on it.

It also helps that the channel is not niche. Ofcom's Online Nation report, published on 10 December 2025, found WhatsApp used by 90% of UK online adults, with 74% using it daily.

The numbers you'll read elsewhere, and why they're useless

Search this comparison and you get the same three every time: WhatsApp has a 98% open rate, forms convert at 4% and live chat at 30%, 78% of customers buy from whoever replies first. We could not trace an original study behind any of them. They are copied from blog to blog with no methodology, no sample size and no date.

The one piece of work here with a name and a method is the Lead Response Management Study, built on InsideSales.com data and led by James Oldroyd, then at MIT Sloan: six companies, three years, more than 15,000 leads. Its finding — the odds of qualifying a lead drop 21 times if you ring at 30 minutes instead of 5 — is still the best available. It is also from 2007, and about phone calls to US B2B leads. Use it for direction, not for your forecast.

What the law says (less than you think)

The Electronic Commerce (EC Directive) Regulations 2002, reg 6, require you to make easily, directly and permanently accessible your details, "including his electronic mail address, which make it possible to contact him rapidly". A form is not a substitute for that address.

No UK statute gives you a deadline to answer a sales enquiry. Replying fast is a commercial decision, not a legal one. The rules bite in the other direction: message someone who never contacted you and that is direct marketing by electronic mail under PECR reg 22 — the ICO's guidance treats in-app and direct messages as electronic mail — so you need consent or the soft opt-in. Switching channel changes nothing there.

What changing channel doesn't fix

This is the part that decides whether any of it helps you.

It doesn't fix response time. A WhatsApp left unanswered for two days is a contact form with a different icon. We've written about that asymmetry and about evenings and weekends.

It doesn't give you tidy data. A form hands you structured fields and a consent tickbox with a timestamp. A conversation doesn't.

"Read" doesn't always arrive. That status is only sent if the customer has read receipts switched on, and plenty of people don't.

And the ordinary WhatsApp Business app lives on a handset. If that handset belongs to a salesperson, their conversations leave with them.

Four checks worth doing this week

  1. Send a test through your own form from a Gmail, a BT or Sky address and an Outlook one. Check junk as well as the inbox.
  2. Open your form's mail settings. If the visitor's address is in From, move it to Reply-To and put one of yours in From.
  3. Compare stored submissions against emails actually received over the same period. That gap is your silent loss.
  4. Take the last twenty enquiries and record how long the first human reply took. Use the median: two minutes on one and three days on another is not "a day and a half".

None of these costs anything, and together they tell you more than any borrowed statistic.

And then there's actually replying

All of the above fixes the plumbing. It doesn't fix there being nobody there at ten at night.

That is what we built Zatio for: it replies in seconds on WhatsApp and on your website chat, says it is an AI in its first message, and hands the conversation to your team with the context when it needs to. It does not answer the phone and it will not fix your DNS. Those two remain yours.

← All articles