Can a ChatGPT Dot be your AI secretary? 36 real daily catch-ups by phone, Slack and overnight (OpenAI Dots)

The short version: what a Dot can carry as your daily secretary, how to set it up, where it gets stuck

Is a Dot worth it as an AI secretary?

Yes for the daily pile of small follow-ups, and not yet for anything urgent or anything you can't check afterwards. In the cases below it pays off most in two ways. First, it turns a quick call or message into a written status: rengaku-ai2's eight commute calls each came back as done, in progress and not started (case 1), and Michael Wall cleared his inbox on one call while doing chores (case 26). Second, it catches what slipped: a forgotten email deadline on day one (case 3), a speaking date the organisers moved without telling Harry McCracken (case 34), a client's retainer commitment found in a call transcript (case 38) and a buyer's financing change buried in a title company's email (case 39). It can also finish a job once you approve it, such as Katie Fifer's QuickBooks invoice (case 5) and Ryan Mish's urgent client form (case 30). It falls short on speed, on showing exactly what it did, and on approvals that don't reach a task it split off. It suits people who already run their day through email, a calendar and Slack or Teams, and who will read a short list each day and approve every send themselves.

How to set it up

1. Check your plan and create the Dot on desktop. A Dot comes with Pro outside the EEA, UK and Switzerland, with Business Premium, and with Enterprise once an admin switches it on (How to get ChatGPT Dots). After it exists, your phone is for messaging and calling it (Getting started).
2. Look over what is already connected to ChatGPT before you create it. A new Dot starts from those apps: 中島大介's Dot was reading his Gmail a minute after it was created (case 19), and a Dot can review connected information and form memories from it even when you haven't asked (Getting started with your dot). For a secretary, Gmail, Google Calendar and Slack are the usual set; add Google Drive when forms and proposals come from your files (cases 5 and 30), and Notion if your meeting notes live there (case 37). Every connection is in the integrations hub.
3. Set your rules once instead of repeating them in every message. On mobile, open Customize, then Custom rules, and set sending, deleting, calendar changes and payments to "Ask before taking action", as 中島大介 advises (case 19). A clear "send it" with a clear recipient may count as approval, while "draft it" is never sent.
4. Tell it how to report: the one decision it needs from you first, then what's done, what's in progress and what's waiting on you, each with a link to the source. Pick one place to review the pile, such as Roland's review pages, Lukas Parolin's nightly pages or Hiromi Ohsugi's project subpages (cases 2, 8 and 37).
5. Say what not to notify you about as clearly as what to watch. Paul J Lipsky's Dot messaged him about every new email until he told it to stop and keep the other watches (case 28).
6. Save the daily sweep as a schedule with a time zone and an end date, and ask the Dot to read it back. Scheduled runs and proactive updates appear in the conversation; to change a run's repeat, time or completion notifications, open it from Recent activity in the Dot's profile or from the Scheduled section in ChatGPT, and review the result even when a run is marked completed (Getting started with your dot). For the same sweep every morning, see the morning brief.
7. Start with a small test: "List today's calendar conflicts and one email that needs a reply, and draft nothing yet." Then use calls, Slack or Teams for status and quick approvals while you're away, and keep long drafts in ChatGPT, where you can open the files.

Where it gets stuck, and what worked

