The Assistant doesn't appear or doesn't answer

Most of the time, an Assistant that works in Preview but not on your site is missing one of two things: the In Deployment switch, or the site's domain in its Origin Domains. Preview checks neither, which is why it keeps working.

The Embedded Assistant's button doesn't appear

Open the browser's developer console on the page. The tag writes one line when it shows nothing:

Console line

Cause

Fix

[WebWorks Assistant] not shown: config returned 403

The Assistant isn't in deployment, or the page's domain isn't one of its Origin Domains. In the browser's network tools, the response to the config request says which: This assistant is not available. or Origin not allowed.

Turn the switch on (Put an Assistant in deployment), or add the domain (Set an Assistant's Origin Domains).

[WebWorks Assistant] not shown: config returned 404

No Assistant has the ID in the tag: it was deleted, or the tag was changed.

Copy the tag again from the Install tab.

[WebWorks Assistant] not shown: config could not be loaded

The request didn't complete: the network, a browser extension or the site's own security policy stopped it.

Allow requests to https://platform.webworks.com from your pages.

No line at all

The tag isn't on this page, or it lost its data-assistant attribute.

Check the page's source for the tag.

A page on localhost or a private address can't be an Origin Domain, so the button never appears there. Test in Preview instead.

The button appears but the panel doesn't open

The console shows [WebWorks Assistant] panel could not be loaded: the panel's script, which loads from https://platform.webworks.com when a visitor first clicks, was blocked. Allow scripts from https://platform.webworks.com on your pages.

The AI Assistant is missing from Reverb 2.0 help

Cause

Fix

Generate Assistant wasn't enabled in the target you published.

Enable it in the target's AI Features settings, then generate and publish again.

The help is open from a file, and Hide AI Tab when file local is enabled.

Open the help from the web server that serves it.

The Reverb Assistant doesn't answer

Cause

Fix

The Assistant isn't in deployment.

Put an Assistant in deployment.

The domain serving the help isn't one of its Origin Domains.

Set an Assistant's Origin Domains.

The target's Assistant ID doesn't match the Assistant, for example after the Assistant was deleted and recreated.

Copy the ID from the Install tab, paste it into the target, and generate again. See Connect the Reverb Assistant to Reverb 2.0 help.

The help is open from a file.

Open it from the web server.

It answers in Preview but not on your site

Preview doesn't check deployment or Origin Domains. Check both, and click Save Changes if the header still shows it: an unsaved Origin Domain isn't in effect.

Visitors get a message instead of an answer

The Assistant is running but refused the question, for a reason such as its daily budget or a visitor's message limit. See Messages visitors see.

Last modified date: 11/02/2026