Voice Activation

By default a visitor has to click the launcher to start talking. That excludes anyone who can't see or reach it. With voice activation on, the widget listens locally for a phrase you choose — “hey acme” — and opens a conversation when it hears it.

#Turning it on

This is configured per project in the dashboard, not in code. Open your project → Appearance → Voice Activation, switch it on, and enter the phrase you want visitors to say.

Use two to four words. A single short word like “go” gets triggered constantly by ordinary conversation, and the dashboard will reject it for that reason.

#How it works

Detection runs entirely in the visitor's browser using the Web Speech API. No connection to Voxide is opened and no session is started until the phrase actually matches — so an idle widget listening in the background costs you nothing.

Browser support

Works in Chrome and Edge. Safari support is partial and Firefox has none. Everywhere else the widget silently stays click-to-talk, so nothing breaks — visitors on unsupported browsers just don't see the feature.

Tell your visitors

While armed, the browser sends audio to its own speech service (Google's, in Chrome) to recognise the phrase. It never reaches Voxide, but it does leave the visitor's device — so this belongs in your privacy policy if you enable it.

#The first click

Browsers require permission before any page can use a microphone, and that prompt has to be triggered by the visitor. So the very first visit still needs one interaction. After they allow it, Chrome remembers the grant for your origin and later visits can arm on their own — which is where the accessibility benefit actually lands.

We would rather say that plainly than claim “no click ever” and have you discover the exception in production.

#Building your own UI

If you render your own interface instead of <VoxideWidget />, feature-detect before offering any wake-word affordance:

typescript

import { isWakeWordSupported } from "@voxide/react";
 
if (isWakeWordSupported()) {
  // safe to show a "listening" indicator
}

← Security & CORS Human Handoff →