AI Chatbot Website Setup for Owners With Several Sites: One Team, Many Brands, No Mix-Ups
AI chatbot website setup gets trickier when you run more than one site: a shop and a blog, two brands, a business in two cities, or client sites as an agency. Each needs its own answers, look and voice, but your team shouldn’t need five inboxes. This guide shows how to organise chat across several websites so customers get the right answers and nobody mixes them up.
โก In short
- Give each website its own knowledge, welcome line, branding and hours; share the team and habits.
- Label every conversation clearly by site so replies match the right brand and policies.
- Keep one master knowledge document per site, plus a shared one for common facts.
- Count visitors and AI usage per site; limits and packs usually apply per website.

Common situations
Why owners end up with several sites
Running several websites is more common than it sounds. A bakery has a main site and a separate wedding-cakes site. A coaching institute has a site per city. A retailer runs two brands aimed at different customers. An agency manages chat for several clients. A founder has a business site and a personal consulting site.
In each case, the same small team often answers chats for all of them. That’s efficient, but it creates risks: quoting the wrong brand’s prices, greeting a wedding-cake customer with the everyday bakery’s offer, or using a casual tone on a formal brand’s site. The goal of a good multi-site AI chatbot website setup is to keep what should be shared (the team, habits and tools) and separate what must be separate (facts, voice and promises).
The rest of this guide walks through the decisions, in the order that avoids the most mistakes.
Shared vs separate
What each website gets on its own, and what they share
| Item | Separate per site | Shared across sites |
|---|---|---|
| Knowledge and saved replies | โ Prices, policies, products differ | Common facts (e.g. company address) can be copied |
| Welcome line and Flows | โ Each site’s top questions | โ |
| Branding and tone | โ Colours, avatar, voice | โ |
| Opening hours | โ If teams or cities differ | If the same team covers all |
| Team and inbox | โ | โ One team, labelled conversations |
| Habits and reviews | Numbers per site | โ One weekly routine covering all |
| Visitor and AI allowances | โ Usually counted per website | โ |
Step 1 ยท Separate knowledge
Each site answers from its own facts
The biggest risk in a multi-site setup is a bot on one site quoting another site’s facts. Prevent it by keeping knowledge strictly per site.
One master document per site
Write a knowledge document for each website: products or services, prices, delivery or service areas, hours, policies and boundaries. Keep a short shared document for facts that are genuinely common, such as your company’s legal name or head office, and copy those into each site’s knowledge.
Name things clearly
In your chat tool, each website is set up separately with its own knowledge and saved replies. Name saved replies with a site prefix if they’re visible across sites, for example “CAKES ยท notice period” and “SHOP ยท delivery”, so the team never picks the wrong one.
Watch for near-duplicates
Two brands with similar products but different prices are the classic trap. Put a line at the top of each site’s knowledge: “This assistant serves [brand] only. Prices and policies here apply only to [brand].” Then test by asking each bot about the other brand’s products. See the knowledge audit guide for preparing each site’s facts.
Step 2 ยท Separate voice and look
Each brand sounds and looks like itself
Branding per site
Set each widget’s colour, avatar, team name and welcome line to match its own website. A luxury brand and a budget brand should feel different in chat, just as their websites do. The branding guide covers colours, avatars and contrast.
Tone per site
Write a short tone note for each brand, three words and a couple of examples, and use it in each bot’s instructions. Formal brands get formal wording; friendly local brands get warmth. See writing bot instructions.
Welcome lines and Flows per site
Each site’s welcome line should name that site’s top questions. Flows should be set per site, on that site’s key pages. A Flow that makes sense for a shop’s cart page means nothing on a consulting site.
Step 3 ยท One team, clear labels
Answering many sites without mix-ups
Your team can answer chats from all your websites in one place, which is efficient. The key is making it obvious which site each conversation came from.
Check the site before replying
Train everyone to glance at the website label on each conversation before typing. It takes a second and prevents the most embarrassing mistakes, such as quoting one brand’s prices to another brand’s customer.
Site-specific saved replies
Use the site prefixes from Step 1 so team members pick the right answer quickly.
Roles by site, if needed
If different people know different brands, assign conversations accordingly. A specialist for the wedding-cakes site, a generalist for the everyday shop.
Shared phone alerts
With the Android app, alerts from all your sites arrive on the same phones. If that gets noisy, decide who receives alerts for which site.
Step 4 ยท Hours and handover
Honest timing for each site
Same team, same hours
If one team covers all sites at the same times, opening hours can match across sites.
Different teams or cities
If a site serves another city, region or time zone, or is answered by a different person, set its hours separately, with its own away message.
Handover rules per site
Sensitive topics may differ: a clinic site needs strict medical handover rules; a gift shop doesn’t. Write each site’s limits into its own instructions. Our customer service rulebook helps sort topics.
Specific to the brand, the team and the hours.
Step 5 ยท Numbers and limits per site
Count each site separately
Each website has its own traffic, questions and value, so measure them separately. In your weekly or monthly numbers, record per site: chats started, answered without a person, visitors who left after one reply, and leads collected. You may find one site’s bot works well while another needs better answers.
Allowances and costs
On LiveChatBot, limits apply per website: each website gets 100 free visitors a month and its own small monthly allowance of AI replies, and packs are bought for a specific website and never expire. An account includes two free websites; each extra website is โน199 for six months. For a busy site and a quiet one, you might buy packs only for the busy one. Details are on the pricing page.
When to merge sites
If two sites share almost everything, the same products, prices and team, consider whether they need to be separate at all. Fewer sites mean less upkeep.
Common mix-ups
Five mistakes multi-site owners make, and the fixes
These mistakes come up again and again when one team runs chat across several sites. Each has a simple fix.
Copy-pasting the first site’s knowledge
The quickest way to launch a second site is to copy everything, and the quickest way to quote the wrong prices. Copy the structure, then rewrite the facts.
One welcome line everywhere
“Hi! Ask us about delivery” makes no sense on a consulting site. Write a welcome line for each site’s real top questions.
Generic team names
If every widget says “Support”, customers on a premium brand’s site get the same feel as a budget brand’s. Name the team per brand.
Forgetting seasonal content on one site
You updated the shop for Diwali but not the wedding-cakes site, or the other way round. Use one monthly checklist that covers every site.
Measuring only the total
Combined numbers hide a struggling site behind a successful one. Record numbers per site so each AI chatbot website gets the attention it needs.
Catching these early takes a quick cross-site test each month: open each site on your phone, ask two common questions, and ask one question about another brand. If every answer is correct and in the right voice, you’re in good shape.
Agencies
Managing chat for client websites
Extra rules when the websites aren’t yours.
Accounts in the client’s name
Set up chat under the client’s account and email; you get team access. They keep ownership if you part ways.
Clear responsibility
Agree who answers chats, who updates knowledge, and who reviews conversations.
Client approval of answers
Have the client sign off key facts and boundaries before launch.
Monthly report
Chats, handled by bot, leads, top new questions, fixes made.
Data handling
Explain where conversations are stored and who can see them; follow the client’s privacy policy.
Offboarding plan
Document everything so the client can take over smoothly.
More on working with clients: AI chatbot services, hire or DIY.
Checklist
Multi-site setup
Tick each for every website you run.
Getting started
Add your second site the right way
If you’re adding a second AI chatbot website to an existing chat setup, resist copying everything from the first. Copy the structure, not the facts: the same sections in the knowledge document, the same habits, the same review routine, but with new content written for the new site. Then run the cross-brand test before launch.
LiveChatBot’s free plan includes two websites per account, each with its own widget, knowledge, saved replies, Flows, hours and allowances, answered by one shared team with the Android app. Start on livechatbot.in, and when your AI chatbot website setup grows beyond two, extra websites are available from the pricing page.
Frequently asked questions
Can one team answer chats for several websites?
Yes. One account can hold several websites, with conversations labelled by site so your team can answer all of them from one place.
How do I stop the bot mixing up brands?
Keep separate knowledge per site, add a line in each bot’s instructions limiting it to that brand, and test by asking about the other brand’s products.
Do limits apply per website?
On LiveChatBot, yes: each website gets its own monthly visitor and AI reply allowances, and packs are bought per website.
How many websites are free?
Two per account. Each extra website is โน199 for six months.
Should agencies set up chat in their own account?
No. Set it up in the client’s account and request team access, so the client keeps ownership.
Keep reading
Related guides
AI Chatbot Tools Beyond the Bot: 12 Free Helpers That Make Your Website Chat Work Better
AI Chatbot Solutions Mapped to Real Problems: 12 Business Headaches and the Fix for Each (Including When It Isn’t a Bot)
AI Chatbot Software Maintenance Calendar: What to Check Daily, Weekly, Monthly and Yearly
Set up your second site the right way
Separate facts, shared team, one routine. Start free on livechatbot.in.