Slack Guide: Stats, Channels & Teams (2026)

Slack is not a social network, and it never tried to be one. But in 2026 it functions as a publishing surface in its own right: an internal newsroom for company updates, a customer-facing channel for release notes and support, and, for hundreds of large public communities, a de facto forum. If your content calendar includes anything that needs to land in a specific room full of specific people, on a schedule, without an algorithm second-guessing whether it gets seen, Slack is one of the few places left where that guarantee still holds.

This guide treats Slack as an adapted-angle platform: not a place to grow followers, but a channel worth scheduling into deliberately, alongside your social calendar. We cover how Slack actually works, what changed in 2025 and 2026, and where scheduled posting fits into real team workflows.

What is Slack?

Slack is a business communication platform organized around workspaces, channels, and threads. Teams use it for real-time messaging, file sharing, voice and video huddles, lightweight automation, and, increasingly, AI-assisted search and summarization. It was acquired by Salesforce for about $27.7 billion in a deal that closed in July 2021, and it now sits inside Salesforce's broader Agentforce and platform business rather than standing alone as a separately reported unit.¹

Unlike consumer social platforms, Slack has no public feed, no follower graph, and no discovery algorithm. Everything happens inside a workspace: a private, invite-only environment tied to an organization, a project, or, in the case of public developer and creator communities, an open topic. Distribution inside Slack is structural rather than algorithmic: post a message to a channel, and everyone in that channel sees it, in order, the same way a Telegram channel broadcasts to every subscriber (see our Telegram guide for the closest social-platform comparison).

Key Slack statistics in 2026

Slack stopped disclosing official daily and monthly active user figures after 2019, so every usage number below is a third-party estimate rather than a company-reported metric. We name the source for each one.

A few things worth flagging directly. The DAU and MAU figures are DemandSage's own modeling, not numbers Slack has confirmed; Business of Apps runs a similar exercise and lands in a comparable range, but neither should be treated as an official company disclosure.² The revenue figure comes from Salesforce CEO Marc Benioff speaking on CNBC's Mad Money in April 2026, where he said: "We're anticipating about $3 billion in revenue this year," and separately that Salesforce had "tripled revenue during that five year period" since buying Slack.³ Salesforce does not break Slack out as a standalone line item in its financial filings; it reports the business inside a combined "Agentforce 360 Platform, Slack and Other" segment, so Benioff's number is the most specific figure currently on record, not an audited disclosure.

Who uses Slack

Slack's install base skews toward technology and knowledge-work industries rather than the broad consumer spread of a platform like Facebook or Instagram. Business of Apps data on Slack's customer mix puts IT and services companies at roughly 46% of installs, computer software at about 20.9%, and staffing and recruiting at around 17%.⁴

Named customers span a wide range of company sizes and sectors: Amazon, PayPal, Target, Airbnb, Shopify, and Pinterest all use Slack internally, and IBM runs the largest single deployment on record, with all 350,000 employees on the platform.⁵ Slack Connect users, meaning companies collaborating with outside partners through shared channels, include Zendesk, Uber, Etsy, IBM, and T-Mobile.

At the top end, Slack says 77% of the Fortune 100 use the platform, and separately that 77 of the Fortune 100 use Slack Connect specifically to build what it calls a shared "digital HQ" with partners and customers.⁶ Those are two related but distinct claims worth keeping straight when citing them. Slack has also been expanding into more regulated industries through Enterprise Grid, its tier built for large organizations that need to link multiple connected workspaces under shared admin controls.

The customer profile splits fairly cleanly by company size and risk tolerance. Slack skews toward small and mid-market companies, developer teams, and agencies that value its interface and app ecosystem. Microsoft Teams, by contrast, dominates large, risk-averse enterprises that already run Microsoft 365 and get Teams bundled in at effectively no marginal cost. That split matters for anyone deciding where to invest scheduled-content effort: a startup or agency audience is more likely to actually see and act on a Slack message than a large traditional enterprise where Teams, not Slack, is the default inbox.

