If your marketing brings visitors to your website but few enquiries reach your inbox, review the enquiry form before adding more activity. Check whether people know what they are requesting, can enter their details comfortably and understand what happens after they press the button. A quiet inbox alone does not prove your form is the problem, but these are useful checks you can make without committing to a redesign.
There is a timely reason to look at data entry. On 28 October 2026, Google announced that Chrome’s enhanced autofill can suggest information from Gmail, including order numbers, tracking information and flight bookings. The rollout begins in the United States for Gemini in Chrome users with Personal Intelligence enabled, on desktop, Android and iOS. It is not an announcement of general availability in the Philippines, Australia or New Zealand.
Our practical takeaway is narrower than the announcement: review the effort your website asks of a customer. You do not need an AI feature to make a standard enquiry form clearer.
Start with the promise beside the form
A visitor should understand the purpose of the form before typing. Does it request a quote, ask a question, arrange a conversation or make a confirmed booking? Those actions carry different expectations.
Read the page heading, the button that opens the form and the form heading together. If one says “Book a consultation” while another says “Request information”, decide which action actually happens and use consistent wording. Explain any important next step, such as a team member contacting the visitor to agree a time.
Illustrative example: an appointment-led business could use “Request an appointment” when staff still need to confirm availability. It should reserve “Your appointment is confirmed” for the point at which the booking has actually been accepted. This is a wording example, not a client result.
Ask only for information you need at this stage
Review each field with the person who handles enquiries. Ask: “What decision does this answer help us make before our first reply?” If nobody uses it at that point, consider removing it or collecting it later.
A service business might need a name, a reply address and a short description of the request. An appointment enquiry may also need the preferred service or location. There is no universal ideal field count: a useful qualifying question can save an unsuitable conversation, while an unnecessary mandatory question adds work.
The W3C Web Accessibility Initiative’s forms tutorial, updated 27 March 2026, recommends simple forms that request only information needed for the process. It also covers labels, instructions, validation and notifications. These are established usability and accessibility principles, not newly invented conversion tactics.
Mark optional fields honestly. If a telephone number is optional, a visitor should be able to continue without one. Keep a request for marketing emails separate from the enquiry itself and explain what the visitor is choosing.
Make typing easier on a phone
Open the page on an actual phone. Without sending an enquiry, move through the fields and note where the experience becomes awkward. Can you see the label after you begin typing? Does the keyboard suit the information requested? Can you reach the main button without an overlay covering it?
For your website developer, Google’s web.dev form guidance provides useful implementation details: visible labels, suitable input types and autocomplete attributes, and stable field names. The guide focuses on payment and address forms; the same standard HTML mechanisms can also help with common contact details in enquiry forms.
- Use an email field for an email address and a telephone field for a phone number.
- Keep field labels visible rather than relying only on disappearing placeholder text.
- Use appropriate autocomplete values for standard details such as name and email.
- Allow people to review and edit information their browser fills in.
Do not build a form that depends on the newest Chrome capability. Visitors may use another browser, decline autofill or enter details manually. Check that ordinary manual entry remains comfortable.
Help people recover when something goes wrong
An error should explain what needs attention and how to fix it. “Please check your email address” gives a clearer next action than a generic failure message at the top of the page. Keep valid entries in place so the visitor does not have to start again.
W3C’s tutorial recommends notifications for both errors and successful completion. For a small business, that means checking the full experience after the button is pressed, not only whether the form looks attractive.
Plan a controlled test with your team using a staging environment or an agreed test route. Confirm that a successful request reaches the intended inbox or system and that the visitor receives an accurate acknowledgement. Avoid sending repeated test enquiries into a live sales queue without coordinating them.
Write the confirmation around your actual process. State that the request was received, explain who will respond and give a response window only if the team can support it. A success message must not promise an appointment, quote or delivery that has not been confirmed.
Separate form friction from a wider marketing problem
Few enquiries can also reflect an unclear offer, unsuitable traffic, seasonal demand or missing measurement. Treat a form review as one part of diagnosis.
Use the records you already trust to answer three questions: are relevant people arriving at the page, are they attempting to enquire, and are completed requests reaching the business? If those stages are not measured, write down the gap instead of treating an empty report as zero customer activity.
For an initial comparison, choose one meaningful outcome, such as received enquiries that match your service. Record the review date, the changes made and relevant context such as a campaign or offer change. Compare periods with enough activity to interpret. A small number of submissions cannot support a confident percentage uplift or a claim that one edit caused the difference.
A focused review you can start this week
- Choose one important page. Start with the page customers actually use to request your main service.
- Check the promise. Make the page, form and button describe the same action.
- Review the fields. Keep what your team needs for the next step and explain unfamiliar requests.
- Try mobile entry. Check labels, keyboards, scrolling and the button without submitting private information.
- Agree a controlled delivery test. Verify error handling, acknowledgement and receipt with the team.
- Record what changed. Review relevant enquiry quality before deciding what to improve next.
If the review identifies a larger issue, JTDC’s website design and marketing services can be scoped around the part of the customer journey that needs work. A focused repair may be a better starting point than replacing the entire website.
Choose a clearer starting point
Not sure whether to prioritise your page, your offer or the enquiry route? Start with a free guided growth check. Answer five questions to see an instant preview, with the option to receive a fuller action list by email. It is a self-assessment based on your answers, not a technical website crawler or a verification of rankings. Use it to choose a practical next step, then validate that priority against your business evidence.
Strategy. Growth. Impact.