1. An approval that never reaches the task. rengaku-ai2's yes didn't carry into a task the Dot had split off, so he asked for the same booking four times and it took about seven hours (case 1). What worked: open the Dot's profile in the desktop app, find the task under In progress, and answer any pending decision, approval, sign-in or connection request there; if the Dot is paused, resume it from the ••• menu (Getting started with your dot).
2. Reports that are long, cautious or vague. rengaku-ai2's reports came back full of caveats (case 1), AI Bri kept checking status herself (case 18), and だい had to ask again whether a job had been accepted, started or finished (case 36). hasegori (@hasegorilla) (13 Oct) found that running several Dots in parallel scattered the topic and blurred the real progress. What worked: ask for the conclusion and your next action first, ask for a status list with those three labels instead of a summary, and give each job one Dot.
3. Too many pings. Paul J Lipsky's Dot repeated alerts his email app already sent (case 28). What worked: put "don't message me about ordinary new mail" in the same ask as the watches you do want, and ask the Dot to confirm what it will and won't notify you about.
4. No record of what it changed. u/Ok_Barracuda_1161's Gmail cleanup worked, but there was no log of individual actions (case 21), and Ryan Mish found it hard to see what had stopped the Dot when something failed (case 30). What worked: after a cleanup, ask the Dot to list everything it moved or changed, and ask for a source link next to every item it reports.
5. Slow pickup, big files and overnight usage. Mark Nguyen's PDF request took about 50 minutes to be picked up (case 16), Kyle Chalmers kept urgent work away from his Dot and gave it a file path when a clip of 20 MB or more wouldn't attach (case 27), and Roland ran out of credit overnight (case 2). Talking to a Dot doesn't count toward ChatGPT usage limits, but Work or Codex tasks it starts do (Meet dots). What worked: hand it background jobs, not live ones, and scope overnight handovers to what you have already approved (case 10).
6. Details it fills in on its own. Mark Nguyen's Dot assumed Gmail when his mail ran on Zoho (case 16), and Katie Fifer's Dot broke a Zoom link while editing a calendar invite (case 5). What worked: name your mail provider and tools up front, check edited invites the first few times, and when materials aren't published yet, tell it not to invent dates or URLs, as 工藤 晶 did (case 35).
7. Relying on it to catch everything. The unasked catches in these cases came from email checked against the calendar, chat history and meeting transcripts (cases 20, 22, 24, 34, 38 and 39), and Allie K. Miller warns that teams shouldn't rely on AI alone to catch conflicts and errors (case 23). What worked: treat what it raises as a second pair of eyes, and keep your own check on deadlines and bills.
8. Work it hands to other chats that you have to redo. Wayne Duan found that the prompts his Dot wrote for its other task chats read like relayed requests (case 33). What worked: ask the Dot to critique and rewrite those briefs before it starts the tasks, and point it at work another tool already finished, as だい's Dot reused what Claude Code had done (case 36).

What it can do, and what it can't yet

What it can do:

• Turn a call or a Slack message into a written status of what's done, in progress and waiting on you.
• Read your email against your calendar and meeting transcripts, and raise clashes, moved dates, forgotten replies and commitments without being asked.
• Sort a brain dump into Today, This Week and Waiting, and draft the follow-ups for you to review.
• Keep a set of pages for projects, reviews or a diary up to date on a schedule.
• Fill a form or an invoice from your files and email, then send it once you approve.
• Keep open tasks moving overnight within what you've approved, and report in the morning.

What it can't do yet:

• Call you; you start every call.
• Show a step-by-step log of what it changed, unless you ask it to list its actions.
• Answer fast enough for live chat or urgent work.
• Take a chat attachment of 20 MB or more; Kyle Chalmers gave it a file path instead (case 27).
• Promise it will catch every deadline or bill.

One message to start with

Be my daily secretary for the next [4] weeks. Every weekday at [8:00] [time zone], check my email since yesterday, my calendar for today and tomorrow, my Slack DMs and [my meeting notes in Notion]. Send me a short list here: first the one decision you need from me, then what's done, what's in progress and what's waiting on me, then clashes, moved dates, forgotten replies and anything someone says I committed to, each with a link to its source. Check for newer replies before calling something outstanding, and say what you couldn't confirm. Don't message me about ordinary new mail. Draft replies where they're needed, but don't send, pay, delete or change my calendar until I say yes. Confirm the schedule you saved.

Quick answers

Can a ChatGPT Dot work as an AI secretary?

Yes, for the daily pile. rengaku-ai2 called his Dot Ciel eight times on the way home over four days, and each call landed in the chat as done, in progress and not started (case 1). From her phone, Katie Fifer had her Dot invoice a customer in QuickBooks after it matched the amount in an email to the contract (case 5). After a red-eye flight, Ryan Mish's Dot found an urgent client form, filled it in from Google Drive and waited for his approval before replying (case 30).

How do I check in from my phone?

Call it or message it. ChatGPT, Slack, Teams and calls all reach the same Dot with the same memory, so a request made on a call shows up in the chat later (Meet dots). At launch you start every call; the Dot can't call you. Michael Wall reached inbox zero on one call while doing chores (case 26). If reports come back long and cautious, ask for "the conclusion and what I need to do, first", as rengaku-ai2 did. To reach it from work chat, see Dots + Slack and Dots + Teams.

Will it send email or change my calendar without asking?

Only if you let it. Under Custom rules each kind of action can be set to "Take action without asking", "Take action if pre-approved", "Ask before taking action" or "Hand off to you" (Getting started with your dot). When 中島大介 asked, his Dot said a clear "send it" with a clear recipient may count as approval, while "draft it" is never sent; the default for a new rule was "Ask before taking action" (case 19). Ryan Mish approved the client form before it went out.

Will it catch things I didn't ask about?

