OpenAI Dots: What Always-On AI Agents Could Mean for Small Businesses

OpenAI announced dots at its September 29, 2026 DevDay event — persistent AI agents designed to keep working toward a goal you've set, in the background, rather than sitting idle until you send the next message. Each dot can be reached from ChatGPT (desktop, web, mobile), Slack, and Microsoft Teams, and OpenAI says it carries context across those channels. That's a real shift from a one-off chat session, but 'always-on' is not the same as 'unsupervised': OpenAI's own documentation describes a tiered approval model, and the most sensitive actions — changing a password, transferring money — always require you to take over and complete them yourself, not the dot.

What OpenAI Dots Are

A dot is OpenAI's term for a persistent agent: instead of a conversation that ends when you close the tab, a dot keeps a running context and continues pursuing whatever goal you've given it, checking in, taking action within its permission settings, and picking back up later rather than forgetting everything between sessions. OpenAI frames this as a shift from reactive chat toward agentic work that continues on its own timeline, not yours.

How Dots Differ From ChatGPT-Style One-Off Sessions

A normal ChatGPT conversation is bounded: you ask, it answers, the context is specific to that thread. A dot is designed to persist — maintaining context about an ongoing objective across multiple sessions and channels (ChatGPT, Slack, Teams), and continuing to work in the background between the moments you actually interact with it. The practical difference for a small business is less about any single answer being smarter and more about not having to re-explain the same ongoing objective every time you open a new chat.

What 'Always-On' Means in Practice

'Always-on' means the dot keeps working on its assigned objective continuously rather than going dormant between prompts — not that it acts without any checkpoint. Every source reviewed for this article describes the same shape: a dot can research, draft, monitor, and prepare work continuously, but the tiered approval model (below) still governs whether and how it actually executes an action that affects your accounts, your data, or your money. This article does not describe dots as fully autonomous employees, because that's not what OpenAI's own permission model describes either.

What a Business Might Delegate

• Ongoing monitoring: tracking a recurring data source or inbox for something that needs attention, rather than someone manually checking it on a schedule.
• Draft preparation: research briefs, meeting prep notes, and recurring report drafts prepared ahead of when they're actually needed.
• Cross-platform coordination: pulling context from multiple connected tools to prepare a recommendation, similar in spirit to Meta's Muse for Small Business (covered in our dedicated article) but built on OpenAI's own connector ecosystem rather than Meta's.
• Recurring, low-stakes drafting work: content ideas, summaries, and first-pass drafts that a human reviews before anything goes out.

What Should Stay Behind Human Approval

OpenAI's own tiered model does most of this work for you, but it's worth knowing the actual tiers rather than assuming a default: changing a password or transferring money always requires you to personally take over — a dot cannot complete these even at the most permissive setting. Permanently deleting data or installing software may require approval each time, regardless of your general settings. A purchase using a card saved on a merchant's site requires your approval, though that approval can be granted in advance for a specific, defined purchase. For anything else, you choose per action type: take action without asking, take action if pre-approved, ask before taking action, or hand off to you — meaning the right posture is deliberately configured, not assumed.

CRM and System-of-Record Architecture

A dot's own memory of an ongoing objective is not the same thing as your business's actual CRM or system of record. Nothing in the sources reviewed for this article describes dots as a replacement for dedicated CRM software — connecting a dot to a CRM-adjacent tool (through whatever connector that tool offers) is what would let a dot read or act on real customer records, and that depends entirely on the specific connector's own scope, not on dots' general capability. Treat a dot's own internal context as working memory for an ongoing task, and your CRM as the durable record a business can actually report on and rely on later.

Tool and Connector Dependencies

OpenAI's own figure of 4,000+ connected apps is a real, if OpenAI-sourced, number — but a large connector count doesn't mean every connector offers the same depth of access. What a dot can actually do inside any specific tool (read-only summary vs. full read/write) depends on that tool's own connector implementation, which this article has no way to verify exhaustively across thousands of apps. Before building a workflow around a specific connector, check that tool's own documentation or settings for exactly what access a dot has been granted, rather than assuming parity across every connected app.

Cost, Permission, and Governance Considerations

Practical Examples by Industry

• Real estate: a dot monitors inbound inquiries and prepares follow-up drafts and research summaries for an agent to review, rather than replacing the agent's own judgment on each lead.
• Ecommerce: recurring campaign and product-performance analysis prepared on a schedule, so a weekly review starts from a draft summary instead of raw dashboards.
• Professional services: document review prep, meeting-prep notes, and recurring summary drafts assembled ahead of when they're actually needed.
• Home services: scheduling preparation and customer follow-up drafts queued for a human to send, not sent automatically.
• Marketing: recurring performance reporting and creative research prepared continuously rather than compiled manually before each meeting.
• Operations: vendor comparison research, task monitoring, and internal status drafts — again, prepared for review, not acted on unsupervised for anything sensitive.

None of these examples assumes native, verified integration with any specific CRM, scheduling tool, or accounting platform — that depends entirely on what connectors are actually available and what access they grant, which a business should confirm directly rather than assume from dots' general app-count claim.

The Required Architecture

The honest shape of this system: a business objective goes to a dot (native OpenAI capability); the dot pulls context from whatever tools it's connected to (connector-dependent, scope varies by tool); it does ongoing work toward that objective (native capability, bounded by the permission tier you set); sensitive or exception-level actions hit an approval/hand-off gate (native capability, with hard limits OpenAI enforces regardless of your settings); and anything that should persist as a business record still needs to land in an actual CRM or system of record (external workflow architecture — not something a dot provides on its own). Labeling each piece this way matters, because conflating 'dot capability' with 'what my business's other systems already do' is the most common way a tool like this gets overstated.

Where NextFlow Fits

A persistent AI agent is only as useful as the systems behind it — a CRM that actually tracks what it drafts, a follow-up process that doesn't drop a lead, and analytics that show what's really happening. NextFlow's AI Solutions, CRM & Automation, Lead Generation, and Website & Landing Pages services are built for exactly that gap, whether the agent doing the drafting is a dot, a Copilot, or a Muse.