Website live chat
Live chat puts a chat bubble on your website — any website — and delivers visitor conversations into the team chat inbox your agents already use for internal chat and SMS. No third-party chat service, no per-seat chat pricing: the widget is served by your own PBX.
Adding it to a site
Admin → Integrations → Live Chat → Add website. Give the site a name, register its
origins (the exact https:// addresses of the pages that will host the widget), choose
where conversations route — a queue, ring group, or single extension — and set a welcome
message. You get a one-line embed snippet:
<script src="https://your-pbx-fqdn/livechat/widget.js" data-key="SITE_KEY" async></script>
Paste it into any platform — WordPress, Squarespace, Shopify, static HTML — before </body>.
The widget is a small launcher plus an iframe served from your PBX, so it works identically
everywhere and inherits nothing from (and imposes nothing on) the host site.
The origin list is the security gate. The browser itself refuses to render the chat frame
on any site you haven't registered (enforced via Content-Security-Policy frame-ancestors), so
a copied snippet is useless elsewhere. Visitor traffic is rate-limited per address, messages
are length-capped, and everything a visitor types is stored and rendered as plain text.
What the visitor sees
The bubble opens a compact chat panel: a name prompt, your welcome message, then a live conversation. Their thread survives page navigation within the tab session. When an agent closes the conversation, the visitor sees it end cleanly.
What your team sees
Visitor conversations appear in Chat beside everything else, badged as web chats and routed to the queue or ring group you chose — every member sees the new conversation, and the first agent to reply claims it (claim-on-send, exactly like team SMS), so two agents never answer the same visitor. Closing the thread from the conversation header ends it on both sides. Chat logs include live-chat conversations alongside internal and SMS history.