ChatGPT DotsUndisclosed

A property manager hands marketing and inbox work to ChatGPT's Dot: article updated, drafts cleared, audits set up - then it says a quote was accepted while the email sits in drafts

anthonyaluna(Reddit 用户 u/anthonyaluna,物业管理公司经营者,原帖作者本人)Reddit · 2026-10-01

Read original

Saved text / editorial summary

原帖正文(Reddit r/AI_Agents,作者 u/anthonyaluna,原帖 Atom 源显示发布日期 2026-10-01;本轮经 Reddit 公开 Atom feed 取得全文,逐字,未经改写): “I run a property management business and spent months building agents in Codex. I’ve spent the past couple of days putting ChatGPT's newest tool, Dot, to work. It updated a live HubSpot article, cleaned up old Outlook drafts after checking for sent replies, and configured site audits and keyword tracking. Then it told me I’d accepted a quote. The email was still in my drafts. It’s also brought back requests I’d already answered. I’ve had to ask what happened to unfinished assignments. Sometimes it’s a browser timeout or sign-in. Sometimes Dot has simply lost track of the work. That’s the new-hire feeling. I have to remember the history and check the follow-through while doing my own work. I’m going to keep testing. I want the time saved to include the time I spend checking the work. What have you handed to your Dot that you don’t have to keep chasing?” 中文对照:他经营一家物业管理公司,之前花几个月在 Codex 上搭过 Agent,最近两天把 ChatGPT 的新工具 Dot 投入实际工作。Dot 更新了一篇已上线的 HubSpot 文章,在检查过是否已有发出去的回复之后清理了 Outlook 里的旧草稿,并配置了站点审计与关键词跟踪。然后它告诉他「你已经接受了一份报价」——而那封邮件还躺在草稿箱里。它还把已经回复过的请求又带了回来。他不得不追问那些未完成的指派后来怎么样了。作者归因:有时是浏览器超时或登录失效,有时是 Dot 自己弄丢了进度。他的总结是这感觉像带新人:他得一边做自己的活儿,一边记住历史并检查它到底有没有做完。他会继续测,但他希望「省下的时间」里要包含他花在检查上的时间。

Business model

Reddit user u/anthonyaluna runs a property management business and spent months building agents in Codex before putting ChatGPT's newest tool, Dot, to work over a couple of days. What worked: it updated a live HubSpot article, cleaned up old Outlook drafts after checking for sent replies, and configured site audits and keyword tracking. What went wrong is more instructive: Dot told him he had accepted a quote, while the email was still sitting in his drafts. It also brought back requests he had already answered, and he found himself asking what happened to unfinished assignments. He attributes this partly to browser timeouts or sign-in failures and partly to Dot simply losing track of the work. His summary is blunt: it feels like having a new hire, where he has to remember the history and check the follow-through while doing his own job. He will keep testing, but he wants the time saved to include the time he spends checking the work. No revenue, client count or cost is disclosed.

The value here is its failure surface: an agent's done and a person's done are not the same thing. The author's own example is a claim that a quote had been accepted while the email sat unsent in drafts - not a glitch but a mismatch in what done means. Requiring evidence for every completion is the minimum bar for handing out this kind of work, and the author himself says the checking time has to count against the saving.

Workflow

  1. Run one task category at a time; do not spread across all of them at once.
  2. Define done as done-with-evidence before starting anything. (AgentFlow's addition; the original post has no evidence mechanism.)
  3. When clearing drafts, check for an already-sent reply first, then decide.
  4. Anything outward-facing - published content, commitments - waits for a human.
  5. End every run with an explicit list of unfinished items. (AgentFlow's addition; the original post only says he had to chase them.)
  6. Separate timeouts and sign-in failures from lost context; they need different responses.
  7. Count the checking time as part of the cost before deciding it is worth it.

Adaptation plan

The post gives no revenue, no client count, no price, no token spend and no time figures. It does not say how many drafts were involved, how the HubSpot edit was verified, or whether the site audit configuration actually took effect. The evidence-for-completion rule is credited to a commenter's suggestion in the thread, not to something the author says he implemented. The workflow, prompt, synthetic example and pitfalls here are AgentFlow's proposals, untested.

Prompt

AgentFlow draft · Untested.

You are my marketing and inbox maintenance assistant. You may draft, clear, configure and query. You do not publish outward-facing content, you do not send outward messages, and you do not accept or commit to any quote on my behalf. Every completion you report must carry evidence I can check.

[INPUT]
This run's category: [content update / draft clearing / site and keyword configuration, one at a time]
Content update: target article [title or link]; scope [sections or points]; evidence form [published link plus before and after]
Draft clearing: scope [mailbox and folder]; check requirement [look for an already-sent reply first]; evidence form [per-draft conclusion plus sent message id or no reply found]
Site configuration: items [site audit / keyword tracking]; evidence form [confirmation screenshot or API response plus next run time]
Left to me: publishing outward content, sending outward messages, accepting or declining any quote, verifying evidence

[EXECUTION STEPS]
1) Restate this run's category, target and evidence form; begin after that is acknowledged.
2) Execute by category: update only the stated scope; when clearing drafts check for sent replies before deciding; configure only the given items.
3) Attach evidence to every output: what changed, what the evidence is, where I can check it. Anything without evidence is reclassified as not done.
4) On a sign-in failure or page timeout, retry once and record it honestly; if it recurs, stop, add it to the unfinished list and state why.
5) If context has been lost - if you no longer know how far the task got - do not guess and continue; restate the context from the start.
6) End every run with a completed list with evidence, an unfinished list with the blocking step and reason, and items needing my confirmation.

[OUTPUT]
- Completed: item plus evidence plus where to check it.
- Unfinished: item plus the blocking step plus reason (sign-in failure / timeout / context lost / no evidence).
- Pending confirmation: anything I must publish or send, listed and marked not published or not sent.
- No completed entry may appear without evidence.

[HUMAN CONFIRMATION]
- Do not publish or push any outward-facing content; finished edits stay in draft until I publish.
- Do not send any email or message and do not reply to any request.
- Do not accept, decline or commit to any quote or commercial term; write those as pending.
- Do not delete drafts whose evidence is missing; if the check is inconclusive, keep them and list them as unfinished.

[FAILURE AND MISSING INPUT]
- Sign-in failure or timeout: retry once, then stop and record; do not keep retrying.
- Context lost: restart from the beginning; do not continue from memory.
- An item without evidence is reclassified as not done, never reported as done.

[SYNTHETIC EXAMPLE - not real data, format only]
Input: category draft clearing; scope example mailbox drafts; evidence form per-draft conclusion plus sent message id or no reply found
Output (completed): draft D-01 / checked / a sent reply exists msg-9001 / cleared; draft D-02 / checked / no reply found / kept for me to handle
Output (unfinished): draft D-03 / blocked at checking sent mail / reason sign-in failure, one retry also failed
Output (pending): D-02 needs my decision whether to reply / not sent

Running costs and pitfalls

The post gives no revenue, no client count, no price, no token spend and no time figures. It does not say how many drafts were involved, how the HubSpot edit was verified, or whether the site audit configuration actually took effect. The evidence-for-completion rule is credited to a commenter's suggestion in the thread, not to something the author says he implemented. The workflow, prompt, synthetic example and pitfalls here are AgentFlow's proposals, untested. No independent cost benchmark is available. Check subscriptions, permissions and external actions before running a workflow.

Author-reported results are not independently audited.

Original text and media remain attributed to their authors.