Deployment

Make your chatbot available to users.

Deploying Your Chatbot

Go to "Settings" > "Deployment"
Click "Deploy"
Wait for the deployment to complete
Copy your chatbot URL

Deployment URL

After deployment, your chatbot is accessible at:

https://your-chatbot-name.wizchat.app

Or with a custom subdomain:

https://support.wizchat.app

Embedding on Your Website

Script Embed

Add this script to your website's HTML:

<script>
  window.chatbotConfig = { chatbotId: "YOUR_CHATBOT_ID" };
</script>
<script src="https://your-chatbot.wizchat.app/embed.js" async></script>

iFrame Embed

Embed as an iframe:

<iframe
  src="https://your-chatbot.wizchat.app"
  width="400"
  height="600"
  frameborder="0"
></iframe>

By default the script embed shows the chatbot as a corner bubble that opens a floating panel. You can instead dock it as a full-height right rail that pushes your page content aside when it opens — a more integrated look for documentation sites and apps. Opt in with displayMode: "sidebar":

<script>
  window.chatbotConfig = {
    chatbotId: "YOUR_CHATBOT_ID",
    displayMode: "sidebar",      // "bubble" (default) or "sidebar"
    reflowTarget: "#content",    // optional: CSS selector of the element to
                                 // push aside; omit to auto-detect
    showLauncher: false          // optional: hide the corner launcher bubble
  };
</script>
<script src="https://your-chatbot.wizchat.app/embed.js" async></script>

Options for sidebar mode:

Option	Default	Description
`displayMode`	`"bubble"`	Set to `"sidebar"` for the docked right rail. Any other value falls back to the bubble.
`reflowTarget`	auto-detect	CSS selector of the element whose right margin is pushed to make room for the rail. When omitted, WizChat targets the Docusaurus root (`#__docusaurus`) if present, otherwise `<body>`.
`showLauncher`	`true`	Set to `false` to drop the corner launcher bubble and open the rail only from your own triggers (see below).
`width`	`400`	Rail width in pixels.

Opening the rail from your own UI. Add the attribute data-wizchat-open to any element on your page (for example a navbar "Ask AI" button) and clicking it toggles the widget. In sidebar mode, visitors can also toggle it with Ctrl/Cmd + /.

<button data-wizchat-open>Ask AI</button>

Mobile

On narrow screens the sidebar falls back to a full-width overlay and does not reflow the page.

Native (in-page) render mode

By default the script embed renders the chat UI inside an iframe. You can instead render the chat panel directly in your page — inside a Shadow DOM, so it stays CSS-isolated from your site — by setting renderMode: "native":

<script>
  window.chatbotConfig = {
    chatbotId: "YOUR_CHATBOT_ID",
    renderMode: "native"        // "iframe" (default) or "native"
  };
</script>
<script src="https://your-chatbot.wizchat.app/embed.js" async></script>

In native mode the panel streams answers from the chatbot's public /api/chat-stream endpoint over Server-Sent Events — there is no iframe and no secret key in the browser (it calls the same CORS- and domain-gated public endpoint the widget already uses, gated by your allowed embedding domains). Model output is rendered through a small escape-first Markdown renderer that allows only a fixed subset — code, bold/italic, headings, lists, and http(s) links — so untrusted answer text can't inject HTML into your page.

renderMode is independent of displayMode: use native rendering with the default "bubble" corner popup or with the "sidebar" docked rail.

Option	Default	Description
`renderMode`	`"iframe"`	Set to `"native"` to draw the chat panel in the host page (Shadow DOM, no iframe). Any other value falls back to the iframe.

note

Native mode is additive — existing iframe embeds are unchanged unless you explicitly set renderMode: "native".

Custom Domains

For Business and Enterprise plans:

Go to "Settings" > "Domain"
Click "Add Custom Domain"
Enter your domain (e.g., chat.yourcompany.com)
Add the provided DNS records to your domain
Click "Verify"

Only matters for login-gated chatbots

If your chatbot is fully public (no login), the embed snippet above works on any site — skip this section. This applies when your chatbot requires login, or has features that unlock after a user signs in (for example an in-widget account assistant / copilot).

A web browser treats an embedded chat bubble as a small window into another website (an iframe). For privacy, browsers partition the login storage of a site shown inside a different site — so when a user signs in inside the widget, the browser drops that login and the chatbot behaves as if logged out. Anonymous chat still works; only the logged-in experience breaks.

The fix: serve the chatbot on a subdomain of the page that embeds it

Put the chatbot on a subdomain of the same site you embed it on, using Custom Domains. Because the chatbot and the host page are then the same site, the browser no longer partitions the login — signing in inside the widget persists, and logged-in features work.

Page hosting the widget	Give the chatbot this domain	Same site?	In-widget login
`www.yourcompany.com`	`copilot.yourcompany.com`	✅ yes	✅ works
`www.yourcompany.com`	`yourbot.wizchat.app`	❌ no (different site)	❌ won't persist

Setup (≈3 steps):

Custom Domain → add a subdomain of your site, e.g. copilot.yourcompany.com (add the CNAME at your DNS provider; WizChat issues the TLS certificate).

Embed on yourcompany.com using the standard snippet, pointed at that subdomain:

<script>
  window.chatbotConfig = { chatbotId: "YOUR_CHATBOT_ID" };
</script>
<script src="https://copilot.yourcompany.com/embed.js" async></script>

Open the page, sign in inside the widget — the login now sticks.

The chatbot, its knowledge base, and all settings are unchanged — only the domain it's served from. (Email/password sign-in needs no extra configuration; if you use Google/SSO sign-in, also add the subdomain to Firebase Auth's authorized domains and any identity-provider redirect allowlist you manage.)

Embedding on a site that is NOT yours

The same-site approach covers embedding a login-gated widget on your own site (on a subdomain of it). Embedding a logged-in widget on a third party's domain that can't share a subdomain with the chatbot isn't supported yet — contact support@wizchat.com if you need that (it's on the roadmap).

Redeployment

Redeploy when you make changes to:

Knowledge base content
AI settings
Appearance settings

To redeploy:

Go to the chatbot Edit page
Save your changes — a redeployment banner will appear when needed
Click the "Redeploy" button on the banner and confirm

note

Some changes take effect immediately without redeployment. Check the specific setting's documentation.

Deployment Status

Status	Description
Not Deployed	Chatbot has never been deployed
Deploying	Deployment in progress
Deployed	Live and accessible
Failed	Deployment failed (check errors)

Troubleshooting

Deployment Failed

Common causes:

Missing required settings
Invalid custom domain configuration
Temporary service issue

Solution: Check error messages and retry.

Changes Not Appearing

Solution: Clear browser cache or use incognito mode to test.

Deploying Your Chatbot​

Deployment URL​

Embedding on Your Website​

Script Embed​

iFrame Embed​

Docked sidebar mode​

Native (in-page) render mode​

Custom Domains​

Embedding a chatbot that requires login​

The fix: serve the chatbot on a subdomain of the page that embeds it​

Redeployment​

Deployment Status​

Troubleshooting​

Deployment Failed​

Changes Not Appearing​

Related​