How do you call a ChatGPT Dot, and can it call you? A voice guide with 57 real calls

The short version: when a call is worth it, how to set it up, where it gets stuck

Is calling your Dot worth it?

Yes, for talking things through and handing over work while your hands or eyes are busy. It isn't yet reliable as the only route for anything that has to happen. The calls that paid off fall into three kinds: a long run of small decisions (a 45-minute call that cleared a day of email and Slack, ten tasks stacked into one call, ten minutes of plans on a dog walk), one job handed over before hanging up, and a quick status check away from the desk. The weak spots are the call connecting at all, spoken requests that never turn into tasks, and anything that sends, posts or approves. In the reports below, the text chat in the same conversation is where work reliably started. So talk on the call, and confirm in writing.

How to set it up

1. Open your Dot's conversation in the ChatGPT mobile app, the desktop app or a desktop browser and select the phone button. In the desktop app you can also select Call in its profile. Mobile web doesn't support Dots.
2. On iPhone there is a shorter way in. With ChatGPT for iOS 1.2026.279 or later, add the Your dot widget to the Home Screen, then turn on Show shortcut buttons under Edit Widget to get a phone button. Or create an Apple shortcut with the Open your dot action in Call mode, and assign it to the Action button. Dictation mode is for a quick spoken note and doesn't work during a call (Message your dot).
3. If calls drop when the iPhone screen locks, turn on Voice → Background conversations in the ChatGPT app's own settings.
4. Give the Dot a standing brief before you rely on short calls: what it prepares and what you decide. Then one sentence on the phone is enough.
5. Start each call with the job in one sentence, and say where the result should go (this chat, Slack, a note) and by when.
6. Before you hang up, ask the Dot to read back what it will do and to post every task it started, with a link, in the chat.
7. Hanging up doesn't stop the work. To stop it, select Pause in the ••• menu of the Dot's profile; delegated tasks stop under Activity and recurring ones under Scheduled.

Where it gets stuck, and what worked

• The call rings out or stays on "Calling…". Send the Dot a text first: if it answers, only the call is broken. Then try another network (home Wi-Fi instead of mobile data), update the app, reboot the Dot from its menu and give it 30 to 60 minutes. Starting and ending an ordinary ChatGPT Voice chat before calling worked once for one person and didn't help Onigiri on an iPhone on 14 October. When OpenAI Support traced one stuck iPhone call on 12 October, the microphone setup had passed and the app gave up while still waiting for the call to start. Support then asked whether such calls end on their own or only when you stop them, so note that in your report.
• It answers after ten rings, or not at all. People were still seeing this in mid-October (cases 37 to 47). Leave the job in the chat and try the call again later; the work doesn't depend on the call.
• The Dot says "I'll handle it" and nothing happens. Spoken handoffs can come back as voice_parent_context_pending or voice_parent_unconfirmed, and no task starts, even while read-only lookups on the same call keep working. Typing the same request into the chat is what fixed it for most people. In one report from 16 October the chat couldn't find the call request at all, yet the next call still had the instructions, and authorising again on that call got the work done.
• Sending, posting or approving by voice. The approval check doesn't treat a call transcript the way it treats a request you typed. Say it on the call, then confirm it in text.
• The voice goes silent or keeps saying "let me check". The answer often arrives as a text message in the chat instead, so read the chat while you're still on the call.
• The call drops without a sound, often on the road. Because you said the job first and asked for the result in writing, a dropped line doesn't lose it. When you'll need proof later, ask for a screenshot or link in the chat (case 49).
• Very long calls use up the allowance. One Pro user who spent more than four hours on calls got a "preview limit" message telling them to try again at 4:10 AM (OpenAI Community); see "Your dot is on a break" for what that pause looks like.
• A wrong name, the wrong voice, or a question you didn't ask. Tell the Dot not to greet you by name, and to read back anything it isn't sure came from you before acting on it.

What it can and can't do yet

What it can do:

• Take your call from the mobile app, the desktop app or a desktop browser, and on iPhone from a Home Screen widget or the Action button.
• Let you type, and share links or images, while you talk, and message you with progress during the call.
• Keep working after you hang up, with the same memory it has in chat, Slack and Teams.
• Use the apps you connected, such as email, calendar and Slack, while you talk, and answer questions about them on the call.

What it can't do yet:

• Call you. OpenAI says calls started by your Dot are planned for after launch.
• Phone a shop or another person for you. The two people who managed this built their own bridge (cases 29 and 30).
• Tell you when a call has dropped (case 39), or draft live in front of you while you speak (case 53).
• Text with you, except in a limited beta for some Pro users in the US; it isn't offered in Business or Enterprise workspaces.

One message to start with

On calls, keep answers short and wait if I pause. I'll give you each job in one sentence. When I'm done, read back every job you heard and start a task for each one. Before we hang up, post the list in this chat with a link to every task you started, and list anything you couldn't start. Don't send, post or approve anything from a call until I confirm it here in text.

Quick answers

How do I call my ChatGPT Dot?

Open your Dot's conversation in the ChatGPT mobile app, the desktop app, or a desktop browser and select the phone button. In the desktop app you can also select Call in its profile. Dots don't work on mobile web (Message your dot).

Can my Dot call me, or make phone calls for me?

Not yet. Your Dot can't start a call to you at launch, and OpenAI says Dot-initiated calls are planned for after launch (Getting started with your dot). The docs don't describe a Dot phoning a shop or another person either, so every call today is one you start in ChatGPT.

Does the work stop when I hang up?

No. Hanging up ends the voice conversation, and work you assigned can keep going. To stop it, open the ••• menu in your Dot's profile and select Pause.

Can I text my Dot instead?

Some Pro users in the US can try texting as a limited beta, set up from the desktop app; it isn't available in Business or Enterprise workspaces. Everyone else can type in the Dot's chat in ChatGPT or connect Slack or Microsoft Teams.

What if the call won't connect?

OpenAI's advice is to keep going by typing in the same conversation while calling isn't working. The mid-October reports further down, from people whose Dot rang out or answered very slowly, show what else helped. If the Dot has vanished from the app altogether, see ChatGPT Dots not showing or disappeared.