Enterprise Grid customers in particular tend to run Slack across multiple connected workspaces rather than one flat organization-wide space, which is part of why growth in regulated industries (finance, healthcare, government contracting) has leaned on Grid's centralized admin controls rather than a single shared workspace. That structure also affects scheduled posting in practice: a message aimed at "the whole company" in a Grid deployment often needs to be scheduled into several linked workspaces rather than one, since membership and channel visibility do not automatically span the full organization.

How Slack works

Everything in Slack sits inside a workspace, the container tied to a single organization (or, for public communities, a single topic or audience). Enterprise Grid can link multiple workspaces under one organization for large companies that need separate spaces for different business units while sharing some administration centrally.

Inside a workspace, conversation happens in a few structured layers:

• Channels: public or private rooms organized by team, topic, or project. Anyone added to a channel sees every message posted there, in order. This is the core distribution unit: reach in Slack is not driven by an algorithm, it is simply equal to channel membership.
• Threads: replies nested under a specific message, keeping side conversations out of the main channel timeline.
• Huddles: lightweight audio and video calls that can be started instantly from any channel or DM, with AI-generated notes available on paid plans.
• Canvases: persistent, collaborative documents that live inside a channel, used for pinned references, project briefs, or running notes that outlast any single message.
• Workflow Builder: a no-code automation tool, available on paid plans, that can post recurring scheduled messages to a channel, route form submissions, or trigger multi-step approval flows without custom code.⁷

Slack Connect extends this model across organizations: a single shared channel can include people from up to 250 different companies, provided both sides are on a paid plan. More than 100,000 customers now use Slack Connect, according to Slack's developer documentation, making it the platform's answer to cross-company collaboration that would otherwise happen over email.⁸

Beyond corporate workspaces, Slack also hosts a long tail of public community workspaces built around shared professional interests. Product School's community reports more than 100,000 product managers; the iOS Developers Slack has more than 40,000 members; PySlackers reports 38,600-plus; the MLOps Community sits around 27,900; and the DevOps Chat community reports about 26,000.⁹ These figures are self-reported by the communities themselves rather than independently audited, but they illustrate how Slack has become a genuine venue for open, topic-based communities, not just closed corporate workspaces, structurally similar to a large public Telegram channel or a niche Discord server (see our Discord guide for the closer community comparison).

Because there is no algorithmic feed anywhere in Slack, the entire distribution model reduces to one rule: a message reaches everyone currently a member of the channel it was posted to, in the order it was sent.

Message formats and limits

Slack messages can range from plain text to fully interactive layouts built with Block Kit, Slack's structured message format. A single Block Kit message can contain up to 50 blocks, and each text object within a block is capped at roughly 3,000 characters.¹⁰ A plain message's total text length can run up to 40,000 characters, and file uploads are capped at 1GB per file on every plan tier, including free.

Native scheduling works two ways. In the app, the message composer has a Schedule for later option built directly into the send button, letting anyone queue a one-off message for a future time. For recurring scheduled messages, teams need Workflow Builder, which is gated to paid plans. Developers building on top of the API get chat.scheduleMessage, which can queue a message up to 120 days in advance, subject to a rate limit of 30 scheduled posts per five-minute window per channel.¹¹

Bots and integrated apps post through incoming webhooks or the chat.postMessage method, both of which support a custom display name and avatar distinct from the posting user's own account. Slack's app directory lists more than 2,600 integrations, one of the deeper third-party ecosystems of any workplace tool.¹² On the free plan specifically, message and file history is capped at 90 days (content is hidden, then deleted, after that window), and a workspace can connect at most 10 apps, both meaningful constraints for teams trying to run Slack as a long-term archive or a broad automation hub without paying.¹³

Slack AI and the 2025-2026 platform changes

Slack went through two significant structural shifts in the past year, one commercial and one architectural.

