If your website brings few useful enquiries, first follow one realistic customer task from the service page to the next conversation. Check whether the visitor can recognise the right service, judge your work, understand the next step and contact someone who will deal with the request.
A confusing page can be improved, but a quiet inbox alone does not prove the design is the cause. For a Formby, Freshfield or L37 business, this review can help define a focused website improvement project.
Check what the evidence actually tells you
Look at the enquiries you receive through the website alongside calls, referrals and bookings where those records exist. Summarise the pattern without sharing private customer details: wrong service, outside coverage, missing job information, or a suitable request.
If available, use search and website reports to identify which pages people reach and what they were looking for. A site receiving little relevant traffic cannot be assessed in the same way as a well-visited service page. Small samples and incomplete tracking limit what you can conclude.
For the difference between profile actions and website search results, use the Business Profile and Search Console guide.
A recorded button click is not the same as a received enquiry, and a received enquiry is not automatically a suitable lead. Compare events with actual messages or booking records where appropriate. Do not assume that a dashboard’s event name proves the customer completed the action.
If messages appear to be submitted but never arrive, start with the contact-form delivery diagnostic. Fixing wording will not repair a notification addressed to an unmonitored inbox.
Choose one customer and one starting page
Write a short task based on a service you actually provide. For example: “I need interior decorating, want to see comparable work and need to find out how a quotation is arranged.” This is an illustrative review task, not a report of a real customer.
Begin on the page that visitor might reach from search, a shared link or a referral. Do not automatically start at the homepage. On a phone, read what appears first and follow the ordinary links without using your knowledge of where everything belongs.
If a visitor arrives through an eligible local profile, check its website link and destination as part of the journey.
Ask someone unfamiliar with the site to try the same task. Let them explain what they think the business offers and where they would go next before helping them. Record the page and the point of confusion. One person’s difficulty can reveal a fix worth investigating; it does not measure how all customers behave.
Make the offer clear before asking for contact
Can the visitor identify the service and decide whether it fits? Check the work included, meaningful exclusions, genuine coverage and how the service is arranged. Information scattered between several pages can leave a person unsure whether an enquiry is appropriate.
Our guide to explaining your service area helps customers judge genuine coverage before enquiring.
Use the customer’s decision to choose what appears near the start. A planned installation needs scope and relevant examples. A professional service may need an explanation of the initial assessment. An urgent-call route is appropriate only where the business genuinely handles that type of request.
Check that useful evidence sits beside the service decision. A well-explained project page may answer a practical doubt; an unexplained gallery may leave it unresolved. Keep qualifications and customer comments accurate and relevant to the work being offered.
If the problem is repeated unsuitable enquiries, improve the information that helps people judge fit. Adding more compulsory form fields may make the request longer without explaining whether you do the job.
Let the contact action mean what it says
Read the action label and follow it. “Request a quotation” should lead to the agreed quotation process. “Book an appointment” should either arrange a booking or clearly explain that the visitor is sending a request for one. Avoid a label that promises an instant answer when a conversation is needed.
A visitor ready to act should be able to find the route on the relevant service page. Keep it visible and identifiable without interrupting the explanation with repeated prompts. Where a telephone alternative is offered, check the number and the business’s actual ability to receive those calls.
Ask for the information needed to decide the next step. Explain required and optional fields, useful formats and any request for photographs. W3C’s form-instruction guidance supports clear labels and relevant help. Our trade quote-form guide develops the field choices in more detail.
Keep an initial contact proportionate. The ICO’s data-minimisation guidance describes collecting personal data that is adequate, relevant and limited to the purpose. Detailed private records can wait for an agreed, suitable process if the service needs them.
Review what happens after the visitor acts
Read the confirmation and error messages. A visitor should know whether the request was accepted and what happens next. Check that an error identifies the problem without losing the useful information already entered.
For examples of clear wording and a way to handle an uncertain send, see the contact-form confirmation and error message guide.
Arrange any test submission with the people responsible for the website and inbox. Use labelled dummy information and agree which notifications will be generated before testing. Follow the request through to the intended recipient and check how a reply would be handled.
Name the person or team that monitors the route. Decide what happens during absence, whether replies are visible to colleagues who need them and when an enquiry is treated as dealt with. State a response time on the website only if the business can maintain it.
Record the stage that failed and who is responsible for the next check: the designer, form administrator or inbox owner.
Turn observations into a small, testable brief
Write each issue as a specific observation, the proposed change and the check that would demonstrate the change works. “The site needs to convert better” gives a designer little to implement.
- Unclear coverage: place the genuine service area beside the relevant offer, then ask a reader to find whether their job location fits.
- Weak project context: explain the relevant work and your role, then check whether the example answers the customer’s original doubt.
- Misleading action: align the button, form and confirmation with the real next step, then follow that path on a phone.
- Missing requests: identify the failed delivery stage and repeat the agreed dummy test after the repair.
Prioritise a broken customer route and materially incorrect information. Then compare content and layout improvements with any wider structural work. The repair-or-redesign guide helps settle that scope without assuming every problem needs a rebuild.
Review the result after the changes
After a change, repeat the same customer task and record whether the identified obstacle remains. Track relevant enquiries and their suitability over a comparable period when there is enough evidence, keeping changes in traffic, services and availability in view. A small rise in messages does not establish what caused it.
To discuss an enquiry-journey improvement with Formby Web Design, send the website address and the task that feels difficult. Include the page involved and a summary of what you observed. There is no need to send customer messages or confidential files with the initial enquiry.
