↑
← All articles

Customer experience

Tell customers what they need before the form starts.

Show customers the information, documents, time and decisions an online form requires before asking them to begin.

A hypothetical home-services business invites customers to request a detailed quote online. The first screen asks for a name and postcode. Four screens later, the form requires room measurements, photographs and a decision about access dates. A customer who expected a two-minute enquiry has to stop and find the missing information. Before someone starts a form, tell them what a successful completion requires. A short, accurate preparation note can reduce the risk of avoidable abandonment without making the opening page feel like another set of terms and conditions.

Make the commitment visible

Summarise the expected time, information and documents near the start button. Use specific language: ‘Allow around ten minutes and have two recent photographs available’ is more useful than ‘This form may take some time’. If the time varies, explain what makes it longer rather than presenting false precision.

Include any decision the customer must make during the process. If they need to choose a service level, nominate an authorised contact or agree a preferred date, they may want to consult someone before beginning.

Separate essential from helpful

Mark which items are required for the request to proceed and which simply help the team respond more accurately. Do not make optional questions look compulsory, and do not wait until submission to reveal that a required document is missing.

Where possible, explain the reason beside the request. A concise purpose can help someone choose the right information and avoid uploading material that is unnecessary. Keep that explanation connected to the field rather than hiding it in a distant privacy notice or help page.

  • What must the customer know before starting?
  • Which documents or images are required?
  • Which questions need another person's input?
  • Can progress be saved safely if preparation is incomplete?

Give people a safe route to pause

If the task is too long to complete in one sitting, make the pause and return route explicit. Say what will be saved, for how long and how the customer gets back. Do not imply that information is stored unless the system has actually confirmed it.

For shorter forms, a checklist may be enough. Let the customer leave, gather what they need and return without losing confidence about the next step. If no save function exists, say so before they invest time in the form.

Test the promise against the real journey

Complete the form with representative synthetic details on a phone and a larger screen. Compare the preparation note with every required field, upload condition and decision. Check error and recovery routes too: an unsupported file or interrupted session should not create a new requirement the customer could not have anticipated.

Review the note whenever the form changes. Adding one mandatory question can alter the preparation, time or people involved. Give the journey an owner who checks the promise as well as the fields.

Rethink's website conversion reviews can help trace these points of hesitation and turn them into a practical improvement list.

Explore website conversion reviews →

Work with Rethink

Discuss your
project.

Talk to Rethink