The June 2025 pricing overhaul folded Slack AI into every paid plan rather than selling it as a standalone add-on. Business+ pricing moved from $12.50 to $15 per user per month, and Slack introduced a new Enterprise+ tier above its existing top tier. The Pro plan's list price stayed the same but gained access to core AI features it previously lacked. The standalone Slack AI add-on some customers had purchased separately was discontinued as part of the same change.¹⁴

Architecturally, Slack repositioned itself around agents. At Salesforce's Dreamforce conference in 2025, Slack announced what it called an "agentic OS" direction: a rebuilt Slackbot with genuinely conversational capabilities, a "Channel Expert" agent designed to answer questions using a channel's own history, and deeper integration for Salesforce's Agentforce agents to operate inside Slack conversations. Alongside this, Slack introduced a Real-Time Search API and a Slack MCP server intended to let third-party AI agents, including ones built by Anthropic, Google, and Perplexity, connect into Slack workspaces.¹⁵ Slack CMO Ryan Gavin framed the ambition plainly at the event: "Slack is the fastest platform for third-party agents being deployed in the industry."¹⁶ Then-CEO Denise Dresser described the broader push in similar terms: "Slack's agent-powered work operating system is redefining what it means to work smarter, not just differently."¹⁷

The other major 2025 change was a sharp API rate-limit crackdown, effective May 29, 2025, that specifically targets apps distributed outside Slack's official Marketplace. For those non-Marketplace, commercially distributed apps, the conversations.history and conversations.replies methods (the endpoints used to read message history) were cut to just one request per minute, returning at most 15 objects per request.¹⁸ Existing installs of affected apps were given a grace period, with the tighter limits taking full effect on March 3, 2026. Slack paired this with a Terms of Service update making the Marketplace the only sanctioned channel for commercially distributing an app, banning bulk export of message data, and prohibiting using API-retrieved data to train large language models.¹⁹

The important nuance, worth stating plainly rather than glossing over: this crackdown targets reading and exporting message history, not posting. The rate limits fall on the endpoints third-party tools use to pull conversation data out of Slack at scale, not on the endpoints used to send messages into it. chat.postMessage and chat.scheduleMessage were not part of the May 2025 changes. A tool built to schedule and publish content into Slack channels, rather than scrape and export existing conversations, sits outside the restricted surface. Internal custom apps built by a single organization for its own use, and apps that go through official Marketplace review, are also unaffected by the tighter limits.

One leadership note worth flagging as current only as of this writing: CEO Denise Dresser departed in December 2025 to become Chief Revenue Officer at OpenAI, and Slack's Chief Product Officer, Rob Seaman, has been serving as interim CEO since.²⁰

How teams use scheduled Slack posting

Scheduled messaging in Slack shows up in a handful of recurring patterns, most of which predate the AI push but have only gotten more automatable since Workflow Builder matured.

Internal comms calendars. Slack's own guidance for internal communications teams recommends pairing scheduled messages with Workflow Builder to keep a predictable cadence: weekly digests, leadership updates, and all-hands reminders that go out at the same time every week regardless of who is around to hit send.²¹ This is the most direct analogue to a social content calendar, just aimed at an internal audience instead of a public one.

Recurring rituals. Standup reminders, end-of-sprint check-ins, and recurring deadline nudges are common Workflow Builder use cases, since they need to fire on a schedule without a human remembering to trigger them.

Community management. Large public Slack communities, the kind with tens of thousands of members like Product School or the MLOps Community, use scheduled and recurring announcements in dedicated channels for event reminders, AMAs, and job-posting digests, functioning much like a moderated announcement channel in a large Discord server.

Changelog and release-notes distribution. Companies with customers on Slack Connect commonly push product updates and release notes directly into shared customer channels on a release cadence, rather than relying on customers to check a changelog page.