Often, from apps it can already read. Vicky Zhao's Dot prepped two back-to-back calls before she said what they were (case 22), Dr. Matheus Rabahi's found a task missing from his calendar by checking email against it (case 24), 日沼諭史's spotted a meeting whose email details didn't match the calendar entry (case 20), and Harry McCracken's caught a speaking date the organisers had moved without telling him (case 34). This background reading doesn't send messages or change apps (Dots privacy FAQs). Meeting transcripts count too: Sarah Rose Siskind's Dot checked a call transcript against email and found that a client had already committed to that month's retainer (case 38). Allie K. Miller's warning still applies: keep your own check on deadlines and bills (case 23). For the same sweep at a set time each morning, set up a morning brief.

Which plan and apps do I need?

A Dot comes with Pro ($100, $200 or $500 tiers) outside the EEA, UK and Switzerland, with Business Premium in any supported region, and with Enterprise once an admin switches it on (How to get ChatGPT Dots; in Europe, see Dots in the EU and UK). Most catch-ups here run on Gmail, Google Calendar and Slack. Add Google Drive when forms and proposals come from your files, as they did for Ryan Mish and Katie Fifer. A new Dot starts from what is already connected to ChatGPT: 中島大介 had Gmail and GitHub connected, and his Dot was reading his Gmail a minute after it was created. Every other connection is in the integrations hub.

Checking in by phone and voice

1. Four days as a work secretary, eight calls on the commute (rengaku-ai2 / Ciel)

Japanese creator rengaku-ai2 (5 Oct 2026) used a Dot named Ciel (シエル) as an AI secretary at work for four days. He called it on the way home to hand over jobs or ask "where is this at?", and the call's content arrived in the chat as a summary split into done, in progress, and not started. He called eight times, and all eight calls were reflected in the work that followed. In three days Ciel split his requests into 22 separate sessions on its own. Together with his own local assistant, the four days covered at least nine replies (sent only by him or when he explicitly asked), a two-step booking, notes from about 220 minutes of recordings, and an eight-hour overnight run that left a draft plan, a diagram, and a short report by morning.

What went wrong: his approval did not carry into a task the Dot had split off, so he asked for the same booking four times and it took about seven hours. Reports tended to be over-cautious and full of caveats, so he now asks up front for "the conclusion and what I need to do, first". Calls sometimes took about ten seconds to connect.

2. "Tasks are dead": calls a few times a day and comments on review pages (Roland)

Roland (@rolandnyamoga) called his Dot his chief of staff on 30 Sep 2026: it builds on everything he already had in Codex, makes pages for product walkthroughs, and is there to call and brainstorm. A day later he wrote that he calls it a few times a day to catch up and give new instructions, and he no longer opens tasks one by one. The Dot makes a page for everything he needs to review; he adds comments and it responds. The cost: he ran out of credit overnight.

3. A forgotten email deadline on day one (Leo Tohyama)

On his first day with Dots, Leo Tohyama (1 Oct 2026, Japanese) got a warning from his Dot about an email deadline he had forgotten, before he noticed it himself. From there it went from checking his mail to drafting replies, used work files stored on his Mac mini, ran a work chat and brought the result back, and he recorded real voice calls with it from his iPhone. His verdict after 22 minutes of footage: for him, it's a secretary.

4. CI failures and event arrival details, asked from the phone (@teemingchew)

@teemingchew (4 Oct 2026) juggles several products and asks his Dot from his phone to investigate CI failures, coordinate fixes, and follow through. It also flags things he would miss, such as the arrival instructions for an upcoming event. Having context across work and life is what keeps him on Dots.

5. A day of ops from the phone, including QuickBooks (Katie Fifer / Technically Curious)

Katie Fifer and Claire Morrison (4 Oct 2026) already had email, calendar, and Google Drive connected. From her phone in one day, Katie's Dot invoiced a customer in QuickBooks after matching the amount in an email to the contract, resolved two scheduling conflicts, drafted a customer proposal from notes and recent proposals, and handled smaller jobs such as forwarding a message and sending an interview invite. In the same write-up, a Zoom link broke while the Dot edited a calendar invite, some forwards went out as .eml attachments that looked like spam, and logins still stalled.

Turning a brain dump into a plan

6. A messy to-do list sorted into Today, This Week, and Waiting (A2ZAI / Norm)

A2ZAI (4 Oct 2026) gave his Dot Norm a to-do list that was really a brain dump. Norm sorted it into Today, This Week, and Waiting, and drafted the messages for him to review. The video shows the drafts only; nothing was sent or cancelled.

7. Out of Notion: ideas, reminders, monthly goals, and deliveries (ashe)

