Customer experience
Your contact form is only half the enquiry journey.
Trace what happens after submission so promising enquiries reach the right person with a useful next step.
Consider a hypothetical example: at 10.15, a prospective customer submits an enquiry. The confirmation page says someone will be in touch. By lunchtime, who has received it, who owns it and what do they know about the request? A form can work perfectly while the enquiry behind it is still waiting in the wrong queue.
Follow the handover after submit
Start with an agreed test enquiry and follow it beyond the website. Check the confirmation the customer sees, the notification your team receives and the system where the enquiry is recorded. Note each handover rather than assuming the technology joins everything together.
Give the enquiry a clear owner. A shared inbox may be the destination, but it is not ownership unless someone is responsible for triage. Define how enquiries are assigned, how absence is covered and when an unassigned item should be escalated.
- Does the customer receive an accurate confirmation?
- Does the notification contain enough context to route the enquiry?
- Can the team see whether someone has taken ownership?
- Is the original source and consent recorded where it is needed?
Define a useful first response
Speed matters, but a quick acknowledgement is not the same as a useful response. Decide what the customer needs next: confirmation that the request has been understood, any essential question, and a realistic explanation of what will happen.
Avoid promising a response time the operating process cannot support. If different enquiry types need different treatment, make that visible in the routing rules and customer message rather than relying on someone to remember.
Test the exception, not only the happy path
Use synthetic details and test a small set of realistic variations. A hypothetical consultancy might try a general question, a request that belongs with a specialist and an enquiry submitted when the usual owner is away. The objective is to see where responsibility becomes unclear.
Check what happens when a notification fails, an enquiry is incomplete or two people start replying. Agree a recovery route and keep the test clearly labelled so it cannot be mistaken for a real sales opportunity.
Improve one break in the chain
Record the journey as a simple sequence: submitted, confirmed, received, assigned, responded and followed up. For each step, name the system or person responsible and the evidence that the step occurred. This gives you a more useful improvement brief than a general request to ‘fix the form’.
Choose the break that creates the most consequential delay or confusion. It may require clearer website copy, a better notification, a routing rule or a change in team practice. Review the result with actual enquiry evidence where appropriate, while respecting customer data and access controls.
Rethink’s website conversion review can examine the journey from interest into enquiry and turn the findings into prioritised actions. Delivery support can then help carry agreed changes through. Start by tracing one recent enquiry from submission to ownership.