Channel posts
Ask the bot inside any channel where it is added. Answer arrives in the same thread, with source links.
@Biel.ai
For Microsoft Teams
Your docs, answered in Teams
Deploy a Biel.ai docs bot inside Microsoft Teams so employees self-serve from runbooks, HR policies, internal SDKs, and product docs without leaving the chat. Standard Teams app package, admin-controlled rollout.
14-day freeSelf-serveLive in 15 min
Engineering›General2:14 PMM
Maya Patel2:14 PM
@Biel how do I rotate prod database credentials? Need to do it without a maintenance window.
BielBot2: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?
Type a new message
Used by teams that take their documentation seriously
Where employees can ask
Four surfaces, one bot.
Teams is where most internal communication lives. Biel meets employees there with the same answer engine that powers your docs site, citing the same sources.
Group chats
Add the bot to a group chat for ad-hoc cross-team questions. Same source-cited answer, scoped to the chat.
Add to chat
Personal chats
Private 1:1 with the bot for questions an employee does not want to ask publicly. Same answer, only they see it.
1:1 with @Biel
Source citations
Every answer carries the doc title and a deep link to the section it came from. Verify in one click.
docs.acme.dev/...
Setup
Standard Teams app package, admin-controlled.
Download the manifest from Biel, upload via Teams Admin Center, link with a setup token. The bot is hosted by Biel, so there is nothing to deploy on your side.
Full setup guide- 01
Download the app package
In your Biel project, open Integrations → Microsoft Teams and click Download app package. You get abiel-teams-app.zipwith the bot manifest and icons. - 02
Admin uploads to Teams
A Teams administrator uploads the package via Teams Admin Center → Manage apps → Upload new app, then sets a permission policy for the users or groups allowed to install it. - 03
Generate a setup token
Back in Biel, click Generate token in the Microsoft Teams card. The token is single-use and links one Teams workspace to one Biel project. - 04
Connect the bot
Search for Biel in the Teams app store, install, open the chat, send the setup token as the first message. The bot confirms the connection.
Without Biel vs with Biel in Teams
Most internal docs questions in Teams today get answered by humans, repeatedly. Biel turns those into self-serve answers and surfaces the gaps your runbooks and policies do not cover.
| Dimension | Teams alone | Biel.ai |
|---|---|---|
| Where employees ask | They DM whoever owns the docs, or post in #help and wait. Same questions repeat across teams. | They ask the bot in a channel, group chat, or personal chat. Answer in seconds with source links. |
| Admin control | Teams Admin Center governs which apps are allowed and who can install them. Custom bots are a project. | Standard Teams app package. Admin uploads through the same flow as any internal app, sets permission policies. |
| Source attribution | Whoever answers links a SharePoint page they remember, if they remember the right page. | Every answer cites the doc title and links to the section. Verifiable, repeatable, attributable. |
| Context across messages | Memory lives in whoever they asked. Repeated questions waste time. | Per-conversation context. Follow-ups resolve without repeating background. /clear resets. |
| Privacy | Channel asks are public to the team. DMs lose the answer to history. | Channel asks are public to the channel; personal-chat asks are private. Same sources, same answer. |
| Where docs gaps come from | Repeated questions surface only when someone notices and writes them up. | Every question lands in the dashboard. Repeated unanswered ones surface as content gaps to fix. |
| Setup | Build a Teams bot in-house: manifest, hosting, OAuth, LLM. Maintain it. | Download package, admin upload, paste token. Bot live in 15 minutes. |
Things teams ask during evaluation
Where can the bot answer?
In team channels, group chats, and personal 1:1 chats. The same Biel project powers all surfaces. Conversation context is per-thread.
Who needs to install it?
A Teams administrator uploads the app package once via the Teams Admin Center. After that, end users install it from the Teams app store like any other app, subject to the permission policy the admin set.
Can different Teams workspaces use different Biel projects?
Yes. Each setup token links one Teams workspace to one Biel project. Generate a fresh token to relink or to connect a different project. Tokens are single-use.
Does it work for internal-only documentation?
Yes. This is the most common Teams pattern: an internal docs project (runbooks, HR policies, SDK guides) connected to Teams so employees self-serve. Index private repos, Confluence spaces, or uploaded files. Answers stay inside your Teams tenant.
Is it trained on our Teams conversations?
No. The bot answers only from the documentation sources you index in your Biel.ai project. Teams 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.
Does it remember the conversation?
Yes, within the same chat.
/clear resets context when you want a clean slate.How long does setup take?
Most teams are live in 15 minutes including admin approval. The bottleneck is usually waiting for the Teams admin, not the integration itself.
Where does our content go?
EU-hosted by default. GDPR compliant. Teams messages addressed to the bot are processed for the answer and not used to train models.
Make your runbooks answer questions.
14-day free trial · No credit card required · From $50/mo
Use a different platform? See our integration pages for Slack, Discord, Confluence, Notion, and GitHub.