We’re introducing Qontext Tag, a new way to ask questions about your company’s knowledge directly in Slack. Tag @Qontext in a channel or thread, and it answers from your context repository, where Qontext keeps your company knowledge structured and current. You can ask follow-up questions in the same thread, and everyone in the channel can follow the conversation.

Many questions that come up at work have already been answered somewhere. A customer commitment is recorded in your CRM, an onboarding process lives in a document, or a decision was made in an earlier Slack conversation. But when someone needs that information, they still have to find it or ask a colleague for help. Even a straightforward question can leave a conversation waiting while someone looks for the answer.

We built Qontext Tag to make that information easier to reach. Qontext already gives agents access to your company’s context. With Qontext Tag, your team can ask questions against that same knowledge from a tool they use throughout the day. It is available in early access, starting with Slack.

Working with Qontext Tag

Once Qontext has been added to a channel, you can mention @Qontext whenever you need information from your context repository. It searches the information it has access to and responds in a thread where you asked. If you need more detail, continue the conversation. Follow-up questions keep the context of the thread, so you don’t have to explain the background again.

For example, a colleague preparing for a customer call could ask, “@Qontext what did we agree on for the Acme renewal?” and then follow up with a question about a specific commitment. Someone working on an RFP could ask whether there is a standard response to a SOC 2 question. A team discussing a new enterprise customer could look up the relevant onboarding steps while working through the handover.

These are questions that often depend on information spread across several tools. Qontext Tag answers from the knowledge brought together in your context repository, giving the team a way to consult it without leaving the discussion. Because the reply is shared in the thread, colleagues can read the answer and ask for clarification themselves.

Slack conversations can also become part of that knowledge. By connecting selected channels as a data source, you can sync messages and thread replies into your repository so Qontext can use them in future answers. This is configured separately from Qontext Tag. Adding the app to a channel does not automatically make its conversation history available for retrieval.

Access and privacy

Administrators control which information Qontext Tag can access. In Qontext, an admin can define its scope down to individual folders and files, using the same approach as access controls for API keys. This lets you make selected company knowledge available through Slack while keeping other parts of the repository outside the tag’s reach.

Answers are visible to everyone in the channel where the question was asked. When setting up Qontext Tag, administrators should choose an access scope appropriate for the channels where it will be used.

Qontext Tag is read-only. It reads from the permitted parts of your context repository and posts its own replies in Slack. It does not change repository content or edit or delete Slack messages. To add or update context, you can use the Qontext app, API, or an MCP client.

In Slack, Qontext only sees channels it has been added to. Data is encrypted in transit and at rest, and your data is never used to train or fine-tune AI models. More information is available on our security page.

Getting started

Qontext Tag is available in early access. To enable it for your workspace, contact support@qontext.ai. You will need a Qontext workspace and a Slack administrator or member with permission to install apps.

Once enabled, open Clients in the Qontext app, select Qontext Tag, and click Add to Slack. Review and approve the requested permissions, and have a Qontext administrator configure which folders and files the tag can access. Then invite Qontext to the appropriate channels by typing /invite @Qontext. Your team can start asking questions by tagging @Qontext.

For the full setup instructions, see our Qontext Tag documentation.