Skip to main content

Website Widget

Put your ReadyChatAI assistant on your own website​

Path: AI Configuration > Configure > Website Widget

If the Website Widget tab is available for your account, use it to style the chat window, limit where it can run, and copy the installation code. The page has three tabs: Settings, Installation, and API Key.

Settings​

The desktop view includes a live preview. It reflects saved settings and warns when the form contains changes you have not saved yet.

Appearance​

  • Theme Color accepts a hexadecimal colour such as #0084ff.
  • Header Text is required and can contain up to 100 characters.
  • Logo accepts PNG, JPG, WebP, or SVG files up to 2 MB.
  • Position places the launcher in the top-left, top-right, bottom-left, or bottom-right corner.

Behaviour​

  • Auto Open opens the widget when a visitor loads the page.
  • Collect Visitor Email asks for an email before the conversation starts. It is not a hard gate: visitors can click Skip instead of Continue, and the form does not ask again on that page. Like the conversation itself, it reappears after a refresh or a click to another page.
  • Greeting Message controls the message visitors see when they open chat.

Press Save Changes after editing these settings.

Restrict the widget to your domains​

Allowed Domains controls which websites may initialize your widget. Add a hostname such as example.com, then press Enter, type a comma, or click Add.

  • Enter only a hostname, without a page path. A port is optional when needed.
  • A base hostname also permits its subdomains. For example, example.com permits shop.example.com.
  • Leaving the list empty allows the widget on any website.

For a live installation, add the domains you control before sharing the embed code. Remove a domain tag and save if that site should no longer load the widget.

Install it​

Open Installation and:

  1. Click Copy to copy the generated embed code.
  2. Open your website's HTML or the custom-code area in your site builder.
  3. Paste the code immediately before the closing </body> tag.
  4. Save and publish the website.
  5. Refresh the public page and check that the chat button appears.

Installation also links to step-by-step guides for common platforms — WordPress, Shopify, Wix, Squarespace, Webflow, GoDaddy Websites+Marketing, and Google Tag Manager — each pointing to the exact menu and box to paste the code into. A few platforms have their own requirements: WordPress.com needs a Business plan to add custom code, Wix and Squarespace require their own paid site plan before the custom-code option appears, Webflow needs a fresh publish after you save, GoDaddy's Websites+Marketing plans have no site-wide footer to paste into, and Shopify's checkout pages never load the widget because Shopify does not run theme code there.

If you cannot edit the site yourself, click Share with your web developer to copy a public link to that same guide. It needs no ReadyChatAI login and shows a placeholder key instead of your real one, so it is safe to hand to a developer or agency with no dashboard access. The real embed key is still visible to browsers once installed, so Allowed Domains is what actually prevents another website from using your configuration.

How visitor conversations work​

Every time a visitor's browser loads or reloads a page carrying the widget, it starts a brand-new anonymous conversation on purpose, so one browser can never inherit a stranger's chat history. Closing and reopening the chat bubble on the same page keeps the conversation, but a refresh, a link to another page on your site, or returning later all start over — earlier messages stay in your Messages inbox, just under a conversation the visitor can no longer reach. This means the same person browsing two pages on your site can appear as two separate conversations.

A visitor who never gives a name (or an email you can derive one from) appears in your Messages inbox as Website Visitor followed by a short id. If they give only an email, ReadyChatAI turns the part before the @ into a name — for example, maria.lopez@example.com becomes "Maria Lopez" — and falls back to Website Visitor if that fails.

Widget replies are billed the same as any other channel: they count against your plan's message allowance, unlike testing in the Playground, which does not. A visitor's message is capped at 2000 characters; a longer message is rejected with an error instead of being sent or split.

Enable or disable it​

The switch beside the tabs enables or disables the widget. Disabling it stops the current key from initializing the widget. You can keep the configuration in place and enable it again later.

Manage the API key​

The API Key tab masks the current key by default. Use Show only when you need to inspect it, or Copy when installing the widget.

Use Regenerate Key only when you intend to replace the current installation. Regeneration immediately invalidates the old key: every website using the old embed code stops working until you copy and publish the newly generated code.

Troubleshooting​

  • No chat button: confirm the widget is enabled, the site is published, and the embed code sits before </body>. If that all checks out, look for a caching plugin still serving the old page, a speed/optimization plugin delaying the script, Cloudflare Rocket Loader rewriting it, a Content-Security-Policy header blocking it, or an ad blocker hiding the launcher.
  • It works on one site but not another: check Allowed Domains for the failing site's hostname.
  • It stopped after key regeneration: replace the old embed code everywhere the widget is installed.
  • The preview differs from the site: save pending changes, then refresh the public page.

Test the assistant's answers separately in the Playground.