How calling a Dot works (official)

• Open your Dot's conversation in ChatGPT and select the phone button. In the desktop app you can also select Call in its profile (Message your dot).
• You can reach your Dot in the ChatGPT mobile app, the desktop app, or a desktop browser. Mobile web is not supported (Message your dot).
• You can type while you talk, and the Dot can message you with progress or a question during the call.
• Ending the call ends the conversation, not the work. Assigned work can continue after you hang up. To stop it, use Pause for the main task, Activity for delegated tasks, and Scheduled for recurring ones (Meet dots).
• It is the same Dot in ChatGPT, Slack, Teams, and a call, so switching to voice does not reset its memory.
• Your Dot cannot call you at launch, so you start every call. OpenAI says calls started by your Dot are planned for after launch (Message your dot). Texting is a separate limited beta for some Pro users in the US, set up from the desktop app and not offered in Business or Enterprise workspaces (Getting started with your dot).

Clear a day of tasks by voice

1. A 45-minute call that handled the day's email and Slack (Riley Brown)

On 1 Oct 2026 Riley Brown called his Dot for 45 minutes, phone in his pocket and AirPods in, and in his words it "handled all my email / slack tasks for the day."

2. Ninety minutes of riffing while the Dot ran ten Codex threads (Ali Abouelatta / Lazyweb)

Ali Abouelatta wrote up his first 72 hours with his Dot, Dottie (4 Oct 2026). She already has a company email, a seat on the Linear board, and her own software seats. He says they spent 90 minutes on the phone while he "just riffed" and watched her take over his laptop and orchestrate 10 Codex threads. He uses a call, Slack, or a comment on a Space to step in halfway through a job, which he says makes him willing to hand over bigger work.

3. A 51-minute call that ended in a blog draft (정옥선 / Kotzi)

Korean AI instructor 정옥선 (@ok_ssam_) kept a call with her Dot 코찌 (Kotzi) going for 51 minutes 44 seconds. From spoken instructions alone, the Dot opened a browser and wrote a full draft in her Naver blog editor. She posted the whole process on YouTube.

4. Ten tasks stacked into one call (AI with Amit / Morpheus)

AI with Amit spent the week after DevDay giving real work to the Dot Morpheus, then got on a live call and stacked 10 tasks into one conversation: flights, NFL tickets, hotels, a late-night food order, and calendar reminders, all running in parallel. Earlier that week the same Dot had sliced 3D-print files, mined YouTube comments for video ideas, and caught a subscription that was about to renew and charge.

5. A few minutes on the phone, and the week was planned (Rabbie 小兔)

On his first call, Rabbie 小兔 (@rabbiekao) spent only a few minutes talking, and the Dot sorted out everything that had to be finished that week. It also went through emails that had just arrived and hadn't been read properly yet, and folded them into the same plan.

6. A flight search and a restaurant booking in parallel, and a lukewarm verdict (Lucas / AiDrops TV)

Lucas from the Brazilian channel AiDrops TV set up a Dot from scratch, called it, and asked for a São Paulo to Rio search on Google Flights and a restaurant reservation at the same time. Lucas then took over the Dot's cloud computer to see the flight results. What held the test back: Slack didn't connect, only one Dot was possible, and computer use felt slow and erratic. The verdict was "esperava mais" (I expected more).

Hand over a job, then hang up

7. One job over the phone, then hang up (Stephanie Nyarko / Remy)

Stephanie Nyarko gave her Dot Remy a real job in her business over a phone call: take a YouTube transcript and turn it into a repurposing pack of clips, LinkedIn posts, and timestamps. She hung up and let it keep working. Before the call she had given Remy an onboarding brief covering what it owns, who her audience is, how she writes, and one rule: "you prepare, I decide." Anything that could affect a client, her reputation, or her money needs a human handoff. She limits which apps Remy can open and checks its quotes and timestamps before using them.

8. Ten minutes of website changes, then the dishes (Allison Johnson / The Verge)

In her Verge hands-on (2 Oct 2026), Allison Johnson had her Dot redesign her personal website. Instead of typing the next round of changes, she called and went through them section by section for 10 minutes, walked away to do the dishes, and got a ping that the next version was ready. It was "not perfect, but better," and she kept iterating by chat and phone dictation. Earlier, when the Dot offered a $35 day pass instead of finding a coworking space's free trial, she asked it on the phone why it missed the option. "I jumped to the wrong conclusion," it said.

9. Talking through the brief instead of writing it (Tina Saul / KINTAL)

Tina Saul named her Dot KORA. Her first call felt like "picking up the phone to a colleague": she could talk through what she was trying to achieve rather than stop and turn every thought into a written prompt, and she says it changed how she delegates. While she was on a call, KORA also alerted her to an urgent email, and she judged that the interruption was right.

What didn't work: calls were sometimes slow to connect, KORA once started answering while the screen still said "calling", and at the end she was unsure whether to hang up or wait for a goodbye.

10. Threads posts discussed on a call, finished after it (Demian Cardo / Mark)

Demian Cardo named the Dot Mark and talked through ideas for Threads posts on a call. When the call ended the work kept going: Mark prepared the posts, and Demian found them finished in the chat. Demian describes the feeling as giving a task by voice and then receiving finished work.

11. A request on the way home, then eight hours overnight (Ren Gaku / シエル)

Japanese creator Ren Gaku (@rengakuai) used the Dot シエル (Shiel) as an AI secretary for four days of real work. Ren could call it on the way home, and what they discussed was summarized in the chat afterward. One request in a chat was split into separate background threads, and it was given eight hours of work to do on its own overnight. Ren notes that usage limits, memory, approvals, and where your data lives all need attention.

12. Four Word documents sent during an eight-minute call (@dn.baas)

Indonesian user @dn.baas stayed on a call with their Dot for more than eight minutes and sent it four Word documents along the way. The Dot asked what it should check the files for and what to do with them next, so the brief was settled by voice. They compared it to "Hermes agent plus Jarvis" that you can direct just by phone.

