Is your contact form losing you enquiries?
Most business websites have a contact form. Far fewer have a good one.
It is easy to treat the contact form as a small detail to deal with shortly before a website goes live. In reality, it is often one of the most important conversion points on the site.
Someone who reaches your contact form may already have read about your organisation, looked at your services, and decided they want to talk to you. Making that final step unnecessarily difficult risks losing an enquiry at precisely the point when the website has almost done its job.
The problem is that abandoned forms are largely invisible. Unless you are specifically monitoring form interactions, you may never know how many people started an enquiry and gave up.
Good contact forms reduce that friction. They ask only for information that is genuinely useful, make it clear what the user needs to do, handle errors helpfully, and explain what happens after an enquiry is submitted.
For most straightforward contact and enquiry forms, we recommend starting with these principles:
- Keep the number of fields to a minimum
- Make a phone number optional unless there is a clear reason not to
- Make required and optional information clear
- Write useful, accessible error messages
- Provide a meaningful confirmation message
- Test that notifications reliably reach the right people
- Provide appropriate privacy information
- Consider how enquiries will be recorded and managed
This article focuses specifically on general contact and enquiry forms. Application forms, booking systems, registrations, and other transactional forms have different requirements.
1. Ask only for the information you need
One of the most common problems with contact forms is asking for too much information too soon.
The reasoning is understandable. Organisations want to qualify enquiries before spending time responding to them, so asking about budgets, deadlines, and requirements can seem efficient. But every question creates work for the person completing the form.
Research into online forms consistently supports a straightforward principle: remove fields that do not serve a clear purpose. The relationship between form length and conversion is more nuanced than simply saying “fewer fields always perform better”, but unnecessary complexity creates friction and can discourage completion. HubSpot’s analysis of more than 40,000 landing pages found that while overall form length had a modest relationship with completion, larger text areas and dropdowns had a stronger negative association than simple text fields.
For a straightforward contact form, four fields are often a useful starting point:
- Name
- Email address
- Phone number, marked optional
- Message
That is normally enough information to start a useful conversation. Details such as budget, timescale, project type, or how someone found you can often be established later. If you genuinely need one of these pieces of information before responding, include it. If you do not, consider removing it.
The purpose of a contact form is to start a conversation, not to complete the qualification process.
Match the form to the organisation
There is no universal contact form that works for every organisation. The right fields depend on the purpose of the enquiry and what you need to do with it.
Local trades and service businesses
Builders, plumbers, decorators, cleaning companies, and similar businesses often work within defined geographical areas. In this situation, asking for a postcode can be useful, as it allows the business to establish whether an enquiry falls within its service area. A full postal address is unlikely to be necessary at this stage and can be collected later if the enquiry progresses.
Professional services
Accountants, solicitors, consultancies, and agencies may benefit from asking what the enquiry relates to. A short field such as “What can we help you with?” can help route an enquiry to the right person or team. Keep the number of options manageable. A long dropdown containing every service your organisation provides can create more work for the user than it saves internally.
Charities and community organisations
Charities and community organisations often serve several distinct audiences, including service users, volunteers, donors, members, professionals, and partner organisations. One generic contact form may not serve all of those groups effectively. Consider using a simple enquiry-type selector or, where the journeys are genuinely different, separate forms designed around the needs of each audience.
E-commerce and booking websites
For an e-commerce or booking-led website, a contact form is rarely the primary conversion mechanism. The basket, checkout, or booking system normally performs that role. Contact forms are more likely to deal with exceptions: unusual requests, questions, complaints, accessibility requirements, or other enquiries that cannot be handled through the normal customer journey. Keep these forms focused. It can also be useful to provide relevant FAQs or support information before the form, allowing users to resolve straightforward questions without having to wait for a response.
2. Make it clear what information is required
Once you have decided which fields to include, make it immediately clear which information is required.
For a basic contact form, name, email address, and message will often be required. A telephone number can normally remain optional. There are exceptions: a callback request form obviously needs a telephone number, and some organisations may have operational reasons for requiring one. But do not make a field compulsory simply because the information would be convenient to have.
Some people prefer to make initial contact by email and will be reluctant to provide a telephone number before they have established a relationship with an organisation. Allowing them to choose removes an unnecessary barrier.
For a short form where most fields are required, a line such as “All fields are required unless marked optional” can make the form easier to understand at a glance.
Clear labels and instructions are also an accessibility requirement. WCAG 2.2 requires labels or instructions where content requires user input, and errors must be identified and described in text.
3. Help people recover from errors
Error handling is easy to overlook because it is only seen when something goes wrong. That makes it no less important. A user who has already taken the time to complete your form should not have to work out why it has been rejected.
Explain what went wrong
Avoid messages such as “Invalid input”. Instead, explain the problem and, where possible, how to correct it: “Please enter a valid email address, for example name@example.com.” Similarly, if a required field has been missed, identify it clearly. WCAG 2.2 requires automatically detected input errors to be identified and described in text, and where the system knows how an error can be corrected, providing that information helps users recover quickly.
Keep the language clear and human
An error message is part of your organisation’s communication with a potential client, customer, member, or supporter. Technical system messages can make a well-designed website suddenly feel impersonal. Instead of “This field is required”, consider “Please enter your email address so we can respond to your enquiry.” The instruction is clearer and explains why the information is needed.
Do not make users start again
If a submission fails because one field contains an error, preserve the information already entered wherever possible. Few things are more frustrating than writing a detailed enquiry, pressing submit, and discovering that the entire form has been cleared because one field was incomplete. Good form design helps people correct mistakes rather than penalising them for making one.
4. Explain what happens after submission
The user experience does not end when someone presses submit. At that point, the person needs reassurance that their enquiry has been received and some idea of what happens next.
Write a useful confirmation message
A confirmation message should normally do three things:
- Confirm that the enquiry has been received
- Explain when the person can expect a response
- Provide an alternative contact method if the matter is urgent
Instead of “Thank you for your message”, consider something more useful: “Thank you. We have received your enquiry and a member of our team will respond within one working day. If your enquiry is urgent, please call us on [telephone number].”
Only promise a response time that your organisation can consistently meet.
5. Ensure enquiries actually arrive
A well-designed contact form is of little value if nobody receives the submissions. Form notifications can fail for several reasons: they may be caught by spam filtering, sent from an incorrectly configured address, or delivered to an inbox that nobody monitors.
Do not assume that a successful on-screen confirmation means the email has arrived. Test the complete journey by submitting the form from the live website and confirming that:
- The user sees the correct confirmation
- The notification reaches the intended recipient
- Replies can be handled correctly
- The submitted information is complete and readable
- Any internal routing works as expected
For business-critical forms, ongoing monitoring is also worth considering. A test before launch confirms that the form worked at that moment; it does not guarantee that email configuration, spam filtering, or third-party services will never change.
6. Get privacy and data protection right
A contact form collects personal data, so data protection needs to be considered before the form goes live.
Under UK GDPR, organisations need an appropriate lawful basis for processing personal data and must provide relevant privacy information when that data is collected. For a normal enquiry form, this does not necessarily mean adding a consent checkbox. Consent is only one of the seven lawful bases available under UK GDPR, and the ICO specifically advises organisations to establish which lawful basis is appropriate rather than assuming consent is always required.
A clear link to your privacy notice should be provided at or near the form. If you intend to use the submitted information for an additional purpose, such as adding someone to an email marketing list, different requirements may apply. Any consent that is required must be specific, informed, and given through a positive action. It should not be bundled into the act of submitting an ordinary enquiry.
Establish the data protection requirements first, then configure the form accordingly.
7. Decide what happens to the enquiry
Finally, consider what happens to the information after someone submits the form. If the only record is an email notification in one person’s inbox, an accidentally deleted or overlooked email can mean a lost enquiry.
For an organisation receiving occasional enquiries, email may be entirely adequate. As enquiry volumes increase, consider whether you need:
- A shared mailbox
- A CRM
- A helpdesk or ticketing system
- A secure record of submissions
- Automated routing to different teams
- Defined ownership and follow-up processes
The technology should match the scale and requirements of the organisation. The important point is that somebody owns the enquiry and there is a reliable way to know whether it has been dealt with.
A good contact form should make getting in touch easy
Contact forms are not complicated pieces of technology, but small decisions can have a disproportionate effect on how easy they are to use.
Ask only for the information you need. Explain clearly what is required. Help users correct mistakes. Confirm what happens next. Test that enquiries actually arrive. Handle personal information appropriately.
Most importantly, look at the form from the perspective of the person using it rather than the organisation receiving it. By the time someone reaches your contact form, your website may already have done most of the work required to generate an enquiry. Do not put unnecessary barriers in the way at the final step.
If you would like help reviewing the forms on your website, speak to the Castlegate IT team.
'
'