Find out what your docs cannot answer
Biel answers reader questions from your documentation, with sources cited on every response. In return, you get the thing writers never had: a log of every question, every gap, and every rating, turned into a ranked backlog of what to write next.
To enable dark mode for Biel.ai on your website, follow these steps:
- Modify your website’s main HTML file.
- Add the attribute
data-theme="dark"to the<html>tag.
<html data-theme="dark">
<!-- Your existing HTML content -->
</html>This change activates the dark mode styling for Biel.ai…
100,000+ technical questions answered, 98.6% rated helpful
Your docs get more usable. You get the data.
Readers stop hunting through pages and start getting cited answers. You stop guessing what is missing and start working from a demand-ranked list.
A ranked backlog of what to write next
Every question the assistant cannot answer from your docs is logged and clustered by topic. That is your content-gap report: a prioritized list of missing pages, driven by real reader demand instead of guesses about what might be useful.
Reader questions, verbatim
You finally see how readers actually phrase things. When users ask "why am I getting a 401" and your page is titled "Authentication lifecycle", that mismatch is your next retitle. The question log is continuous, free user research.
Numbers that prove the docs are working
Satisfaction ratings, resolution rates, and question volume give you evidence for the review cycle. Docs work is notoriously hard to measure; a thumbs-up rate on answers drawn from your pages is a number leadership understands.
Answers that stay inside your docs
Responses are generated only from your indexed content and cite the source page. No invented flags, no answers from someone else’s product. When the docs do not cover it, the assistant says so, and that gap lands in your report.
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.
Installs without an engineering ticket
One script tag, or a native plugin for Docusaurus, MkDocs, and Sphinx. Most writers have it live in about 15 minutes, styled to match the site. Self-serve, from $50/month.
“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.”