OpenAI Dots examples: three tasks to explore

People have reported using a Dot to track projects, investigate an email problem and assemble a subscription inventory. These examples can help you choose a small first task, but they are creator reports rather than our own execution tests.

We reviewed the linked original posts on October 10, 2026. Start with information you can check, a specific output and a clear limit on actions the assistant may take. Check the access and tools available in your own account before trying a workflow.

Keep track of the projects you start

Tiffany Kyazze, posting as @TechTiffai, says her Dot tracks the projects she starts. Her September 30 post establishes that reported use, but does not describe an integration, update schedule or completeness test.

For a small trial, provide three current projects and ask for a table showing the goal, next step and any missing information. Then check every row against your own notes. This is an editorial suggestion for making the task reviewable, not Tiffany's original prompt.

Suggested prompt: “Use these three project notes to make a status table. Separate stated facts from guesses, include the next action for each project and ask about missing information. Do not change any project files.”

Read the original creator post

View the credited gallery entry

Investigate an email issue before taking action

Sean McLellan, @Oceanswave, reports connecting his Dot, HAL 9000, to email. He says it noticed a potential charge concerning an Amazon return and handled the dispute, then created a Personal Scratchpad.

The post does not provide an audited dispute transcript, approval history or confirmed refund. Treat the reported result as one person's account. A useful first trial is to identify the relevant messages and draft a response you can inspect.

Suggested prompt: “Review the messages I provide about this return. Summarize the dates and claims with links or message references. Draft a reply for my review and identify anything uncertain. Do not send it or make account changes.”

Use only the messages needed for the trial. Check the original order and correspondence yourself before approving any response; the example does not establish which email provider or account configuration will work for you.

Read the original creator post

View the credited gallery entry

Build a subscription inventory

Nate, @natebjones, reports using Dot to assemble a list of subscriptions across home and work. He then describes using Muse for the follow-up work. The inventory step is attributed to Dot; the later outcome belongs to a combined workflow.

We have not verified the claimed financial result. Start with a list you can reconcile against receipts or statements, and keep cancellation decisions separate from discovery.

Suggested prompt: “From these receipts, list each subscription, its billing interval, latest stated charge and source reference. Mark missing or conflicting information. Do not cancel subscriptions, contact providers or change billing settings.”

Check whether each item is still active, whether its amount includes taxes and whether its billing interval is clear. An annual estimate from incomplete receipts should be marked as an estimate rather than presented as a confirmed saving.

Read the original creator post

View the credited gallery entry

Choose an output you can verify

A status table, referenced email summary or receipt-backed inventory gives you something concrete to review. Define completion before starting: which records must be covered, which uncertainties must be flagged and which actions require your approval.

Browse the credited Dots gallery for more reports. For task-specific tools, read the separate Codex skills installation guide. A Codex skill listing does not establish that it works inside Dots.