Quick answer
Zero UI means using voice, gestures or automation instead of relying on a screen. It can make a simple task easier, but only if customers know what’s happening and can correct a mistake. Removing buttons is easy; removing frustration takes more thought.
Where a screen-free journey helps
Checking an order shouldn’t need a tour of your website. A short spoken answer may be enough. Comparing contract terms is another matter: people need something they can scan, question and return to. Start with the task, then choose the interface.
| Task | Useful approach | Keep available |
|---|---|---|
| Order status | A short answer tied to the right order | A written record and support link |
| Repeat purchase | Confirm the item, quantity and price | A review step before ordering |
| Product comparison | A visible side-by-side comparison | Accessible text and detailed specifications |
| Preference update | State exactly what will change | A way to review and undo the change |
Make mistakes easy to recognise
Suppose a customer asks to repeat an order containing several products. The assistant should identify the intended item before proceeding. Reading back a product name is useful only if the customer also knows the quantity, delivery address and amount to be charged.
Design the recovery path alongside the successful journey. Let people interrupt, correct a choice or move to another channel without starting from scratch. A system that repeatedly mishears a name should offer a different input method rather than another identical prompt.
Accessibility is part of the brief
Voice can help some people and exclude others. Background noise, speech differences, hearing needs and a shared workplace all affect whether a spoken exchange is suitable. Gestures also depend on a person’s movement and the device’s ability to recognise it.
Keep essential information available in another usable form. The W3C guidance on non-text content explains the role of text alternatives. The wider design still needs testing with the people and devices the service is meant to support.
Measure the whole task
Count successful completions, corrections, abandoned attempts and transfers to support. Look at time to completion across the whole journey, including recovery. A short voice interaction followed by a long support call is not a saving.
Use the findings to decide which tasks deserve this interface. Removing a visible control is worthwhile when customers retain enough information and control to get the result they intended. Use customer experience analytics to connect task failures with feedback.
Apply the same test to digital journeys: measure qualified task completion and keep people in control when automation acts. See our guides to B2B landing page optimisation and AI agent governance.