Ashe Magalhaes (@ashebytes) posted a nine-minute screen recording on 4 Oct 2026 about how the Dot is "lifting me out of notion". In the shorter reel she pushes ideas to it for triage, has it remind her of things like calling her East Coast doctor, keeps three high-level goals for the month, and, back in San Francisco, has it schedule deliveries, pickups, and Uber Couriers and add calendar events. She is willing to trade short-term bugginess for a system whose integrations and context hand-off she trusts, and can see herself using it for three months.

8. Pages for life, projects, and a diary, updated every night at 23:30 (Lukas Parolin)

Lukas Parolin (3 Oct 2026, written in Spanish) asked his Dot to create pages for his personal life, his main projects, and a log that doubles as a diary. Every night at 23:30 it reads everything from the day and updates those pages. He says it is starting to ask him questions about himself as it learns.

9. One task list became four or five chats (@R6mezMedhat / JOJO)

@R6mezMedhat (30 Sep 2026) gave his Dot JOJO a list of tasks, and it created four or five other chats to carry them out; his screenshot shows the chat list.

10. A bedtime handover for eight hours of work (@koh_kira)

Japanese poster @koh_kira (2 Oct 2026) leaves his Dot one standing message before bed: for the next eight hours, keep moving the remaining tasks in each session forward within what he has already asked for and approved, restart sessions that stopped, switch approach when stuck, park anything that needs his input and keep going on the rest, notify him only about important changes, and after eight hours report what is done, what is left, and why anything is on hold. He says he wakes up to finished work. His wording is adapted in the copyable asks below.

Inbox, calendar, and approvals

11. A three-day email review with the approvals waiting on him (Júlio Andrade)

Júlio Andrade (IA para Médicos, Portuguese) connected his MacBook, phone, Google Calendar, and email, plus a simulated clinic dashboard, and asked his Dot to review three days of email. It reported his priorities on camera: ad creatives waiting for his approval, the final sales-video page, access to media materials, and a Stripe verification deadline. He then closed the computer to see what would happen, and the Dot kept answering from his phone.

12. Email and calendar working from Korea (Ginger)

Ginger (@se0ngj1n1ee) (Korea, 30 Sep 2026) connected email and calendar and found that both worked from Korea. Her takeaway was that she no longer needs to wait for Muse to launch in Korea.

13. Schedules moved over, then reminders and opinions (@infp_horong)

Korean user @infp_horong (2 Oct 2026) had once built a Jarvis-like app and shelved it over token costs. After moving their schedule over through ChatGPT, the Dot puts events on the calendar, sends reminders, and offers its own opinions. Their mail is on a company system, so email isn't connected yet.

14. Duplicate charges and unanswered emails (Michella / Harvy)

Brazilian creator Michella (@michella.ia) (3 Oct 2026) named her Dot Harvy. In its first week it found duplicate charges, reminded her of emails left unanswered, notified her when she might have forgotten something, and searched the web for products she wants, telling her when a better price turned up. She uses it every day and is still finding new things to hand over.

15. Secretary for a one-person company (Otou-san no Himitsu Kichi)

The Japanese channel THE オトウサンノヒミツキチ (recorded 5 Oct 2026) runs a one-person company and shows the whole setup: ChatGPT split into one project per job, the Dot as secretary, email replies with a last check so the wording stays his own, sales tracking and invoices in spreadsheets, Google Drive next to Notion, and small apps he built with Codex, such as a project board. He says he always checks important content and anything going outside himself.

16. An agency day across Slack and Calendar (Mark Nguyen / Toby)

Mark Nguyen (3 Oct 2026) spent about five hours of real agency work with his Dot Toby. Early on it surfaced a Monday client discussion about work outside the budget plus a calendar overlap, found another conflict on Wednesday, and flagged that a client spreadsheet looked view-only before a follow-up. A group message eventually went through by an explicit route, but a DM to a colleague failed on the first route. A PDF summary request sent around 4:24 p.m. Pacific was picked up around 5:13 and answered around 5:15, which is fine for background ops and too slow for live chat. Email stalled because Toby assumed Gmail while his stack used Zoho.

17. Check-ins by phone, Slack, and schedule (Diana / Sparky)

Diana at AI Agents Library (tested 30 Sep to 1 Oct 2026) connected Gmail, Calendar, Drive, Slack, GitHub, and Stripe tools to her Dot Sparky. Across ten business tasks, the ops wins were meeting prep for an editorial call (first answered as chat text until she asked for cards), seven days of inbox triage with urgency signals that still needed a human pass for things already fixed elsewhere, and a weekday 9:00 a.m. vendor-page monitor that notified her phone when the run finished. Slack worked as a quieter control surface, and calling the Dot was handy for status. She did not claim multi-week reliability from one scheduled run.

