Revisited from the Foresaw archive. The argument and structure have been updated for this edition.
Speaking a request can be a convenient way to begin a shopping task. It can also hide ambiguity that a visual interface makes easier to notice: which product, which quantity, which address, and which final price?
The product challenge is to preserve convenience without making an uncertain interpretation feel like a completed purchase.
Choose a task that benefits from conversation
A repeat order, a product question, and a complex comparison are different experiences. Some tasks suit a short spoken exchange; others need visual information and more deliberate review.
Define the scope before making conversation the interface for the entire shopping journey.
Treat uncertainty as part of the interaction
A request can be incomplete, ambiguous, or misheard. Give the customer a useful way to clarify it. Do not conceal uncertainty behind a fluent response.
Offer a transition to a screen or another channel when that is the clearest way to compare options or explain a condition.
Confirm consequential actions
Before committing to an order, present the important details in a form the customer can review. Make correction and cancellation understandable.
Authentication and authorization should fit the action being taken, rather than assuming that the ability to speak to a device establishes permission to purchase.
Keep the service consistent
The conversation needs reliable connections to product information, availability, order management, and support. If those systems disagree, a natural interface can make the inconsistency harder to see.
Design and evaluate the entire journey, including recovery. The best conversational experience is one that helps the customer remain in control.
Adapted from “The Rise of Voice Commerce: A Game-Changer for Online Retail.”
First published on Foresaw. Reworked for this edition.