A contact form is often the last step between a promising visitor and a new conversation. If it feels like an interrogation, breaks on a phone or sends a message nobody sees, the problem is larger than a slightly untidy page. A person who was ready to ask about your service may simply leave.
The fix is not automatically a shorter form. A useful enquiry form asks for enough information to start the right conversation, makes each request understandable, and reliably tells both parties what happened. Here is how I would examine that whole journey on a small service-business website.
Why contact forms lose good enquiries
There are three places to look: before the visitor starts, while they fill it in, and after they press Submit. A form can pass a visual review and still fail at any of them.
Before starting, the visitor may not know whether the business handles their sort of work, whether they will be pushed into a sales call, or what response to expect. During completion, a required phone number or unclear error can make the task seem harder than the enquiry warrants. Afterwards, a cheerful “Thank you” on screen is little comfort if the notification email never arrives.
That wider view matters. GOV.UK’s guidance on mapping a user’s whole problem considers online and offline steps, backend processes and dead ends together. A private company does not need to copy a government service. The useful principle is that the enquiry does not end at the button.
Start with the question the visitor is trying to answer
Imagine an owner of a local practice has found your site through a recommendation. They want to know whether you can help with a particular issue and whether a first conversation would be worthwhile. A form headed “Contact us” with eleven required fields may feel like a disproportionate demand. A short explanation beside it could do more than changing the button colour:
Tell me briefly what you need help with. I will read your message and reply by email within two working days. You do not need a finished brief.
That copy is only an example; the promised response time must match what the business can actually deliver. Its job is to remove uncertainty about what to write, who will read it and what happens next. It is especially helpful for a service that is unfamiliar, costly or personal.
Nielsen Norman Group’s research on commitment and trust describes how a larger request for information or effort calls for greater confidence from the visitor. I would treat that as a design question, not a formula for “conversion”: has the page earned the information it asks for?
Ask for what is needed at this stage
Name, a way to reply and a short description may be enough to begin. A phone number can be useful when a call is genuinely part of the service, but making it compulsory merely because the field exists can exclude people who prefer email or cannot conveniently take calls. A budget question may help qualify a complex project; it may also stop someone who does not yet know the likely cost. The right set of fields depends on the conversation you intend to have.
Before adding a field, ask: what decision will this answer help us make before we reply? If the answer is “we might need it later”, ask later. The GOV.UK Design System advises teams to know why they ask each question and to ask only for information they really need. Ireland’s Data Protection Commission explains data minimisation as limiting personal data to what is necessary for its purpose. A simpler initial enquiry can therefore serve both the visitor and sound data-handling practice.
Keep the distinction between required and optional fields honest. If “How did you hear about us?” is useful for your records, it need not block somebody who is ready to ask for help. Conversely, a builder should not remove a genuinely necessary detail just to make a form look minimal. For a venue booking, the date or approximate guest numbers might be essential to deciding whether an enquiry can be handled at all.
Explain fields in ordinary language
Labels should say what belongs in each field. “Tell me about your project” is warmer than “Requirements”, but a little guidance may still help: “What are you trying to achieve, and is there an existing website?” If you need a specific format, show it before somebody submits.
Do not make placeholder text inside an empty box do all the explanatory work. It vanishes when the person types. The W3C Web Accessibility Initiative’s form instructions recommend clear instructions and explain why placeholders are not replacements for labels. Visible labels also make a form easier to scan and review.
The language around a form deserves the same attention as the fields themselves. “Submit” describes the mechanics. “Send enquiry” tells a person what they are doing. If the next step is an appointment request rather than a confirmed booking, say so. It is a small distinction, but a visitor should not have to guess whether clicking the button commits them to a date or begins a discussion.
Make errors recoverable
A good form assumes normal human mistakes. Somebody mistypes an email address, misses a required field or enters a date in an unexpected format. The form should identify the specific problem, say how to fix it and preserve the answers already entered. “There was an error” is a poor return for ten minutes of effort.
W3C’s guidance on form notifications recommends clear success and error messages, including references to the affected field and a way to correct it. In practice, I would test with a keyboard as well as a mouse, deliberately leave a field empty, and check whether I can find the message and recover without starting again. A red border alone is easy to miss and does not explain what went wrong.
Mobile testing is equally important. Can you see the label when the keyboard opens? Is the button reachable without fighting a sticky banner? Does a country-code selector work? Does an anti-spam challenge reject a genuine visitor or demand a fiddly task on a small screen? A form that works on a large desktop monitor is not yet a tested form.
Prevent spam without punishing genuine visitors
Spam is real, and an unprotected form can consume a surprising amount of time. The answer is to choose proportionate protections and test them from a visitor’s point of view. Depending on the form and site, that may include built-in spam filtering, a hidden field intended to catch automated submissions, rate limits or a challenge. Each option can fail in different ways.
A question such as “Confirm you are based in Ireland” may help qualify a locally focused service, but it can also exclude a legitimate overseas owner seeking work on an Irish business. A mandatory explanation box may reduce low-effort submissions, yet asking for a long project brief at first contact can deter someone whose needs are still emerging. The aim is to reduce nuisance while leaving a reasonable path for the right person.
After any change to spam controls, send real test enquiries from a normal browser and a phone. Check the visitor’s experience, the stored submission if the form keeps one, and the inbox. A setting that cuts spam to zero by quietly cutting all enquiries is not a victory.
The journey continues after Send
There are at least three things to verify after a form appears to submit. First, does the visitor see a clear success message that says what happens next? Second, does the business receive the enquiry in a place someone actually checks? Third, is there a way to investigate when email delivery fails?
For a WordPress site, a form plugin may hand a notification to WordPress’s mail function, which then hands it on to the server or a configured mail service. A successful handoff is not proof that the message arrived in a person’s inbox: WordPress’s own wp_mail() documentation explicitly distinguishes a successful return from confirmed receipt. That is why I test the full route, including the receiving mailbox and spam folder, rather than relying on the form’s green confirmation alone.
Some sites keep a copy of submissions inside WordPress, which can provide a useful fallback if a notification is missed. That brings responsibilities of its own: decide who can access the messages, how long they are kept and whether the privacy information explains the collection. The right setup depends on the sensitivity of what people might send. A medical or financial practice should be especially careful about inviting detailed personal information through a general enquiry box.
Tell visitors what response to expect, then make that promise workable. A small business need not claim to be available around the clock. “I usually reply within two working days” is more helpful than silence, provided someone monitors the inbox and has cover when away. Where a message might be urgent, provide an appropriate alternative contact route rather than implying the form is monitored continuously.
A practical five-minute form test
Open the site as if you were a new visitor, preferably on a phone and away from the administrator’s logged-in view. Then try this:
- Find the right contact route from a service page, not only from the main menu.
- Read the copy immediately around the form. Is it clear what to send and what will happen?
- Leave a required field blank. Is the error specific, visible and easy to correct?
- Complete the form with an unfamiliar email address and a realistic message. Check the success message.
- Confirm the enquiry actually arrives, including any stored entry, notification and reply path.
This quick test will not replace accessibility testing, privacy review or a thorough delivery check, but it can uncover obvious problems. Repeat it after plugin updates, a redesign, a change to spam protection or a change in the mailbox that receives enquiries. If enquiry volume drops unexpectedly, test the route before concluding that demand has disappeared.
When the form is only part of the problem
Sometimes the form itself is fine. The visitor reaches it without enough information to feel ready. A vague service page, missing examples, unclear geographic coverage or a call to action that appears too early can all make the final request feel premature. Conversely, a beautifully reassuring page cannot rescue a broken submit action.
This is why I would review the form alongside the service page and the message that follows it. The homepage guide on enquiries looks at what happens before someone is ready to make contact. The diagnosis-before-rebuild article explains why it makes sense to find the failing step before proposing a larger redesign.
On a professionally planned WordPress site, the form can be designed around the actual service: the right questions, a clear route from the relevant page, accessible feedback, reliable notifications and an agreed follow-up process. Those decisions are where design and implementation meet. They are also why hiring a designer is about more than choosing a form plugin or dropping a template onto a page.
If your site receives fewer useful enquiries than you expect, I can look at the route from service page to inbox and help identify whether the issue sits in the copy, the form, the delivery setup or the wider page design. Ask me about a website review; a sensible repair may be smaller than a rebuild.
Sources and further reading
- W3C WAI: Forms tutorial — labels, instructions, errors and feedback.
- Irish Data Protection Commission: Principles of Data Protection — including data minimisation.
- GOV.UK Service Manual: Map and understand a user’s whole problem — considering the full service journey.
- WordPress Developer Resources:
wp_mail()— what the sending function’s result does and does not confirm.
Important note
This article provides general information and professional commentary. It is not advice tailored to your particular business, website or circumstances, and it should not be treated as legal, financial, privacy, accessibility, cybersecurity or other specialist advice. Any opinions are my own professional judgement based on the information available when the article was researched.
Products, prices, services, software and official guidance can change. External links are provided for reference; I do not control third-party websites and cannot guarantee their continuing availability, accuracy or content. A link does not imply endorsement of everything published by that source.
Check current official information before making an important decision. Test technical changes safely, keep a verified backup, and obtain appropriately qualified advice where the consequences warrant it. Any sponsorship, free product, affiliate link or other commercial relationship relevant to the article will be clearly disclosed.
