Summary
One HolderChat account can own many chatbots. Use separate bots for different brands, languages, departments, or websites. Each bot has its own API token, knowledge base, and widget embed code.
Prerequisites
- HolderChat account with at least one bot
When to create multiple bots
| Scenario | Recommendation |
|---|---|
| Different brands or domains | One bot per brand |
| Different languages with separate content | One bot per language, or one bot with language packs |
| Sales vs support content | Separate bots with focused knowledge |
| WordPress site + non-WP marketing site | Connector bot for WP; dashboard bot for other site |
Step-by-step: Create another bot
Dashboard path
- Go to Dashboard
- Click create new chatbot (same flow as first bot)
- Add knowledge sources specific to this bot
- Rebuild Bot until Active
- Use a unique Chatbot Name for easy identification
WordPress path
- Each WordPress site gets one bot via Create Chatbot in the Connector plugin
- Multiple WP sites = multiple bots (one provision per domain)
Organizing your bots
- Use clear names:
Acme Support,Acme Sales DE - Note the bot ID in
/edit-chat?id=for support tickets - Keep embed tokens separate — never reuse one token for two sites
Dashboard at scale
- Pagination shows 20 bots per page
- Filter mentally by status: fix Error bots first
- Delete unused bots to reduce clutter
What triggers a rebuild
Rebuilds are per bot. Changing bot A does not affect bot B.
Limitations
- Each bot consumes processing time on rebuild
- WordPress Connector: one ConnectedSite per domain
- Free beta may apply fair-use limits at launch (currently no hard cap advertised)
Troubleshooting
Symptom: Wrong bot answers on my website
Cause: Wrong embed token installed.
Fix: Open correct bot → Get Code → replace script on site.
Symptom: Two WordPress sites, one account
Cause: Each site provisions separately.
Fix: Install Connector on each site; use Link to HolderChat account on each.