Skip to content

Use case: internal knowledge

An internal knowledge assistant that answers your team in Slack

Train an intoCHAT agent on the Notion pages and Google Drive files where your policies, how-tos and product notes already live. Colleagues ask it in a direct message or with an @mention, and it answers in the thread from those documents, so the people who wrote them get fewer interruptions.

Example: a question in #ask-ops

Visitor: @intochat how many unused vacation days can I carry over into next year?

Agent: According to the Time off policy, you can carry over up to 5 unused vacation days. They have to be taken by 31 March; days carried over after that date expire.

Visitor: @intochat and if my manager asked me to postpone my vacation because of a project?

Agent: The policy doesn’t cover postponed vacation for project reasons, so I can’t confirm an exception. HR decides these cases. Do you want me to pass this conversation to the HR team by email?

The answers are written down. People still ask a colleague.

How many vacation days carry over? Which VPN client do we use on a new laptop? What is in the enterprise plan, and can sales promise SSO? Most companies have written the answers somewhere: an HR handbook in Notion, an IT setup guide in Google Docs, a pricing sheet in Google Sheets. But searching three tools in the middle of a task feels slower than asking in Slack, so the questions land on the same few people in ops, HR, IT and product, again and again. An internal knowledge assistant moves that first answer to the place where people already ask. It only works if it answers from your real documents, stays in the thread instead of flooding channels, keeps up when a page changes, and leaves room for a person when the documents don’t cover the question. That is the workflow below, built on the Slack agent and the Notion and Google Drive sources in intoCHAT.

What changes for your team

The documents stay where they are. The questions get a first answer where they are asked.

  • Answers where people already ask

    Colleagues send the app a direct message, or mention it in a channel it was invited to. The reply goes into a thread under the question, so busy channels stay readable.

  • One assistant across Notion and Drive

    Import the HR handbook from Notion, the IT guide from Google Docs and the price list from Google Sheets into the same agent. Nobody has to know which tool a page lives in.

  • Fewer repeat interruptions for experts

    The people who know the answers see the questions their documents already cover answered without them, and step in only for what the documents leave open.

  • Gaps in your docs become visible

    Questions the agent struggled with are collected on the Knowledge tab, so you know which page to write or fix next instead of guessing.

  • A person is still one step away

    When the documents don’t cover it, the agent can hand the conversation to your team, and a teammate can answer in the same Slack thread from intoCHAT.

The workflow in intoCHAT, step by step

  1. Create a dedicated internal agent

    Start a separate agent for internal knowledge instead of reusing your customer-facing one. Write instructions for colleagues: the tone, who to contact for what, and what to say when the documents have no answer. A Slack workspace answers for one agent, so this agent becomes your workspace’s assistant.

  2. Import your Notion pages

    On the Knowledge tab, choose Notion under Add knowledge, connect the workspace and tick the pages you shared with intoCHAT, up to 25 per import. Subpages are separate pages, so select them too. Database entries can be imported one by one.

  3. Pick your Google Drive files

    Choose Drive under Add knowledge, connect Google Drive and pick up to 10 files at a time: Docs, Sheets, Slides, PDFs, Word, text or Markdown. intoCHAT can open only the files you pick, nothing else in your Drive. Add files, Q&A pairs or public website pages if you need them (pages behind a login can’t be crawled).

  4. Add the agent to Slack

    On the Share tab, click Add to Slack on the Slack card and allow the app in your workspace. Invite it to the channels where questions come up with /invite @intochat. Colleagues can also open the app under Apps and message it directly.

  5. Keep the documents in sync

    Turn on auto-resync on the Knowledge tab, daily or weekly. Notion pages edited since the last read are read again, and Drive files modified since the last check too; only changed text is retrained. For an urgent change, click Sync now on the Drive option or import the Notion page again.

  6. Review the threads and close the gaps

    Slack threads appear on the Conversations tab with a Slack badge. Check Questions to improve on the Knowledge tab, then fix the Notion page or Drive file and resync it, or add a Q&A pair for an answer that must be exact.

