A journey is a series of questions
A customer may first hear about a business from a neighbour, search for its name later, check a service page and only then make a call. Another person may go straight from an advert to a booking form. A customer journey map is a simple way to think through those steps and the information needed at each one.
You do not need a complex diagram to begin. Pick one type of customer and one service, then list what the person is trying to achieve. A homeowner looking for an installation, for example, may want to understand whether the work is available locally, how estimates work and what details they should provide.
Identify how people first find you
Ask recent customers how they heard about you, while recognising that they may remember only one of several touchpoints. Look at the places people could encounter your business: recommendations, search results, an eligible Google Business Profile, social posts, a shop sign or a partner organisation's directory.
Check the first impression at each point. Does the description name the real service? Does a link lead to a relevant page instead of a generic homepage? Are contact details and opening information current? Accurate, consistent information is more useful than trying to cover every possible local search phrase.
Understand what visitors compare
Once people reach your website they often want to judge fit, not read a list of marketing claims. Explain what the service includes, the type of customer or project it suits, where it is available and what happens after an enquiry. If pricing depends on a quote, describe the factors that influence it rather than inventing a fixed price.
Think about reasons to hesitate: a visitor may not know whether a small job is accepted, whether an appointment is necessary, or which locations are covered. Answering these points near the relevant service reduces the effort of finding out and can also improve the quality of enquiries.
For a clearer route through your own site, explore website design in St Albans or our website design service.
Examine the point of contact
Try each enquiry route on a phone and a larger screen. Check that buttons are easy to understand, telephone links use the correct number, form labels remain visible and any required fields are genuinely needed. Send an agreed test message and confirm that the intended person receives it and that the acknowledgement makes sense.
A visitor should know what happens next. If response times vary, avoid promising an exact turnaround you cannot reliably meet; instead explain the normal process and any information that will help you respond. Offer an alternative route where appropriate, particularly if the primary form is unavailable.
Do not stop at the submission
The journey includes the period after an enquiry. Agree who checks the inbox, what happens when someone is away, and how to recognise messages that need a specialist response. A brief acknowledgement can confirm receipt without implying that a booking or contract has already been accepted.
Record the common reasons an enquiry is a good fit or unsuitable, using only information your business needs. A pattern of requests for a service you no longer offer is a prompt to update the page, listings or campaign targeting. Feedback from the team is often as valuable as a dashboard.
Make one useful improvement at a time
Turn your observations into a short list with the problem, a proposed change and a way to check it. For instance: people ask whether work covers a nearby village; add an accurate coverage explanation and see whether that question becomes less common. Keep a note of other changes that could affect the result.
Repeat the exercise for another service once the first journey is clearer. Not every visitor follows the same route, so treat the map as a working hypothesis rather than a prediction. Ask real customers and colleagues whether the language reflects their experience, and revise it as your business changes.
A worked example: from recommendation to quote
Imagine a customer in Hertfordshire receives a recommendation for a home-service business. They search for the business name on their phone, visit its website and find a service page. The page explains the kind of work accepted but does not say whether the business covers their village. The visitor leaves to call someone else; the journey has failed even though the service itself may have been suitable.
The business could add an accurate coverage explanation and a clear way to ask about exceptions. The next task is to test the contact route: does the form ask for a location and a short description, and does the team receive the message? Do not mistake this illustrative journey for a real customer case or assume the same solution fits every business.
When reviewing a journey, mark what you have observed and what you are inferring. You may know that customers often ask about coverage, but not know exactly why a particular visitor left. Use that distinction to choose a sensible test instead of presenting a hypothesis as a measured result.
