Web chat widget

Put your agent on your website as a chat bubble. Visitors can type — or, if you switch it on, talk — and get answers from the same agent and the same knowledge that powers your phone line. One line of code to embed.

Where: Dashboard → Agents → your agent → Web Chat. For a full walkthrough see the Website chat widget use case.

The Widget Status toggle at the top turns the bubble on or off across all your sites. Below it, the Public Key is what the embed snippet carries — it’s safe to expose, and if it ever ends up somewhere you don’t want it, Regenerate it (your current snippet stops working until you paste the new one).

Choose the channels

The widget has two channels, each with its own toggle — enable one or both:

Text chat — the typed conversation.
Voice calls — adds a Call button to the widget header. The visitor taps it and talks to your agent right in the browser, on the same voice pipeline as your phone line. Needs the visitor’s microphone permission, and your site must be served over HTTPS.

Chat → voice continuity: when a visitor who’s been typing starts a call, the call continues the same conversation — the agent keeps the context and won’t make them repeat themselves, and the call lands on the same conversation record in your history.

Appearance

Primary color — the bubble and header; match your brand.
Position — bottom-right or bottom-left.
Header title, welcome message, launcher tooltip — the texts visitors see.
Logo URL (optional) — your logo in the widget header instead of the default initial.
Show “Powered by Televox AI” — untick to hide the branding line at the bottom.

Language

The widget has its own language setting, independent of the agent:

Widget Language — English, or العربية, which renders the whole widget right-to-left with Arabic labels.
Let visitors switch language — adds a compact EN | ع toggle in the widget header so bilingual visitors choose for themselves. With the switcher on, your title, welcome message and launcher tooltip each get an Arabic variant, edited on the EN | العربية tabs.

For Multilingual agents, the language the visitor is using is also the language a voice call started from the widget runs in. Details in Languages.

Allowed domains

Add every domain you’ll embed on (e.g. yourbusiness.com). The widget only runs on these — a copied key won’t work anywhere else, which is the main protection against someone putting your bubble (and your bill) on their site. Subdomains are covered automatically: allowing acme.com also allows shop.acme.com. With no domains listed, the widget is blocked everywhere.

Copy the embed snippet

The tab shows a one-line snippet unique to this agent. Copy it.


<!-- copy the exact snippet shown on the Web chat widget tab -->
<script src="https://admin.televox.ai/widget.js" data-key="YOUR_PUBLIC_KEY" async></script>

Paste it on your site

Add the snippet just before the closing </body> tag of your pages (or your site builder’s “custom code / footer” area). Publish — the bubble appears.

If the bubble doesn’t show up, the allowed domains almost always don’t include the site’s domain. Add the bare domain (acme.com) — that covers www. and every other subdomain. Listing only www.acme.com does not cover acme.com.

Rate limits and the daily message cap

The widget is public by nature, so it ships with guardrails that bound what a bad actor (or a runaway script) can cost you:

Daily Message Limit — a cap you set (below the domain list) on how many messages the widget can process per day, across all visitors. It defaults to 1,000 and is checked on every message, not just when a chat opens. Once it’s reached, visitors see that chat is temporarily unavailable; the count resets the next day. If the same agent also answers WhatsApp, both channels count toward the same daily total.
Built-in rate limits (not configurable) — a visitor can send at most 30 messages a minute, a single message is capped at 4,000 characters, and starting voice calls is rate-limited per visitor. Opening chats is rate-limited per visitor and per widget key, so rotating IP addresses doesn’t help an abuser.

What visitors get

Instant answers grounded in your knowledge — same accuracy as the phone agent.
A voice call one tap away, if you’ve enabled it — no phone dialing, no app.
Their language: a fully Arabic (RTL) widget, or an in-widget switcher that lets them pick.
Lead capture via Extractors, just like on calls.
Chat → voice continuity: a visitor can move from typing to a voice call and the agent keeps the context — it won’t make them repeat themselves.

Best practices

Use the same agent for chat and phone so answers stay consistent everywhere.
Set a helpful welcome message that invites a real question (“Ask me about our services or hours”).
Test on the live domain — the allowed-domain rule means it won’t run on localhost unless you add it.
If you enable voice, test the Call button on the live (HTTPS) site and grant the mic prompt once — that’s the flow your visitors will see.

Next steps

Full walkthrough Arabic & the language switcher Improve answers (Knowledge)