Design the form, the confirmation, and the office handoff together. The experience is complete only when somebody can act on the request.
Answer the questions before the form
A customer arrives with a practical question: can this business help me, and what should I do next? A service page should answer that before asking for personal details. Show the work you cover, the area you serve, and how the enquiry process works.
For a plumbing business, that could mean making it easy to distinguish a general job enquiry from the business-approved route for urgent requests. For HVAC, it may mean separating maintenance, a repair enquiry, and an installation estimate. The customer should not have to understand your internal categories to proceed.
Make every field earn its place
Walk through the form with the person who receives the requests. Ask what each field changes about the next action. If nobody uses an answer, consider removing the question. If staff always ask the same follow-up, consider whether one clearer field could avoid that extra exchange.
Use plain labels that remain visible after someone starts typing. Explain optional fields and make errors specific enough to correct. On mobile, a short form with useful prompts can be more effective than a compact form that leaves people guessing.
Prototype the full journey
A polished form is not enough if the next screen is vague. Include the confirmation state in the prototype: what was submitted, what happens next, and whether the team still needs to confirm a booking. Make it clear which action the customer has completed.
Include the office view too. Show how the request appears, what context travels with it, and what the recipient does next. Designing both sides exposes missing information before the development work becomes expensive to change.
Test with ordinary and awkward examples
Try a request with a long address, an unfamiliar service description, and a missing optional field. Review what happens when submission fails or someone uses a keyboard. Check whether a person can understand and complete the journey without relying on decorative motion or an icon alone.
Ask people to describe what they expect after submitting. If their expectations differ from your process, revise the content. That misunderstanding is useful design feedback, even when the interface looks finished.
Choose a focused design package
A practical design sprint can cover the service-page structure, one enquiry journey, the confirmation state, and the office handoff. Deliver a clickable prototype and implementation notes that explain the behaviour as well as the appearance.
After release, review incomplete requests, clarification conversations, and the ease of processing submissions. Use that evidence to improve the journey. A good enquiry experience earns its value by making the first useful conversation easier for both sides.
PUT IT TO WORK
Walk through one enquiry on your phone.
A homeowner submits a plumbing enquiry with a location and a description. The confirmation explains that the office will review it, and the office receives those details with a callback method. The design succeeds when both sides understand the next step, including what happens if submission fails.
- Explain the service before asking for details.
- Remove fields that do not affect the next action.
- Keep labels visible while people type.
- Design success, error, and duplicate-submission states.
- Test the office handoff as well as the public form.
A clickable enquiry journey covering the form, successful submission, correction of errors, and the office’s view of the request.
Choose a design sprint when the problem is an unclear journey. Include implementation when the existing form or office tools cannot support the improved experience.
Put the idea into practice.
Explore a focused approach for plumbing, including the workflow, proposed measures, and a done-for-you starting scope.
You’ll see what we deliver, what your team needs to provide, and how the result is reviewed. A written proposal confirms the scope and price before work begins.
Explore the solution