OpenAI Dots for Enterprise: Always-On Agents, Missing Admin Console (2026 Review)
OpenAI Dots brings always-on GPT-6 Astra agents to ChatGPT Pro and Business plans. We review pricing, safety, and the specialist-dots gap for IT leaders.
TLDR: OpenAI Dots, launched at DevDay on September 29, gives every Pro and Business Premium user a persistent GPT-6 Astra agent with its own cloud computer, 4,000+ app connectors, and read-only background research - at no extra charge. For individual power users, that’s a strong deal. But the enterprise story is unfinished: the org-managed “specialist dots” are in invite-only pilots with no GA date, no published pricing, and no admin console, and the Microsoft Agent 365 governance integration is a press release, not a product. If you’re an IT leader, treat Dots as sanctioned shadow AI until specialist dots ship - set a policy now, because your Pro users already have it.
Why This Matters Now
OpenAI didn’t launch a feature on September 29. It launched a new employment model for software: agents that keep working after you log off. Dots arrive three weeks after Meta’s Muse, four days after Microsoft’s Copilot overhaul, and inside the same month as major Salesforce and Amazon agent launches. Five platforms are now competing to own the “always-on coworker” slot in your org chart.
But here’s what the launch-day coverage skipped: the version of Dots your employees got yesterday and the version your IT team can actually govern are two different products. The first is live. The second doesn’t exist yet. That gap - between availability and governability - is the whole story for enterprise buyers, and it’s what this review is about.
Dots at a Glance: How It Compares
| Dimension | OpenAI Dots | Meta Muse | Microsoft Copilot (Autopilot) | Salesforce Agentforce |
|---|---|---|---|---|
| Launch date | Sept 29, 2026 | Sept 8, 2026 | Sept 25, 2026 | 2024 (mature) |
| Underlying model | GPT-6 Astra | Undisclosed | Frontier models + Work IQ | Atlas reasoning engine |
| Runtime | Dedicated cloud computer per dot | Per-user VM + Sentinel permissions | M365 graph-grounded | Salesforce platform |
| App connectors | 4,000+ via ChatGPT plugins | Connectors (count undisclosed) | M365 + third-party | Salesforce-native + MuleSoft |
| Access channels | ChatGPT, Slack, Teams, voice calls | iOS, Android, muse.ai, WhatsApp | Teams, Office, Windows | Slack, Salesforce UI |
| Enterprise admin story | Pilots only, no console | Early | Agent 365 governance (GA) | Full (established) |
| Entry price | Bundled in Pro/Business Premium | Free tier available | M365 license required | Usage-based (Flex credits) |
| Data grounding | Connected apps (unstructured) | Connected apps | Work IQ / governed graph | Data Cloud |
| Best for | Individual power users today | Consumers + early adopters | M365-standardized orgs | Salesforce-centered orgs |
The Personal Dot: What’s Actually Live
Every Pro ($200/month) and Business Premium ($100-125/seat/month) user gets one dot included at no extra cost, rolling out now in eligible markets. Enterprise workspaces can try a beta, but only if the workspace admin enables it. Setup happens in the ChatGPT desktop app or desktop browser: you name your dot (it gets an @yourname-agentname handle), connect your apps, and it introduces itself.
The dot runs on its own cloud computer with its own browser. You can open that computer any time and watch it work. It carries context across ChatGPT, Slack, Teams, and voice calls, so a project that starts on desktop continues in a Slack thread without re-explaining anything. Conversations with your dot don’t count against ChatGPT usage limits - though tasks it kicks off in Codex or ChatGPT Work bill normally.
The standout capability is “proactive research.” When you’re not actively working with it, your dot scans already-connected apps in read-only mode - it can’t send messages, change content, or drive your browser. OpenAI’s own example: an early tester’s dot noticed an uninvoiced publication, drafted the invoice, and sent it after approval. That’s the dream in one anecdote.
Where the personal dot earns its keep
For a senior IC or a founder-type operator, a persistent agent that holds state across days is a genuine step past chatbots. The old pattern - re-prompting ChatGPT every morning with yesterday’s context pasted back in - dies with this architecture. The cloud computer means work continues while you’re in meetings, and Activity View gives you an audit trail of background actions to review.
But don’t mistake “always-on” for “autonomous.” Dots ship with built-in rules for when to act and when to ask, plus Custom Rules you configure yourself. Certain sensitive actions - changing a password is OpenAI’s example - always stay with you. And OpenAI’s own documentation says it plainly: “Dots can still make mistakes, so always review consequential work.”
Earned insight: The “first dot free” framing is doing heavy lifting. OpenAI extended higher usage limits for the first month after launch only - after that, your plan’s “allowance for deeper work” applies, and additional dots or faster output will cost extra under undisclosed pricing. In three enterprise AI rollouts I’ve watched, day-one free allowances always become the anchor for budget fights in quarter two. Get the overage pricing in writing before you standardize on Dots, because right now there is nothing to put in writing.
Personal Dots Strengths:
- Persistent cloud computer holds multi-day state - no more re-prompting context every session
- 4,000+ app connectors on day one, the largest launch-day integration surface of any agent in the September wave
- Read-only proactive research is a genuinely conservative default for background autonomy
- Dot conversations don’t consume ChatGPT usage limits
Personal Dots Weaknesses:
- “Extended limits” expire after the first month; steady-state allowances and multi-dot pricing are undisclosed
- Excludes EEA and Switzerland at launch - a non-starter detail for multinationals that launch coverage buried
- Saved-password login means your credentials live in OpenAI’s cloud computer, not just your vault
- No team visibility: Activity View is per-user, so managers can’t see what employee dots are doing
Specialist Dots: The Enterprise Product That Isn’t Shipping
This is the section that matters most, and it’s the shortest - because there’s almost nothing to review.
Specialist dots are OpenAI’s answer to the enterprise question: agents with their own identity, credentials, IT-provisioned hardware, and deep integrations with systems of record, taking on defined responsibilities like procurement, invoice processing, email marketing, customer support, and commercial contracting. OpenAI says it’s building on internal testing across exactly those functions.
But specialist dots are in “focused enterprise pilots” where “engineering teams will work directly with organizations to define each dot’s responsibilities.” Translation: white-glove onboarding, no self-serve path, no published timeline, no pricing, no admin console you can log into today. If you want one, you email OpenAI and hope.
The Agent 365-shaped hole
OpenAI also announced it’s “working with Microsoft to integrate specialist dots with their enterprise governance and security controls in Agent 365.” Read that sentence twice. It’s a partnership intent, not a shipped integration. Microsoft’s Agent 365 governance layer is real and generally available - but Dots doesn’t plug into it yet. Until it does, there is no SSO-scoped provisioning, no conditional-access policy, no DLP boundary, and no eDiscovery story for anything a dot touches.
Warning: Your employees’ personal dots can already read connected Slack, Teams, and email data in background mode. Without an admin console, you cannot inventory which apps your org’s dots can reach, cannot revoke a dot when someone leaves, and cannot see an exfiltration event if a dot is prompt-injected through a connected app. Treat every personal dot in your tenant as an unsanctioned OAuth grant with read access to collaboration data - because functionally, that’s what it is.
Specialist Dots Strengths (on paper):
- Per-dot identity and credentials is the correct enterprise primitive - closer to a service account than a chatbot
- IT-provisioned hardware option addresses data-residency objections that kill most cloud-agent deals
- Systems-of-record integrations (procurement, invoicing, contracting) target real back-office cost centers
- Agent 365 integration, when it ships, would inherit the strongest governance layer in the market
Specialist Dots Weaknesses (in practice):
- Invite-only pilots with no GA date - you cannot buy this today at any price
- No published pricing for specialist dots, additional personal dots, or speed scaling
- No admin console, no SCIM provisioning, no offboarding path disclosed
- Agent 365 integration is pre-shipment; Copilot Autopilot already lives inside that governance boundary
The Safety Model, Read Skeptically
Credit where it’s due: OpenAI published more safety architecture on day one than most agent vendors manage in a year. Each dot runs on an isolated cloud computer. Saved passwords authenticate sites without exposing credentials to the model. Proactive research is restricted to read-only tools. Auto-review checks consequential actions against your instructions and Custom Rules before executing. A monitoring system can pause or stop a dot mid-task. Business, Enterprise, and Edu workspace content isn’t used for training by default.
But three things in the fine print deserve your attention. First, “we don’t train directly on proactive research or your dot’s notes to itself” is followed by “information from them may be used if it helps inform an eligible conversation” - a carve-out wide enough to drive a compliance review through. Second, the sandbox model assumes the threat comes from outside instructions; it says less about a compromised connected app feeding a dot malicious content through a trusted OAuth channel - which is exactly how the Hugging Face rogue-agent incident earlier this month played out, and which had OpenAI shelving a model days before DevDay. Third, none of these controls are administrable. A safety architecture your IT team can’t configure, monitor, or audit is a consumer safety architecture wearing enterprise clothes.
Earned insight: The early-tester sentiment is splitting exactly along the line I’d expect. On r/OpenAI, the top reaction called Dots “designed by unserious people living in a complete bubble to (badly) automate aspects of being a human that no one wants automated” - harsh, but it names the real adoption risk: employees who didn’t ask for an always-on observer. Meanwhile, a hands-on tester who ran Dots and Muse side by side for a day recommended Muse to most people. When the launch-week enthusiasts prefer the competitor, the enterprise upsell gets harder, not easier.
Pricing Reality: The TCO Nobody Published Yet
Here’s every number OpenAI has confirmed as of September 30, 2026, and what it actually costs to run Dots in a 500-person org.
| Cost layer | Published figure | Source / verified |
|---|---|---|
| First personal dot | Included in Pro / Business Premium at no extra cost | OpenAI announcement, Sept 29 |
| ChatGPT Pro | $200/user/month | OpenAI pricing (long-standing) |
| New Pro 500 tier | $500/month (adds Ultrafast 300 tok/s for Codex/Work) | DevDay announcement, Sept 29 |
| Business Standard seats | $25/user/month ($20 annual) | OpenAI, Aug 2026 |
| Business Premium seats | $100-125/user/month | Third-party pricing trackers, Aug 2026 |
| Enterprise | ~$60/seat, quote-only | Third-party pricing trackers, Aug 2026 |
| Additional dots / speed scaling | Undisclosed (“in the future”) | OpenAI announcement |
| Specialist dots | Undisclosed (pilot only) | OpenAI announcement |
| GPT-6.1 Sol API (agent workloads) | $2/M input, $0.10/M cached, $10/M output | DevDay announcement, Sept 29 |
| Steady-state “deeper work” allowance | Undisclosed after first-month extension | OpenAI announcement |
Now the math your CFO will ask for. A 500-person org on Business Premium at $100/seat is $50,000/month before a single dot does anything. That’s the floor, and it’s already 4-5x the Standard-seat cost - justified only if dots displace real labor. OpenAI’s Pro 200 plan simultaneously had its usage allowance cut (per TNW’s DevDay coverage), which means heavy users face a forced choice between throttling and the $500 Pro 500 tier - a 2.5x jump for speed, not capability.
But the TCO trap isn’t the seat price. It’s the review labor. Every dot action on consequential work needs human review - OpenAI says so explicitly. Budget five minutes of reviewer time per accepted task at a $60/hour loaded cost and 100 tasks per user per month, and you’re adding $500/month in human oversight per active user. The seat is the cheap part. The supervision is the product.
Tip: Don’t roll Dots into your Enterprise agreement renewal yet. Run a 30-user pilot on existing Business Premium seats (the dot is already included), instrument review-time per task for 30 days, and bring that number - not OpenAI’s demo - to your renewal negotiation. You need your own cost-per-supervised-task before committing seats at 4-5x Standard pricing.
Who Should Use Dots - and Who Should Wait
Good fit: Individual power users already paying for Pro or Business Premium - researchers, founders, senior engineers, and operators who live in Slack and can supervise an agent’s output. If your threat model tolerates a cloud computer holding your connected-app credentials, the day-one bundle is genuinely useful. Small firms without an IT gatekeeper function can adopt fastest, since there’s nothing to govern yet.
Not a good fit: Regulated industries (healthcare, financial services, EU-headquartered firms - the EEA exclusion alone ends the conversation), orgs that require SSO provisioning and offboarding for every identity with data access, and any team that needs eDiscovery or DLP coverage over agent activity. If your security questionnaire asks “list all third parties with persistent read access to our collaboration data” and your answer would include “each employee’s personal dot, which we can’t inventory” - you’re not ready.
Bottom Line
Dots is the best personal agent OpenAI has ever shipped and the least governable enterprise product in the September launch wave. The persistent cloud computer, the 4,000-connector surface, and the conservative read-only default for background work are real engineering achievements - Meta’s three-week head start notwithstanding. For the individual practitioner, the included dot is the strongest argument yet for a Pro or Premium seat.
But StackScout writes for the person who has to answer the CISO’s questions, and on those questions Dots fails today: no admin console, no GA date for specialist dots, no published multi-dot pricing, no Agent 365 integration, no EEA availability, and a training-data carve-out your privacy counsel will flag. Microsoft’s Copilot lives inside your existing governance boundary right now. Agentforce lives inside your Salesforce boundary. Dots lives inside OpenAI’s cloud, administered by your end users.
Rating: 4.3 / 5 for individual power users on Pro or Business Premium. 2.4 / 5 for enterprise IT buyers evaluating an org-wide agent platform today - revisit when specialist dots reach GA with published pricing and the Agent 365 integration ships.
Your 30-day action: publish an interimDots policy before your next security review - allow personal dots on Standard seats only, prohibit connecting email and HR systems until specialist dots ship, and start a 30-user Premium pilot with review-time instrumentation so your renewal negotiation runs on your numbers, not OpenAI’s demo.
FAQ
Does OpenAI Dots integrate with Salesforce?
Not directly. Dots reaches workplace tools through ChatGPT’s 4,000+ app plugin ecosystem plus native Slack and Teams messaging - and since Salesforce owns Slack, a dot can operate inside your Slack workspaces, which the WSJ’s CIO coverage specifically flagged. But there’s no native Salesforce app, no Data Cloud grounding, and no Agentforce interoperability announced. If your agents need to read and write CRM records with field-level security, Agentforce remains the only option in this comparison that inherits Salesforce permissions natively. Revisit if the specialist-dots program announces a systems-of-record connector for Salesforce.
How much does OpenAI Dots cost for enterprise?
Your first personal dot is included in ChatGPT Pro ($200/user/month) or Business Premium ($100-125/seat/month) at no extra charge, with extended deeper-work limits for the first month. Enterprise workspaces (~$60/seat, quote-only) get a beta gated on admin enablement. Everything beyond that - additional dots, speed scaling, specialist dots, steady-state work allowances - has no published price as of September 30, 2026. For TCO planning, model the seat plus roughly $500/month per active user in human review labor (100 tasks at 5 minutes each at $60/hour loaded cost).
Is OpenAI Dots available in Europe?
No - not at launch. Dots rolled out in “eligible markets” that exclude the EEA and Switzerland, per launch-day comparison coverage. OpenAI hasn’t published a timeline for European availability. For EU-headquartered or GDPR-constrained orgs, this is a hard blocker, not a roadmap item: you can’t pilot what you can’t provision. Microsoft Copilot and Agentforce both ship with EU data-residency options today, so European buyers should evaluate those first and revisit Dots when regional availability is confirmed.
How is OpenAI Dots different from Meta Muse?
Both are always-on agents with dedicated cloud runtimes, but they diverge on distribution and enterprise posture. Muse launched September 8 with a free tier, mobile-first apps (iOS, Android, muse.ai, WhatsApp), and 2.8 million downloads that beat ChatGPT’s early growth pace. Dots is paid-only (Pro/Business Premium/Enterprise), lives inside ChatGPT, Slack, and Teams, and leads with a 4,000-app connector ecosystem and a named model (GPT-6 Astra). Neither has a mature enterprise admin story, but early hands-on testers have favored Muse for general use. Enterprises should note Muse’s Sentinel permission layer vs. Dots’ Custom Rules plus auto-review - different names for the same unsolved problem of scoping agent autonomy.
Can IT admins control or monitor employee Dots?
No - and this is the single biggest enterprise gap. There is no admin console, no SCIM provisioning, no org-wide policy control, and no offboarding path for personal dots. Activity View shows background work per user only. Workspace content in Business, Enterprise, and Edu plans isn’t used for model training by default, which helps, but your IT team cannot inventory which apps your org’s dots can reach or revoke access at scale. The promised remedy - specialist dots managed through Microsoft Agent 365 governance - is in invite-only pilots with no GA date.
What model powers OpenAI Dots?
GPT-6 Astra, OpenAI’s flagship model positioned around cybersecurity and agentic capabilities. DevDay also introduced GPT-6.1 Sol, a cost-efficient sibling at $2 per million input tokens and $10 per million output tokens - under a quarter of Astra’s price with near-comparable agentic coding and computer-use performance, per OpenAI. Expect future dots to route routine background work to Sol-class models while reserving Astra for complex tasks; that routing decision will determine whether per-task economics work at org scale. Our standalone GPT-6 Astra review covers the model’s enterprise profile in depth.
Should we wait for specialist dots or pilot personal dots now?
Pilot personal dots now, on a contained basis - don’t wait. Specialist dots have no GA date, and the employees with Pro seats already have personal dots whether you’ve sanctioned them or not. The right move is a 30-user pilot on existing Business Premium seats with three guardrails: Standard seats only outside the pilot, no email or HR system connections until specialist dots ship, and instrumented review-time tracking so you learn your true cost per supervised task. That data becomes your negotiating leverage when specialist dots reach GA and OpenAI’s sales team comes calling.
Related Articles
Discussion