Answers from your
internal documentation.
Connect approved runbooks, guides, and procedures. Let your team ask in the tools it already uses.
14 days free. No credit card required.
In your team’s chat.
Slack
Microsoft Teams
DiscordAnswers in your team’s tools.
- Your chosen sources
- Connect supported websites, Confluence, GitHub repositories, and uploaded files.
- Your team’s channels
- Answer documentation questions in Slack, Microsoft Teams, Discord, or an internal interface.
- Source references
- Help employees check the procedure behind an answer, where source links are available.
- Recurring questions
- Review what people ask and which explanations need attention.
Start with the sources.
Plan who can read them.
Connecting private content and authorizing readers are separate decisions. Review your audience, authentication, and project boundaries before rollout.
Read the Security OverviewRoll out with your team.
Choose a defined use case
Start with a maintained set of docs and the people who should use them.
Discuss the scopeReview access
Confirm source credentials, reader authentication, and project boundaries.
Security OverviewTest, then connect
Check representative questions before enabling your chosen chat channel.
Chat integrations
“Easy to set up, yet the positive effects are felt immediately.”
Questions
Is our content used to train AI models?
No. Your indexed content and conversations are not used to train AI models. Read the Security Overview.
Can different departments have different access?
Discuss deployments that require department-level permissions with us. Project-scoped keys and embedding restrictions do not replace reader authentication.
How do sources stay current?
Refresh from the dashboard or use the scheduled updates included in your plan. API-triggered refresh requires Business or Enterprise.