Web widget & text mode

A web agent runs your flow over a browser connection instead of a phone call — embedded on your own site as a widget, in one of two public modes:

• WEB_FULL — full audio, like a phone call. Optionally paired with a text transcript/input channel running alongside the audio.
• WEB_TEXT — no audio at all; a chat-style, text-only conversation.

Creating a web agent

A web agent is a separate object from a phone number: it points at a flow the same way a phone number does, but is dispatched from your embedded widget instead of a DID. Give it a mode (WEB_FULL / WEB_TEXT), and — if you want the text channel — enable the chat scope on it (see Text-only sessions below for who can turn this on).

Embedding

A web agent session is dispatched with a project- and agent-scoped publishable key. The JavaScript snippet / SDK for embedding a widget on your own site is still being finalized — see Voice Embed (Developer preview) for where the embed-code side of this will land once it’s ready.

Text-only sessions

WEB_TEXT is metered but billed at €0 per minute — it’s free to run, but it still shows up in your usage/call history (with a real duration, zero billed minutes) so you can see how much it’s being used.

Two gates apply to the text channel:

• Plan gate. WEB_TEXT sessions require your project’s plan to be Growth or above — a lower-plan project attempting a text-only session is rejected with a clear reason, rather than silently falling back to voice.
• Concurrency cap. Each plan has a maximum number of simultaneous WEB_TEXT sessions per project (the exact numbers are still being finalized — check your plan’s page for the current limit). A session past the cap is rejected rather than queued.

WEB_FULL web sessions aren’t subject to either gate — they’re billed the same way a phone call is, by duration, at your plan’s normal per-minute rate.

What’s still rolling out

• The embeddable widget script itself (the piece you actually paste onto your site) is not published yet — this page will be updated with the real snippet once it lands (see Voice Embed).
• Per-plan WEB_TEXT concurrency numbers are placeholders pending a pricing decision; this page will be updated once they’re finalized.