> ## Knowledge Base Index
> Fetch the complete knowledge base index at: https://help.chrisp.chat/sitemap.xml
> Use this file to discover available pages before exploring further.
> Pure-Markdown content can be obtained by appending a '.md' suffix to the content URLs listed in the sitemap (without the trailing slash).

# How to split incoming conversations into multiple workspaces

__Use multiple Website IDs only when you need truly separate chatboxes on different parts of your site.__

If your goal is simply to separate teams inside one workspace, sub-inboxes are usually the better option. This guide covers the more advanced setup: showing different Crisp chatboxes on different website sections by loading a different Website ID depending on the current page.

|| Before using this approach, consider [sub-inboxes](https://help.crisp.chat/en/article/how-can-i-create-sub-inboxes-in-my-crisp-workspace-ke3xk7/) first. They are usually simpler to manage when you only need department separation.

---

# When this setup makes sense

This approach is useful when different parts of your site should truly belong to different Crisp workspaces or different website IDs.

__Typical examples include:__

* One chatbox for sales pages and another for support pages
* Separate chatboxes per product line or business unit
* Different chatboxes across subdomains or distinct website sections

Because each Website ID is independent, this gives a harder separation than routing or sub-inboxes.

---

# How the setup works

__At a high level, you will:__

* Create one Crisp workspace or Website ID per support area
* Invite the appropriate team members to each workspace
* Load the matching `` `CRISP_WEBSITE_ID` `` depending on the current URL path

That means the chatbox displayed on `` `/pricing` `` can be different from the chatbox displayed on `` `/support` `` or `` `/contact` ``.

---

# Example implementation

In your website JavaScript, you can choose the Website ID dynamically based on the current path:

```
<script type="text/javascript">  const WEBSITE_IDS = {    pricing: "SALES_WEBSITE_ID",    solutions: "PRODUCT_WEBSITE_ID",    issue: "REPAIRS_WEBSITE_ID",    contact: "SUPPORT_WEBSITE_ID",    default: "DEFAULT_WEBSITE_ID"  };  var path = window.location.pathname;  path = path.replace(/\//g, "");  window.CRISP_WEBSITE_ID = (WEBSITE_IDS[path] || WEBSITE_IDS.default);  window.$crisp = [];  (function() {    d = document;    s = d.createElement("script");    s.src = "https://client.crisp.chat/l.js";    s.async = 1;    d.getElementsByTagName("head")[0].appendChild(s);  })();</script>
```

__Example behavior:__

* [`` `https://acme.com/pricing` ``](https://acme.com/pricing) can load the sales chatbox
* [`` `https://acme.com/solutions` ``](https://acme.com/solutions) can load the product chatbox
* [`` `https://acme.com/contact` ``](https://acme.com/contact) can load the support chatbox
* Any other page can fall back to the default chatbox

---

# Choose between this and sub-inboxes

Use this Website ID approach only when you really need separate chatbox identities or separate workspaces.

Use sub-inboxes when you want one shared workspace with internal separation for teams, routing, or visibility.

Read the dedicated guide: [How can I create sub-inboxes in my Crisp Workspace?](https://help.crisp.chat/en/article/how-can-i-create-sub-inboxes-in-my-crisp-workspace-ke3xk7/)