# How to run live chat on multiple websites from one dashboard

> Run live chat on several websites from one account: when to split sites, how to set each one up, one inbox for all of them, and routing each site to the right people.

Source: https://pengo.chat/blog/live-chat-for-multiple-websites/
Topic: Playbooks
Updated: 2026-10-21

## The short version

- One live chat account can cover **several websites**. Each site gets its own snippet, widget, AI knowledge and settings, while your **team, inbox and billing stay shared**.
- Add a separate website when two sites need a **different look, different answers or separate reporting**. One site on two addresses, such as example.com and shop.example.com, can share one snippet.
- Every chat lands in **one inbox**. Choose All websites to see everything with a website badge on each conversation, or pick one site to focus on it.
- Give each site **its own widget and its own Pengo Intelligence knowledge**, then copy the parts you want to reuse to your other websites.
- Use **website access** so each teammate sees and gets notified about only the sites they work on, and read **analytics per website** to see how each one is doing.

If you run more than one website, you've probably wondered whether each one needs its own chat tool. A second store, a brand for a new market, a product site next to the main one, a handful of client sites, a side project that started getting traffic. Each new site seems to bring another account, another login and another inbox to watch.

It doesn't have to. One live chat account can cover all of them, with each site keeping its own look, its own answers and its own team, and every conversation arriving in one place. This guide shows how to set that up: when to split sites, how to add each one, how your team works across them, and how to keep each site's reporting separate. For the feature itself, see [live chat for multiple websites](/multiple-websites/).

## What "multiple websites in one account" means

> **Live chat for multiple websites**
>
Live chat for multiple websites means one account, or workspace, that runs a chat widget on several sites. Each site has its own snippet and settings, so it can look and answer differently, while one shared team answers every site's conversations from a single inbox.

It helps to separate the two layers. Some things belong to each **website**. Others belong to the **workspace** that holds them all.

| Belongs to each website | Shared across the workspace |
|---|---|
| Snippet and website ID | Your team |
| Widget look, home screen, forms, language and sounds | The inbox |
| Business hours and proactive triggers | Billing |
| Routing and response targets | The AI credits pool |
| Pengo Intelligence knowledge, behavior and actions | |
| Allowed domains, integrations and help center | |

That split is what makes one account work for several sites. Customers on each site see a chat that belongs there. Your team sees one queue.

## One site on two domains, or two separate websites?

Before you add anything, decide what counts as a separate website. The test is simple: **would the two sites need to differ?**

Add a separate website when the sites need:

- **A different look.** Different brands, colors, logos or welcome messages.
- **Different answers.** A wholesale site and a retail store have different prices, terms and policies. A UK site and a US site have different delivery times. If the AI should answer differently, they're separate websites.
- **Separate reporting.** If you want to know how many chats each site gets, how fast you reply on each, or how much the AI resolves on each, keep them apart.

Use the same snippet on both when it's really one site on two addresses. Your main site at example.com and your store at shop.example.com usually share a brand, a policy page and a team. They can run one snippet, with one widget and one Pengo Intelligence setup.

When in doubt, split. Separate websites can always share setup, as you'll see below, but one website can't report on its two halves separately.

_Figure: The deciding question is whether the two sites need to differ. One site on two addresses runs one snippet with one look and one set of answers; a site that needs a different look, different answers or its own reporting becomes a separate website with its own snippet._

## Set up each website

Adding a website takes a few minutes. Repeat these steps for each site.

  ### Add the website with a name and URL
  Give it a name your team will recognize at a glance, such as the brand or store name, and enter the site's address. The name shows up across the dashboard and in notifications, so pick one that's short and clear.
  
  ### Let Pengo learn from the site
  Choose to learn from the site, and Pengo reads up to 25 pages in the background to train Pengo Intelligence on that site's content. A new website starts with no knowledge, so this gives the AI something accurate to answer from on day one. You can add or refine knowledge later.
  
  ### Install that website's own snippet
  Each website has its own snippet with its own website ID. Paste it on the matching site, or follow the install guide for your platform: HTML, WordPress, Shopify, Webflow, Wix, Squarespace, Framer, Ghost, Bubble, Next.js, React, Vue or Nuxt, and Google Tag Manager. WordPress sites can use the Pengo plugin.
  
  ### Check that it's live
  Install status shows whether each website's widget is live. Open the site in a private window, send a test chat and make sure it arrives in your inbox.
  

