The stale link
You sent the article knowing it was wrong
The screenshot was two redesigns old. Fixing it meant an hour you didn’t have. So you sent it anyway and hoped they wouldn’t scroll.
✦
Never answer the same question twice
Cited AI support from your docs.
usedocs.app answers customers from the product docs you already ship. When the answer is missing, it refuses to guess and drafts the article for you to approve.
✓ 100 messages / mo · No credit card
✓ Cited answers, not guesses
✓ Nothing publishes without you
Works with your stack
- GitBook
- Notion
- OpenAPI
- GitHub
- Slack
- Discord
- Teams
- Zendesk
- Intercom
- Markdown
- llms.txt
Sound familiar?
Your help center has been next weekend’s problem for six months.
It isn’t that you don’t care. You ship constantly. Every renamed button quietly makes an article wrong. No test fails. Nothing flags it. You find out when a customer does.
The same ticket
You’ve answered this exact question 200 times
It should live in the help center. Instead it lives in your inbox, costing you ten minutes a week. Writing it up properly never reaches the top of the list.
The quiet churn
A trial user got stuck and never came back
They wanted to help themselves. The doc was missing or a chatbot guessed. You won’t get a ticket. Just a trial that never converted.
Meet usedocs
You build the product. usedocs keeps the docs honest.
usedocs is an AI support agent trained on your documentation.
01
It answers from your real docs
Crawl the help center, sitemap, GitBook, Notion, OpenAPI, or files you already have. Every answer cites the page a customer can open.
02
It drafts every miss
When the docs don’t support an answer, usedocs refuses instead of inventing one. That miss becomes a clustered gap and a reviewable draft.
03
You approve before it goes live
Publish the draft, edit it, or dismiss it. GitHub merges can draft articles and changelog entries the same way — never auto-published.
Also included: a hosted help center, cited chat widget, OpenAPI Try It docs, product changelog, and a custom help domain on Business.
How it works
Connect the docs you already have.
No new knowledge base. Point usedocs at the help you already published, test the questions support already hears, then ship a cited widget.
1
Connect your docs
Crawl a docs site or sitemap, or import GitBook, OpenAPI, Notion, Markdown, PDF, or DOCX.
2
Test cited answers
Ask the questions support already hears. Inspect sources, then force a miss and confirm it refuses.
3
Embed the support widget
Paste one script tag. Monitor gaps, drafts, and escalations in the inbox after you go live.
Documentation
My Documentation
Page views
24.5K
+12.5%
Searches
8.2K
+8.1%
Helpful
96%
+3.4%
Views over time
Jun 12 — Jul 12
The support loop
A clearer picture of what happens after “I don’t know.”
Usedocs connects the answer, the missing article, and the person who decides what ships next.
01 / Honest fallback
Every miss feeds the next answer.
A customer question becomes a cited answer when the docs support it. When they do not, usedocs refuses, captures the gap, and gives your team a reviewable draft.
One loop. Better coverage every time you approve an update.
02 / One knowledge base
Connect once. Reach every support surface.
Bring the docs you already have into one grounded layer, then serve answers wherever customers and agents already work.
03 / Human handoff
The bot knows when to bring in a person.
High-confidence answers stay self-serve. Inbox triage + escalation alerts capture each unresolved question with the context you need to review it in the Monitor inbox on your own schedule.
Built for docs & support teams
The surface your team already owns.
SaaS support, the writing backlog, or the help center — start from the job you already run, not another feature list.
⌁
Source: Getting Started
SaaS support
Put self-serve on the product site so setup and billing questions don’t start as tickets.
AI support for SaaS →
⌕
Content gapsThis week
Docs writing backlog
See which themes readers actually miss, then open the queue from live traffic instead of a quarterly audit.
Content gap analysis →
↗
Gap draft ready
Hosted help center
When customers want to browse, not chat — publish articles and drop the widget on the same help surface.
Help center chatbot →
Use cases
Built for the support job you are hiring.
01
SaaS support
Deflect setup, billing, and integration questions with an AI support agent trained on product docs.
02
Documentation chatbot
Put a cited AI chatbot on your docs site so readers get answers without hunting through pages.
03
Help center chatbot
Answer from published help articles, cite the source, and hand off when self-serve is not enough.
04
Content gap analysis
Turn unanswered questions into a writing backlog instead of another quarterly docs audit.
05
Developer docs
Answer API, SDK, and webhook questions from the reference you already publish.
06
Ferndesk alternative
Compare a self-updating help center with a cited support agent plus docs ops.
Compare usedocs
See how usedocs compares with other support tools.
Other tools answer. usedocs cites the page and refuses when the docs do not. Browse the comparison hub, or start with the Ferndesk alternative if you are comparing self updating help centers.
f
→
Ferndesk alternative
Compare self-updating help centers, AI docs agents, cited answers, content gaps, and pricing.
i
→
Intercom Fin alternative
Compare an omnichannel AI agent suite with docs-first cited support and flat message pricing.
c
→
Chatbase alternative
Compare website chatbots with a docs-trained support agent, citations, and gap analytics.
d
→
DocsBot alternative
Compare documentation chatbots on citations, per-message pricing, inbox, and content gaps.
g
→
CustomGPT alternative
Compare custom GPT platforms with docs-first support, gap drafts, and startup-friendly pricing.
z
→
Zendesk alternative
Compare documentation-led AI support with a traditional help desk and ticketing platform.
Also see SiteGPT, Help Scout, GitBook, and the full comparison library.
Pricing
Simple pricing for AI customer support.
Looking for an enterprise plan? Choose Business — unlimited bots and seats, custom help domain, higher draft/PR/screenshot limits, and priority integration support at $299/mo (or $239/mo billed annually).
Free
For evaluating docs coverage and widget fit.
$0
/mo
Start free
- 100 messages each month
- 1 bot · 1 seat
- Cited answers + gap capture
- Cited chat widget + help-center link
- Public help center (path URL)
- 3 screenshots · starter drafts
Pro
For small product and developer relations teams.
$29
/mo
Upgrade to Pro
- 5,000 messages / month
- Up to 3 bots · 3 seats
- Help center + GitBook / OpenAPI
- PR auto-drafts + changelog
- Slack, Discord, Teams + webhooks
- Branding removal · 20 screenshots
Growth
For support teams handling heavier doc traffic.
$79
/mo
Choose Growth
- 12,000 messages / month
- Up to 5 bots · 8 seats
- Private KB · multi-locale · 100 screenshots
- GitHub / Notion publish + SEO JSON-LD
- Queued handoff alerts
- Analytics, ROI minutes saved, exports
Business
Enterprise-ready
For multi-team docs support and enterprise-scale controls — our top plan when you need more than Growth.
$299
/mo
Talk with us
- 25,000 messages / month
- Unlimited bots and seats
- Custom help domain bundled
- Higher draft · PR · screenshot limits
- Priority integration support
Annual billing is shown as an equivalent monthly rate and billed annually.
FAQ
Questions, answered.
An AI support agent answers customer questions from your documentation, cites the source page, and hands off to a human when the docs do not contain the answer. See the full definition.
No. usedocs.app is a docs-trained AI support agent. Usedesk (usedocs.com) is a separate helpdesk product. See About usedocs.
Yes. Sign in with Google, GitHub, or a magic link. Free includes 100 messages each month — no credit card required.
Business is the enterprise-ready plan: $299/mo (or $239/mo billed annually), unlimited bots and seats, custom help domain, higher draft/PR/screenshot limits, and priority integration support. Growth ($79/mo) sits between Pro and Business for heavier doc traffic.
It declines instead of inventing. Missed questions become content gaps you can draft into FAQs and help articles.
Yes. Escalations notify Slack, Discord, Teams, or webhooks. Review it in the Monitor inbox on your own schedule.
Yes. Categories, SEO/JSON-LD, sitemap, imports, and human approve-to-publish. Business can map a Custom help domain.
Yes. Connect GitHub so merges and releases draft help articles and changelog entries for review — never auto-published.
Chat stays in the widget. A header link opens your published help center in a new tab. Answers cite source pages.
Yes. The Answer API exposes the same cited RAG pipeline over HTTP. See the Answer API guide.
Yes. Crawl docs sites or import GitBook, OpenAPI, Notion, Zendesk, Intercom, Markdown, PDF, and DOCX.
Ready when you are
Stop answering the same question twice.
Start free, connect the docs you already have, and turn the next miss into a draft — no credit card.
