Embeddable voice widget
An embeddable voice widget is a website interface that lets a visitor start a spoken conversation with a voice agent directly from a web page instead of dialing a phone number. It gives the site a voice entry point while keeping the conversation connected to an agent's call workflow and records.
How an embeddable voice widget works
The website loads the widget through a component or script. When a visitor chooses to begin, the browser asks for microphone access and starts an audio session with the configured voice agent. The visitor speaks and hears the agent through the device, while the surrounding page can continue to provide visual context such as product details, support instructions, or an appointment form.
A widget may always connect to one agent, or the site can use page and visitor context to determine where a new session should go. That routing decision should be limited to information the business is prepared to send into the call workflow. The spoken experience still needs the same prompt rules, tool permissions, escalation paths, and quality checks as a phone-based agent.
Deployment controls are important because the widget is exposed in a browser. A publishable credential should be restricted to approved website origins, and the business should be able to disable access without removing every embed. Microphone notices, recording disclosures, and consent handling also need to match the business's location, audience, and data practices.
Why it matters for voice agents
A web visitor may want an immediate answer but prefer speaking to typing or calling a separate number. The widget removes the dialing step and lets the conversation begin at the point where the question arises. It can serve sales, scheduling, or support flows, but it should not be treated as a separate quality channel: teams still need to review transcripts, recordings, outcomes, and handoffs.
The site should also provide a usable alternative when microphone access is denied, the environment is too noisy, or speaking is not appropriate. Clear start and stop controls help visitors understand when a session is active.
In practice on ThunderPhone
ThunderPhone's voice widget supports React and script-tag installation, agent-bound and webhook-routed modes, domain allowlists, origin-locked publishable keys, and enable or disable controls. Widget sessions use the same call infrastructure as phone calls and can produce the same transcript, recording, and grading data. They also appear in call history.