28. Stop pinging about every email; keep the other watches (Paul J Lipsky)

YouTuber Paul J Lipsky (4 Oct 2026; Outskill-sponsored video, disclosed) said that by default his Dot started messaging him throughout the day about emails he was receiving. He already got notifications from his email app on his phone, so he told it he did not need those pings, but he did want it to stay on top of his other work. It followed that direction.

30. An urgent client form found after a red-eye, filled in from Drive and approved before sending (Ryan Mish / Runpoint)

Ryan Mish of Runpoint (field note, 6 Oct 2026) got home from a red-eye flight without sleep, the day after Dots launched, and asked his new Dot to check his email and Slack: was there anything urgent he needed to finish before the end of the day? There was. The Dot found an urgent client requirement, opened his Google Drive, filled out the required form, and had him approve it before it sent the email reply saying the form was ready. A week later his view was mixed. The connection to his information was useful, but managing Codex tasks and cloud development through Dots was shaky enough that he keeps development in Codex directly, and when something failed it was harder to see what had stopped the Dot than he wanted. He keeps his Dot for accountability, meeting transcripts and to-dos. His advice for a first job: give the Dot your calendar and meeting transcripts, and ask it to identify your commitments and help you keep them.

Where it needed babysitting

18. "Prepared is not the outcome" (AI Bri)

AI Bri (@systempromptai) (5 Oct 2026) used Dots for personal and business work through 4 Oct: delegated tasks, research, newsletters and social posts, a GTD-style task tracker, and video production. She kept having to remember her own requests, check status, correct output, and find another way through approval problems, and the tracker stopped giving her a clear picture. The earlier video she discusses did eventually get published. Her point: useful work still has to become dependable before you supervise less.

33. Asked the Dot to critique the prompts it wrote for its other tasks (Wayne Duan / GlobalAgingAI, 13 Oct)

Wayne Duan (@GlobalAgingAI) (13 Oct 2026) had been using ChatGPT Dot heavily for a few days. The prompts it wrote for its other task chats kept producing work he had to redo. So he asked Dot to critique itself. Its verdict: its prompts read like relayed requests — and he notes yours probably do too.

Starting from what's already connected

19. A minute after it was created, it read his Gmail and offered three jobs (中島大介 / なかじ)

中島大介 (note, 30 September 2026, in Japanese) created a Dot the day after launch on a ChatGPT Pro 200 account in a desktop browser, and left the plugin permission at its default of allowing low-risk tools. Gmail and GitHub were already connected to his ChatGPT; he connected nothing new for the Dot. About two minutes after he chose the cloud computer, the Dot introduced itself in Japanese (the page needed one reload). It then said it would look for ways to help, and about a minute later reported three jobs it had found in his email: work out the cause and the fix for error notices from an automation tool that were still arriving that day, narrow down where to look for a gap between the number of payments and the number of tracked records, and check the sign-up flow behind a course applicant's question and prepare a reply. It said it couldn't confirm from the email whether any of them had been resolved, asked which one to take on, and sent nothing. This is proactive research, which OpenAI limits to read-only tools.

He then asked, without having it do anything, whether it asks before sending email or changing the calendar. The Dot said not every time: a clear "send it" with a clear recipient and purpose may count as approval, a request to "draft it" won't be sent, and sharing confidential information or making serious commitments needs explicit approval. When he opened Custom rules, the default for a new rule was "Ask before taking action". His advice is to look over your connected plugins before you create a Dot, and to set sending and deleting to ask first right after.

20. The emails that really needed an answer, and a meeting that didn't match the calendar (日沼諭史, Impress AI Watch)

日沼諭史 writes a beginners' AI column for Impress AI Watch and tried a Dot on a Pro 100 plan with Google services connected (AI Watch, 9 October 2026, in Japanese). Checking in the background, the Dot didn't just list unanswered emails; it picked out the ones he really had to deal with, and he found some he had genuinely forgotten. It also noticed when the date, time or place agreed with someone by email differed slightly from the entry in his calendar, and told him to check. The overnight Blender job he gave the same Dot is case 35 on video and animation.

21. A Gmail cleanup that worked, with no record of what it did (u/Ok_Barracuda_1161)

Reddit user u/Ok_Barracuda_1161 gave a Dot a basic job: sort a Gmail inbox into folders and mark the emails as read. It finished fine. What stood out to them was that there were no logs or traces of what it had actually done. A Codex session shows reasoning summaries, tool calls, plugin calls and commands; with the Dot, the only way they found to check its actions was to ask the Dot what it did.

Noticed before being asked

None of these owners asked for a check. The Dot read email, the calendar, chat history, meeting transcripts or its own memory, and raised the problem first.

