Fix widget loading and microphone access

Widget does not appear

1. Open the widget's settings in the clinic workspace and confirm it is enabled.
2. Confirm it references an available published agent version.
3. Copy the current generated embed and install it on the intended website page.
4. Check that the site's content-security policy permits the widget script and its required connections.
5. Inspect the website's browser console and network errors if loading is blocked.

Use the generated embed served from widget.verbatik.com. A visual editor preview shows appearance; it does not prove a live visitor can start a session. Avoid adding duplicate embeds for the same widget.

“Widget origin is not allowed”

Enter each exact website origin in the allowed list, for example https://clinic.example. An origin contains the scheme and hostname, plus a port when relevant. It does not contain a page path, query string or trailing slash.

https://clinic.example and https://www.clinic.example are different origins. Add a staging hostname separately when you test there. Public sites use HTTPS; opening a downloaded HTML file produces an unsupported opaque origin. Do not replace an exact allowlist with a wildcard to hide a configuration problem.

Voice is silent or microphone is denied

A visitor must allow microphone permission and click the call control. Check the browser's site-permission setting and the selected device. If your website embeds the page inside another iframe, its permissions policy also needs to permit microphone use. Ask the website administrator to check that embedding policy rather than changing the widget's API credentials.

If the server reports that all receptionists are busy or a rate limit was reached, end unused sessions and wait before starting another. Repeatedly reloading does not bypass session or account limits. If the widget changed while loading, reload the page before starting a new session.

Frequently asked questions

The icon is missing. Is calling broken? An unavailable logo or welcome image is a branding issue; inspect its URL and image access separately from the session error.

Why does booking work in the agent test but not the widget? The widget has its own Execute connected tools permission and selected published version. Review both before enabling real writes.

Continue with widget installation and customization and voice troubleshooting.