1. Can a visitor explain what you do?
Ask someone unfamiliar with your organization to read a service page. Can they describe the service, who it is for and what to do next?
2. Is there one clear next step?
Give each service page a relevant enquiry, booking or contact action. Avoid asking visitors to choose between several unrelated actions at once.
3. Does the contact path work on a phone?
Try the form, telephone link and email link on a small screen. Check labels, validation and what happens when a visitor has no email app configured.
4. Does the visitor know whether anything was sent?
A button click is not a delivered enquiry. Make the difference between opening a draft and submitting a message clear. Test the recipient inbox as well as the screen.
5. Is someone responsible for the reply?
Agree who checks new enquiries, who takes over during absence and how the team can see that follow-up has happened.
6. Do you ask only for useful information?
Collect enough to route and respond to the enquiry. Avoid unnecessary sensitive details and explain how the information will be used.
7. Can you tell where enquiries get stuck?
Keep a simple record of enquiry date, source, owner, next action and outcome. Look at missed follow-ups and time to first useful reply before adding new software.
Choose one improvement.
Identify the most important gap, name an owner and agree how you will know it is working better. Fixing one unclear handoff can be a more useful starting point than replacing your whole website.
This checklist is general operational guidance, not a guarantee of more enquiries or sales.
Discuss your enquiry journey