Analysis
Enquiry journey check
Do visitors understand your offer? We review one service page and the path to an enquiry, even without analytics data.
Websites & enquiries
Less explaining. More relevant enquiries.
Your offer is on the website, yet you explain the same basics before every enquiry. We work on the information and steps visitors need to send a relevant enquiry.
Browse services in the shop View a work sampleWhat should be clear before first contact?
An enquiry begins well before the form: does the offer fit the situation? Which documents are needed? What happens after submission? These questions belong where they arise. Recurring questions can identify a specific task for your website.
Distinguish your services
When a business offers several courses or packages, visitors need to recognise the differences. Requirements, outcomes and scope help them choose.
Make an enquiry actionable
A good form asks for the information you actually need for the next step. Clear field labels and useful error messages are part of that.
Fictional working example
The right workshop enquiry
A fictional bicycle workshop receives requests about repairs, servicing and spare parts through one free-text field. The team has to ask for the bicycle model and issue every time.
The change
The page explains the services. The form captures the issue and bicycle type. A preferred appointment remains a request until the workshop confirms it.
How we check
The workshop reviews subsequent enquiries to see which details are still missing and which follow-up questions disappear. More submitted forms alone do not show whether enquiries are relevant.
Choosing starts before the form.
'Individual training' or 'group course'? A new customer may not know the difference. Before completing a form, they need requirements, the process and price. If those are missing, your inbox has to explain them. A comparison beside the offer saves them searching several pages.
We therefore examine the page before the form. Can visitors choose for themselves, or do they first need your advice? In the latter case, the contact journey should ask about their situation rather than demand a precise service selection. After submission, they also need to know whether the enquiry arrived and what happens next.
Build a form or booking flowSuitable services
All services on this topic Where should you start?
Find unclear information
The enquiry journey check examines one service page and contact journey. Your website and typical everyday questions are enough to start.
Implement the journey
The required information and rules are already clear. A form or booking flow can then become a specific development task.
Implementation
Build a form or booking flow
A form guides people through entering information, validation and confirmation, connected to an existing messaging or booking service.
What makes an enquiry relevant?
Before changing anything, define the information you need to take the next step. A workshop may need the bicycle type and issue; a course provider may need prior experience and preferred format. A long free-text answer is not automatically more useful than a few clearly labelled fields. Extra required information should have a specific role in processing the enquiry.
Later evaluation should also consider what happens after the enquiry. More forms can create more work if many do not fit your offer. Record which enquiries are actionable and which become projects. A financial scenario needs this conversion-to-sale rate, order value and margin. Submitted forms alone are not revenue.
Read the guideHow we work
From offer to contact journey.
Review the offer and enquiry journey
Which questions recur before a project? We use those questions to review the service page and form, including mobile use and invalid entries.
Agree the handover
The report identifies locations and suggested changes. We also record where the enquiry arrives, who replies and what feedback visitors should receive. This helps define the technical implementation.
Explain your service
Describe in your own words what you offer, who it suits and any requirements. Mention cases you cannot take on too. These become clear selection criteria for the page.
Show the current journey
A page link and a description of how enquiries are processed are enough to start: who reads them, which details are regularly missing and what happens next? Anonymised examples make the task easier to understand.
Define what the enquiry should do
A message, an appointment request and a confirmed booking are different outcomes. Describe which one your page should produce. That determines whether a free date field is sufficient or availability must be checked.
Do I need analytics?
Existing pages and specific observations are enough for a qualitative review. Usage data can additionally help investigate where visitors leave.
Can you improve an existing contact journey?
Yes. We can examine the content, fields, feedback and technical handover of an existing enquiry flow. Before implementation, we agree the system, scope and access required.
Does this help with irrelevant enquiries?
If visitors do not recognise important requirements or limitations, the service page is a useful starting point. The review identifies unclear information. The actual relevance of enquiries must then be assessed within the business.
What is already settled before an enquiry?
If the offer and website exist, we can examine how they work together. Are requirements explained in the right place? Does the form ask for usable information? Typical questions from your business guide the review.
If price or scope is still open, visitors need a way to request advice. A short form about their situation is then more suitable than a long package selector. Fixed courses or appointments instead need clear selection and availability.
Further reading