In short: Start with one knowledge base. Split only when different AI agents need different facts — another location, brand or line of business — or when you have internal knowledge for your team. AI agents see only the knowledge bases listed in their Search knowledge base job; the lead-card AI assistant sees every knowledge base with Use in the AI assistant switched on.
Two controls decide who sees what
| Control | Where | Who it affects |
|---|---|---|
| Search knowledge base job | AI & Automation → AI Assistant Jobs | The AI agents you attach the job to: 2-Way SMS AI Assistant, website chat assistant, AI Voice Assistant |
| Use in the AI assistant switch | The knowledge base’s Edit dialog | The AI assistant on the lead card, for your team |
Together they give you four combinations:
| Knowledge base is… | In an AI Assistant Job? | Use in the AI assistant | Typical content |
|---|---|---|---|
| Public | Yes | On | Hours, prices, services, policies — what customers and your team both need |
| Internal | No | On | Sales playbook, objection handling, offers, qualifying questions — for your team only |
| For one AI agent only | Yes | Off | Content written for one channel, such as short phone answers |
| Parked | No | Off | Drafts you are still preparing |
When one knowledge base is enough
Most small businesses with one location and one brand need a single public knowledge base. It is easier to keep current, and every AI agent gives the same answers.
When to split
| Situation | How to organize | How to connect |
|---|---|---|
| Several locations with different hours, addresses or prices | One shared knowledge base for common facts + one per location | Each location’s SMS, chat or voice AI assistant gets a job with the shared and its own knowledge base |
| Several brands or websites | One knowledge base per brand | Each website’s chat assistant gets its own job |
| Different teams, e.g. sales line and service line | One knowledge base per team | The SMS and voice AI assistants on the sales line and the service line get different jobs |
| Internal knowledge for reps | A separate internal knowledge base | No AI Assistant Job; Use in the AI assistant on |
| A lot of content | Split by topic: services, policies, products | List the ones each AI agent needs in its job, up to 7 |
An AI agent can search up to 7 knowledge bases, and an account can have up to 25.
Set up an internal knowledge base for your team
- Create a knowledge base, for example “Sales playbook”, with Use in the AI assistant on.
- Add what helps your reps: how to qualify a lead, which offer fits which customer, answers to common objections, follow-up templates, next steps after a quote.
- Do not add it to any Search knowledge base job.
- Ask the AI assistant on a lead card, e.g. “What should I offer?” — the answer can now use your playbook. See Ask the AI Assistant on the Lead Card.
AI agents never search a knowledge base that no job lists. Keep in mind that everyone on your team who can open the Knowledge Base page — including call agents — can read internal knowledge bases.
What never goes into a knowledge base
AI agents can quote anything in the knowledge bases they search, and your whole team can read every knowledge base. Keep these out of all of them:
- customers’ personal data — names with phone numbers, addresses, dates of birth, ID numbers;
- payment details, account numbers, passwords and access codes;
- health, legal or financial records about individual customers;
- anything you would not want read aloud to a customer by an AI agent — such as cost prices, margins or discount limits — out of every knowledge base that an AI Assistant Job lists.
Tips & best practices
- Name knowledge bases by audience and content, e.g. “Public — services and prices”, “Internal — sales playbook”. The names appear in job settings and in answer sources.
- Use the description to say who the knowledge base is for.
- Avoid duplicates across knowledge bases. Keep shared facts in one shared knowledge base, so a price changes in one place.
- Check what each AI agent can reach. Open each Search knowledge base job and review its list after you add a knowledge base.
FAQ
Can an AI agent see an internal knowledge base by accident? Only if a Search knowledge base job attached to it lists it. Check the jobs before you add sensitive internal content.
Can I limit a knowledge base to certain users? No. Everyone who can open the Knowledge Base page can read every knowledge base in the account. Keep that in mind when you decide what to add.
Does turning off “Use in the AI assistant” affect my AI agents? No. The switch only controls the lead-card AI assistant.
Should I make one knowledge base per channel? Usually not. SMS, chat and phone can share one knowledge base. Split only if a channel needs different content.
Related articles
- Create a Knowledge Base
- Connect a Knowledge Base to Your AI Agents for SMS, Chat and Voice
- Ask the AI Assistant on the Lead Card
- Knowledge Base: Teach Your AI Agents About Your Business
Still feeling stuck? Please send us your questions using this form.