A Live Chat Widget for Your Own Website, in One Script Tag
Editor now ships an embeddable live-chat widget you can drop into any website with a single script tag and a workspace ID.
If you've ever installed a live-chat bubble on a website, you already know the drill: paste a script tag, hand it a site or workspace identifier, and a chat widget appears in the corner ready to talk to visitors. Editor now ships its own version of that same pattern, built into the platform rather than bolted on through a third-party vendor.
What it does
The widget is initialized with a small snippet that points at your workspace ID and takes over from there — no separate account to manage, no extra login for your team to remember. You can configure where it sits on the page, what greeting it opens with, and which domains are allowed to load it at all, so the widget only ever runs on sites you've explicitly approved. It also supports an auto-open behavior and per-page show/hide rules, so you can choose to surface it prominently on a pricing page and stay out of the way on a documentation page, for example.
Because it's part of the same platform that already hosts your CRM and campaign tools, a conversation started through the widget lands in the same place your team already works — it isn't a separate inbox living in a separate tool.
A quick honest note on the name
The code that powers this widget refers to it internally as "OpChat" — that's the name you'll find in the configuration object and the script's own API if you go looking under the hood. We're describing it here by what it does — an embeddable, script-tag live-chat widget for your own site — rather than asserting a specific public-facing brand name for it, since that naming may still be in flux. If you're integrating it today, go by the actual script and configuration keys documented for your workspace rather than any name used in casual reference, this piece included.
Why it's worth having in-house
The pitch for an embeddable chat widget is always the same: install simplicity, fast load times, and enough customization to match your site without fighting the tool. Having it live inside the same workspace as the rest of your customer-facing tools means one less vendor relationship, one less login, and one less integration to keep working when something upstream changes. If your site doesn't have a way for a visitor to just ask a question yet, this is a one-tag way to add one.