Open the widget from your own buttons
window.AsksWidget now exposes open(), close(), and version — wire “Chat with us” links anywhere on your page to the widget.
Your page finally gets a say in when the widget opens. The embed now exposes a tiny JavaScript API: AsksWidget.open() and AsksWidget.close()for wiring any “Chat with us” button, link, or banner to the chat — and AsksWidget.versiontells you exactly which build your storefront is serving when you're debugging.
document.querySelector("#chat-with-us").addEventListener("click", () => {window.AsksWidget.open();});
Four members, no framework
The embed exposes a small API on window.AsksWidget: init()for manual initialization when script attributes won't do, open() and close() to control the panel, and version, the build identifier of the loaded script. Wire open()to any “Chat with us” button, footer link, or banner and the widget opens from your UI instead of only its own launcher. Plain JavaScript on the global — it works with any embed installation, whatever your site is built with. Both calls are no-ops until the widget has mounted, so calling early is safe.
version answers the debugging question
Widget rendering issues usually start with one question: which build is this page actually serving? Checking window.AsksWidget.version in the storefront console answers it exactly — useful when a CDN or theme cache might be holding an older script, and worth including when you report a widget issue.
See what's new in your workspace
Everything on this page is live today. Asks trains on your website and resolves customer conversations on every channel — free to try, live in minutes.