Use browser voice safely in the website widget

Check the browser and website policy

• Use a current browser with microphone support and test from the exact allowed website origin.
• Keep the widget frame and API origins in the site's Content Security Policy. The parent page must allow microphone access for the widget frame with Permissions-Policy.
• Decide whether this widget uses Human support or AI support. Human support connects the visitor in the browser with an available teammate and does not require a phone number. AI support starts the configured DobroDesk voice assistant. Calls to or from a support number use the separate Phone channel.
• The widget never starts microphone capture on page load. To request a call, a visitor must tap the phone icon in the message composer. A blocked parent policy cannot be bypassed from inside the frame.

Configure voice access and widget languages

1. 1

   For AI calls, open Settings > Channels > Voice policy. A workspace Owner or Admin must allow AI calls to use the shared wallet and set a monthly purchase limit. Teammate calls do not require AI consent.

   

2. 2

   Set the maximum concurrent calls and new calls per day, then save. Until a policy is saved, teammate calls through the widget allow four concurrent calls and 100 new calls a day per workspace. Different operators can handle calls in parallel. Each operator handles one call at a time across Phone and widget voice.

3. 3

   Open Settings > Channels > Website widgets, select the widget and open Voice settings. For AI voice, enable it after workspace consent, then choose Default language and Allowed languages. The list accepts 1 to 32 language tags and must include the default language.

4. 4

   Choose Human call recording and transcription. Off is the default. Ask the visitor before recording lets the visitor allow recording or continue the call without it. Record with a notice shows a recording notice before a human call starts. These choices apply to teammate calls from this widget, not AI calls or calls to a Phone number. Human call recording remains configurable when AI voice is off. Audio recordings expire after 30 days. Playback then becomes unavailable while the transcript and call details follow the chat retention policy. An active legal hold can delay physical deletion.

5. 5

   Save the widget. Language fields stay hidden until voice is enabled. Keep the browser microphone, Permissions-Policy and CSP checks from this guide in place.

Start and stop a voice session

1. 1

   Open the website widget and tap the phone icon in the message composer. Opening the widget does not request microphone access.

2. 2

   Follow the recording prompt or notice when one appears, then allow microphone access when the browser asks. While the call is connecting, choose Cancel call setup to stop it.

3. 3

   Once connected, a red square Stop control appears where the microphone was. Tap it to end the call. Dictation stays hidden until the call ends.

4. 4

   For Human support, wait for an available teammate to answer or continue the text conversation if nobody is available. During an AI call, choose Talk to a teammate when it appears to request a human and follow any recording prompt or notice.

Recover from a blocked or interrupted session

1. 1

   If the browser denies the microphone, choose the text conversation or change the site permission, then tap the phone icon again.

2. 2

   If the phone icon is unavailable, check the exact origin, the widget configuration, CSP and the parent Permissions-Policy header. A policy error must be fixed on the website, not inside the widget.

3. 3

   If you cannot hear the call, allow sound in your browser settings, then tap the phone icon again.

4. 4

   If the widget cannot confirm that a teammate call ended, keep it open and choose Retry ending call. Continue in text if the end remains unconfirmed.

5. 5

   If another call stops unexpectedly, tap the phone icon once more and keep the text path available. Record repeated failures with the time, origin and browser.

• A voice call starts only after the visitor chooses it, and the microphone does not turn on when the page loads. Human-call recording is off by default and follows the notice or visitor choice configured for this widget. The AI voice assistant can reply during an active AI call.