Setup checklist and limits

  • Plan and permissions

    The Slack agent is available from Starter. Installing needs permission to add apps to your Slack workspace, and connecting Slack or Google Drive needs the owner or an admin in intoCHAT.

  • What is read from your documents

    From Notion: headings, text, lists, tables and toggles, but only captions of images and files, and only the title property. From Drive: Docs, Slides, PDFs, Word, text and Markdown, and up to 1,000 rows per sheet.

  • Characters per agent

    All sources count toward the agent’s character limit: 100,000 on Free, 500,000 on Starter and 1,000,000 on Pro. An import that would go over it is refused as a whole, so your knowledge stays as it was.

  • Not a permissions system

    Everyone who can message the app gets answers from all of the agent’s knowledge. It doesn’t check who may see which page. Leave out confidential material such as salaries, HR cases or contracts.

  • Keep the agent off public pages

    A private agent doesn’t answer in Slack, so this agent stays public and its direct link works for anyone who has it. Don’t embed it on a public website, and leave its Help Page switched off.

  • Text in, text out

    The agent reads the text of Slack messages; files and images posted in Slack are ignored. Forms, booking and source links aren’t shown in Slack. API actions, procedures and hand-off by email work as in the widget.

  • Volume and messages

    A workspace can send the agent up to 300 messages an hour. Each AI reply counts on your plan like a widget reply: 1 message with the default model, more with a larger model. Your team’s replies don’t count.

  • What Slack data is read

    Only direct messages to the app and messages that mention it. intoCHAT doesn’t read other channel messages or import your Slack history. Per conversation it stores the messages and the Slack user ID and display name.

Frequently asked questions

What is an internal knowledge assistant in Slack?

It is an AI agent your colleagues ask in Slack instead of searching several tools or interrupting a colleague. With intoCHAT you train it on your own Notion pages, Google Drive files and other documents, add it to your workspace, and it answers direct messages and @mentions in threads from that content.

Can it answer from Notion and Google Drive at the same time?

Yes. Both are sources of the same agent, next to uploaded files, Q&A pairs and website pages. Notion is connected per intoCHAT account, so you pick from the pages you shared with intoCHAT. With Google Drive, intoCHAT can open only the files you choose in Google’s file picker. On some installations the Notion option isn’t offered; you can then export pages from Notion as Markdown or PDF and upload them as files.

Does it stay up to date when we edit a page?

Imported text doesn’t change by itself. Turn on auto-resync, daily or weekly: Notion pages edited since the last read and Drive files modified since the last check are read again, up to 30 of each per run, and only changed text is retrained. You can also click Sync now for Drive or import a Notion page again at any time.

Can I restrict which employees see which documents?

No. The Slack agent is not a permissions system: anyone in the workspace who can message the app gets answers from all of the agent’s knowledge, and anything in its knowledge can end up in an answer. Import only what everyone who can reach the app may read, and keep confidential documents out.

Can I make the agent private so only my team can use it?

Not while it answers in Slack. A private agent doesn’t answer in Slack, and the “Only verified visitors can chat” setting would stop the Slack replies too. Keep the agent public, don’t add it to a public website, and leave its Help Page off, which is how it starts.

What happens when the documents don’t have the answer?

Write in its instructions what to do, for example name the right team or channel. With hand-off by email on, the agent offers to pass the conversation to your team, and it enters the Inbox. A teammate can reply from intoCHAT: the answer is posted in the Slack thread with their first name, and the AI pauses on that thread for 24 hours.

Will it read our channels or our Slack history?

No. It only receives direct messages to the app and messages that mention it in channels it was invited to. In a thread, each question needs a new mention. It doesn’t import past messages, and files or images posted in Slack are ignored.

Which plan do I need and what does it cost?

The Slack agent starts on Starter at $19 a month with 2,500 messages, 3 agents and 500,000 characters per agent. Pro costs $49 a month for 10,000 messages, 10 agents and 1,000,000 characters per agent. Each AI reply in Slack counts as 1 message with the default model, 2 with Claude Sonnet or Gemini Pro and 5 with Claude Opus.

Give your team answers from your own docs, in Slack

Create an agent free, import a few Notion pages or Drive files and test it in the Playground. Upgrade to Starter to add it to your Slack workspace.

Create your agent free

Free plan, no credit card needed.