In brief
A polished homepage cannot recover an enquiry that never reaches your team. Test the journey from the first click to a useful reply.
Start at the point where a visitor needs help
A website redesign often starts with colours, layouts and reference sites. Before choosing any of them, try becoming a new customer. Open the service page on a phone, decide whether the offer is relevant, and attempt to make an enquiry.
Write down every uncertain step. Is it clear what the company does? Does the contact button lead to the expected destination? Does someone actually receive the message? These observations create a more useful brief than “make the website modern”.
Ask for enough information to respond
An initial enquiry is not a complete project specification. Ask for information your team genuinely needs for the first useful reply, then collect detail during the conversation. W3C’s forms guidance supports clear labels, relevant fields, understandable instructions and feedback when submission succeeds or fails.
For example, a service enquiry may need a contact method, the service of interest and a short description. That is an illustrative starting point, not a universal form template. Do not require an attachment merely because an upload field is available.
Test the handover, not only the form
Use clearly marked test information and confirm the entire handover with the person who receives enquiries. A success message in the browser is only one checkpoint.
- Check required-field errors without losing the visitor’s other answers.
- Submit on both a phone and a desktop.
- Confirm the message arrives in the intended inbox or work queue.
- Verify that someone can identify which service the enquiry concerns.
- Test an unavailable destination and decide what the visitor should see.
Define ownership after submission
Agree who reviews new enquiries, who covers absence and how an enquiry is marked as handled. If the same message arrives through two channels, the team needs a way to recognise it rather than replying twice with conflicting information.
Measure a small number of outcomes: valid enquiries received, enquiries awaiting a reply and enquiries that progressed to a useful discussion. Avoid interpreting every page view as buying intent.
Turn findings into the redesign brief
Separate visual changes from functional defects. A confusing service explanation needs better content; a failed notification needs a technical fix; an unanswered message needs an operational owner.
The redesign should address those specific problems while preserving what already works. A clearer next step and a reliable response process are often more valuable than adding another animation.
