Articles / Voice chat

Website voice guide

AI Voice Chatbots for Websites: When Speaking Beats Typing

A voice chatbot gives visitors another way to ask for help on your website. It works best when speaking makes a real task easier and people can still choose text, silence or a human when that suits them.

Be clear about what “voice chatbot” means

Voice features can describe different interactions. A visitor might speak a short message that becomes text, hear a written answer read aloud, or have a live spoken exchange with an AI agent. Those are different experiences, so explain what your site offers before asking someone to use a microphone.

ChatNexus offers optional live voice in website chat. When Voice AI is enabled, a visitor can speak with the same website agent instead of typing; the browser asks for microphone access when they start voice, and text chat remains available. See the current feature overview for details.

Choose a task where speech helps

Voice is useful when a visitor wants to explain a situation in their own words, ask a follow-up without composing another message, or use a website while typing is awkward. A service enquiry, product-fit question or request for help navigating a process can be a sensible first use case. The agent still needs approved information and a defined next step; changing the input from typing to speaking does not make uncertain answers more reliable.

Start with one task and compare it with the text experience. If the spoken version takes longer, creates more confusion or adds no benefit for the visitor, keep text as the main route and make voice an option for the people who prefer it.

Keep text and human support easy to reach

Some visitors are in a quiet office, on public transport, sharing a space or simply prefer to read. Others may be unable to use a microphone. Do not start voice automatically, hide the text input or make speech the only path to important information. Keep the written conversation visible where possible, and make the controls for starting and stopping voice easy to understand.

A voice interface should also show what is happening. Visitors need a clear listening state, visible transcription or confirmation of what the system heard, an indication when the agent is responding, and a useful recovery path if microphone access or the connection fails. Let people correct a misheard request instead of forcing them to start over.

Set microphone expectations before the first turn

Ask for microphone permission only when a visitor chooses voice. Briefly explain why access is needed and what the visitor can do if they decline. Tell people where to find the site’s privacy information and avoid inviting them to dictate payment details, passwords or other sensitive information into a public website chat. Route account or case-specific work through an authenticated workflow or a person.

The assistant should follow the same source, scope and escalation rules in voice that it follows in text. Review the AI chatbot security checklist before connecting private or sensitive information.

Test the complete voice journey

Test on the browsers and devices your customers use. Include the first-use permission prompt, a denied permission, background noise, interruptions, a long pause, a misheard word, a follow-up question and a request that should go to a person. Check that text remains usable throughout and that a failed voice session does not lose the conversation.

• Can a first-time visitor tell how to start and stop speaking?
• Can they see or correct what the system heard?
• Does the agent answer from the same approved knowledge as text chat?
• Can the visitor switch to typing or reach a human without repeating everything?
• Does the experience recover clearly if permission or connectivity fails?

Measure completed visitor tasks, answer quality, handoff outcomes and voice failures alongside usage. A high number of voice starts does not show that people received help. Use the same task definitions for voice and text so the team can see whether each route is genuinely useful. Our chatbot analytics guide explains how to choose outcome measures.

Start with an optional, well-tested voice route

Voice can make a website conversation feel more immediate, but only when the visitor stays in control. Choose one common task, enable the experience deliberately, test it on real devices and keep a clear text and human alternative. You can try the ChatNexus website agent or read the website chatbot setup guide before planning your rollout.