The one mistake to watch for here is pasting the wrong snippet on the wrong site. The website ID in the snippet tells Pengo which website a chat belongs to, so a mix-up sends one brand's chats to another brand's settings. Copy each snippet straight from the website it belongs to. The [install guides](/help/install/) cover each platform step by step.

## One inbox for every site

Once two or more websites are live, the website switcher in the dashboard header becomes your main tool. Open it and choose:

- **All websites** to see everything at once. Each conversation shows a **website badge**, so you always know which site a customer is on before you reply.
- **A single website** to focus on it. The inbox, live visitors, analytics and Intelligence all follow your choice.

Most teams leave the switcher on All websites while answering chats and switch to one site when they're working on it, such as reviewing its AI answers or checking who's browsing its pricing page right now.

_Figure: Three websites, three widgets in three colors, one inbox. On All websites, every conversation carries a website badge, so the team knows which site a customer is on before replying._

This is where one account pays off. There's no tab per site and no second inbox someone forgets to check. A customer from your wholesale site and a customer from your retail store sit in the same queue, each clearly labeled, and your [shared inbox](/inbox/) handles them the same way: assignment, routing and response targets.

## Give each site its own widget and AI

Visitors should feel like the chat belongs to the site they're on. Because each website has its own settings, every part of the experience can match:

- **Look and home screen.** Colors and the home screen visitors see first. See what you can change on the [chat widget](/widget/).
- **Language.** A site for German customers can greet them in German.
- **Forms.** Ask for an order number on the store and a company name on the wholesale site.
- **Sounds and business hours.** A US site and an EU site keep different hours, and each site's away message can say when the team is back.
- **Proactive triggers.** Greet visitors on one site's pricing page without touching the others.
- **Integrations.** Connect email, SMS, Slack, Shopify, Stripe, HubSpot, booking and webhooks per website, so each store's Shopify data shows on that store's chats.
- **Help center.** Each website can have its own help center with its own articles.

### Separate knowledge for separate answers

The most important per-site setting is **Pengo Intelligence**. Each website has its own knowledge, behavior and actions. The AI on your retail store answers from the retail store's content, and the AI on your wholesale site answers from the wholesale terms. A visitor on one site never gets the other site's prices or return policy.

That's also why a new website starts with no knowledge. Learning from the site when you add it fills the gap, and you can add help articles, files and Q&A from there. Read more about how [Pengo Intelligence](/ai/) answers from your own content.

### Reuse what should be the same

Separate doesn't mean starting from scratch every time. Two shortcuts save most of the work:

- **Also apply to all websites.** When you save a setting for one website, you can apply it to every website at once. Useful for shared things like sounds or a standard form.
- **Copy setup to other websites.** Copy a website's Intelligence setup and knowledge items to your other sites. Set up tone, behavior and your shared policies once, then adjust what's different.

A sensible pattern for several brands: build the first website completely, including its widget, forms, hours and Intelligence setup. Copy the Intelligence setup and the knowledge that's genuinely shared to the next website, then learn from the new site for everything specific to it.

## Route the right people to the right site

With one inbox, the next question is who sees what. A teammate who only works on one brand shouldn't be pinged about all five.

Each teammate has **website access**:

- **All websites**, which includes current websites and any you add later. Good for owners, leads and anyone covering every site.
- **Specific websites**, for people who work on one brand, one region or one client.

Teammates are only notified about websites they can access, and each notification’s title names the website: **New chat:** and then the site’s name. Someone covering two sites knows which one is calling before they open the app.

_Figure: Website access decides who hears about what. Hannah has all websites, so a site added later is covered automatically; Owen and Maya have specific websites. A chat on Ashby Dental notifies Hannah and Maya, with the website name in the title, and leaves Owen alone._

Within each website, set **routing** to decide who gets its chats, and **response targets** to set how fast replies should come. A busy store can have tighter targets than a quiet product site.