13. Visa forms filled in while the Dot asks questions (kerbinagent, Reddit)

On r/OpenAI, kerbinagent called this the one life-changing use case they had found: give the Dot a long US immigration or UK/Schengen visa form, call it at the same time, and ask it to ask you questions whenever it needs clarification. They say the questions are the most useful part.

Build something by phone

14. Blender lighting fixed over a call (阿石OMP / Peter)

Hong Kong creator 阿石OMP named the Dot Peter. 阿石OMP saved photos to the Dot's cloud computer, then called it and asked it to open Blender, improve the lighting on a 3D model, and export a rendered image; the video shows the finished render (Threads post). After comparing it with ChatGPT Work, the verdict was "not in a rush" to switch.

15. A Tokyo Skytree 3D model ordered by phone (じゅりん / AIビジネス活用塾)

Japanese creator じゅりん (@aibusiness8877) called the Dot to ask for a 3D model of Tokyo Skytree. The Dot built it with Blender and Three.js on its cloud computer, and the finished model appears at 42:44 in the first-impressions video. Earlier in the same video the Dot started on a task before being asked.

16. Video edits talked through while running a launch (Every)

Dan Shipper, founder of Every, wrote on 7 Oct 2026 that Dots had "taken over" the company. One example: Every's head of video talked his Dot through video edits by voice while running around getting a launch out. Dan's own Dot, Boo, posted his model-testing results to Slack over a weekend and brought back the replies. Dan's complaint is permissions: he has to approve the same basic thing several times, and sometimes the Dot still says it can't do it.

Steer work that is already running

17. Steering a project from the grocery store (Brian / Ava)

On Human Behind the Machine (recorded 4 Oct 2026), Brian describes calling his Dot Ava from the grocery store to steer the animation work for Ash's Diary, a story from his tabletop campaign. He wants Ava to babysit long local GPU jobs, keeps the final creative approval himself, and reviews scenes in a local gallery where he can approve a version or send back specific revision notes.

18. Two movie tickets bought over a call (IA Masiva / Iris)

The Spanish-language channel IA Masiva asked its Dot Iris to buy two movie tickets during a voice call. Iris signed in to their Cinemark account through a secure form, walked the purchase through, and handed control back to them. The same test also covered 53 email follow-ups, which are on the email triage page.

19. A second call to ask "what are you working on?" (John Aspinall / Dolly)

John Aspinall called his new Dot twice on day two. After the first call he heard a female voice and renamed it from Roger to Dolly. He then fired off an infographic, electricity research, a Times Square restaurant search, and a cat-toy search in parallel, and used the second call to ask what it was working on. Amazon blocked the Dot's browser, and his usage still showed 94% left at the end of the test.

20. Six check-in calls in one day (Roland Nyamoga)

Roland Nyamoga was overwhelmed by several Codex tasks at once and kept losing track of where each one had stopped. The Dot took over the orchestration and kept tables, graphs, and progress in Pages that Roland could review. By the time of the post, Roland had called it about six times that day just to check on the work.

21. A call that found links, then hit a computer failure (Futurepedia)

In Futurepedia's early-access test, summarized by João Queirós, a phone conversation with the Dot found product links, but the Dot's cloud computer failed after a reset, and a Codex browser was the workaround. Finding links on a call is not the same as finishing the browser task, so check the result afterward.

For a work example, Pat Simmons got a board count on a voice call and saw the approval list arrive in Slack about a minute after he hung up; see Slack assistant.

Calls you make every day

22. A nightly 8 PM Spanish practice call (Pat Simmons / László)

Pat Simmons asked his Dot László to call him every night at 8 PM to practice Spanish. Because a Dot can't place calls yet, he calls it from the app instead. He says it takes a moment to pick up, then holds the conversation with almost no delay.

23. A first call that started with "what do you know about me?" (@olivece2017)

A Korean elementary-school teacher with 22 years in the classroom (@olivece2017 on Threads, 5 Oct 2026) had already used her Dot for file organization and a web app. On her first call she asked what it knew about her; it recalled her 22-year teaching career, her homeroom-notes tool (담임노트+), Google Teacher Lab, and her push to become a Google Trainer. They then talked through how to share teacher-made apps with other teachers.

What a call feels like

24. A ringback tone and read receipts (Talent Cloud)

Japanese company Talent Cloud tested a Dot on a Pro 100 account in Japan (30 Sep 2026). Pressing the phone icon shows "Calling..." and plays a ringback tone; the Dot picked up after about 10 seconds, and the conversation ran inside the same chat screen rather than a separate call screen. Messages also get read receipts almost immediately. The writer found this human-like design a little unsettling rather than simply convenient.

25. Asking the Dot for its phone number (Dan Baker)

Dan Baker (2 Oct 2026) called his Dot and asked whether it had a regular phone number. As far as they could find, it doesn't. His point: a microphone button feels like dictation, while a phone button means someone is already on the other end, who keeps working after you hang up.

26. Thirty minutes on a call that already knew the context (Kerdo)

Kerdo (@AbdoKerdawy) expected Dot calls to be ChatGPT Voice with a cute avatar, then stayed on one for about 30 minutes (29:34 on the call screen). The Dot already knew the context, what they were working on, and how Kerdo likes things done, so the call could "just continue." Kerdo calls it "an AI coworker on speed dial", and adds that it stayed calm even when cursed and yelled at.

27. Korean and English on the same call (Wild Duck Labs)

Korean channel Wild Duck Labs tried its first call in both Korean and English on a $100 Pro plan. The call led on to real work: the Dot found scheduled tasks that had been hidden, and later fixed an app sync bug. It started out on the wrong track, but once pointed in the right direction it moved work between chat, Work, and Codex projects like a middle manager. When asked how pricing works, the Dot said it didn't know for sure.

When calls fail, and two workarounds

If your calls ring and then show "Couldn't connect", users on GitHub got them working again by rebooting the Dot or restarting its own computer, and one by texting the Dot to answer while it rang. Those reports are collected on the Dots not working page. What happened during the 4–10 October outage, and what brought calls back, is laid out after case 30 below.

