Skip to main content
Configure > Tools > Web Widgets manages website voice conversations. For a text-chat launcher, use Chat Agents.

​
Create a voice widget

  1. Open Web Widgets and choose Create Widget when your account has capacity.
  2. In General, set its name and select an Incoming AI Agent. Flow Agents are not supported by this selector. A default-agent option is also shown; select a saved agent when you need a specific configuration.
  3. Set Active or Paused status.
  4. In Branding, configure the icon, brand/button text, colors, and terms requirement. White-label output follows the account’s current entitlement.
  5. In Settings, set allowed domains, optional business hours/days and timezone, and supported advanced limits.
  6. Save the widget.
Advanced settings include maximum duration, per-IP cooldown, and maximum concurrent sessions. These are upper configuration limits; credits, provider readiness, and current capacity can still prevent a session. Voice and chat widgets share the configured combined widget count allowance.

​
Embed and verify

Open the widget card menu and choose Get Embed Code. Copy the complete generated snippet into your website. Use the generated origin and token rather than inventing a script URL or inserting account/provider credentials. A visitor starts a conversation through an explicit click, accepts terms when required, and grants microphone permission. Use a secure website context that supports browser audio. No call should be assumed to start merely because the script loaded. The configured agent determines the voice runtime and compatible languages: ElevenLabs, OpenAI Realtime, or gated GPT Live where available. Widget availability also checks status, domains, business hours, credits, concurrency, and provider configuration. If access is denied, inspect these settings and the application message. Regenerate Token invalidates the previous embed token. After rotating it, replace installed snippets that still use the old token.

​
Knowledge, actions, and records

Assigned knowledge can be retrieved during a supported widget session. Appointment booking must be enabled and supported for that runtime. GPT Live browser widgets currently reject appointment mutation when playback confirmation is unavailable; do not promise booking solely because the toggle is enabled. Review the widget’s statistics and Call Logs for available session records, transcripts, and usage. OpenAI website voice sessions do not have a server-side audio recording in the call view. Voice widget sessions consume account credits under the current policy; use the current account/usage display for charges. For a custom website button, use the feature-detected VoiceWidget host API v1. This controls the same embedded session and preserves its consent and finalization flow.