22. Prep for two back-to-back calls, before she said what they were (Vicky Zhao)

Vicky Zhao (YouTube, 12 Oct 2026) tested an early version of her Dot. On the first day she only said "give me a few minutes", and the Dot worked out that she was about to go into back-to-back calls with editors, less than an hour away, and offered to prep her. It also spotted a second job in her business, a fix to draft for a course review. The prep doc began with a "read this first" note, reminded her of her own proposal, pulled questions from an email thread in her work inbox and notes from earlier conversations, looked up the people involved, and kept the two calls apart, with different questions for the editor and for the marketing lead. She didn't show the private details on screen. Later, while it was finding out how to reset a Dot, she dropped in an unrelated message to a friend about meeting up in Toronto, and it worked on both at once. When she was about to ask for the link to a recording, it had already sent it.

23. Scheduling conflicts, missing meeting details and billing notices (Allie K. Miller)

Allie K. Miller (X, 9 Oct 2026) says her Dot has already caught scheduling conflicts, missing meeting information, and important billing notices. She adds a warning to business leaders: teams shouldn't rely only on AI to catch conflicts and errors, and she can already see herself "falling into the trap a bit".

24. A task that wasn't on the calendar, found by checking email against it (Dr. Matheus Rabahi)

Dr. Matheus Rabahi (Instagram, 9 Oct 2026, in Portuguese), a doctor who posts about AI for physicians, uses his Dot as a personal assistant. It reads his email, checks it against his calendar, and picks out appointments and open tasks without being asked. On the day he posted, it reminded him of a task he hadn't even put in his calendar.

25. Reminders from Messenger chats with his wife, and a recipe site from six months of them (Marco / AI & Design)

Marco (@AIandDesign) (X, 6 Oct 2026) listed three things his Dot had done. One morning he planned his week with it on a phone call: the calendar, the plan, and what he mustn't forget. It found redundant or unnecessary subscriptions and cancelled them. He also had it log in to his Facebook, because he and his wife talk on Messenger all the time; now the Dot reminds him of the events and to-dos she mentions there. It went through about six months of their messages and built a website of the "this looks yummy, we should cook it some time" recipes she tends to send him. Before handing a Dot a Facebook login, read case 28 on Shopping & saving money: another owner's accounts were temporarily locked when Meta flagged the Dot as a bot.

29. A reader's Substack complaint, tested before he asked (Ethan Mollick)

Ethan Mollick (X, 12 Oct 2026) got an email from a reader who said that after subscribing to his Substack, they had been signed up for other publications automatically, which shouldn't happen. Without being asked, his Dot ran its own test and tried to reproduce the problem; he called it "proactive customer service". In the screenshot he posted, the Dot reports one useful clue: Substack offers additional publications after someone subscribes, and his recommendations page lists nine, which could explain what the reader saw. It checked the public signup screen in its own browser without subscribing. It also said what it could not confirm: the default selections, and what the reader actually clicked. Substack's own explanation confirms the extra step, the Dot noted, but doesn't show that anyone was enrolled automatically.

31. An observability signal became a fix branch, then production, without being asked (Adolfo Builes)

Adolfo Builes (@abuiles) (X, 10 Oct 2026) gave his Dot access to observability (o11y) dashboards for @withandeo customers. One morning the Dot picked up a signal on its own, created a branch with the fix, and by the time he posted that fix was already in production. He framed it as what the future of software looks like when an assistant can watch live systems. He did not publish the dashboard screenshots or the PR link in that post.

34. A speaking date the organisers had moved without telling him, caught from calendar and email (Harry McCracken, Fast Company)

Harry McCracken (Fast Company, "Plugged In", 9 Oct 2026) gave his Dot access to his calendar and email. Shortly afterwards, without being asked, it alerted him to a discrepancy: he had entered a speaking engagement on one date, but the confirmation email mentioned a different day. The organisers had rescheduled the event and forgotten to tell him; had he shown up on the original day, he writes, his audience would have been an empty room. He calls it the first time AI "saved my bacon", and says it was only one of several times the Dot brought a significant fact to his attention without him asking. The article doesn't name the event or give the dates.

37. A personal workspace that updates itself, with project subpages and notes from meeting transcripts (Hiromi Ohsugi)

Hiromi Ohsugi, a labor and social security attorney who manages several businesses, told OpenAI's ChatGPT Pro Community newsletter (15 Oct 2026, quoted in translation from Japanese) that the Dot, named Remy, built a personal scratchpad without being asked, gathering information from Gmail, Google Calendar, Slack and Notion. Each project has its own subpage, which keeps several businesses from blurring together, and the Dot sends reminders about things that would otherwise slip, such as booking a flight or finishing a client process before a deadline. Hiromi's meetings are transcribed in Notion, and the Dot used those transcripts to update the scratchpad on its own; Hiromi says the updates were accurate.