28. "Call failed" the day after a 28-minute call (@DevAdventur3s, Julian Goldie)

@DevAdventur3s reported on 1 Oct 2026 that calls to their Dot failed on every phone they tried, a day after the same Dot had held a 28-minute call (RuntimeWire write-up). By their account, OpenAI's Tibo said a fix was coming and that a Dot might not answer while it is busy. In a day-one test, Julian Goldie also found that the call button didn't connect.

The Dot also can't call other people for you. The same Reddit user from case 13 put it bluntly: being autistic, the whole point for them was not having to talk to people, and the Dot can't make calls.

29. Giving the Dot a way to place calls itself (AI 서대표)

In a three-day test, AI 서대표 (@AISeoceo) connected a separate voice AI service, VOX, to the Dot by command line, as an experiment in letting the Dot place a phone call itself to confirm details. This runs through a third-party service and is not a built-in Dot feature.

30. A Google Voice bridge for call centers (Josu San Martin)

Josu San Martin gave the Dot the ability to place calls through Google Voice, so it can talk to call centers and fight on Josu's behalf. The setup is published as instructions in a GitHub repo that you point your agent to. Like case 29, this is a self-built bridge, not something a Dot does out of the box.

From a call into your own notes

31. A day talked through on a call, appended to her Obsidian diary (やのたん / ドゥー子)

Japanese note writer やのたん (3 Oct 2026, in Japanese) named her Dot ドゥー子 and uses calls to turn talk into records. She told it about her day on a voice call and had it add the account to her diary in Obsidian, the notes app she uses. For that she connected her Mac and approved the write first; afterwards the Dot reported that it had appended the entry and kept what was already there. She still reads the result to check it matches what she meant. The ask she suggests ends with what to do and where: "Sum up what I just said for today's diary. Keep what's already written and add it at the end." She also had the Dot use past conversations and the diary entries she allowed it to read as background for work questions, and drafted the note article itself by talking it through with ドゥー子 on a call.

A quick inbox check by phone

32. "Anything in my unread email I need to deal with today?" on a short call (Eray Hamurlu)

In the same test video (9 Oct 2026, in Turkish), Eray Hamurlu called his Dot with the call button at the top right and asked it to look at his unread email and sum it up. The Dot said it would pick out the important messages and the ones waiting for his reply, went through the last 50 unread messages, and reported back on the same call: mostly newsletters and automatic notifications, a few collaboration offers, and a new campaign from LearnWorlds, with nothing urgent he had to handle that day. He also noticed that while the call runs, the app open on his computer shows a small call icon with the call's length in the top-right bar, and the timer matched his phone. Earlier in the video he started a flight search from his phone (see travel planning, case 42).

Talking while the work keeps going

33. A 91-minute call, with feedback given while the work ran in the background (Viktor Malinovskyi)

Three days in, Viktor Malinovskyi shared a screenshot of a 91-minute call with his Dot (LinkedIn post). He has got used to saying "take care of this, dot" out loud and then carrying on with his own work. What he likes is how naturally talking connects to doing: his Dot keeps its answers shorter on calls, and he can give feedback while the work continues in the background. One job he did this way was a lead search in AiSDR, where he changed the search criteria by voice over a few rounds without typing (small business, case 36). What interests him most, he writes, is one ongoing assistant: delegate, give feedback, come back to the result.

34. A WebXR world updated by talking, while standing inside it (Ben McNulty)

Software engineer Ben McNulty (@benlivenow) posted on Threads on 11 October that he had called his Dot and talked through updates to a WebXR world while standing inside it (Threads). In his words, "just normal weekend coding stuff in 2026." The post doesn't say which changes he asked for or how the Dot made them. It is a good example of when a call beats typing: your hands and eyes are busy inside the thing you're building. For more building by phone, see cases 14 to 16 above and build apps & sites.

A 70-minute call, a distorted one, and a Dot that went quiet

35. Seventy minutes on the phone, then a call that failed (Maya Bello)

Maya Bello (YouTube, 12 Oct 2026) planned an App Store icon test for her app on a call with her Dot (what it found is in build apps & sites, case 37). When the Dot listed the steps out loud, she asked it to put them in the chat as well so she could see them. She says she was on one call for about 70 minutes, walking around her home, and that it felt like staying on the line with internet support until a job gets done; she thinks she worked a little longer because of it, and she couldn't tell how much usage the call took. It didn't always work. Once, the Dot's voice became badly distorted and then the call failed. Another time a message showed as read at 11:03, and at 11:09 there was still no sign of work: the Dot's computer showed it wasn't working on anything, so she sent "Hey, I would love an update" to check in. What she likes is that her app, her YouTube and her social media ideas all share one context; what she misses is the option to keep them apart.

A walk with the laptop closed

36. Laptop shut, a walk and a call, and the Dot sorts it out afterwards (おけもん / はるちゃん)

おけもん (Okemon) wrote up 12 days with a Dot named はるちゃん on the Libecity knowledge library (11 October 2026, in Japanese; the post itself was drafted with the Dot). By their count the two exchanged about 730,000 characters in that time. A few days after spotting the phone button, on the evening of 6 October, Okemon told the Dot the computer was now shut and the plan was to walk and talk through things that didn't need it. The call wandered from people Okemon wanted to catch up with and places worth visiting someday to things to try next, with the odd aside about how strong the evening wind was. Afterwards the Dot organised what had been said and tied it to what Okemon wants to do. By the end of the day Okemon had walked more than 20,000 steps for the first time in a while. Their split is Claude Code or Codex when sitting at the Mac to build something, and a call to the Dot when the Mac is closed and they're out walking. The same post is frank about calls: several times the Dot didn't answer, or the call cut off right away, so for Okemon it isn't yet something that picks up every time.

Calls that ring out, or drop without a sound

37. Latest iOS app, and the Dot never answers the call (DistinctLee / V.)

