GuideBeing chosen
How to turn website visitors into useful enquiries
Pick one service page, open it on a phone and follow the enquiry through to the inbox. This guide shows you what to check and what a pass looks like.
On this page
- Start with one service page
- Where does the journey break down
- Build the explanation around a real job
- Put evidence where it answers a doubt
- Make the action specific
- Ask for enough information to respond
- Test the receiving process
- Review the enquiries you actually receive
- Leave the review with three decisions
- Get help with the page that needs attention
Start with one service page
A service website needs to answer four questions: “Is this for me?”, “What will I get?”, “Why should I trust you?” and “What happens if I get in touch?”
Ask someone unfamiliar with the page to answer those questions without your help. Have them point to the words or evidence they used. If they have to guess, record the missing answer before discussing fonts, colours or a redesign.
Where does the journey break down
| What you notice | What to inspect | A sensible first improvement |
|---|---|---|
| Visitors ask whether you provide a service already listed | Heading, service explanation and page structure | Make that service and its boundaries easier to understand |
| Enquiries come from places you do not cover | Area information beside the offer and form | State genuine coverage before the visitor commits time |
| People start the form but report difficulty finishing | Required fields, mobile layout and error feedback | Remove unnecessary demands and explain how to correct mistakes |
| The form reports success but the team cannot find enquiries | Receiving inbox, spam handling and delivery records | Test the complete delivery route |
| Enquiries arrive but are often unsuitable | Promise, qualification questions and follow-up | Define what a useful enquiry looks like and adjust the journey |
Fix a failed contact route first. If enquiries reach the team but often concern the wrong work or area, correct that explanation before trying to increase traffic.
Build the explanation around a real job
A broad statement such as “Complete solutions for your business” leaves the visitor to work out what you sell.
Here is a draft opening for a fictional electrician serving Bristol. The area and service are illustrative:
Electrical fault finding for homes in Bristol. Tell us what has stopped working and your postcode. We will confirm whether we cover the address and explain the next step before arranging a visit.
The opening names the job and location, asks for information the business can use and distinguishes an enquiry from a booked visit. Use your actual service area and process.
Continue with the work included, relevant exclusions, information needed for a quote and any factors that change the price. If the service needs assessment, explain what that assessment establishes.
Put evidence where it answers a doubt
Match the evidence to the doubt. If someone is wondering whether you handle work like theirs, show a relevant project with a caption explaining what you did. If they are unsure about the process, explain the steps and who approves the work. A general testimonial about being “friendly” does not answer a question about the scope.
Without suitable photographs, use a specific scope, a process diagram or a labelled demonstration. Do not dress an illustration up as a completed customer project.
Make the action specific
Choose the action the team can actually fulfil. “Request a quote”, “Discuss a project” and “Check availability” describe different commitments.
Keep the main action consistent through the page. If the form requests an estimate, call it “Request an estimate”. Use “Book” only where the process actually allows the customer to book. Put comparisons and inclusions beside the decision rather than making them competing primary buttons.
Ask for enough information to respond
For a local service enquiry, this is a starting point to adapt:
| Field | Why ask for it now |
|---|---|
| Name and a suitable reply route | So the team can respond; do not require both phone and email unless both are needed |
| Postcode | To check service coverage where location matters |
| Service or short description | To route the request and understand the job |
| Preferred timing, if relevant | To identify a deadline without promising availability |
Leave a full billing address and invoicing details until they are needed. A business name may help with commercial work but need not block a homeowner from enquiring.
Every field needs an understandable label. Required and optional information should be clear. Labels must also be connected to their controls in the page code so assistive technology can identify them. W3C explains form labels.
If an entry needs correcting, explain the problem and preserve the visitor’s other answers. A success state should describe the completed step, and an error state should offer a way forward. W3C’s guidance covers form feedback.
Test the receiving process
Arrange a controlled test with the person managing enquiries. Use a unique reference such as TEST-WEB-01 so the team can distinguish it from customer work. Check the following:
| Test | Pass |
|---|---|
| Open the page signed out on a phone | The offer, form and submit button are usable |
| Submit with a required field missing | The error identifies the field and keeps the other answers |
| Submit valid test details | The intended recipient receives the correct service, message and reply address |
| Reply from the business inbox | The reply reaches the test sender |
| Check any customer acknowledgement | It arrives and describes the next step accurately |
Record a website confirmation and inbox receipt separately. If the page says success but the message is missing, inspect the receiving inbox, spam folder and sending records before declaring the test passed. Re-test after the fault is fixed.
Review the enquiries you actually receive
Take the next ten enquiries as a small working sample, not a performance benchmark. For each, note whether the job is something you sell, whether it is in your area and whether you had enough information to reply. Do not copy private messages into a shared design document.
Look for a repeated explanation the page could have supplied earlier. Four requests from outside your area suggest checking how coverage is presented. Repeated requests for a service you do not provide suggest checking the heading, advertising and service list. These observations help choose a change; they do not establish its effect.
Leave the review with three decisions
Get help with the page that needs attention
Discuss your website with Ascent and include the page address and the problem you found. Conversion optimisation can focus on an existing journey; a wider structural change belongs in a website design brief.