Help Center
DocsLive Chat
Add a live-chat bubble to your own website and answer visitors from the Service Inbox
Live Chat puts a floating chat bubble on your own website. When a visitor opens it and sends a message, a support ticket is created in your Service Inbox with a Live chat origin chip, and your agents reply from the same three-pane workspace they use for every other channel. There is no separate chat console to learn — live chat is just another way a ticket can arrive.
The chat widget resolves your organization from your enabled Help Center. That keeps setup to a single switch: once your Help Center is turned on with a public address, the chat widget can mount against it. If your Help Center is off, the bubble shows a friendly “chat isn't available” state rather than a broken widget.
Enable your Help Center
Go to Service → Settings → Help Center, choose a public address (the Public address field), and turn Public Help Center on in the Publish section. See Your Public Help Center for the full walkthrough. The address you pick is your organization key for the chat widget.
Add the one-line script to your site
Drop a single <script> tag onto any page of your website, just before the closing </body>. Replace your-address with the public address you chose above:
Publish your site
The bubble appears in the bottom corner. Visitors click it, type a message, and it becomes a ticket in your Inbox in real time.
The embed snippet
<script src="https://app.laureo.io/embed/chat.js" data-org-slug="your-address" async></script>The script is self-contained — no other tags, stylesheets, or dependencies. It mounts a launcher and, when opened, a panel that frames the chat against your app origin, so the widget never needs access to anything on your own site.
data-org-slug— Required. Your Help Center's public address, which tells the widget whose Inbox to route chats to.data-position— Optional.bottom-right(default) orbottom-left.data-launcher-label— Optional. The accessible label on the bubble (default “Chat with us”).
The chat window picks up your Help Center brand color automatically, so the conversation matches the rest of your customer-facing surfaces without extra configuration.
A live-chat conversation opens in the center pane like any ticket. You reply in real time, add internal notes, assign it to a teammate, insert a macro, pull in a knowledge base article, or (on Ultra) let the AI copilot draft a response. The Live chat chip on the ticket tells you at a glance that the customer is (or was) chatting live, so you can prioritize an active conversation over an email that can wait.
Turn one visitor away from the ticket, and undo it from Service settings.
Every live-chat ticket has a Block visitor action in the Customer tab of the context panel. It takes two presses: the first arms it and spells out what it will do, the second commits. That is the only place a block starts, and it works whether or not the visitor left an address.
What blocking does
- Ends the conversation in front of you: the visitor's live session stops being served from the moment you block, mid-thread if need be.
- Turns away new chats from that same widget session and from the email address on file, when the visitor left one. The address is the arm that lasts.
- Tells the visitor nothing: they get the ordinary “chat isn't available” state, identical to what a site with no chat set up shows, so a blocked party cannot confirm they were blocked.
- Does not follow a stranger around: an anonymous visitor who left no address and reloads the page arrives as someone new. Devices are never fingerprinted, so the durable protection is the address.