Lethabo Lee Ntshudisane (@DistinctLee) (X, 10 Oct 2026) wrote that he loves his Dot, then the catch: "it doesn't answer when I call it on mobile at all." He was on the latest version of the ChatGPT app on iOS. The same week he also uses the Dot (named V.) to steer Claude Projects for engineering work — that angle is on the Codex orchestration page; the call failure is the part that belongs here. Typing to the Dot still worked for him.

38. Calling is hit and miss, and the path to the Dot is laggy (Shreyansh Parakh)

Shreyansh Parakh (@shreyansh_IND) (X, 13 Oct 2026), replying in a product thread, asked for a way to open his Dot straight from the mobile Home Screen: ChatGPT → Dot → laggy UI was frustrating. In the same post he added: "calling the dot seems to be a hit and miss feature!" He did not name a workaround; the request is for a more reliable call path and a shorter route into the Dot. OpenAI's docs now describe exactly that shorter route on iPhone: a Your dot Home Screen widget with a phone button, and a Call-mode shortcut you can put on the Action button (setup steps at the top of this page).

39. A call that drops without a sound, so the talking goes on to nobody (Nick Fernandez)

Nick Fernandez (@nickf_ai) (X, 13 Oct 2026) says the Dot gets used every day. Twice in the previous few days the call dropped with no sign it had: Nick kept talking for a few minutes before realising nobody was listening, usually only noticing when Nick's mum called back. The post asks OpenAI for some signal when a call with the Dot ends.

40. Fifteen rings, then the call failed (Crafty)

Crafty (@TRS_Crafty) (13 Oct, reply to @thsottiaux) wrote that everything with Dots either gets blocked, needs approval, or takes five minutes for a simple task. The same morning Crafty called the Dot; it rang fifteen times and then failed. The post also says a Discord connector is connected but doesn't work — that wish is not covered here.

A lunch break spent on a call

41. A call over lunch instead of a show: a prospect researched, yesterday caught up, replies drafted (Saksham Gaur)

Saksham Gaur (@Whysaksham) (13 Oct), who runs an agency in tech media, has used Dots since launch but still won't give it full access to the browser or the virtual computer it runs on. One day, instead of putting on YouTube or The Sopranos while eating, he called the Dot and worked through tasks while he talked: learning about a prospect's business his team is about to onboard, catching up on everything that happened the day before, and drafting update emails and Slack replies while going over the new client's context. He said he had been feeling lethargic and still got the work done "with pinpoint accuracy", all while he was munching. Later in the thread he adds that each morning, while he does admin, he catches up on every sales activity through the Dot. If you try a meal-time call, ask for the replies as drafts and read them once you are back at the keyboard.

Slow pickups, silent voice, and "let me check"

42. Ten-plus rings, and the Dot says it never heard the phone (Dave)

Dave (@LLdavedave) (14 Oct) wrote that whenever he calls his Dot it usually takes 10+ rings before it answers, and occasionally it never answers. When he asks why, the Dot says it didn't register the ringing, even though the "call" already shows up in the chat history. He says it has been like this since launch.

43. Voice stays silent, then the replies dump after you hang up (Aaron Lundsten)

Aaron Lundsten (@LundstenA) (14 Oct, reply to @derrickcchoi) wrote that voice is still broken for him: give the Dot a bunch of tasks and it just never responds. That day, when he ended the chat, a bunch of messages suddenly appear in his Dot channel — but voice can't see them anymore. Text after the call is not a substitute for answers during the call.

44. Three days of "let me check" on phone and laptop (@Splendid_0823)

@Splendid_0823 (13 Oct, reply to @reach_vb) wrote that for the past three days, calling the Dot from both phone and laptop, the voice assistant hasn't been able to answer any questions: it just keeps repeating "let me check" or "let me pull that up." Same stall pattern as the "answer comes by text" reports below — hang up and read the chat, or switch to typing.

Calls the Dot doesn't pick up

45. Called the Dot; it just didn't answer (Louis Pereira)

Louis Pereira (@louispereira) (14 Oct) wrote that things were "getting a bit too realistic": he called his Dot, and it just… didn't answer the call. He posted a screenshot of the unanswered attempt.

46. Pickup takes so long he asked OpenAI why (Jelly)

Jelly (@jellycharts) (14 Oct, reply to @thsottiaux) asked why his Dot takes so long to pick up. No workaround in the post — just the slow-answer friction that matches Dave's 10+ rings report (#42) from the same day.

47. Loving Dots, except the Dot won't pick up (Anmoll)

