Find out what your docs cannot answer
Give readers source-linked answers, then use their questions, ratings, and unresolved topics to prioritize documentation work.
Used by documentation and developer-experience teams
Why docs teams run Biel
Learn what readers need from their questions
A backlog of what to write next
Review unresolved questions grouped by topic, then use reader demand to decide what to document next.
See the wording readers use
The question log shows the terms readers use, helping you find gaps between their language and your navigation or page titles.
Metrics for documentation reviews
Use question volume, ratings, and unresolved topics alongside your existing documentation metrics.
Answers grounded in your docs
Readers get an answer with links to your indexed documentation. They can check the source, while your team reviews questions that need better coverage.
Every site you maintain, one assistant
Guide site, API reference, wiki, even sites on different platforms: one index covers them all, and readers get routed to the right site. The Tezos team runs one assistant across docs.tezos.com and docs.etherlink.com.
Works with your documentation platform
Add the widget through a platform plugin or script tag. Keep your existing publishing workflow and customize the appearance to match your docs.
“The main benefit is learning what questions our users ask and whether the bot can answer them. We've made many doc updates when we learned that customers asked for particular info and the bot wasn't able to answer.”