Someone has read about your service, decided you might be able to help and reached your contact page. That is a useful moment to make things straightforward.
A long form, an unclear button or silence after pressing Send can turn a simple enquiry into an uncertain one. Before adding more ways to attract visitors, check what happens when an interested person tries to reach you.
Start by completing your own contact journey on a phone. Follow it all the way through to the inbox where the message should arrive.
Ask for what you need to begin
Look at each field and ask whether it is needed for the first reply. A name, a suitable contact method and a short explanation may be enough for a service enquiry.
Some businesses genuinely need more information to route a request. If you ask for it, make the reason clear. Avoid demanding a detailed specification from someone who is still working out what help they need.
Label optional fields so visitors do not have to guess whether they can leave them empty.
Use labels that stay visible
A hint inside an empty field can be useful, but it should not replace a visible label. Once someone starts typing, they still need to know what the field is asking for.
Instructions should be close to the relevant question and written in ordinary language. If something goes wrong, explain which field needs attention and how to correct it.
The W3C provides guidance on labelling form controls and writing form instructions. A developer can check that the visible labels and underlying form controls work together properly.
Offer a useful alternative
Some visitors would rather email directly or talk. Show the contact methods you can realistically support and keep their details current.
A booking link is helpful if choosing an appointment is genuinely part of your process. It is unnecessary if the first step is simply a conversation about what is needed.
Explain any important limitations, such as visits being by appointment. Do not publish a telephone number nobody is responsible for answering.
Explain what happens next
After sending, visitors need a clear confirmation that their enquiry was submitted. If sending fails, they need an honest message and a way to try again or contact you another way.
Only promise a response time you can maintain. If you send an automatic acknowledgement, make it clear that it is an acknowledgement rather than a personal reply.
Check whether an error leaves the visitor’s message available to correct. Having to type a carefully written enquiry again is an avoidable frustration.
Test delivery, not just the button
Use an email address outside your own business to send a test. Confirm that the enquiry reaches the intended inbox and that Reply goes to the person who submitted it.
Check the spam folder, any forwarding arrangement and the process for covering absences. An on-screen success message alone does not prove that someone received the email.
Repeat the check after changes to your form or email setup. Agree who will notice and investigate missing enquiries.
Give every enquiry an owner
The website is only the beginning. Decide who responds, where enquiries are recorded and how follow-ups are tracked.
Estuary Connect can help connect website design with practical enquiry handling and, where appropriate, Salesforce. Ask us to look at your contact journey if the steps between “Send” and a useful reply need attention.