Field notes. John Arndt, Soxoa. Published .
A small business rarely needs another place to ask questions. It needs the proposal checked, the handoff prepared, or the outstanding decisions gathered before Friday. OpenAI's dots are relevant because they are designed to keep working between conversations.
OpenAI describes a dot as an ongoing agent with its own cloud computer and browser, capable of research, document preparation, and data analysis while your computer is off. This guide uses the official documentation checked on September 29, 2026; the examples below are proposed pilots, not results from Soxoa client deployments. Meet dots.
Check access before planning around it
Rollout is gradual. OpenAI lists Pro 100, Pro 200, and Pro 500 for users over 18 outside the EEA, UK, and Switzerland; Business Premium and Enterprise are rolling out worldwide. Enterprise requires administrator enablement. An eligible plan does not guarantee immediate access. Work and Codex tasks use their respective allowances; check current limits before budgeting recurring work. Availability and access.
Create your dot on desktop. App connections, messaging channels, and local computer access are separate choices. Start with the sources needed for your first assignment. Using local files or apps through a connected computer requires that computer to be online with ChatGPT open. Getting started.
Three responsibilities worth evaluating
Choose work where a person can recognize a good result quickly. Confirm that the necessary apps and actions are available in your account before connecting live business information. These examples describe the responsibility to test, not a promise that every integration is supported.
- The Monday operations brief
- Give the dot an approved job-status sheet and meeting notes. Ask for overdue items, missing owners, and the decisions needed this week, with a source beside each item. Have your operations lead check the brief before the team meeting. Track missed issues and the time spent correcting it.
- The proposal consistency check
- Provide a draft proposal, approved scope, and rate sheet. Ask for inconsistencies in dates, quantities, deliverables, and totals. Require a list of questions when records disagree. Keep pricing decisions and customer delivery with the person responsible for the account.
- The supplier decision packet
- Provide comparable quotes and a short list of requirements. Ask for a comparison that preserves delivery dates, exclusions, and unanswered questions. Review the original quotes alongside the output. The useful result is a shorter decision meeting, with no purchase or supplier contact included in the assignment.
Give the first assignment an end date
An illustrative starting instruction: 'For the next two Mondays at 8:30 a.m. Pacific, read only the approved job-status sheet and notes in this project. Prepare a one-page brief with overdue work, missing owners, and decisions due this week. Link each finding to its source. Put uncertain items in a questions section. Save the brief here; do not contact customers, change records, or make purchases. Confirm the schedule and stop after the second brief.'
Review the first output before allowing a second run. If someone must reconstruct the whole brief to trust it, narrow the assignment or improve the source records. Record setup time, review time, errors, and the manual baseline in the automation assessment worksheet.
Know how to review and stop the work
OpenAI's controls distinguish instructions, plugin permissions, and optional custom rules. A request to draft does not authorize sending. Rules can require approval for an action, but they are not an error-proof guarantee. Review tasks in Activity and recurring work in Scheduled. Control your dot.
Pause stops the dot's current main task. Delegated tasks and future scheduled runs need separate attention; stopping work does not undo completed actions. Make that distinction part of the handoff to whoever owns the pilot. Stopping work.
Expand only when the first job is useful
At the end of the pilot, compare accepted output, review effort, and recurring cost with the existing process. Continue when the work is more reliable or takes less effort after review. Revise or stop when it adds another queue to manage.
Soxoa's Live Build Workshop can help a team choose the workflow, test approved examples, and leave with a named owner and written operating steps. Schedule a strategy call with one recurring task you want to improve.
Common questions
- What should a small business give a dot first?
- One bounded responsibility with approved source material, a concrete output, a reviewer, and an end date. An internal brief or a comparison of supplied documents makes the result easier to evaluate.
- How should we measure a dots pilot?
- Compare accepted results, missed issues, correction time, and recurring cost with the manual process. Count the effort needed to review the output as part of the work.