Slack, Teams, and Soon Your Phone: Where Dots Actually Talk to You

The most consumer-relevant design decision behind Dots isn't the model or the permission system — it's the choice not to make dots live inside a single app. A dot runs on its own dedicated cloud computer, separate from any device, and OpenAI built multiple front doors into it rather than one: ChatGPT itself, Slack, Microsoft Teams, and — per the September 29 launch coverage — phone and text access with an audio model "coming soon."

What's actually shipped versus what's promised

Setting up a dot requires the ChatGPT desktop app or a browser, per 9to5Google's reporting on the launch; once created, a dot can be interacted with from the ChatGPT mobile app as well. Slack and Microsoft Teams integration are both live at launch — a deliberate choice to meet users in the tools where actual work conversations already happen, rather than requiring anyone to open a separate ChatGPT tab to check on a dot's progress. That's the single most practical decision in the whole launch: an always-on agent is only as useful as the notification surface it can reach you through, and Slack/Teams are where most knowledge workers already live during the day.

Text message and voice-call access, by contrast, are explicitly framed as forthcoming rather than shipped. MacRumors confirms text options are "coming soon," and the broader launch coverage frames an audio model for phone access the same way. Until those ship, a dot that needs to reach a user who's away from a keyboard — mid-commute, between meetings — has no channel to do it through, which is a real gap for the "keeps working after you close the tab and returns when things change" pitch OpenAI is making. A dot that finishes something important at 6pm and can only tell you inside ChatGPT is a dot whose most valuable moment — the moment it needs your attention — is gated behind you happening to check an app.

Why the plugin ecosystem matters more than the messaging channels

The communication channels get more attention because they're visible, but the deeper integration layer is OpenAI's plugin ecosystem, which connects dots to more than 4,000 applications, per VentureBeat's coverage. That's the difference between a dot that can tell you something happened and a dot that can actually do something in the tool where the work lives — updating a CRM record, pulling a file from a connected drive, posting a status update into a project management tool. Slack and Teams are notification and conversation surfaces; the plugin ecosystem is where a dot's actual task execution happens. The Plugin Ecosystem Behind Dots covers that layer in more depth.

The channel you reach a dot through and the tools a dot can actually act on are two different layers of the same product. OpenAI shipped the second layer broadly on day one; the first layer — especially phone access — is still catching up.

How this compares to the other two launches

Grok Bot takes a narrower but more immediately complete approach to reachability: it's available on desktop and iOS at launch, with users messaging bots conversationally through phone and desktop threads, according to sources reviewed for this series. Grok Bot on Desktop and iOS: What's Actually Shipped covers that rollout directly — notably, xAI shipped mobile access to Grok Bot roughly seven weeks before OpenAI's phone channel for Dots is even expected to arrive, giving xAI a real head start on the "reach me anywhere" front even with a comparatively plainer permission model underneath.

Meta's Muse, meanwhile, rolled out on iOS, Android, and the web at muse.ai from its September 8 launch, with hands-free glasses integration described as "coming soon" rather than shipped — a different bet on reachability entirely, one aimed at ambient, always-available interaction rather than meeting users inside existing workplace chat tools. Three companies, three different theories about where an always-on agent should actually surface, and none of them has yet shipped the complete vision they announced — Dots is missing phone access, Grok Bot lacks a confirmed formal safety framework for the credentials it uses across those channels, and Muse's glasses integration is still pending. The channel map for all three products is, as of this week, a work in progress rather than a finished feature set.

For anyone deciding which of these tools to actually adopt this quarter, the practical question is less "which vision is more ambitious" and more "which channels are live today, for the specific way my team already works." On that narrower question, Dots' Slack and Teams integration at launch is a genuinely strong opening move — it's just not yet the complete "reach me anywhere" story OpenAI is describing.

Why Slack and Teams first was the right call

It's worth pausing on why OpenAI chose Slack and Microsoft Teams as the first-class channels rather than, say, email or SMS. Both tools already function as the default notification layer for most knowledge work — they're where approvals happen, where status updates get posted, where a colleague would naturally ping you if something needed attention. Building a dot's primary interaction surface there, rather than forcing users into a dedicated ChatGPT tab, means a dot's updates arrive alongside the rest of a person's actual workday rather than in a separate silo competing for attention. It's a small design decision with outsized consequences for adoption: an agent that's easy to check in on casually, between other messages, gets used differently than one that requires a deliberate context-switch into its own app. Whether that same logic extends cleanly to a phone call — inherently a more intrusive, synchronous channel than a Slack message — once OpenAI ships it is a genuinely open design question, not a given.

Part 17 of 30 in the ChatGPT Dots series. Previously: Who Gets a Dot First: Pro, Business Premium, and the Eligibility Map. Next: Agent 365 and the Enterprise Path Microsoft Is Building for Dots. Browse more builder insights or explore AI skills at aiskill.market.