Anmoll (@anmoll_w) (11 Oct) wrote that he is "absolutely loving" ChatGPT Dots — "But just like my stakeholders, my dot doesn't pick up my call." He asked whether that was a bug or a choice, and posted a screenshot. Same unanswered-call pattern as DistinctLee (#37) and Louis (#45), a few days earlier.

Calls from the car and on a walk

These reports are about where people make the call rather than whether it connects: on the interstate, on the way to a parts store, at the wheel with several coding threads open, and on a long walk. Two of them also say what still gets in the way on the road.

48. Thirty-one minutes on the interstate: lease amendments, code, email and Slack (Clinton Mills)

Clinton Mills (@Clintonm9) (14 Oct) spent 31 minutes driving down the interstate talking to their Dot on the phone. Along the way the call handled lease amendments, code changes, emails and Slack messages. Their summary: "What a time to be alive."

49. A brake-pad price check on the way to the store, with a screenshot for the counter (Hey...Juan)

Hey...Juan (@JuanAG_IT) (11 Oct) called their Dot while driving to O'Reilly's for brake pads. They normally buy parts from a local wholesaler that is cheaper, but it is only open Monday to Friday, and looking up a single part on its website usually takes about five minutes. On the call they described what they were after. The Dot found the pads and added a caution: check whether the rear has heavy-duty rotors before buying. Not fully trusting the answer, they asked the Dot to send a screenshot into the chat. At the counter they asked whether O'Reilly's price matched the local wholesaler's, and it did. The screenshot from the call was already on their phone as they walked in.

50. Six threads of work started while driving, with a "meta" thread to catch the Dot up (Aaryan Kapoor)

Aaryan Kapoor (@TheAaryanKapoor) (14 Oct) connected their Dot to T3 Code and kicked off six threads' worth of work by talking to it while driving. Their tip: keep one "meta" thread that knows the state of every other thread, so the Dot gets caught up faster.

51. Sold after the first hour-long walk (Der.dev)

Der.dev (@erd0xbc) (11 Oct, reply to @thsottiaux) has used Dots every day since launch, and says the first hour-long walk spent talking to the Dot is what sold them on it.

52. Four or five rings and drop-outs on the road, but staying (Chris Alarcon)

Chris Alarcon (@chrisralarcon) (14 Oct) moved their jobs from Grok Bot to ChatGPT Dots. They wrote that Grok Bot picks up a voice call instantly, while the Dot takes four or five rings, the model is slower, and the call cuts off a lot on the road ("maybe that's just the road"). They are keeping the Dot anyway.

53. Wanting the Dot to draft while you talk (Ajwang Rading)

Ajwang Rading (@AjwangRading) (14 Oct, reply to @reach_vb) asked for Dots to draft in real time during a call, the way advanced voice mode does, so an idea spoken on the call takes shape while they are still talking. They also asked for faster answers on calls. They like the collaborative feel of ChatGPT Work and want more of that with their Dot.

A file move from the car, a recipe at the stove, friends and kids on the line, and a ten-minute dog walk

One of these is an X post from Mitchell Hashimoto. The other three come from two long write-ups by people who use their Dot every day: Eric Porres's two-week diary with his Dot, Jarvis (Substack, 13 October 2026), and Mete Polat's review of his Dot, Satori (Substack, 15 October 2026). Eric's trip calls from the same post are on travel planning, cases 53–54.

54. Last night's benchmarks moved between two Macs, asked for on a call during a food pickup (Mitchell Hashimoto / Chungus)

Mitchell Hashimoto (@mitchellh) (7 Oct) called his Dot, Chungus, while he was picking up Mexican food. He asked it to transfer some Rex benchmarks from the night before, which were on his Mac Studio, to his MacBook Pro via Tailscale. When he got to his desk, the files were already there. He ended the post with "What a … time to be alive." The post doesn't describe the setup behind it; Tailscale is his own private network between the machines, not a Dots feature.

55. A couscous recipe from an old chat, asked out loud at the stove (Eric Porres / Jarvis)

Eric was making couscous with a pressure-cooker method he had worked out in ChatGPT a few months earlier, but he couldn't remember the order of the steps. With a wooden spoon in one hand and no keyboard nearby, he asked Jarvis out loud. Two parts butter to one of oil? Yes. Toast the grains first? Yes. Garlic now? Later, or it burns before the couscous is done. How long off the heat? Five minutes, natural release. Jarvis had the recipe from that old chat, and the answers came one at a time, in the order his hands needed them. His closing line: the couscous was fine, and garlic goes in late.

56. A call handed to friends and kids: Dublin tips, a Brooklyn brunch, a chess opening and debate dates (Eric Porres / Jarvis)

Eric wanted some of his friends to experience Jarvis, so he called it and talked to it the way he would to a person, then introduced it around: two friends who wanted to see what an assistant does with a computer of its own, another heading to Dublin who wanted recommendations, and two more hunting for a sit-down brunch in Brooklyn. Everyone asked their own questions and interrupted, and the demo turned into a conversation. Then his kids found it. One of his sons spent a call on the Vienna Gambit and how to play attacking chess; his brother worked his debate tournament dates around fencing. Eric is open that this isn't hands-off yet: he interrupts, reconsiders and mangles names, calls drop, and sometimes Jarvis frames the problem wrong and he has to restate it. Jarvis also wrote him a summary of their voice calls, one of the two documents the Jarvis quotes in his post come from.

57. Ten minutes of plans on the morning dog walk, and the rough edges of calling (Mete Polat / Satori)

Mete Polat, a product designer, keeps one ongoing thread with Satori and mixes voice notes and calls in it: an idea for an article to file as a note, his Japan visa process to start, some feedback on a landing page, all in one go. Satori pulls out the actionable parts and starts a separate thread for each. Calls help him unload his mind while doing something else, so he often spends ten minutes of the morning dog walk talking through his plans for the day, knowing the Dot will have acted on them by the time he is home. He also lists what still feels rough. Calls were mostly broken for the first few days, and the fake ring lasts 10–20 seconds before it tries to connect. If he takes a second too long to find a thought, it chimes in with an empty affirmation, and after saying it will go and do something, it can go silent for minutes until he asks what's going on. It also kept getting his name wrong: right now and then, apologetic every time he corrected it, and then "hey meat" on the next call (it's pronounced meh-teh).

Calls that won't connect or keep dropping: what brought them back (Oct 4–10)

From 4 to 10 October, Dot calls failed for a lot of people at once. The reports below come from the main GitHub issue and two OpenAI Community threads (one, two), plus two threads about calls that connect and then go wrong. The pattern was the same almost everywhere: ordinary ChatGPT Voice worked, typing to the Dot worked, and only the call to the Dot failed. In most reports, then, the problem was specific to calling the Dot, not the microphone or the phone.

How the week went

• 4 Oct: hashpuppy heard about two rings and then "Couldn't connect. Check your connection and try again." on an Android phone and on Linux desktop web, over Wi-Fi and mobile data. Switching the voice from Live to Standard changed nothing.
• 7 Oct: the wave. Linda9 got "Couldn't connect the call. Please try again." on iPhone, web, Mac and Windows, even on mobile data with Wi-Fi off. cm.h heard two rings and a timeout from about noon US Eastern time. BKimAtCCA had calls working that morning after a Windows app update, then failing in the app and in Chrome. zhouziyueharry saw the same on Windows, web and Android. mkostrus-gif in Kyrgyzstan tried a US VPN endpoint and got exactly the same failure.
• 8 Oct: calls that had worked a few hours earlier stopped for Zachariah-Jack on a Galaxy S24 Ultra, and they were still failing after closing and reopening the app. isakandrey-ship-it was mid-call on an iPhone when, for under a second, they heard what sounded like other voices; the call froze and every retry failed for the next three hours. They asked OpenAI to check it privately and said it is not proof of anything.
• 9 Oct: OpenAI Support wrote in the community thread that fixes for Dot call connections had rolled out on 8 October, and asked people to try again.
• 10 Oct: not everyone was back. Shismo said calls still timed out after the fix, while regular Voice and text worked, and gave a support case number.

