Lavenity 1.0 is the first public release of our live-chat product: a lightweight widget for your website and a shared inbox for the team that answers.
What shipped in the first public release
Messages travel over WebSocket and appear without a refresh. Visitors and agents both see sent → delivered → read, plus a live “typing…” indicator so the conversation feels present.
History survives reloads and return visits. If the network drops, outbound messages wait in an outbox and send without duplicates when connectivity returns.
Realtime delivery, history, and message states
On the team side, every conversation from every site lands in one inbox. Filter open and closed threads, see who is online, invite teammates, and close chats when they are resolved.
Security stays in the default path: the chat UI is isolated in an iframe on our origin, visitor sessions use signed tokens, and the widget only loads on domains you allowlist.
Team collaboration and security by default
If you already have a workspace, nothing changes in how you install the snippet. New teams can start with the 14-day trial and be live in about five minutes.
Where a new team should begin
Create the workspace, add the production domain and a separate staging domain when needed, paste the installation snippet, and send a test message from a private window. Check delivery, read state, typing, and history after reload. Invite the full team only after this end-to-end path works.
Agree on the basic workflow before real traffic begins: who watches new requests, when a chat is closed, how a complex issue is handed off, and what first-response time the team can honestly maintain. Lavenity provides the shared inbox; a shared operating rule creates the service quality.
Frequently asked question
Must the widget be reinstalled for Lavenity updates?
No. The website keeps using the same asynchronous loader and site ID. Widget and configuration updates arrive through Lavenity, so the standard installation snippet does not need to be replaced after every release.