Separate knowledge by purpose
Keep policies, offerings, operating guidance, and other subject areas in focused collections instead of one unstructured prompt.
Knowledge base
Give every AI reply a source of truth your team can maintain.
Organize business information into focused knowledge bases, keep pages reviewable, and connect the right source material to each AI agent.
What changes
Less fragmented work. Clearer customer follow-through.
Make updates reviewable
Edit source pages directly and review proposed changes before they become part of the information an agent relies on.
Connect only what is relevant
Bind the appropriate knowledge bases to each agent so it does not receive unrelated workspace content by default.
How it works
Start with the way your business already works.
01
Create a focused knowledge base
Choose a clear subject and add pages that contain the business facts the team is prepared to maintain.
02
Review and keep it current
Update outdated guidance, resolve conflicting information, and keep responsibility for source content visible.
03
Attach it to an agent
Make the knowledge base available to the agent that needs it and test how the information is retrieved.
Where it fits
Useful across the moments customers and operators share.
Use case 1
Customer policies
Maintain cancellation rules, preparation instructions, accepted payment methods, and service boundaries.
Use case 2
Offerings and locations
Document what the business provides, where it is available, and which details vary by branch.
Use case 3
Internal operating guidance
Give agents approved context for routing, handoff, and the next step without exposing unrelated internal material.
A practical boundary: A knowledge base improves consistency only when the source information is accurate. StrataDesk keeps knowledge editable and reviewable; your team remains the owner of the facts.
Common questions
What teams ask about knowledge base.
Is a knowledge base the same as an agent prompt?
No. The prompt defines how an agent should behave. A knowledge base contains the business information the agent may retrieve while doing that work.
Can one knowledge base be used by multiple agents?
Yes. A maintained knowledge base can be connected to the agents that need that subject matter.
What should not go into the knowledge base?
Avoid secrets, unnecessary personal information, and material the agent is not authorized to use. Keep sensitive workflows behind appropriate human review.
Explore next
See how the pieces work together.
Platform
AI agents
Configure how an agent should respond, connect the business resources it may use, and define the situations that need a person instead of an improvised answer.
Read moreSolutions
AI for customer support
Give customers consistent answers from maintained business knowledge, keep the full conversation in one place, and route exceptions to a person without making the customer begin again.
Read morePlatform
Unified inbox
Bring supported messaging channels into a shared workspace where your team can see context, take ownership, and move a conversation into action without losing the thread.
Read moreSee the platform in motion.
Start with the interactive workspace demo, then sign in when you are ready to work with your team.