The contact form is the conversion on most small business websites and it is the component most likely to fail without telling anybody. What a builder does with submissions matters more than how the form looks.
Short answer
A builder's contact form needs to deliver reliably, keep a record inside the platform as well as sending an email, resist spam without blocking real people, and handle consent and retention properly. Test it yourself regularly, because a form that stops delivering is invisible until somebody complains.
A form that stops delivering looks exactly like a form nobody is using. There is no error, no bounce anybody sees, and no signal at all until a customer who found you through a search engine or an answer engine mentions they wrote and never heard back.
The causes are ordinary. A changed email address, a filter that started treating the messages as spam, a plan change, or a provider tightening delivery rules. None of them announces itself.
So the requirement is a record inside the platform as well as an email. Then a delivery problem costs you a delay rather than the enquiry itself, which is the difference that matters.
Where submissions are stored, how long they are kept, whether more than one address can receive them, and whether you can export them. Our page on contact forms covers the arrangement that survives.
Whether the confirmation to the sender is automatic and says something useful. A form with no acknowledgment is indistinguishable from a broken one, and people assume the worst within about an hour.
And whether you can test it without sending yourself a message that looks like every other test. Dated test submissions in the record make a quarterly check take under a minute.
Every public form attracts automated submissions. The usual answers are a hidden field that only a machine fills in, a simple timing check, or a challenge, and they differ enormously in how much they cost real users.
Challenges are the harshest. They exclude some people entirely and irritate the rest, and for a small business form the volume rarely justifies the cost to genuine enquiries.
Publishing an email address is worse. Addresses in plain text are collected automatically, which is why every site we build routes contact through a form instead.
The list below is what separates a form that produces work from one that produces a mystery. Most builders handle the first three and vary on the rest.
Forms are where accessibility fails most often. Fields without labels, errors shown only in color, and controls that cannot be reached with a keyboard all exclude people rather than inconveniencing them.
Our page on accessible forms covers what a working version looks like, and our page on error messages covers the part most often wrong.
Test yours by filling it in with a keyboard only. If you cannot reach the submit button without a mouse, neither can a meaningful number of your visitors.
A form collects personal information, which brings obligations about what you do with it and how long you keep it. Our page on form data and retention covers the general shape.
Say what you will use it for, and do not add people to a mailing list because they asked a question. That is the commonest consent failure on small business sites and it is easily avoided.
Delete old submissions on a schedule. Keeping every enquiry forever is a liability rather than an asset. Nothing here is legal advice and requirements differ by where your visitors are.
Every field costs completions. Ask for what you genuinely need to reply usefully and get the rest in the conversation that follows, which is a better place for it anyway.
For most trades that is a name, a contact route, and what they need. Our page on quote requests covers the exception, which is a photograph where the work is visible.
Then respond within whatever time you stated. A fast reply converts more than any improvement to the form, and it is the part entirely within your control.
A form that stops delivering looks like a form nobody is using. Causes include a changed address, a spam filter, a plan change or tightened delivery rules, and none of them produces a visible error.
Yes, as well as emailed. Then a delivery problem costs you a delay rather than the enquiry itself, which is the difference between an inconvenience and a lost customer.
A hidden field a machine fills in, or a simple timing check. Challenges are harsher: they exclude some people entirely, and for small business volumes the cost to genuine enquiries rarely justifies it.
Not unless they agreed to that specifically. Adding somebody who asked a question is the commonest consent failure on small business sites, and it is easily avoided. Nothing here is legal advice.
15-day free trial. Card required. Cancel before day 15 and you pay nothing.