Running chat bots for websites in the plural is a different problem from adding one bot to one site. Many firms with 10 to 250 staff have a main site, a second brand, a recruitment site and a handful of campaign landing pages, and each needs a bot that speaks for the right part of the business. This article answers how to run several bots without ending up with several inboxes, duplicated contacts and answers that contradict each other.
The problem with one bot per site, set up separately
The usual pattern is that each website gets its own chat tool, chosen by whoever built that site. After two years you have three vendors, three logins, three sets of contacts and no single view of who has spoken to you. A prospect who chats on your main site and then on your specialist brand's site appears as two strangers.
On the levelpartner.ai platform every widget and every agent reports into one account. Conversations land in one inbox, contacts are matched by email and phone, and you can still give each site its own agent with its own knowledge and tone.
Deciding how many agents you need
Not every website needs its own agent. Use this rule: one agent per distinct audience, not per domain.
- A second brand selling to a different buyer gets its own agent.
- A campaign landing page for an existing service shares the main agent.
- A recruitment site gets a small agent focused on roles and applications, or no bot at all.
- A client portal or membership area gets a support-focused agent with different hand-off rules.
Fewer agents means less to maintain. Two well-kept agents beat five neglected ones.
Before you start
- A list of every website and landing page you control, with its audience.
- Your decision on which sites share an agent and which get their own.
- A shared knowledge source for facts that are true across all brands, such as office locations.
- Access to add the widget code to each site.
- A routing plan: who in the team answers hand-offs from each site.
Get the main agent stable on your primary website before you build the second. Each further agent is its own bot, trained on that brand's pages and answers, with its own name, greeting and tone, while the shared facts sit in one knowledge base attached to every agent. For sites built elsewhere, copy the widget code into the site instead of using the Settings dropdown.
How to set it up
Repeat these steps for each site.
- Open Sites > Chat Widget and click + New.
- Choose the type of chat widget you want to create.
- Open Sites, then Websites or Funnels, and select the site.
- In the Settings tab, use the Chat Widget dropdown for that site.
- Go to AI Agents > Conversation AI and open the brand's bot.
- Select the Deploy tab and turn on Chat Widget.
- Open the Chat Widget channel's edit icon and turn on Assign channel.
- Select that site's widget and add tag conditions if needed.
- Click Update, save the bot and test the widget on the site.
What it replaces and the weekly effort
Consolidating replaces separate chat subscriptions, separate inboxes and the monthly job of exporting contacts from one tool to another. More importantly, it replaces the blind spot. When a prospect has spoken to two of your brands, the person who picks up the second conversation can see the first.
Plan on fifteen minutes per agent per week for transcript review. If that adds up to more time than you have, you have too many agents. Merge the ones with low volume.
Imagine a group with a main consulting site, a separate training brand and a recruitment site. One sensible split is two agents, one for consulting and one for training, both drawing on a shared facts document, plus a widget with no AI agent on the recruitment site that routes messages straight to HR. If weekly review takes about 35 minutes in total, and moving contacts between three old tools used to take roughly two hours, the group would get back about 85 minutes a week.
Attaching the main agent's full knowledge to the second brand's bot is the commonest error. The training brand's bot then offers consulting calls, and visitors get confused about who they are dealing with. Give each brand its own knowledge base and share only the common facts.
When not to split into several bots
If your second site sells the same service to the same buyer under a different name, one agent with a brand-aware instruction is enough. Splitting only makes sense when the questions, the answers and the people who follow up are genuinely different.
Troubleshooting
The same person appears twice in the CRM. They gave an email on one site and only a phone number on another. Ask for both early in each conversation so contacts merge.
Shared facts drift apart. Someone edited the facts on one agent rather than in the shared document. Keep shared facts in one source and edit only there.
Hand-offs from the second site go unanswered. Routing still points at the main sales team. Update the user in that bot's Human Handover action and check notifications.
Reporting mixes all sites together. Tag contacts by site, for example with a workflow that runs when a contact replies through a given widget, then filter on that tag.
Frequently asked questions
Do I need a separate licence for each website?
No. One licence covers every feature with unlimited users and contacts, so you can run widgets on as many of your own sites as you need. Usage such as AI replies is billed as used.
Can different bots share one calendar?
Yes, if the same people take the first calls. Give each brand its own calendar when different staff handle them, so bookings reach the right diary. The AI appointment setter guide covers booking rules.
How do I keep tone consistent across brands?
Write a short tone section for each agent with two example replies. Shared facts stay in one document; tone stays per brand. See the GPT-style chat bot guide for instruction writing.
Where should I start if I only have one site today?
Start with setting up a chat bot for your website, then add page-level greetings with the chat bot site guide. Add a second agent only when a second audience appears.