Install a website voice or chat widget

Website widgets let visitors speak or chat with a published agent from your site. The embed loads from widget.verbatik.com; you manage the agent and appearance in the dashboard.

Create and customize

1. Open Website widgets and choose Create widget. A published voice agent produces a calling widget; a published chat agent produces a text widget.
2. Set the widget name, agent and published version.
3. In Colors and theme, set Theme, Screen position, Brand color and optional Header color.
4. Customize Header title, Header subtitle, Welcome title, Welcome message and Primary button label.
5. Set the Launcher label and Launcher icon. Under Logo and first image, choose a logo/icon and welcome image with a meaningful image description.
6. Review the live preview. If website branding was imported during onboarding, the clinic icon and brand defaults may already be filled. A deliberate widget override takes precedence.

Set deployment limits

Add exact allowed website origins, one per line, such as https://yourclinic.com and https://www.yourclinic.com. Do not include paths, a trailing slash or wildcards. Production sites require HTTPS; local HTTP is accepted only for localhost/127.0.0.1 testing.

Set the concurrent-session limit and decide whether Execute tools should be enabled. Keep tools off for an information-only preview. Enable them only after reviewing the published agent’s permissions and testing real action receipts. The widget has its own enabled state; saving an agent draft does not automatically change a pinned widget version.

Install

Save the widget, open Install your widget, and copy the generated code before the site’s closing body tag. It has this shape; replace the example ID with the saved ID:

<script src="https://widget.verbatik.com/verbatik-widget.js" data-widget="YOUR_WIDGET_ID" defer></script>

No account API key belongs in the embed. Saved appearance changes load automatically.

Verify on the real site

Open the allowed domain, accept microphone permission for voice, start a session and check transcript, playback, interruptions and hangup. Check chat separately if you deploy a chat agent. Test narrow screens and keyboard operation. If a session is blocked, check the exact origin, published version, enabled state, available capacity and account/provider readiness.

A browser visitor has no automatic telephone identity. Do not assume the widget can send an SMS or transfer a browser session to a staff PSTN line using a number it was never given.