A website contact form has one job: turn a visitor into a request that someone handles. Not a lost email, and not a row in a spreadsheet nobody opens.

Last week, a business owner called us after three hours stuck on his. The form displayed, the visitor clicked, yet nothing arrived anywhere. In the end, the cause came down to one field.

Website contact form: the missing field mistake

A website contact form that does not create the contact is a form that loses clients. With this business owner, the request did go out. However, it never reached his follow-up tool.

First, we opened the execution log. It is the first reflex, but almost nobody has it. Every request is written there, with the step where it failed. And there, the message was clear: creating the contact failed because the first name was not passed along.

In fact, his form did send the first name, but under a different field name than the one expected. So the tool received a request with no identity and rejected it. In total, three hours stuck over one field mapping. Then two minutes to fix it.

Why coding your form by hand is a bad idea

A website contact form coded by hand to look nicer often opens a security hole. In fact, that is exactly what we found with this business owner.

He had written his form in code, so he could control the look. For requests to land somewhere, the code contained the receiving address, in plain text, visible to anyone who looks at the page. Yet bots look at pages. Then they find that address and send it whatever they want.

The result: spam, fake contacts, and sometimes real requests drowned in the middle. So we made a simple decision with him. Drop the code, go back to the native form from his tool, and rework the look with styling only. As a result, same rendering, zero exposed address.

The four rules of a website contact form that holds up

A website contact form holds up on four rules. However, none of them requires knowing how to code.

  • First, it creates the contact. Each field in the form maps to a field in your tool, first name included.
  • Then, it alerts someone. A notification lands on a phone, not in an inbox checked the next day.
  • Also, it replies to the visitor. A confirmation goes out within the minute, with what happens next.
  • Finally, it blocks bots. A discreet bot check, such as Cloudflare’s Turnstile, which works without showing the visitor a painful test.
Hand filling out a paper form on a shop counter, a picture of the website contact form

For example, with this business owner, the phone notification was the real discovery. Before, he checked his requests in the evening. Now he knows within the minute that a request came in, and he calls back while the visitor is still at their screen.

What happens after the click matters more than the form

The website contact form is only the front door. In fact, what matters is the path the request takes once it is through the door.

A request must first become a contact, then trigger a reply, then enter a follow-up sequence if nobody calls back. It is the same path we describe in our article on the sales funnel: every link without a handoff is a hole that leaks.

Meanwhile, the same business owner had a second question. A client had filled out the form twice, and he wanted to put her back at the right spot in his email sequence, without sending her the welcome message again. Doable, as long as it happens outside traffic hours, so it does not disrupt the other requests in progress.

The monthly test that avoids bad surprises

A website contact form gets tested once a month, end to end. Five minutes, and then you know whether it loses requests.

Fill it out yourself, from your phone, like a visitor. Then check three things: the contact is created, the notification arrived, the confirmation went out. If not, open the execution log before touching anything.

Finally, keep a record. One row in a table, with the date and the result. That way, the day something breaks, you will know since when.

Ask yourself this question before closing this article

When did you last fill out your own website contact form? If you cannot remember, then do it now.

And if the path after the click feels blurry, write to us.

Frequently asked questions

What should a website contact form do?

A website contact form must do three things: create the contact in your follow-up tool, alert someone on your team right away, and reply to the visitor to confirm the request arrived.

Should you code your own form to make it look better?

No. A hand-coded form often exposes keys in plain text on the page, and bots use them to send you spam. Use the native form from your tool and adjust its look with styling, not code.

How do you know if your contact form is losing requests?

Send yourself a test request every month and follow it to the end: contact created, notification received, reply sent. Then check the execution log of your tool. Every failure is written there.

Terry Vilver, co-founder of Meriaky

About the author

Terry Vilver · Co-founder of Meriaky

A computer engineer with 5 years of experience between EDF (France’s national electricity provider) and Meriaky. At EDF, he built a ticketing system that automatically assigns customer files to the right operators. For the past 2 years at Meriaky, he has been helping small business owners free themselves from repetitive tasks: client follow-up runs automatically, and they save time and money.

His LinkedIn profile