Slack
The Slack bot answers your team's questions from your organization's knowledge inside Slack. It is an internal answering surface: it does not create tickets or hand conversations to a person.
Add to Slack
Open Settings, then Connectors under Connections & data. You need to be able to manage connectors.
On the Slack card, click Add to Slack and approve the install in Slack. There is no Slack app to create and nothing to configure.
The card now reads "Org-shared bot · {workspace}". Click Manage to set defaults.
One connection serves the whole organization. Every answer runs with the access of the person who connected Slack, capped by the sensitivity setting below, so connect with an account whose access matches what the workspace should be able to see.
Defaults under Manage
Answering defaults: a Default agent (Auto-pick, or any active agent open to the whole organization) and a Default effort (Auto, Fast, Standard, Thorough). Auto-pick uses an agent with Slack turned on in its Channels step, otherwise your oldest shared agent. Anyone can override these per question with the flags below.
Maximum answer sensitivity: Standard, Confidential, or Highly sensitive. Slack is a shared-channel surface, so everyone in a channel reads the reply. Standard is the default, and the stricter of this and the answering agent's own ceiling applies.
Include the responder's private mail & calendar: off by default.
Answer scope: Everywhere it's invited or Only selected channels. Direct messages always answer.
Ingest channel knowledge: optionally capture public channels as knowledge. A thread is captured once it settles, about a day after the last message. The bot's own answers are never captured.
Click Save defaults or Save scope after changes.
Invite the bot to channels
Invite the bot to each channel where it should answer, public or private. In the channel, type:
/invite @Records Labs
Channel membership is managed in Slack, not in Records Labs. You can also skip channels and DM the bot.
Ask a question
@mention in a channel. Type @Records Labs followed by your question. The bot reacts with eyes while it works and replies in a thread under your message. An @mention inside an existing thread gets up to the last ten turns of that thread as context, so you can ask follow-ups. A reply in a thread without an @mention is not answered.
Direct message. DM the bot with a question. DMs answer regardless of the channel scope.
/ask. Type /ask and your question. The answer is ephemeral: only you see it. /ask works in any channel, even ones the bot has not joined, but it has no thread memory. /ask help shows the help card.
Pick an agent or depth per question
Add flags before the question:
--deepanswers with Thorough depth.--fastanswers with Fast.--effort=standard(or--depth=…) sets any depth level: auto, fast, standard, thorough, research.--agent=<handle>answers with a specific agent. Use the agent's permanent handle, not its display name. The agent's Channels step shows the handle when API or MCP access is on. Only agents open to the whole organization can be picked; anything else falls back to the default.--council=<name>answers with a saved council.
Example: @Records Labs --deep --agent=support-faq what's our return policy?
When you use a flag, the reply ends with "Answered by {agent} agent · {effort} depth" (plus the council's name when you used --council). Flags without a question return "Add a question after the options". Unknown values are ignored.
What you get back
Answers are posted as Slack blocks with the sources cited from your knowledge, up to eight sources. Very long answers are split into sections and cut with "…" if they would exceed Slack's limits. If no answer text comes back, the bot says "I couldn't find an answer to that in the connected knowledge."
What Slack cannot do
No tickets, no hand-off and no escalation. Slack is for your team, not for customers, and it does not appear on the Help Desk Channels page.
Answers are not saved as chat sessions.
There is no per-channel agent picker; set the default agent, or use
--agentper question.Every answer is capped at the Maximum answer sensitivity, so Confidential or Highly sensitive material is only available if an admin raised the cap.
Disconnecting
On the Slack card, click Disconnect and confirm "Disconnect Slack?". The bot stops answering in your workspace. If Slack removes the app or revokes its tokens, admins get a "Slack needs reconnecting" notification and the Slack card shows "not connected". Click Add to Slack to install the bot again and resume.