Voice is enabled per installation
The merchant decides whether voice belongs in the visitor experience for a particular website or store. Text chat remains available as the core interaction path.
Visitors ask in their own words
A visitor can speak the same kinds of product, delivery, return, compatibility, or navigation questions they could type. The spoken request is converted to text before the assistant processes it.
Answers use the configured knowledge
Voice does not create new store facts. The answer depends on the website pages, product information, and policies the merchant has connected and kept current.
Unsupported questions should not become guesses
If the configured knowledge does not support a product claim, delivery promise, policy exception, or private account answer, the assistant should say the information is unavailable or route the exception to the approved human path.
Merchants control the privacy notice
Store owners should explain their visitor-data handling and voice-related choices in the privacy information appropriate for their business and jurisdiction.
Test voice with real visitor scenarios
Evaluate common questions about sizes, compatibility, delivery, returns, and next steps. Feature testing helps verify the configured experience; it is not a guarantee about recognition quality or business outcomes.