Cross-posting social announcements. Teams increasingly treat Slack as one more distribution leg for announcements that already exist elsewhere: a product launch post that goes out on X or LinkedIn also gets scheduled into the company's #announcements channel, timed for when employees are actually online, so staff can see it and amplify it rather than discovering it secondhand.

This is the posterly angle: Slack is not a platform you build a following on the way you would Instagram or X, but it is a channel with a guaranteed audience (everyone in that channel, no algorithm in the way) that deserves the same scheduling discipline as any other part of a content calendar. posterly's Slack scheduler lets you queue channel posts on the same calendar as your social platforms, so a release note, a community update, or a cross-posted announcement lands in Slack at the right time without a separate manual step. For more on how content needs differ by platform, see our platform-specific content guide.

The practical benefit of treating Slack this way is less about reach and more about reliability. A social post can slip a few hours without much consequence; a changelog message that misses a customer's business hours in a Slack Connect channel, or a company update that lands after most of the team has logged off, loses much of its value. Scheduling into Slack alongside the rest of a content calendar means the timing decision gets made once, in advance, rather than depending on someone remembering to open Slack at the right moment.

Slack vs Teams vs Discord

Three different tools, three different jobs, and worth being precise about where each wins.

Slack vs Microsoft Teams: Teams wins on raw scale and price, largely because it comes bundled into Microsoft 365 subscriptions many enterprises already pay for. Microsoft last disclosed Teams passing 320 million monthly active users in 2023 and has not updated the figure publicly since; Slack's user counts, by contrast, are all third-party estimates in the tens of millions of daily actives. Market-share trackers disagree on exact numbers depending on methodology, with some putting Teams around 37% of the team-collaboration market against roughly 13 to 18% for Slack.²² Slack tends to win on interface quality, its app ecosystem (2,600-plus integrations), developer-friendly culture, and external collaboration: Slack Connect's 250-companies-per-channel ceiling is more flexible than Teams' shared-channel equivalent, which most reviewers describe as more limited in practice.²³

Slack vs Discord: the common framing is that "Slack builds for productivity, Discord builds for community."²⁴ Discord's free tier keeps unlimited message history, offers always-on voice channels, and has a mature role and permissions system built for large, consumer-facing communities. Slack counters with enterprise-grade security and compliance, deeper AI features, and a stronger professional integration ecosystem, but its 90-day free history limit and per-user pricing make it expensive to run as the primary home for a huge free community. In practice, professional communities that gather around a specific industry or skill (product management, MLOps, iOS development) tend to accept that cost for the "this is where work already happens" advantage; purely social or gaming communities gravitate to Discord instead. See our Discord guide for more detail on that side of the comparison.

The bigger picture: Slack is simultaneously an internal comms channel, a B2B customer-facing channel through Connect, and a venue for open professional communities. Very few platforms are asked to do all three at once, which is exactly why treating it as a single scheduled-posting surface, rather than three separate ad hoc habits, tends to work better in practice.

Final word

Slack in 2026 is not trying to be a social network, and comparing its user counts directly to Instagram or TikTok misses the point of what it actually does. What it offers instead is something increasingly rare: a distribution surface with zero algorithmic interference, where a scheduled message reaches exactly the people in that channel, exactly when you send it. Between the June 2025 pricing overhaul folding AI into every paid tier, the agentic push introduced at Dreamforce, and a rate-limit crackdown that (by design) leaves posting untouched while tightening history exports, Slack's 2025 to 2026 changes mostly reinforce the same idea: it wants to be the place agents and humans both work, not just talk.

For teams already treating Slack as a real distribution channel, whether that is internal comms, customer-facing changelog delivery through Connect, or managing a public community, scheduled posting deserves the same planning discipline as any other platform in the calendar. If Slack is one leg of a broader content operation, posterly's Slack scheduler puts it on the same calendar as the rest of your channels; see our pricing if you're deciding how it fits your plan, or browse our other platform guides if you're still working out where to focus.