Skip to main content
WebChat is the fastest way to put BoundBot in front of customers. It creates an embeddable widget backed by a public key, optional origin restrictions, visitor identity controls, image upload, and browser voice.

​
Create a channel

Open Channels -> WebChat and click Connect WebChat. Set these fields:
  • Bot: the bot that should answer on this widget
  • Widget display name: the channel label shown inside setup and UI flows
  • Allowed origins: optional list of domains that are allowed to embed the widget. If you are unsure of the exact origins or you are testing locally, leave this field empty so the widget is not blocked by a mismatch—this avoids connectivity and Origin not allowed issues until you lock in production domains.
If you finished onboarding, you may already have a default WebChat channel ready to review instead of creating a new one.
If you saved an incorrect origin or you are testing locally, keep Allowed origins empty to avoid Origin not allowed errors. Add origins only when you are ready to restrict embedding to specific production domains.

​
What you manage on the channel page

From the WebChat channel table, you can manage:
  • the bot assignment
  • channel status
  • public key usage
  • allowed origins
  • key rotation on supported plans
  • anonymous or authenticated visitor mode
  • the generated script embed

​
Customize the widget

Open Settings → Customize Widget and select the channel. You can change:
  • appearance, size, position, colors, border radius, and branding
  • the bot assignment, starter suggestions, and optional voice greeting
  • page paths where the widget should be hidden or exclusively shown
  • script and direct-iframe installation code
Save the configuration before copying a fresh production embed from the Install tab.

​
Test before embedding

Use Playground to test the exact bot and WebChat combination before you install the widget on a live site. If a conversation is muted for human handoff, WebChat will stop sending AI replies in that thread until your team turns auto reply back on from Inbox. During testing, also confirm that visitors can:
  • upload a JPEG, PNG, WebP, or GIF up to 10 MB and receive a relevant answer
  • start a browser voice call after granting microphone access
  • complete a booking request if you use native scheduling
Voice calls happen inside WebChat; BoundBot does not provide or route a telephone number. See WebChat voice for call behavior, credits, grounding, and troubleshooting.

​
Use authenticated visitors

Choose Authenticated visitors when the bot must answer private account or order questions. You configure a trusted issuer and generate a signing secret, then your website server creates short-lived identity tokens for logged-in customers. Use the script embed for this mode. Never create identity tokens in browser JavaScript or expose the signing secret. The developer guide includes the claims, server example, login callback, and order-ownership checks.

​
Embed on your site

When you are ready to install, use the embed guide in Embed WebChat. If your site runs on WordPress, you can also use the WordPress plugin.
When your production domains are known and stable, add them to Allowed origins early so only those sites can embed the widget. Until then, leaving the field empty keeps local and staging tests working without origin errors.

Embed WebChat

Install the widget on your site with the iframe or script pattern.

WebChat voice

Let visitors talk to the bot from their browser and keep transcripts in Inbox.

Playground

Test the live WebChat pipeline before you publish it.

Quickstart

Follow the fastest setup path from onboarding to a working website chat.

Website sources

Keep the bot aligned with your site content before you send production traffic.