FlowOS in Slack and Teams

Mention @FlowOS. Work moves forward in the thread.

FlowOS reads the thread, understands what was said and answers in the conversation, right where your team already talks.

Request a demo →Read the setup guide

Available for Slack and Microsoft Teams, set up with your administrator.

Example in Slack. Works the same way in Microsoft Teams.

How it works

Three moves, no new tool.

01

Mention it

Write @FlowOS in an enabled channel or a direct message, or type /flowos in Slack. To pick an agent: agent:followup or /flowos followup <request>. FlowOS takes earlier messages in the thread into account.

02

Schedule it

A scheduled task posts its deliverable to a channel every day, week or month: the Monday review in #leadership, the Friday report in #sales.

03

Get the deliverable

A short answer lands in the thread. A long deliverable is saved as a FlowOS document, in the Slack or Teams folder, with a summary and the link in the thread.

How teams use it

A request in the thread, a deliverable in return.

Twelve ready-to-use agents. A few examples of what employees ask for every day.

Meeting minutes

Turn a thread into decisions and action items

After a meeting or a long discussion, FlowOS takes the notes and the thread and pulls out the decisions, the action items with their owners and the open questions. Nothing is added that isn't in the conversation.

@FlowOS agent:meeting

Features

All of FlowOS, in the conversation.

12 ready-to-use agents

If you don't name one, the FlowOS Assistant answers and tells you which agent to use next time. @FlowOS help shows the list.

FlowOS AssistantClient follow-upCommercial proposalTender analysisMeeting minutesSummaryTranslationProfessional emailMarket watchData analysisHR FAQClient meeting prep

Thread context

FlowOS reads earlier messages in the thread before answering: no need to explain everything again.

A shared resource

The answer lands in the channel: the whole team sees it, picks it up and builds on it.

Scheduled tasks in channels

Every day, week or month, a task posts its deliverable to an enabled channel.

Deliverables saved in FlowOS

Long deliverables become FlowOS documents, in the Slack or Teams folder, private if the request came from a direct message.

Customer context from the ERP

The client meeting prep agent reads the customer's FlowOS ERP record, filtered by your ERP role.

Same models, same rules

Agents use your FlowOS workspace's models: Europe-only mode applies when it's on, with the same usage caps.

Administration

Administrators stay in control.

  • Installed once

    In Slack, the administrator clicks Add to Slack from FlowOS. In Teams, they import the app and enter your Microsoft 365 organization ID.

  • Enabled channel by channel

    FlowOS only answers in enabled channels. A mention elsewhere is ignored and the channel shows up so it can be enabled in one click.

  • Default agent and direct messages

    The administrator picks the agent that answers when none is named and can turn off direct messages.

  • Recognized employees

    Each Slack or Teams account is linked to the FlowOS account by email address. Anyone else is asked to request access.

  • Everything in the audit log

    Every request is logged: who, in which channel, with which agent. A per-person request limit applies.

  • No training

    Thinking Platforms does not use any conversation to train models. Messages are only used to answer.

Good to know

What FlowOS doesn't do.

Attachments

Files attached in Slack or Teams are not read. Paste the text into the message.

No web access

Slack and Teams agents don't access the web: they work on what's in the thread and what you paste.

Never on its own

FlowOS answers when it's mentioned and posts scheduled tasks. It posts nothing else and never pings you unprompted.

Teams and scheduled tasks

In Teams, a scheduled task can only post to a channel after a first exchange with FlowOS in that channel. Scheduled posts go to channels, not direct messages.

Setup

Set up with your administrator.

Setup happens once for the whole organization. The setup guide covers the Slack and Microsoft configuration in detail.

Slack
  1. Your administrator opens FlowOS, Connections, Slack and Microsoft Teams, then clicks Add to Slack.
  2. They authorize the app in your Slack workspace and choose the channels to enable.
  3. They invite @FlowOS to each enabled channel.
  4. Employees mention @FlowOS, or type /flowos help to see the agents.
Microsoft Teams
  1. Your administrator imports the FlowOS app into the Teams admin center.
  2. They enter your Microsoft 365 organization ID in FlowOS.
  3. They enable channels, in one click from the list of channels where @FlowOS was mentioned.
  4. Employees write @FlowOS help to see the agents.

Request the setup guide

Your team already talks in Slack and Teams. FlowOS answers there.

A 30-minute demo, then setup with your administrator.

Request a demo →