{"id":13460,"date":"2026-09-23T10:00:00","date_gmt":"2026-09-23T10:00:00","guid":{"rendered":"https:\/\/meriaky.com\/?p=13460"},"modified":"2026-09-20T19:14:58","modified_gmt":"2026-09-20T19:14:58","slug":"website-contact-form","status":"publish","type":"post","link":"https:\/\/meriaky.com\/en\/blog\/website-contact-form\/","title":{"rendered":"Website contact form: three hours lost over one missing field"},"content":{"rendered":"\n

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

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.<\/p>\n\n\n\n

Website contact form: the missing field mistake<\/h2>\n\n\n\n

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.<\/p>\n\n\n\n

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.<\/p>\n\n\n\n

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.<\/p>\n\n\n\n

Why coding your form by hand is a bad idea<\/h2>\n\n\n\n

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.<\/p>\n\n\n\n

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.<\/p>\n\n\n\n

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.<\/p>\n\n\n\n

The four rules of a website contact form that holds up<\/h2>\n\n\n\n

A website contact form holds up on four rules. However, none of them requires knowing how to code.<\/p>\n\n\n\n