Public channels
Invite the bot once. Mention @Biel.ai in any thread and the answer lands inline, with source links readers can click.
/invite @Biel.ai
For Slack workspaces
Your docs, answered in Slack
Mention @Biel.ai in any channel or DM the bot directly. Source-cited answers from your indexed documentation, in the place your team is already working. Setup is a few clicks.
14-day freeSelf-serveLive in 15 min
#eng-platform2:14 PMM
Maya Patel2:14 PM
@Biel how do I rotate prod database credentials? Need to do it without a maintenance window.
BielApp2:14 PM
Use the dual-credential rotation in
infra/runbooks/db-rotate. Provision the new secret, deploy with both old and new active, drain traffic to the new one, then revoke the old. The script handles the handoff automatically; expected downtime is zero.📄runbooks/db-rotation.md📄platform/secrets-policy
D
Daniel Reis2:16 PM
@Biel does the same procedure work for the staging cluster?
Message #eng-platform
Used by teams that take their documentation seriously
Where readers can ask
Four surfaces, one bot.
Slack is where your team and your power users already are. Biel meets them there with the same answer engine that powers your docs site, citing the same sources.
Direct messages
Private lookups for someone who does not want to ask the question publicly. Same answer, same sources, only they see it.
DM @Biel.ai
Threads with context
Per-channel conversation memory so follow-up questions resolve without repeating yourself. Reset with /clear.
/clear
Source citations
Every answer carries the doc title and a deep link to the section it came from. Readers verify in one click.
docs.acme.dev/...
Setup
Live in five minutes, no code.
OAuth into your Slack workspace, invite the bot, ask. The bot is hosted by Biel.ai, so there is nothing to deploy.
Full setup guide- 01
Connect your workspace
Open your Biel project, scroll to Integrations, click Add to Slack. OAuth handles the rest. - 02
Invite the bot to a channel
In any channel where you want it to respond, run/invite @Biel.ai. The bot only sees channels it has been invited to. - 03
Mention or DM
Mention@Biel.aiwith a question in a channel, or DM the bot directly. Answer arrives inline with source links. - 04
Reset when needed
Per-channel context is kept so follow-ups work./clearstarts a fresh conversation.
Without Biel vs with Biel in Slack
Most docs questions in Slack today get answered by humans. Most get answered more than once. Biel turns those into self-serve answers and surfaces the gaps your docs do not cover.
| Dimension | Slack alone | Biel.ai |
|---|---|---|
| Where readers ask | They DM whoever wrote the docs, or post in #help and wait. Half the questions repeat. | They @-mention the bot in any channel or DM it. Answer in seconds, in the channel where they already are. |
| Source attribution | A link to a doc page someone remembered, if they remember the right page. | Every answer cites the doc title and links to the section. Readers verify with one click. |
| Context across messages | Memory lives in the brain of whoever they asked. Repeat questions waste everyone. | Per-channel conversation context. Follow-up questions resolve without repeating background. /clear resets. |
| Privacy | Public-channel asks expose every question to the room. DMs lose the answer to history. | Channel asks are public; DMs are private. Either way, the answer carries the same sources. |
| What gets surfaced as a docs gap | Repeated questions get fixed when someone notices. Most do not get noticed. | Every question lands in the dashboard. Repeated unanswered questions surface as content gaps to fix. |
| Setup | Build a custom bot in-house. Maintain it forever. | Click Add to Slack. Bot live in 5 minutes. No code. |
Things teams ask during evaluation
Where can the bot answer?
Any channel it has been invited to, plus direct messages. Channels you do not invite it to stay private.
Does it remember the conversation?
Yes, per channel. Follow-up questions in the same channel resolve with context.
/clear starts a fresh conversation when you want a clean slate.Can different channels point to different projects?
Each Slack workspace connects to one Biel.ai project. Run multiple projects (one for product docs, one for internal runbooks) and connect each to a separate workspace, or use the workspace-wide project for all channels.
Will the bot see private messages between teammates?
No. The bot only reads messages addressed to it: mentions in channels it has been invited to, and DMs to it directly. Other channel traffic is invisible.
Is it trained on our Slack conversations?
No. The bot answers only from the documentation sources you index in your Biel.ai project. Slack messages are not used to train models and are not a knowledge source for answers. The bot reads a question, queries your indexed docs, replies.
What happens to the questions asked in Slack?
They land in your Biel.ai dashboard alongside web-widget questions. Repeated unanswered questions surface in the Content Gaps view.
How long does setup take?
Click Add to Slack, approve the OAuth scopes, and invite the bot to a channel. Most teams are live in five minutes.
Where does our content go?
EU-hosted by default. GDPR compliant. Slack messages addressed to the bot are processed for the answer and not used to train models.
Stop being your team’s human FAQ.
14-day free trial · No credit card required · From $50/mo
Use a different platform? See our integration pages for Discord, Microsoft Teams, Docusaurus, MkDocs, and GitHub.