Your contact form is where leads go to die

Every website has one. Name, email, message, send. It has been the default since roughly 2004 and it survives because it is easy to build, not because it works. If you have ever filled one in yourself, you already know the feeling: you are fairly sure you have just posted a letter into a wall.

What the form actually does to your conversion rate

Three things, all bad.

• It asks for effort before it gives value. A visitor with a thirty-second question has to hand over an email address and then wait an unknown amount of time. Most do not; they leave and ask a competitor whose number is one tap away.
• It has no acknowledgement worth the name. "Thanks, we'll be in touch" is not a receipt. The customer cannot tell whether it arrived, and neither can you.
• It arrives as email, which is where urgency goes to be triaged. A form submission at 8pm on Friday is read on Monday, in a folder alongside invoices and newsletters, competing with everything else in an inbox.

The result is a response time measured in hours for a decision the customer is making in minutes. Everyone in sales already knows the shape of this curve: the odds of converting a lead collapse quickly after the first few minutes and keep collapsing. What is strange is how much money businesses spend driving traffic to a page whose last step is designed to lose it.

Why messaging fixes it and a chatbot mostly doesn't

The instinct is to bolt a chat widget on. Sometimes that helps. Usually it produces a second version of the same failure, for a specific reason: a website chat widget only exists while the tab is open. The customer closes the tab, the conversation is gone, and if your answer arrives ten minutes later there is nowhere for it to land.

A WhatsApp conversation does not have that property. It persists in an app the customer already checks, on a thread they can return to, with a message history both sides can see. If you answer in four minutes, they get a notification. If you answer in forty, they still get it, and the context is still there.

A chat widget is a conversation that ends when the browser tab does. That is the whole difference.

What we built

Let's Tok replaces the form with a WhatsApp conversation on your own business number. A visitor taps, the thread opens with the context of the page they came from, and an automated flow you configure answers the routine questions immediately — hours, price ranges, delivery, availability, whatever people actually ask you.

Three design decisions are worth calling out, because they are the ones we would want to know about if we were buying it:

• The number is yours. You connect your own WhatsApp Business Account through Meta's official flow. The business identity on every message is your business, not ours. We are the software behind the conversation and never the sender.
• A human is always one message away. The automated flow's job is to be fast on the easy 70%, not to hold the customer hostage. Ask for a person and you get routed to one in a shared inbox your team works from.
• The default automation contains no model at all. It is a deterministic flow you can read and predict. The AI answering layer — which can read your site and answer from it — is a separate thing you switch on for your account if you want it.

The part that surprised us

We expected the win to be response time. It is, but the larger effect in the businesses testing it has been volume. People who would never fill in a form will send a message, because a message costs them nothing and commits them to nothing. Enquiry counts went up before conversion rates did.

That has an unglamorous implication: more messages means more work, and a business that turns this on without deciding who answers has bought itself a problem. Which is why the shared inbox and the escalation rules shipped in the first version rather than the third.