Slack Just Got a Lot More Powerful: Channel Intelligence and Chat Come to WorkSights AI

Slack is where your team communicates. And if you pay attention to how people communicate — which channels they're active in, where conversations are happening, what's being discussed — you get a genuine signal about where attention and energy are going across your organisation.

Of course, for most knowledge workers, Slack is not where the work gets done. Your engineers are in GitHub and Jira. Your salespeople are in HubSpot or Salesforce. Tasks and Projects are tracked in Monday.com or Basecamp. Your team's documents live in Notion, Google Drive or SharePoint. But the conversations that connect all of that work — the decisions, the questions, the coordination — a lot of that happens in Slack. And until now, WorkSights AI couldn't see any of it.

That just changed.

The Slack 1.0 Connection

Before this upgrade, our Slack integration did two things:

Presence signals — every five minutes, WorkSights AI would check whether team members were active in Slack on desktop (deliberately filtering out mobile activity, which tends to be noise rather than signal). This gave leaders a reliable picture of working patterns and engagement across the day.

Notifications — WorkSights AI could deliver Observer alerts and reports directly into Slack, so leaders and managers didn't have to rely on email alone to stay across what the system was surfacing.

Both of those remain. What we've added on top is significantly more powerful.

New: Joining Channels to Understand Where Attention Is Going

WorkSights AI can now be configured to join your public and shared Slack channels — sitting quietly and building a picture of where communication activity is happening across the organisation.

A few things worth being clear about up front:

• Public and shared channels only. WorkSights AI will never join private channels or read direct messages. This is a hard boundary, not a configurable one.
• Admin-controlled, always. WorkSights AI never joins a channel automatically. As a workspace admin, you explicitly choose which channels to add it to — whether that's a specific handful or a broader selection. Nothing happens without a deliberate decision on your part.
• No disruption. When WorkSights joins a channel, Slack posts the standard system message — then it's invisible. No bot messages, no noise, no interruption to the channel's normal flow.

Two Privacy Modes

How WorkSights AI uses what it sees is also your choice. Admins can select one of two options:

Metadata only (default) — WorkSights captures that a person posted in a channel, but not what they said. No message content, just the signal: who is active, in which channels, and how often.

Even at the metadata level, this is genuinely useful. When the AI knows that your #customer-escalations channel has had a spike in activity from three specific team members over the past 48 hours, it can surface that pattern without ever reading a single message.

Full content — WorkSights captures the actual message content from the channels it has joined, adding it to the AI memory layer that powers both Observer insights and Chat. This enables much richer qualitative intelligence — understanding not just where people are focused, but what they're discussing, deciding, and working through.

The choice is yours. It applies only to channels WorkSights has been configured to join, and you can change it at any time.

New: Chat with WorkSights AI Directly from Slack

The second major upgrade is something leaders have been asking for since we bought AI Chat into WorkSights AI: the ability to ask WorkSights AI questions directly from Slack, without switching to the web app.

It works the same way as chat in the WorkSights AI web interface. You ask a question — in a WorkSights-connected channel or via direct message — and the system automatically assembles the relevant context from its memory in the cloud. If it doesn't have enough information from your initial message, it will ask clarifying questions until it knows what to do. You don't pull files, attach reports, or manually provide background. It just works.

You can ask questions like:

• "What has the engineering team been focused on this week?"
• "Where has Sally been focused on in the last 2 weeks? I need to prep for our 1:1 meeting ASAP!"
• "What are the main pull requests we've been working on over the past two weeks?"

And you get a real, contextual answer — grounded in what's actually happening across your business, not a generic AI response.

One Conversation, Two Surfaces

Here's the part that makes this genuinely useful rather than just convenient: the conversation history is unified.

Chat threads you start in Slack appear in the WorkSights AI web app. It's one continuous conversation history you can go back to land search for — not two separate systems that happen to look similar.

In practice, this means you can start a thread from your phone while you're out, pick it up on your laptop when you're back at your desk, and the full context is there either way. No re-explaining, no context-switching cost.

What This Adds Up To

WorkSights AI already pulls signals from the tools where work gets done — Google Workspace, Microsoft 365, GitHub, Jira, HubSpot, Notion, Zoom, Basecamp, Monday.com. Each of those adds another layer to the picture of how your business is actually operating.

This upgrade adds the communication layer. The conversations happening around the work. Where attention is being directed. What teams are talking about and coordinating on.

Combined with the Observer Agents that watch continuously across all of that data, and the Chat interface that lets you ask questions of it on demand, this is a meaningfully more complete picture than was possible before.

If you're already a WorkSights AI user, channel joining and Slack chat are available now in your settings. If you'd like to see how it works for your business, get started here.

‍