If you're an agency running chat for clients, this is how you keep each client's site separate inside one workspace. Give each client its own website and give each teammate access to the clients they handle. Our page for [agencies](/agencies/) covers this setup in more detail.

## Keep AI credits fair across sites

AI credits are **one shared pool** for the workspace, so every website draws from the same balance. That keeps things simple: there's nothing to split up front, and a quiet site doesn't leave credits sitting unused.

If one site is far busier than the rest, the workspace owner can **cap a single website's monthly AI credits**. The cap keeps one site from using more than its share, so the AI keeps answering on every other site.

## Keep each site's snippet on its own domains

By default, a snippet loads wherever it's pasted. To make sure each website's widget runs only where it should, turn on **allowed domains** for that website and list its domains.

Each entry matches **one exact domain**. example.com doesn't cover www.example.com or shop.example.com, so add each address the site uses, including staging domains. This also protects you from a copied snippet sending someone else's chats into your inbox. The [domains and multiple websites guide](/help/install/domains-and-multiple-websites/) has the full steps.

## See how each site is doing

Analytics follow the website switcher too. Choose **All websites** for the full picture: total chats, response times and how much the AI resolves across everything you run. Choose **one website** to see that site on its own.

Comparing sites side by side tells you a lot. One site might get twice the chats of another with the same traffic, which usually points to a confusing page or a missing answer. One site's AI might resolve fewer chats than the rest, which usually means its knowledge needs filling in. Per-site reporting turns "chat is busy" into "this site needs attention".

## Your multi-site setup checklist

**Running live chat on several websites**

- [ ] List every site you run, including subdomains and staging domains
- [ ] Decide which are separate websites and which share a snippet
- [ ] Add each website with a clear name and its URL
- [ ] Let Pengo learn from each site, or add its knowledge yourself
- [ ] Paste each website’s own snippet on the matching site
- [ ] Check install status shows every widget as live, then send a test chat from each site
- [ ] Set each site’s look, language, forms, business hours and triggers
- [ ] Copy shared Intelligence setup and knowledge to your other websites
- [ ] Give each teammate website access to the sites they work on
- [ ] Set routing and response targets for each website
- [ ] Turn on allowed domains for each website and add every domain it uses
- [ ] Review analytics for each site after the first week

Running chat on several websites comes down to one decision per site, whether it's separate or shared, and then the same short setup each time. After that, your team works from one inbox, each site keeps its own voice and its own answers, and you can see exactly how each one is doing. When you're ready to add your sites, start with [live chat for multiple websites](/multiple-websites/).

## Questions people ask

### Can I use one live chat tool for multiple websites?

Yes. In Pengo, one workspace holds all of your websites. Each website has its own snippet, widget, Pengo Intelligence knowledge and settings, and all of their conversations arrive in one shared inbox your whole team works from. See [live chat for multiple websites](/multiple-websites/).

### Should I add a second website or use the same snippet on both domains?

Use the same snippet when it's really one site on two addresses, such as example.com and shop.example.com, and both should look and answer the same. Add a separate website when the sites need a different look, different answers or their own reporting.

### Can each website have its own AI knowledge?

Yes. Each website has its own Pengo Intelligence setup: its knowledge, behavior and actions. A new website starts with no knowledge, so the AI answers each site's visitors only from that site's content. You can have Pengo learn from up to 25 pages of the site when you add it, and copy setup to your other websites when they should share it.

### Can I limit which teammates see which websites?

Yes. Each teammate's website access is either all websites, including ones you add later, or specific websites. Teammates are only notified about websites they can access, and each notification’s title includes the website name.

### How do AI credits work across several websites?

AI credits are one shared pool for the whole workspace, so every website draws from the same balance. The workspace owner can cap a single website's monthly AI credits to keep one busy site from using more than its share.

### How do I stop someone else using my chat snippet on their site?

Turn on allowed domains for that website and list every domain it runs on. Each entry is one exact domain, so add www, shop and staging domains separately. The widget then loads only on those domains. Our [domains and multiple websites guide](/help/install/domains-and-multiple-websites/) has the steps.
