Web Widget

Embed a customisable chat widget on your website - install, theme, authenticate, and manage content

The Wexio Web Widget (Web Messenger) is a chat widget you embed on your website. Visitors get a launcher that opens a panel with up to five tabs - Home, Messages, Help, News, and Profile - backed by your AI assistant, help articles, and news posts.

You set its look, content, and behaviour in the Widget settings, then embed it with one script tag, a Web Component, or a framework package.

The web widget launcher and open panel on a website

This section covers embedding and configuring the widget. To reply to web conversations, see the main Documentation tab.

Two Audiences, One Widget

You areStart here
An admin setting it up in the dashboardCreate a widget → Configure
A developer embedding it on a siteQuickstart → Install → Authentication

Delivery Modes

The widget uses one runtime, loaded by the loader from https://cdn.wexio.io. The runtime is the same in every mode. Only where it mounts changes.

ModeHost embeds withRuns inPick it when
Script loader<script src=".../loader.js">IframeOne-line install, full sandbox. Non-technical operators.
Web Component<wexio-widget> elementShadow DOMAny framework or vanilla, no build step.
Framework packagenpm install + native componentShadow DOMIdiomatic props/events in your framework.

The framework packages are thin wrappers around the Web Component. They exist for React, Vue 3, Angular, and Ember.

To choose a method, read Install Methods. To see working code, open the examples.

How It Fits Together

  • Its own entity. A Web Messenger is a WebIntegration record, separate from your messaging channels (Telegram, WhatsApp, and so on). It has a publicKey (embed identity, safe to expose) and a sharedSecret (server-to-server auth, shown once). You get one widget per organisation currently.
  • Plan-gated. It is available from the Standard tier upward. Hiding the Wexio badge requires Pro or Enterprise.
  • Role-gated. Creating or deleting the integration and editing widget settings requires Admin/Owner. Editors manage help articles and news. Agents can only view the web pages.
  • Dashboard routes. Widget settings (Brand in the sidebar): /{org}/web/brand. Help center: /{org}/web/help. News: /{org}/web/articles.

The public key (pk_live_…) is safe to put in client-side HTML. The shared secret is server-to-server only - never embed it in a page. See Authentication.

Was this page helpful?

On this page