Integrations
Using Dots in Slack and Teams (and Everywhere Else)
A Dot is not tied to one window. You can start work in ChatGPT, continue it in Slack or Teams, and eventually text it — and the context follows you.
Last verified: September 30, 2026 · Reviewed by AstraDot editorial desk
Most AI assistants live in exactly one place. Dots are designed to be reachable from wherever work already happens. OpenAI says you can talk to a Dot through ChatGPT on desktop, web, and mobile; through Slack and Teams; and — on a limited Pro waitlist — by texting over iMessage and RCS. Just as important, Dots carry context across those channels, so you are not starting from zero each time you switch.
This guide explains which channel to use for what, how to get set up in Slack and Teams, and the small routing habits that keep an always-on agent useful instead of noisy. For the underlying product, start with what OpenAI Dots are.
The channels you can reach a Dot from
Think of these as doors into the same room, not separate assistants. Each door is better for a different kind of moment.
| Channel | How it works | What it is best for |
|---|---|---|
| ChatGPT (desktop, web, mobile) | You reach out | Setup, review, and hands-on work. |
| Slack | Two-way, in a channel or DM | Team-facing updates and quick back-and-forth. |
| Microsoft Teams | Two-way, in a team or chat | Organizations that already run on Teams. |
| Texting (iMessage / RCS) | Limited Pro waitlist | On-the-go nudges, once you have access. |
How context carries across channels
A running theme in OpenAI's launch material is that a Dot works on projects, not single replies. Because it keeps context, a request you make in ChatGPT can be followed up in Slack without a long preamble. If you asked a Dot to turn raw customer feedback into tested pull requests, you can check status from a team chat instead of reopening the desktop app.
That continuity is the point, and it is also where discipline helps. Point a Dot at the specific project or thread you mean, and restate anything critical. Context carrying across channels does not mean every detail travels perfectly — and since Dots can make mistakes, confirm the important parts before acting.
When to use which channel
A simple rule of thumb: use ChatGPT when you need to see the work, Slack when the work belongs to a team conversation, and Teams when your organization already lives there. Texting is for short, mobile moments once you have waitlist access.
Deep work in ChatGPT
Setup, approvals, inspecting the Dot's computer and files, and anything where you want the full activity view in front of you.
Team work wherever the team is
Status updates, quick unblockers, and shared context in Slack or Teams, using the channel your colleagues already check.
Setting up Slack
Slack support is part of the Dots rollout to eligible plans. Once your Dot is live, you connect Slack through your ChatGPT workspace and the app controls you already use for the rest of the plugin ecosystem. In practice the work is: confirm your plan has access, connect the Slack workspace you want, choose channels or direct messages where the Dot should be reachable, and then check the activity view after the first exchange to confirm it behaved as expected. Because Dots connect to more than 4,000 apps, treat Slack like any other connection: add it because a task needs it, and scope it to the right channels.
Setting up Teams
Teams support follows the same model, aimed at organizations that run their day on Microsoft. You connect it through your workspace, and your admin's app controls decide what is available. This is also the world where specialist Dots and Microsoft Agent 365 matter: larger organizations will want governance and security controls wrapped around organizational agents. For a personal Dot, the setup is lighter, but the same principle applies — start with the narrowest connection that does the job.
The texting waitlist
Texting is the newest and least available channel. OpenAI says iMessage and RCS support is coming on a limited waitlist for Pro users. It is worth treating as a convenience channel rather than your main workspace: on-the-go prompts, quick confirmations, and short status pings. Availability, timing, and pricing for wider access are not published, so watch OpenAI's own documentation rather than relying on third-party dates.
Practical tips for routing work
- One project per thread. Keep a Dot focused on a named project so context does not blur across topics.
- Match channel to audience. If the output is for colleagues, ask in their channel; if it is for you, keep it in ChatGPT or a DM.
- Put approvals where you will see them. If a Dot needs your sign-off, route that to the channel you actually watch.
- Let the Dot message you. Dots can reach out; use that for long-running work instead of polling.
- Review the activity view regularly across channels — it is the quickest way to catch a Dot drifting.
Source: OpenAI, Introducing dots and the OpenAI help center, checked 2026-09-30. Unpublished details are marked as such.