Sales Bob

Docs

Embed troubleshooting

1. Widget not appearing

The snippet you paste on your site is one line:

<script src="https://sales.ceobob.com/widget.js?slug=YOUR-AGENT-SLUG" async></script>

If no chat bubble shows up, there are two common causes.

Cause A: your site sends Cross-Origin-Embedder-Policy: require-corp

This header blocks third-party embeds. The browser console shows ERR_BLOCKED_BY_RESPONSE.NotSameOriginAfterDefaultedToSameOriginByCoep. Remove this response header from your site:

Cross-Origin-Embedder-Policy: require-corp

If you must keep it, use credentialless instead of require-corp. The Sales Bob script, chat page, and its assets already send the matching opt-in headers, so credentialless works.

Cause B: your Content-Security-Policy excludes sales.ceobob.com

Add these entries to your policy. Both are required: the first lets the script load, the second lets the chat window open inside it.

script-src https://sales.ceobob.com;
frame-src https://sales.ceobob.com;

Append them to your existing directives rather than replacing them. If your policy uses default-src only, add both directives explicitly.

2. Reading the [Sales Bob] warning

When the widget cannot load, it writes one warning to the browser console naming the cause. To read it:

  • Chrome or Edge: press F12, or Cmd + Option + J on macOS, then open the Console tab.
  • Firefox: press F12, or Cmd + Option + K on macOS.
  • Safari: enable Develop in Settings, Advanced, then press Cmd + Option + C.

Reload the page with the console open and look for a line starting with [Sales Bob]. A Cross-Origin-Embedder-Policy message points to Cause A above; a Content-Security-Policy message names the exact directive to fix.

3. Support

Still stuck? Send the console warning and the URL of the page you embedded on to Master22Solutions via master22solutions.com.