
A prospective customer has read about your service and decided to get in touch. Your enquiry form is the last part of the website they need to use before that conversation can begin.
This is where small details matter. A confusing question, a button hidden by the phone keyboard or a message that never reaches your inbox can interrupt an otherwise useful website.
Good website enquiry form design makes the next step clear and gives your team enough information to respond. Use this checklist when planning a new site, reviewing a redesign or checking why existing visitors are not getting in touch.
1. Match the button to the conversation
Decide what happens after someone contacts you. Will you ask a few questions, prepare a quote or arrange an initial call? The words on your website should describe that step accurately.
For a project-based business, “Tell us about your project” may fit better than “Book now” when there is no appointment to book. “Request a quote” works when the information collected actually starts your quoting process.
Keep the wording consistent between the service page, the contact page and the form button. If a visitor selects a specific service before opening the form, carry that choice through where practical.
Give people a relevant reason to enquire near the button. A short note about the type of work you handle or your service area can help them decide whether to continue.
2. Ask for enough information to reply
Review every field with a simple question: do we need this before the first conversation? A detailed project brief can often wait until you know the enquiry is a good fit.
For a small service business, a starting point could be:
- Name: so you know who you are speaking with.
- Email: where you will send the reply.
- What do you need help with? a short message field with a useful prompt.
- Phone, if useful: clearly marked optional unless a call is essential.
Adapt the form to your work. A local trade business may need a suburb to check its service area. A designer may benefit from an existing website address. Explain unfamiliar requests, and avoid making visitors choose an answer they cannot reasonably know yet.
If attachments are useful, say which file types and sizes are accepted before someone tries to upload. Keep the first enquiry focused and explain how the information will be used, with a link to your privacy notice.
3. Design for a phone and a keyboard
Open the form on an actual phone. Use a simple vertical layout, readable text and comfortably separated controls. Check that the on-screen keyboard does not hide instructions or make the send button difficult to reach.
Keep visible labels above the fields. Placeholder text disappears as someone types, so it should not be the only way to identify a question. Labels also need to be associated with the correct controls in the website code, as explained in W3C’s form labelling guidance.
Ask your developer to use appropriate email and telephone field types and relevant autocomplete settings. These help browsers offer suitable input tools and saved information. Google’s web.dev guide to autofill explains the implementation.
Then try the form using only a keyboard. You should be able to move through fields in a sensible order, see which control has focus and reach the submit button. Also check the layout with text enlarged. A tidy desktop screenshot does not establish that a form is usable.
4. Make mistakes easy to fix
Test the awkward cases deliberately: leave a required field empty, enter an incomplete email address and try an attachment outside the allowed limits.
Each error should identify the problem and explain the correction near the relevant field. “Enter an email address with an @ symbol” is more helpful than “Invalid input”. Use text as well as colour, and retain the information already entered wherever possible.
Ask how errors and success messages will be communicated to screen-reader users. W3C’s form notification guidance covers feedback that people can understand and act on.
A connection failure needs its own message. The website should not claim success when it cannot confirm acceptance. Provide a working alternative contact method so visitors have somewhere to turn if the form fails.
5. Explain what happens after sending
A successful submission should leave the visitor confident about what happens next. Avoid clearing the form and leaving them on an unchanged page.
A straightforward example is: “Thanks, your enquiry has been received. Our team will review your project details and reply by email.” Use wording that reflects how your business actually works. Add a response timeframe only if your team can reliably meet it.
If you send an automatic acknowledgement email, distinguish it from a personal response. Do not imply that a booking is confirmed, a quote is accepted or work has started unless that is genuinely the outcome.
The confirmation can also link to useful preparation, such as a short explanation of your process. Keep the immediate priority clear: the person should know whether their enquiry was accepted.
6. Check the journey all the way to the inbox
A confirmation on the screen does not prove the enquiry reached the person responsible for answering it. Before launch, send an agreed test message and check the destination inbox, spam folder and any connected enquiry system.
Confirm that the message contains every field, attachments work if included, and replying reaches the enquirer. Use clearly labelled test data rather than a real customer’s details.
Agree who owns the process after launch. Who checks incoming messages? What happens when that person is away? Who investigates a delivery failure or a sudden increase in spam?
Ask your website provider which form service is being used, whether it has ongoing charges or submission limits, and what protection against automated spam is included. Any anti-spam step should also be checked for usability. Re-test after changes to the form, email account or delivery settings.
7. Review useful enquiries, not just button clicks
Start with a simple record of genuine enquiries and whether they relate to the work you want. A busy inbox filled with spam or unsuitable requests is a different problem from a form that nobody can submit.
If analytics is included, ask your developer to distinguish a click on the send button from a successfully accepted submission. Keep names, email addresses and message contents out of analytics events.
Compare results over a sensible period and consider changes in traffic sources, campaigns and seasonality. A small number of visits or enquiries can fluctuate considerably. Form improvements cannot guarantee leads or sales, but clear testing helps you find specific obstacles.
Bring the enquiry process into your website brief
Before approving the build, check that the brief covers the form fields, mobile layout, error messages, confirmation, delivery destination and ongoing responsibility. These details are easier to agree while the website is being planned.
If you are still deciding how to organise the wider site, our four-page small business website guide explains how Home, Services, About and Contact can work together.
LogoNow offers website design and development for businesses planning a new site or a redesign. Tell us about your website project, the customers you want to hear from and what should happen after they enquire. Bring your current website address, if you have one, so we can discuss the pages and functions your project needs.