Sources
The knowledge base chatbot that reads the live source.
A knowledge base chatbot answers customers from your documentation instead of a script. Outlearn's reads Helpjuice, Zendesk, Confluence, Google Drive, SharePoint, Slack and a crawl of your website, twenty systems in all, keeps them synced, and shows the article behind every answer.
Free plan, no card. Nothing migrated, nothing re-uploaded. Last updated 7 September 2026.
Measured, not promised
Half of real conversations end on the docs alone
The connector count is from the product. The rest are production numbers with the denominator attached, from the AI support benchmark.
- 20
- connected systems it reads in place, plus files, URLs and snippets
- 29,003
- real customer conversations, Oct 2025 to Aug 2026
- 45.9%
- resolved by the agent on its own, no human involved
- 50.8%
- resolved on its own in the last 90 days, as it learned the docs
How it works
An AI knowledge base chatbot that connects, syncs, cites and scopes
Connect what you already maintain
Help centre, wiki, drive, ticket history, team chat. Twenty systems read in place, no export and no migration. Add uploaded files, a website crawl or a typed snippet for the answers that live nowhere yet.
It keeps reading
Auto-sync monitors connected sources and pulls in updates as they happen. Need it now? Three dots, Resync: the agent keeps answering from the old content until the new content lands.
Answers with the article attached
It searches every active source at once, writes the reply from the most relevant content, and shows a Sources chip the reader can open. Not a paraphrase of a copy someone uploaded in March.
Internal stays internal
Every source and snippet is Public or Internal. A public visitor never receives an internal answer, even when it is the best match. The same agent serves your team the internal one.
Try it
A chatbot that reads documentation wherever it lives
Pick the place an answer lives. The reply changes, the agent and the chip under it do not.
Where does the answer live?
Eight kinds of source, one agent. It searches every active source at once, writes the reply from the most relevant content, and attaches the article it used.
Helpjuice
Knowledge base
Answers straight from the published article, re-read as it changes.
Knowledge in
Twenty connectors, three manual imports, one agent
Connect a source once and it is read in place. The docs' advice: quality beats quantity, so connect the accurate sources and leave the stale ones off.
Knowledge bases
- Helpjuice
- Help Scout
- Helpdocs
- KnowledgeOwl
- Confluence
Ticketing
- Zendesk
- Intercom
- Freshworks
- Salesforce
Team chats
- Slack
- Microsoft Teams
- Google Chat
- Gmail
Cloud storage and code
- Google Drive
- SharePoint
- OneDrive
- Dropbox
- Box
- GitHub
Manual
- Website URL
- Uploaded files
- Snippets
The Sources tab
On or off, Public or Internal, synced or imported
Every source is one row. Turn it off and the agent stops answering from it; resync it and the agent keeps answering from the old content until the new content lands.
Sources · 5 active
+ Add sourceHelp centre
Helpjuice · 214 articles
PublicAuto-sync · 12 min ago
Engineering wiki
Confluence · 3 spaces
InternalAuto-sync · 40 min ago
Closed tickets
Zendesk · last 12 months
PublicAuto-sync · 1 h ago
example.com
Website crawl · 138 pages
PublicOne-time import · Re-crawl
Student discount
Snippet
PublicSaved · 2 days ago
Add snippet
No integrationTitle
Content
Who can get this answer
Auto-sync covers Helpjuice, Confluence, KnowledgeOwl, Helpdocs, Help Scout, Google Drive, Dropbox, Box, OneDrive, Freshworks, Intercom, Zendesk, Slack, Microsoft Teams, Google Chat and Gmail. Uploaded files and website crawls are one-time imports you re-upload or re-crawl. Set up Sources before anything else: an agent with no content cannot answer anything.
The difference
Most knowledge base chatbots read a copy
A typical knowledge base chatbot
Outlearn
You export the help centre and upload it. Then upload it again next month.
Connects to the live source and keeps reading it. Edit the article on Tuesday, that is Tuesday's answer.
One knowledge base, and only the knowledge base.
The help centre, the wiki, the drive, the closed tickets, the Slack thread, the website and a typed snippet, searched together.
An answer, and you take its word for it.
An answer with the article attached, so the reader and your team can check it in one tap.
Everything you connect is visible to everyone who asks.
Public or Internal per source; the same agent answers visitors from the public docs and your team from the internal ones.
Priced per seat, or per resolution.
Credits for the AI's work. No seats, free plan to start, 14-day trial on paid plans.
Pricing, for the record: credits for the AI's work, never per seat, never per resolution. Free $0 with 100 credits, Starter $99/month with 2,000 credits, Growth $199/month with 4,500 credits, Scale $599/month with 15,000 credits. 14-day trial on paid plans, no card. Full detail on the pricing page. When the docs run out, the agent hands off to a person with the transcript rather than guessing.
Connect one source, ask it the question your team answers most, and open the chip under the reply.
Your help centre URL or one connector, the Preview button. A few minutes on the free plan, no card.
The questions teams ask about knowledge base chatbots
What is a knowledge base chatbot?
A chatbot that answers customer questions from your existing documentation, such as a help centre, a wiki or a set of policy documents, instead of following a script you build by hand.
Outlearn's version reads twenty connected systems, uploaded files, crawled web pages and typed snippets, searches all of them at once, and shows the article behind every answer.
Which knowledge bases and documents can it read?
Helpjuice, Help Scout, Helpdocs, KnowledgeOwl and Confluence for documentation; Zendesk, Intercom, Freshworks and Salesforce for tickets and records; Slack, Microsoft Teams, Google Chat and Gmail for team knowledge; Google Drive, SharePoint, OneDrive, Dropbox, Box and GitHub for files and code. Beyond the connectors: uploaded PDF, DOCX, CSV, XLSX, TXT, MD and HTML files, any publicly accessible web page, and snippets written directly in the dashboard.
How does it stay up to date when the documentation changes?
Auto-sync monitors connected sources for changes and pulls in updates as they happen; Helpjuice, Confluence, KnowledgeOwl, Helpdocs, Help Scout, Google Drive, Dropbox, Box, OneDrive, Freshworks, Intercom, Zendesk, Slack, Microsoft Teams, Google Chat and Gmail stay in sync on their own. Uploaded files and website crawls are one-time imports you re-upload or re-crawl. You can also trigger a resync from the three-dot menu on any source: the agent keeps using the existing content while it runs, then deleted content is removed and new content added.
Does it show where an answer came from?
Yes.
Every reply carries a Sources chip the reader can open to see the article, page or file the answer was written from. It is the difference between trusting the chatbot and checking it.
Can it answer from internal documentation without exposing it to customers?
Yes.
Each source and snippet is marked Public, for anyone including unauthenticated visitors on your website or chat widget, or Internal, for authenticated team members and users verified by your system. An internal source never appears in a conversation with a public visitor, even when it is the most relevant answer, so one agent can serve both audiences.
What if a question is not in the knowledge base?
Write a snippet: a short answer typed in the dashboard, Public or Internal, no integration needed.
The docs recommend them for frequent questions the knowledge base does not cover, quick answers that do not warrant a full article, temporary content, and questions the agent keeps getting wrong. The analytics also list the week's content gaps, so you know which snippet to write next.
How is it priced, and how long does setup take?
Credits for the AI's work, never per seat and never per resolution.
The free plan needs no card, and every paid plan has a 14-day trial. Setup is your website URL or one connected source; the docs' advice is to set up Sources before anything else, because an agent with no content cannot answer anything.
Keep reading
The AI customer service agent
Reads your live docs, answers with the source, takes the action mid-chat, and hands the rest to a person.
Chatbot to human handoff
The full transcript and an AI summary go with the conversation; the customer never repeats themselves.
Helpjuice AI Chatbot
Turn the Helpjuice knowledge base your team already maintains into customer answers.
Zendesk AI Chatbot
Reads your Guide articles and closed tickets, opens tickets mid-conversation.