38. A client's retainer commitment, confirmed from a call transcript and email (Sarah Rose Siskind)

Science comedy writer Sarah Rose Siskind (Hello SciCom; same newsletter, 15 Oct 2026) had spent a long time asking AI tools to take the initiative and raise "unknown unknowns", with mixed success. Right after a call, the Dot, named Hal, looked up the call's transcript and corrected a client's mistake, confirming that the client had committed by email to that month's retainer.

39. A financing change buried in a title company's email (Dustin Fox)

Real estate professional Dustin Fox (same newsletter, 15 Oct 2026) was representing the seller on a property when the Dot pointed out that the buyer had changed their financing without the seller's consent. The change was buried in an email from the title company and, in Dustin's words, "would have gone embarrassingly unnoticed by me, my assistant, and even the buyer's agent".

Handing off by call, or before bed

26. Inbox zero on one phone call, while doing chores (Michael Wall)

Michael Wall (@sound4movement) (X, 5 Oct 2026) got to inbox zero "without a screen and hands free" while doing chores around the house, on one phone call that stayed on a single thread. His rating for the experience: "coworker vibes 10/10". The three-hour work block he had planned for Monday morning was sorted on Sunday. In OpenAI's ChatGPT Pro Community newsletter (15 Oct 2026) he described a bigger hands-free job: over a voice call, his Dot, Dusty, contacted the third-party distributors and took down four albums he no longer wanted on streaming services, filling in forms he never saw.

27. Overnight jobs for "Robot Kyle", a 20 MB upload limit, and a second brain he keeps himself (Kyle Chalmers)

Kyle Chalmers (YouTube, 9 Oct 2026) named his Dot "Robot Kyle". It picked up the plugins he had already connected to ChatGPT and could see his earlier ChatGPT and Codex conversations, so he could ask things like "find the principles from vidIQ's last 30 videos that I could use in my content process". He recorded at 11 pm and handed it several tasks to run overnight, including editing the intro of that video. Attaching the clip failed, because the Dot didn't accept files of 20 MB or larger, so he gave it a file path instead. He also found it slow and wouldn't use it for anything urgent. He keeps his own "second brain" of markdown notes in Obsidian, compiled every night from his Claude Code and Codex sessions, so his memory doesn't depend on any one product, and he shares the prompt he uses to load it into his Dot.

32. A one-hour call on the go, then Amp agents kept shipping features (max.berlin / @maxjendrall)

max.berlin (@maxjendrall) (13 Oct 2026) added Amp as an MCP to his ChatGPT Dot. While on the go he called the Dot for about an hour; the Dot handed work to his self-hosted Amp agents, which kept working through a large set of features and open tasks after he left the phone. He uses Amp so ChatGPT and Claude models sit in one place, and noted he does not need a paid Amp plan for this setup.

Course follow-up after class

35. Four fictional student follow-ups: Excel tracker, A4 PDF, and Zoom Help research (工藤 晶)

工藤 晶 (note, 10 Oct 2026; also shared via Made with Dots) taught a short course and wanted the post-class pile handled without inventing missing details. He used a fictional set of four student contacts — no real inbox watch and no sends. He asked his Dot to build a follow-up table with columns for the student, the message, status, next step, and a reply draft, ordered by what he should check first, and told it not to invent dates or URLs while the recording and handouts were still unpublished. The Dot returned an Excel sheet plus a matching check PDF, opened the PDF on its own cloud computer, and left the draft replies without fake publish dates. For student C's homework question ("I can't pick just three headlines"), it made a one-page A4 PDF for beginner instructors: a choose-three flow with an arrow diagram and a fill-in worksheet, then scrolled the file on its own screen so he could verify. When he handed in more updates by hand — B resolved, E asked the same question as C, A would watch the recording on a phone — it reordered the queue and kept B out of active work without treating "B found the files" as "everything is published". For A's phone-viewing question it opened Zoom's official Help in its browser, split confirmed (cloud recordings can stream in a browser) from unconfirmed (no clear "phone needs no app" line on the pages it checked), and listed three beginner caveats instead of guessing. Limits he names: he passed the extra contacts himself (the Dot did not watch mail), there is wait time during work, and he reads every draft before any send or publish.

While away from the desk

36. Walking voice: Outlook, progress-billing mail, and a subcontractor draft left unsent (だい / AI×施工管理)

