The widget is a single script tag, but the details are where a chat window either feels trustworthy or feels bolted on. Here is what a visitor gets on your site.
A conversation that keeps up
Messages arrive in real time over a websocket, with an automatic fallback to polling on networks that block them — corporate proxies included. Visitors see typing indicators, delivery ticks on their own messages, and a retry control if something fails to send rather than a message that quietly disappears.
Close the laptop and come back and the conversation resumes rather than starting over. While every agent is busy the visitor is told their place in the queue — "you're next in line" beats an empty window with a spinner.
It looks like your site, not ours
The widget renders inside a Shadow DOM, so your CSS cannot break it and it cannot break your CSS — the usual cause of a chat button that looks fine on the homepage and collapses on a product page.
Set the accent colour and position from the embed, and it follows the visitor's dark-mode preference. The whole bundle is about 29 KB gzipped and loads asynchronously, so it is not what makes your page slow.
Usable by everyone
Built to WCAG 2.1 AA: keyboard reachable throughout, focus moves into the dialog when it opens and returns to the launcher when it closes, Escape closes it, and the interface respects a reduced-motion preference.
In the ASP.NET Core edition the interface ships in 33 languages, including Chinese (Simplified and Traditional) and right-to-left Arabic, Hebrew, Persian and Urdu, following the visitor's browser language unless you pin one.
Nobody arrives at a dead end
When no agent is available the widget offers a leave-a-message form instead of pretending to be online, and those submissions land in Missed Chats with the visitor's details so nothing is lost overnight.
When the conversation ends the visitor can rate it, and the ratings roll up into a satisfaction summary on your dashboard.