What brought calls back

• Reboot the Dot, then wait. zhouziyueharry posted "try reboot" in both threads. Liri rebooted and calls came back about an hour later, not right away. Porringuimalvado said the restart took 30 minutes but worked. Linda9, who had tried everything on 7 October, was connected on 9 October after updating the app and rebooting the Dot. If you reboot and the next call still fails, give it half an hour to an hour before you decide it didn't work.
• Change the network, not the device. tonydehnke found that after a reboot, calls from an iPhone connected on Wi-Fi but rang unanswered on direct cellular (Public Mobile, Canada). Cellular routed through Tailscale with a Mac at home as the exit node connected again. That's one carrier in one country, but if calls fail only when you're out, try Wi-Fi before anything else.
• Start an ordinary Voice chat first. Saentzee had a log line saying "Voice transport hangup was not confirmed". They opened a regular chat, started and ended a normal Voice conversation, then called the Dot, and it connected. They were careful to say this worked once and may have been the service recovering at the same moment.
• If the screen locks and the call drops on iPhone, it may be a setting. psicompany.com lost a live demo because the iPhone locked mid-call, which regular Voice doesn't allow, and houmark had the same on iOS 27. Houmark then fixed it in the ChatGPT app's own settings, under Voice → Background conversations, not in the iPhone's settings app. With that on, the call stayed up through the lock screen and app switches.

What didn't help

• Clearing the Android app's data and cache, and switching microphone permission off and on (aspin).
• Restarting your own phone or computer, trying another browser, or signing out (Saentzee, sffiltech-openclaw).
• Starting and ending an ordinary Voice chat before calling the Dot, for Onigiri on an iPhone on 14 October; calls still stayed on "Calling…".
• A VPN to another country (mkostrus-gif) and switching Live to Standard voice (hashpuppy).
• A Reboot that said it was submitted: feiyanchen2026-cmyk chose Your dot → ⋯ → Reboot, got a confirmation, and calls still failed on Windows web, iOS and Android. They also couldn't find a restart button inside the Dot's remote Linux desktop.

When the call connects but the answer comes by text

jimong18 had a different problem on 9 October: the call connected, and the Dot, Maven, said things like "Let me check", but the answer never came back as speech. It appeared as a text message in the Dot chat instead, first for Gmail and Calendar questions, then for general ones too. If that happens, read the chat while you're still on the call. The work has usually happened; only the spoken reply is missing. @Splendid_0823 (case 44 above) hit the same "let me check" loop for three days on both phone and laptop.

A check order for calls that won't connect

This order is based on the reports above.

1. Send the Dot a text message. If it answers, your Dot is fine and the problem is only the call.
2. Make a regular ChatGPT Voice call. If that fails too, check your network or microphone. If it works, the problem is the Dot call.
3. Try a different network, such as home Wi-Fi instead of mobile data.
4. Update the ChatGPT app, then reboot the Dot from its menu. Wait 30 to 60 minutes before you try again.
5. On iPhone, turn on Voice → Background conversations in the ChatGPT app if calls drop when the screen locks.
6. If it still fails, report it with the time and time zone of each failed call, your app version, and whether regular Voice worked. That is what OpenAI Support asked people for. When they traced one stuck iPhone call, they also asked whether it ended on its own or only when the caller stopped it (OpenAI Support, 12 October), so note that too.

While calls are down, you can ask the Dot in text:

My calls to you aren't connecting, but text works. Until I tell you calls are working again, keep anything you'd normally tell me on a call short and in this chat, and put any decision you need from me in the first line.

What gets lost between a call and the work

The cases above show what a good call can do. The reports below are about the gap that opens when the call ends: you said something out loud, and later the work isn't there. Most come from Dot users in the openai/codex GitHub issues and a few from the OpenAI Community, grouped by what went wrong.

Spoken requests that never became work

• hpsazz1 (Windows, 6 Oct) asked for a task during a call, and every attempt came back with voice_parent_context_pending or voice_parent_unconfirmed. Retrying didn't help. Typing the same instruction into the text chat worked, and the task ran.
• deluan (Mac, then Android, 7 Oct) got "Not sent. The spoken context could not be confirmed yet." Hanging up, calling again, and switching from the computer to the phone gave the same message. Requests sent as text went through.
• philbritton (iOS, 8 Oct) asked the Dot on a call to take an approved outside action. The handoff came back as "outcome uncertain", and nothing showed up in the target conversation. Updates from the Dot's main thread still reached the call, so the problem ran in one direction only.
• moruku36 (9 Oct) asked by phone for stopped work to carry on, and remembers the Dot saying it would. Back in the text chat, the Dot couldn't find the call content and nothing had resumed. They restated the request in text two minutes later, and after that the work resumed.
• joshskyhi (Mac, 8 Oct) used a call to ask for work in an admin console already open in Chrome. The handoffs kept coming back unconfirmed, no browser task ever appeared, and in the end they switched to doing it by hand with instructions.
• kendonB (30 Sep) asked by voice for a Slack group DM with a colleague and a "hello". The automatic approval check refused it because it didn't count a forwarded voice transcript as permission, and refused again on retry. They were told to repeat the request as text in the main chat.
• lukebrevoort (iOS, 14 Oct) asked on a call, with explicit permission, for a calendar study block to move, a research task to start and a study Space to be created. Every handoff came back voice_parent_unconfirmed with "The outcome is uncertain", and none of it happened: the calendar still showed the old time and no new Space existed. On the same call, read-only calendar and Space lookups, web searches and sending a draft to the Dot's chat all worked.
• nkpryor (16 Oct) gave detailed instructions and permission on a call to update recurring events on two calendars, and the Dot said it would. Asked for status in the text chat, it said the call summary was unavailable and asked for the instructions again, and the calendar was unchanged. On a later call the voice side repeated the original instructions accurately; after nkpryor authorised it again on that call, the calendar tools ran and both calendars were corrected. The lesson they draw is that voice and text don't yet share what was promised, so check the result rather than the promise.

