> For the complete documentation index, see [llms.txt](https://docs.rapidbott.com/help-center/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.rapidbott.com/help-center/common-error-log-database/common-errors/webchat-omnichannel-errors.md).

# Webchat/Omnichannel Errors

### **Error: The web chat widget isn’t showing up** <a href="#error-the-web-chat-widget-isnt-showing-up" id="error-the-web-chat-widget-isnt-showing-up"></a>

The reason might be one of the two reasons below:

· You didn’t whitelist your website domain

· You didn’t install the script to your website or landing page properly.

You can find the “Whitelist Domain” setting as per screenshot below

<figure><img src="/files/GnUMuJB9q4rszw7xQJEm" alt=""><figcaption></figcaption></figure>

To verify the script you need to install on your website, you can inspect the webpage source code, and make sure the script is on the page.

### **Error: “Message not sent because outside 30 days”** <a href="#error-message-not-sent-because-outside-30-days" id="error-message-not-sent-because-outside-30-days"></a>

Web chat channels will use cookies to identify the user. These cookies have an expiration date of 30 days. After 30 days, if the user hasn't visited your website and refreshed the cookies, the cookie(user) will expire.

Any message you are trying to web chat will not be able to be delivered to the user. And you will see this error in your error logs.

If you have requested the user to use SSO to login in the web chat, and connect the same web chat user with other social channels, you might still reach out to the user who is out of the 30 days window.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.rapidbott.com/help-center/common-error-log-database/common-errors/webchat-omnichannel-errors.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.