だい / AI×施工管理 (note, 3 Oct 2026) manages civil-works sites: checking the job, talking with subcontractors, and safety checks on one side, and mail, meeting notes, weekly and monthly papers on the other. Work remembered while out used to pile up until he got back to the office. On a morning walk he called his Dot by voice and asked it to check Outlook, see whether HQ had sent the progress-billing (出来高) mail, and—using last month's sent folder—draft a mail to subcontractors with the payment materials attached. While they talked, the Dot sorted who wrote and what they needed, and checked submitted reports against HQ payment docs. What helped was that Claude Code had already done part of the work: the Dot reused those records instead of starting over. The subcontractor draft was ready with attachments; he did not send it—he reads it himself first. He also asked for an electronic update of safety documents; that job stalled on checking whether original images were preserved, and by the time he wrote the note he had not yet confirmed the shared-folder update. Status replies were sometimes vague (accepted? started? finished?), so he had to ask again. Line he set early: outbound mail and anything that affects outside parties stay behind his own review.

More asks you can copy

Quiet the email pings, keep other watches (from case 28):

Stop messaging me about ordinary new emails — I already get those on my phone. Keep watching [billing failures / calendar moves / project threads] and only ping me when something there needs a decision. Confirm what you will and will not notify me about.

Look into a complaint without changing anything (from case 29):

When a reader or customer emails me about a problem with [my newsletter / shop / signup page], try to reproduce it in your own browser without subscribing, buying, or changing any setting. Tell me what you checked, what you could and couldn't confirm, and the most likely cause. Draft a reply for me to review; don't send it.

Phone catch-up:

I'll call you on my way home. When I ask "where are we?", tell me what's done, what's in progress, and what's waiting on me, in that order, with the one decision you need from me first. After the call, put the same summary in this chat.

Brain dump into a plan:

Here is everything on my mind. Sort it into Today, This Week, and Waiting (on someone else). For each Waiting item, draft the follow-up message, and leave the drafts for me to review.

Bedtime handover:

I'm offline for the next [8] hours. Keep moving the open tasks forward within what I've already asked for and approved. If something needs my input, park it and move on to the next one. Message me only about important changes. When I'm back, report what's done, what's left, and why anything is on hold, conclusion first.

Inbox and calendar sweep:

Look through the last [3] days of email and my calendar for the next [5] days. List what is waiting on my approval, any deadlines, and any meetings that clash, each with a link to the source. Draft replies where they're needed, and ask me before sending anything or changing an event.

Weekday ops pulse:

Every weekday at [time] [timezone] for [4] weeks, check Gmail since yesterday, today's calendar, and my Slack DMs. Send me meetings that need prep, emails that need my reply, and anything waiting on my approval. Confirm the schedule you saved.

Watch for what I'd miss (from cases 22 to 25):

Every weekday at [time] [timezone], compare my email from the last day with my calendar for the next [3] days. Tell me about clashes, meetings that are missing a link or an agenda, bills or renewals that changed, and anything someone asked me to do that isn't on my calendar, each with the email it came from. Don't send, pay or change anything; draft what I'd need and wait for my yes.

Before the end of the day (from case 30):

Check my email and Slack since [time]. Is there anything urgent I need to finish before the end of today? For each item, show me where it came from, prepare what it needs from my files (a form, a reply draft), and wait for my approval before you send or submit anything.

Critique your own task briefs (from case 33):

Open the prompts you wrote for your other task chats in the last [3] days. For each, say whether it reads like a relayed request or a real brief an operator could run without asking me again, list what is missing, and rewrite one improved brief. Don't start those tasks until I approve the rewrite.

Post-course follow-up table (from case 35):

Take these course follow-up messages and build a tracker with columns for the student, what they asked, status, next step, and a reply draft. Sort by what I should check first. Do not invent dates, URLs, or publish status for anything still unpublished. Do not send or publish anything. Show me the file on your computer when it is ready.

While away from the desk (from case 36):

I'm away from my desk. Check Outlook. Has HQ sent the progress-billing mail? Using last month's sent folder to the same subcontractors, draft the reply with the payment materials attached—do not send. Check what prior Claude Code work already finished and only pick up what's left. If a job stalls (for example an image-preservation check on safety docs), say exactly what is blocked.

Related

• Use cases hub · Voice calls · Email triage · Morning brief · Meeting prep · Slack assistant · Errands & life admin · Codex orchestration · Project follow-up
• Dots + Gmail · Dots + Google Calendar · Dots + Slack
• Getting started · Pricing / usage · Features
• How to get ChatGPT Dots · Dots in the EU & UK · Morning brief workflow · Dots + Google Drive · Dots + Teams · Dots + GitHub