Calls that dropped or got stuck mid-call

• ljjay (iPhone, 8 Oct): when the phone locked itself during a call, the call ended.
• RayzorYv (web and Windows, 7–8 Oct) refreshed the web page during a call and lost the hang-up button. After that, every new call failed with "Voice transport hangup was not confirmed", even after restarting the app and rebooting the PC. Text messages to the Dot kept working.
• grtninja (Windows, 8 Oct) found that the live transcript of a call sat in a separate, unnamed conversation that didn't appear in the sidebar. After 13 minutes 36 seconds it showed "Turn ended by Auto-review" and stopped, while the call carried on in a newly created conversation. The phone still showed the full transcript in the Dot's main chat.

What the Dot heard and said

• NaturalMatchaKing (5 Oct) was greeted with a wrong, made-up name on two calls in a row, and the Dot repeated it when asked. On the third call, telling the Dot to leave names out of the greeting fixed it.
• The same user reported on 9 Oct hearing a short echo of their own voice, then a different male voice asking work questions they hadn't asked, which the Dot answered as if they had. No harmful action was reported, but they now avoid calls.
• wchwawa (1 Oct) said goodnight, the Dot said goodbye, and the call stayed open. Asked to hang up, the Dot said they had to press the end-call button themselves.

Calls that never connected, and what fixed them

• rokoo44 has seen calls stuck on "Calling…" on both Mac and iPhone from 30 Sep through 8 Oct, with no error. Restarting the apps didn't help; text works.
• kcrazy had calls end on their own about 12–13 seconds in. TheBeems got "The call failed" on Android over Wi-Fi and 4G on 7 Oct, after calls had worked earlier that day, while ordinary ChatGPT Voice still worked.
• Two fixes from the same thread: dmzu-cn said updating the app made calls work again, and hmchen fixed it by right-clicking the Dot in the desktop app and choosing Reboot. More of these are on the Dots not working page.

What these reports add up to

1. A call is good for talking things through, but in these reports the text chat is where requests reliably turned into tasks. Everyone who later typed the same request saw it go through, and the one person who got it done by voice had to authorise it again on a second call.
2. When a request involves sending, posting, or approving something, voice is the weakest route. The approval check treats a call transcript differently from a message you typed, which matches what people describe on the Run Codex tasks page.
3. "I'll handle it" on a call is not proof that anything started. Check the chat for a task link or a written note before you put the phone away.
4. A dropped call usually leaves the Dot itself fine: in every report that mentions it, text messages kept working. If calls keep failing, update the app and reboot the Dot before anything else.

Copyable prompts for these failures

Each prompt targets a failure that at least two of the reports above describe.

Before you hang up (moruku36, philbritton, hpsazz1, grtninja):

Before we hang up, write in our chat every task you started from this call, with a link to each one. List anything I asked for that you couldn't start or send, so I can type it myself.

For anything that sends, posts, or approves (kendonB, hpsazz1, joshskyhi):

Don't send, post, or approve anything because of what I say on this call. Write it as a short request in our chat, and I'll confirm it there in text.

Only act on what you're sure I said (NaturalMatchaKing's two reports):

On calls, don't greet me by name. If you hear a question or an instruction you're not sure came from me, read it back and wait for my yes before you do anything with it.

After a call drops (ljjay, RayzorYv, grtninja):

Our call just dropped. Tell me the last thing you heard from me and what you had started. Don't repeat or restart anything until I confirm.

Ending the call (wchwawa, moruku36):

That's everything. Say back in one sentence what you'll do and when I'll hear from you, then I'll hang up.

Copyable asks for your next call

Delegate, then hang up:

I'm about to hang up. Take this job: [job]. Sources: [files, links, or connected apps]. Done means [definition of done]. Send the result to me in [ChatGPT / Slack DM] by [time] [timezone]. Draft only; don't send, post, or buy anything.

Clear the small stuff while you walk:

Go through my unread email and Slack from today one item at a time. For each one, tell me in one sentence what it needs, and I'll say reply, skip, or later. Draft the replies I approve and send me the list in writing when we hang up.

Status check while you're away from the desk:

Give me a 60-second status on [project]: what finished since [time], what is blocked, and the one decision you need from me. Then message me the same summary in writing with links.

From the car:

I'm driving, so keep answers short and don't ask me to read anything. First repeat the job back to me in one sentence: [job]. When you find the answer, put a screenshot or link in our chat so I can show it later. If the call drops, keep going and message me the result.

Several threads at once:

Keep one status thread that lists every open thread, what each one is doing, and what is blocked. Read it before you start anything new from this call, and update it when we hang up.

From a walk or the stove (based on cases 54–57):

I'm walking [or: cooking], so keep answers short, and if I pause, wait for me instead of filling the silence. I'll list what's on my mind for today. When I'm done, read back each job you heard in one sentence, start a separate thread for each, and tell me which ones need my yes. If I ask how to do something step by step, give me one step at a time and wait for "next". Once the work has started, put the list in our chat, and if a job will take longer than [10] minutes, tell me when to expect an update.

Related

• Getting started · Features · How to get Dots · Who can get Dots · Use cases hub · Slack assistant · Email triage · Run Codex tasks
• AI secretary for the daily pile: real cases: eight calls on a commute, review pages instead of task lists, and a bedtime handover
• Teachers & students: a teacher's Dot reviewing student work, and a voice Italian tutor
• Content pipeline: real examples: turn a call, webinar, or video into clips, posts, and blog drafts
• When the Dot stops mid-job with an abuse-prevention message: "Your dot is on a break": what users saw
• Dots not showing up? · Integrations · Pricing