GPT DotFIELD GUIDE
Home/Guides
Guides

How do you use a ChatGPT Dot as a Slack assistant? DM it, forward a message or @ it in a thread: setup, reply times, and what to do when replies get stuck (OpenAI Dots)

Connect Slack from your Dot's profile, then DM it, forward it a message or mention it in a thread, and mention it again in every follow-up. Setup steps, admin approval, reply times, and what helped when channel posts failed, answers landed in the wrong place or a send was refused, plus weekday board summaries, partner questions answered with the email history checked first, and copyable asks.

GPT Dot · Updated
Official ChatGPT Dots demo: Dot Jojo posts as an AGENT in a Slack project channel
Image source

The short version: what a Dot does well as a Slack assistant, how to set it up, and where replies get stuck

Is a Dot a good Slack assistant?

Yes, for work that can wait a few minutes. You can DM it a job, forward it a message to deal with, or have it send you a status at a fixed time and bring you the decisions. Pat Simmons gets a weekday 9 PM board summary and approves the cleanup in Slack (case 1), Brooke Bachesta forwards a message with "deal with this" and her Dot updates five tools (case 26), and Dan Shipper's Dot posts his results and brings the replies back so he can stay out of Slack (case 4). It is also good at the slow part of answering someone: when a partner's question lands in Slack, Makoto Takeuchi's Dot reads the related emails and other apps first, lays out the background, drafts the reply, and sends it once he writes "answer with this" (case 28). It isn't yet a reliable real-time teammate in channels. Answers took about three minutes at LOLIPOP! and about 50 minutes for a colleague's request at The Slide Factory, channel posts have failed while DMs worked, follow-ups in a thread are ignored unless they mention the Dot again, and some people couldn't get the Dot's own Slack app installed at all (cases 10, 13, 15 and 25). It suits people who already live in Slack, want one place to hand over tasks and approve sends, and keep urgent questions with a person.

How to set it up

  1. Check that you have a Dot. It 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). It is the same Dot as in ChatGPT, with the same memory, but a Slack thread only shows the messages sent there.
  2. Settle the Dot's name first, especially if your company has a rule for handles. The Slack handle is created at setup. Renaming the Dot later didn't change it for bradynapier, and deleting the app to start over left them unable to add the Dot back (case 12).
  3. On desktop, open the Dot's profile, select Add and connect Slack (Message your dot). On a company workspace, an admin has to turn on both Use dots (Beta) and Add dots to Slack and Microsoft Teams, a Slack owner may have to approve the app, and each member then completes their own setup (Manage dots in ChatGPT workspaces). If the first try says "Slack setup failed. Try again.", a second try worked for LOLIPOP! (case 15). Don't confuse it with the ChatGPT Agents app in Slack, which deploys shared workspace agents to channels (ChatGPT Agents app in Slack); a Dot is your own agent with its own handle.
  4. Read the permission screen before you allow it. uehara's asked for scopes such as "post as you", "read DMs" and "create channels", and actions taken through his logged-in apps were recorded under his own name (case 18).
  5. Start in the DM, then test each channel. Send one small read-only job in the DM and see how long it takes. Then add the Dot to a channel and mention it in a thread, because it ignores channel messages that don't mention it (case 15). Mention it again in every follow-up in that thread, or move the back-and-forth to the DM: a follow-up without a new mention doesn't reach it (openai/codex #55095; more on the Slack integration page). Before you rely on a channel, ask it to reply in a thread there and send you the link.
  6. Say who it works for and where each update goes. By default it responds to you. You can tell it to engage with others, and it may message you privately first to ask what you're comfortable sharing before it replies in a channel (Message your dot). Other people's DMs and mentions don't start work for your Dot, so agree that teammates' requests reach it through you. Anything it posts in a channel is visible to that channel's members. OpenAI suggests keeping routine progress in ChatGPT and having decisions brought to you in Slack.
  7. Make every watch explicit. Adding the Dot to a channel doesn't set up a watch: name the channels, what to look for and when to tell you, then ask it to confirm the recurring task. Give scheduled jobs a fixed time, place and format, as in Pat Simmons's weekday 9 PM summary with counts and blockers (case 1). For replies to people outside your team, ask it to check the related mail and earlier threads before it drafts, as Makoto Takeuchi's Dot does (case 28).

Where it gets stuck, and what fixed it

  • Setup fails, or the handle won't change. bradynapier's rename never reached Slack and re-adding failed after the app was deleted (case 12), and scottinallcaps went through Add to Slack again and again while the Dot's own Slack app was never created (case 25). What worked: name the Dot before you connect, and don't delete the app just to rename it. When the Dot's app never appears, Marcroberts's Dot keeps the job going through the Slack plugin on a schedule. It posts under the plugin account's name and only notices mentions at the next check (case 25).
  • It reads the channel, but posts fail with -32603. DMs kept working for nittajun and u/Thin_Ordinary4931 (case 13). What worked: nittajun's channel replies came back when the Dot used its own Slack sending route, while the general send route still failed for markguoz and Vino4. Ask for the thread link after every channel post, and keep the replies you depend on in the DM until the link shows the post.
  • A follow-up in the thread gets no answer. In a channel thread, each new message reached loweaxerium's Dot only when it mentioned the Dot again, and they asked OpenAI for a mode that follows the whole thread (#55095). What helps: mention the Dot in every reply you want it to see, or ask it to move the conversation to your DM after the first answer.
  • The answer is somewhere you didn't look. uehara's 81-second answer sat in a thread behind "1 reply" (case 18), Tim Perelman's Slack question was answered in the main ChatGPT chat (case 20), and replies that mentioned nittajun didn't show under Mentions (case 14). What helped: open the thread before you ask again, tell the Dot to answer where you asked, and agree up front where each kind of update goes.
  • A send is refused. kendonB's request on a voice call was rejected because the transcript didn't count as his authorization (case 16), open-workbench's finished answer was blocked as "already sent" when only the acknowledgement was in the thread (case 17), and Dan Shipper had to approve the same basic thing several times (case 4). When a coordinating Dot passed don-ludemann-aa's approval for Slack, Outlook and Teams alerts on to a worker task on his Windows computer, Auto-review sometimes accepted it and sometimes refused it as untrusted, and asked for his consent again inside the worker task (openai/codex #55408). What helped: give the go-ahead in writing, in the chat or task where the work actually runs, ask the Dot to read the thread back and quote the exact refusal, and let it retry once at most before you step in.
  • It's slow, or goes quiet after "I'll check". LOLIPOP! waited about three minutes per answer, a colleague at The Slide Factory waited about 50 minutes, and uehara's mention summary failed on the way back with no word until he nudged (cases 10, 15 and 18). What helped: use Slack for things that can wait, ask the Dot to post a short "seen it, answer by…" note when it can't start, and ask for the status after a few minutes of silence.
  • Replies stop altogether. Joseph Vitko's Dot could no longer reply in Slack, with no error shown (case 21). Check the Slack connection on the Dot's profile and whether the workspace still has the Dot's app before you recreate anything; see Dots not showing or not working.
  • Other agents in the channel don't wake. Ahmad Alkabra's Dot answered mentions under its own identity, but Muse and Grok bots didn't wake, so he still relayed links and replies by hand (case 23). What helps: have the Dot write the exact handoff text for you to paste, rather than expecting agents to call each other.

What it can and can't do yet

What it already does well:

  • Sending a status summary or a morning check to your DM at a set time (Pat Simmons, Desmond Dixon).
  • Flagging urgent messages with a draft reply, and sending only after you say "send it" (MindStudio, AI Never Sleep).
  • Answering a partner's Slack question with the background pulled from mail and other apps, then sending your approved reply (Makoto Takeuchi).
  • Handling a forwarded message across several tools and listing what it changed (Brooke Bachesta, Gabriel Chua).
  • Posting results to a channel and collecting the replies while you stay out of Slack (Dan Shipper, Peter Yang).
  • Keeping a shared client channel moving towards decisions (Matthew Bradford).
  • Watching an alert channel, such as the one Sentry posts errors to, once the plugin is connected (proximalcoast).
  • Keeping more than one Dot within reach as Slack DMs, while ChatGPT pins only one (Chris).

What it doesn't do yet, or not reliably:

  • Answering in real time; expect minutes, sometimes much longer (cases 10 and 15).
  • Posting in every channel; some posts have failed while DMs worked (case 13).
  • Following a thread after the first answer without a new mention (#55095).
  • Taking work straight from teammates' DMs or mentions, since only the owner directs it.
  • Treating a spoken yes on a voice call, or an approval passed along by another task, as approval for a send (case 16, #55408).
  • Changing its Slack handle after setup, or being added back after its app was deleted (case 12).
  • Waking on a mention when you run Slack through the plugin instead of the Dot's own app (case 25).
  • Handing work to other agents in the channel without you relaying it (case 23).

If your team is on Microsoft Teams instead, see Teams. For daily catch-ups that combine Slack with mail and calendar, see the AI secretary page.

One prompt to copy

Built from what worked for Pat Simmons, AI Never Sleep, Brooke Bachesta and Makoto Takeuchi, and written to avoid the delivery and approval problems above:

You are my assistant in Slack. Every weekday at [time] [timezone], DM me what needs me today from my DMs and #[channels], each with the thread link, who asked and a draft reply in my voice. Before you draft a reply to someone outside my team, check the related emails and earlier threads, and list in one line what you checked. When I forward you a message and say "deal with this", restate what it changes in one line, list every place you would update and wait for my written yes. Don't send or change anything until I write "send it". Answer in the place where I asked you. If a channel thread needs more than one answer from me, ask me in your DM with me. After every channel post, read the thread back and send me the link; if a send is refused or fails, tell me the exact error and keep the reply in your DM with me. Act on other people's messages only when I forward them to you. If you can't start on something within [N] minutes, tell me when to expect it.

Prompts for single problems, such as delivery tests, forwarded messages and the plugin workaround, are under More copyable asks at the bottom.

Work it handles through Slack

1. A weekday 9 PM board summary and a cleanup approved on a call (Pat Simmons)

Pat Simmons of AI for Mortals connected the Dot, László, to Slack because the mobile app wasn't showing it yet, and kept handing it jobs on the way home, with shopping choices and screenshots landing in Slack threads. László found Code Queue, the board Pat's coding agents use, and set up a status summary in Slack every weekday at 9 PM. On a later voice call Pat asked it to propose which stale issues to close; about a minute after the call ended, the "Code Queue cleanup" list for Pat's approval was waiting in Slack. João Queirós's write-up singles out the same loop: decide on a call, approve in Slack.

2. Urgent messages flagged with a draft reply, and a scratchpad for a packed day (MindStudio)

In MindStudio's first-week guide, Slack was already connected in ChatGPT, so the Dot used it from the start. It flagged Slack messages that looked urgent and offered draft replies without being asked each time, surfaced a relevant Slack thread on its own during the week, and put emails, Slack messages and the calendar into one personal scratchpad agenda for a day full of meetings.

3. Connected in minutes, with a price suggested and a reply sent only after "send it" (AI Never Sleep, 5 Oct)

The Korean blog AI Never Sleep named its Dot 네슬 and connected Gmail, Google Calendar, Slack and a few other plugins. The author found the Slack bot easy to connect, and noted there was no need to write up context in markdown files first, as they had to for Hermes or OpenClaw: past conversations came from ChatGPT memory and recent news from the connected mail and calendar. In the first conversation the Dot proposed jobs on its own, including a reply to a collaboration request. Asked what to charge, it suggested a three-channel bundle at 800,000 won plus VAT. The author changed the scope, asked for a draft with a site link and said not to send it; the Dot showed the draft and confirmed it hadn't sent anything, then sent it exactly as approved after "좋아 이렇게 보내줘" ("good, send it like this"). Unasked, it also flagged a number to check in the next morning's meeting material, and the following day reported that the missing data had been updated.

4. Weekend results posted to Slack, replies brought back (Dan Shipper / Boo, Every)

Dan Shipper, CEO of Every, wrote on 7 Oct that over the weekend his Dot, Boo, posted his model-testing results to Slack and brought the replies back to him, so he could keep working without opening Slack and losing an hour there. He says people at Every use their Dots to catch Slack messages they missed, pull key details out of school emails and flag account-access requests. His complaint was about permissions: he had to approve the same basic thing several times, and sometimes the Dot still said it couldn't do it after he had approved.

5. Slack read together with mail, calendar and Codex agents, turned into tickets (Madiyar, 30 Sep)

Madiyar wrote in Russian that his Dot reads his calendar, mail and Slack on its own, checks his Codex agents and tells him what is going wrong there, creates tickets, and asks which tasks to hand to other agents. Slack is one input among several here: the useful output is a ticket and a delegation question, not a Slack summary.

6. Competitor research for a friend's course, asked in a Slack DM (Peter Yang / Zoe, 29 Sep)

In his launch-day video, Peter Yang added his Dot Zoe to a direct Slack thread in his newsletter's community with Colin, an AI instructor who sells a course on Maven, and asked it to research similar Maven courses and name the two or three changes that would make Colin's page an easy yes. About six minutes later Zoe proposed a headline built around the finished work students leave with, plus three changes drawn from the other courses. Colin found it a little slow; Peter didn't. The full case, with the community review that followed, is on Teaching & learning.

7. A morning check of Slack and email, and a CRM error fixed after one yes (Desmond Dixon, 7 Oct)

Desmond Dixon, who writes a newsletter for service-business owners, ran his business through a Dot for 48 hours, much of it by text from his phone while he was five hours from home. Every morning the Dot went through his Slack and email and then asked what it could take off his plate. One morning it noticed a booking error in his CRM and asked whether it could fix it; he said yes, and it did. The same 48 hours also show the limits: when his computer went to sleep, everything stopped, it still needed him to approve things, and coding was weak. He scored it 6 out of 10, closer to 9 as a virtual assistant, and cancelled his subscription for now.

22. An on-call Dot that watches Sentry errors in Slack (Joseph / proximalcoast, 13 Oct)

Joseph (@proximalcoast) (13 Oct 2026) wrote that he built his own on-call agent: take a ChatGPT Dot, integrate it with Slack, set up Sentry with their MCP as a custom plugin ("so easy, and correct permissions"), then tell the Dot to watch whatever channel Sentry sends errors to, and tag your releases. The post stops at "Tag your releases" and doesn't say how the watch went after that. The next day he quoted the same post to say he should not be emailed to "check out dots" when Dots is already heavily integrated into his workflow.

23. One Slack channel, three agents, and the human as courier (Ahmad Alkabra, 13 Oct)

Ahmad Alkabra (@ahmadalkabra) (13 Oct 2026) put his OpenAI Dot, a Grok Bot, and Muse in one Slack channel. Too often he was the courier: copying links, asking an agent to read a thread, and relaying its reply to another agent. Agent identity is a problem; reliable handoffs are the bigger one. His Dot has its own Slack identity and answers mentions. His Muse connection reads Slack but nothing wakes it, and the same goes for Grok bots: a keyword listener worked briefly, then failed, and he was back to manual relays. He asked Slack for a consistent way to mention an agent with context, get an acknowledgment under its own identity, let agents hand work to each other without him forwarding messages, see who owns the next action, and avoid duplicate work and re-reads of long threads.

24. Forward a Slack design note; Dot finds the Drive template (Gabriel Chua, 14 Oct)

Gabriel Chua (@gabrielchua) (14 Oct 2026) wrote that he loves using his Dot in Slack and forwarding it 1,001 messages. One handoff across tools: Codex was building his Tokyo and Seoul DevDay presentation as a Sites app (not a slide deck); Design flagged font sizes and referenced an existing template he had skipped while vibe-coding; he did not know where the template lived; so he forwarded the Slack message to his Dot: find it in Drive, extract the typography, pull the remotely hosted source, and compare the two. He notes it is hard to demo Dots in Slack without spilling the secret sauce.

26. "Deal with this": one forwarded Slack message, five tools updated (Brooke Bachesta / Crux, 29 Sep)

Brooke Bachesta, who works at OpenAI, wrote on LinkedIn on launch day (29 Sep 2026) about her Dot, Crux. Inside the Slack app she forwarded messages to Crux with nothing more than "deal with this", and it worked out what to do. One of those messages was someone telling her they could no longer make an in-person training. Crux updated every relevant row in her Airtable, updated the spreadsheet her leaders look at, removed the person from Slack and from the calendar invites, made sure their booking in Navan, the travel tool, was updated, and then told her it had done all of those things. She also uses Crux to find gaps in programs she has built, shore up automations and suggest better workflows.

27. A follow-up Slack message drafted unasked, and specific tasks that work better than waiting (Matt Socha, 6 Oct)

Matt Socha (LinkedIn, 6 Oct 2026) set up a Dot without expecting much. The first moment it clicked was a follow-up Slack message the Dot wrote for him without being asked; he read it and thought it was actually good. Beyond that one draft, the proactive side hadn't landed for him yet, and he was still waiting for a pattern to show. What did work was giving it tasks: he hands it something specific, it handles it, and he moves on. He plans to keep using it.

28. A partner's Slack question answered with the email history checked first (Makoto Takeuchi / Mina, 16 Oct)

Makoto Takeuchi (note, 16 Oct 2026) works with partner franchise stores at a support service for older people and calls his Dot, Mina, his first secretary. When a partner store sends a question in Slack, the message alone is often not enough to answer it, because the background sits in earlier emails and other places. Mina reads the related emails and other connected apps, lays out the history and the current situation, and drafts a reply. He checks whether the facts are right, whether the wording will come across, and what he wants to add, then tells it "answer with this" (これで回答しておいて), and Mina sends the reply in Slack. He also gets reminders he never asked for: things to remember, items added to his task list, and replies that should go out soon. He writes that it doesn't notice everything and isn't always right, but having a second pair of eyes on the state of his work takes a load off him.

Teammates and group channels

The documented rule is short: only the Dot's owner can direct it, and other people's DMs or mentions don't start work for it. You can tell it to engage with others, and it may ask you privately what it can share before it replies in a channel (see the setup steps at the top). The early reports below describe team and client use in looser terms, so read them with that rule in mind.

8. "Your team can message your bot directly" (Justin Schroeder, 29 Sep)

Justin Schroeder had early access and called Slack the place where Dots "really shines": his team could message his Dot directly, and it could take actions such as spinning up new panes. He posted this on launch day, from the preview, before OpenAI published the workspace admin article quoted above. He also disliked that any account he had authorized in ChatGPT was open to the Dot without a separate grant.

9. Team requests and research, with Slack and voice connected (Abdallah Khraisat, 4 Oct)

Abdallah Khraisat, who builds AI systems for companies, wrote on Threads in Arabic that after connecting his Dot to Slack it takes instructions from his team's messages and researches on its own, and that giving it a virtual machine turned his day into handing over results to check instead of watching a chat. His video describes the setup as Slack plus voice calls, used to answer team requests. Neither post says whether teammates' messages started work by themselves or he passed them on.

10. Part of the group chat, but 50 minutes behind it (Mark Nguyen / Toby, 2 Oct)

At the agency The Slide Factory, Mark Nguyen connected his Dot Toby to Slack. It announced the connection before checking that it could reach the colleague he wanted to message, and that DM failed; a message to the group through an explicit route eventually worked. In the group, Toby delivered a joke two-word reply word for word at Mark's request, credited to him. Mark then gave it permission to handle routine group conversation and non-sensitive work requests within limits, but a colleague's request for a PDF summary at about 4:24 p.m. was only picked up around 5:13 and answered at 5:15. His conclusion: permission set what Toby may do, not whether it will notice every mention in time.

11. A client channel brought back from small talk to requirements in two days (Matthew Bradford / Riri, 9 Oct)

Matthew Bradford, a developer who runs client projects, wrote after one week with his Dot Riri that the most impressive job was in a Slack channel he shared with a client. Riri watched the conversation and helped guide the client towards decisions about how they wanted to run their business, so a development project could start; Matthew mostly observed and stepped in where he could steer. The channel had drifted into casual chat (another chat agent in it, Ordo, produced an unprompted JSON dump that everyone joked about), but Riri kept pushing the requirements, and within two days the group had something actionable. Outside Slack, he says Riri drafts email replies by default for him to review and updates his CRM and task board when a tracked task changes, often without being told.

19. ChatGPT pins one Dot; Slack holds the rest (Chris @qwts_chris_dev, 12 Oct)

Chris (@qwts_chris_dev) wrote that even though he could only pin one Dot in the ChatGPT app, he can add the rest in Slack. His screenshot of Slack Direct messages shows chris-q-dottie (selected, with a "1" badge), Devin, and chris-q-jane, two Dot-style handles side by side in the DM list. Useful when you want more than one specialist Dot reachable without relying on the single pin in ChatGPT.

Where Slack setups break

12. A company naming rule, a handle that wouldn't change, and a Dot that couldn't be added back (bradynapier, 7 Oct)

On the OpenAI Developer Community, bradynapier connected their Dot to Slack and got an auto-generated handle built from their name and the Dot's. Their company wanted handles like "bradens-dot" so everyone could tell the Dots apart. Renaming the Dot didn't update the Slack tag, so they removed the Dot's app from Slack to start over, and after that every attempt to add it back failed with a generic error, even though the app was approved and colleagues' Dots worked in the same workspace. Their Dot wrote up the troubleshooting for the bug report. If your team has a naming rule, settle the Dot's name before you connect Slack, and don't delete the app just to rename it.

13. It reads the channel but can't reply there, while DMs work (nittajun, 2 Oct; u/Thin_Ordinary4931, 5 Oct)

nittajun reported on GitHub that their Dot received mentions in two new private channels and could read the messages, but every reply in those threads failed with "Mcp error: -32603: MCP request failed". Replies in a conversation started from the Dot's DM worked. Making a channel public and making the bot a channel manager didn't help. Others on the same issue saw a plain top-level test post fail the same way, and three days later u/Thin_Ordinary4931 asked on r/codex whether anyone else's Dot could see Slack messages but failed to post with the same error. On 4 October nittajun posted an update: channel replies were working again through the Dot's dedicated Slack sending route, confirmed by reading the messages back in two channels and by the recipient, while the general message-sending route still returned -32603. markguoz hit that error on 5 October with a channel post through the general send tool, and Vino4 reported the same on 9 October. If channel posts fail, ask the Dot to reply through its own Slack identity, read the thread back, and keep the replies you depend on in the DM until a link shows the post.

14. Replies that mention you don't show under Mentions (nittajun, 4 Oct)

In a second GitHub report, nittajun found that when the Dot replied in an existing DM thread and mentioned them, the reply showed in Slack's Activity under All but not in the Mentions view, although Slack search found it. That makes it hard to see only the replies that need you among routine progress updates. Agree on where each kind of update goes: progress in ChatGPT, decisions in a Slack DM.

15. A first setup error, no reply without a mention, about three minutes per answer (LOLIPOP! AI media)

The Japanese hosting company's AI media team tested a Dot for their Dots explainer. Setup asks you to choose the Dot's handle and the Slack workspace; the first try failed with "Slack setup failed. Try again.", which they found clear, and the second worked. In a channel the Dot ignored messages that didn't mention it. Mentioned in a thread, it replied in that thread, but the reply took about three minutes, and there was no emoji reaction to show the message had arrived, so from Slack alone it was hard to tell whether it had been received. Their verdict: better for periodic sorting than for real-time chat.

16. Asked on a voice call, refused in Slack (kendonB, 30 Sep)

On launch week, kendonB asked his Dot by voice to create a Slack group DM with himself, the Dot and a colleague, and to send "hello". The Dot found the colleague and tried to do it through its own Slack identity, but the automatic approval review rejected the action because it didn't accept the voice transcript as his authorization. A retry after checking the transcript was refused too, so no group DM was created and nothing was sent. He was told to repeat the request as text in the main Dot chat. If a Slack message matters, give the go-ahead in writing.

17. A new reply blocked as "already sent" when only the acknowledgement had gone out (open-workbench, 4 Oct)

In openai/codex #50956, open-workbench describes a Dot that had posted a quick acknowledgement in a Slack thread and was then explicitly asked to post the finished answer there. The send was declined with a reason equivalent to "the same content has already been sent or is in progress", but reading the thread back showed only the acknowledgement, not the answer. It happened with a new answer and with a completed-result update, and one retry after the readback was declined the same way. Later replies went through after another explicit request from the owner. In the same sequence the owner also saw "Your dot was paused out of precaution" and had to resume it; the report doesn't claim the two are connected.

18. An answer in 81 seconds, hidden in a thread, and a summary lost on the way back (uehara, 7–9 Oct)

uehara connected a Dot to Gmail, Calendar, Slack, Notion and more and timed 17 tasks from his own work. Right after it was added to Slack, the Dot sent a self-introduction by DM that included a warning: in group conversations, everyone in the conversation can see its replies. A DM asking "Tell me how many events I have left today, with titles only. Do not change any events." was sent at 21:06:42 by Slack's timestamps. The acknowledgement came 13 seconds later and the answer 81 seconds later, but as a thread reply, so the DM list showed only "1 reply" and the answer stayed out of sight until the thread was opened. A separate request, a 3-line summary of uehara's Slack mentions, went quiet for 5 minutes after a short "I'll check". When nudged, the Dot said the check had been completed but there had been an error sending the result. uehara also noted that the permission screen for adding the Dot to Slack asked for scopes such as "post as you", "read DMs" and "create channels", and that actions it took through his logged-in apps were recorded under his own name (DEV Community).

20. Asked in Slack, answered in the main ChatGPT chat (Tim Perelman, 13 Oct)

Tim (@TimPerelman) (13 Oct) wrote that when something was asked through Slack, the Dot answered in its main ChatGPT chat instead, then apologized for responding in the wrong channel when confronted.

21. Dot can no longer reply in Slack (Joseph Vitko, 13 Oct)

Joseph Vitko (@JosephVitko) (13 Oct) replied to @reach_vb that for some reason the Dot can no longer reply in Slack, calling it a "super annoying blocker." No error text was posted. If Slack used to work and replies suddenly stop, check the Slack connection on the Dot's profile and whether the workspace still has the Dots app installed before recreating anything; see also Dots not showing or not working.

25. When the Dot's own Slack app won't install: Slack through the plugin, on a schedule (scottinallcaps, Marcroberts, 16 Oct)

In the same OpenAI Community thread as case 12, scottinallcaps wrote on 16 October that they had removed the ChatGPT app from both workspaces, deleted the Dot-specific app from Slack, uninstalled the Slack plugin in ChatGPT and Codex, and gone through "Add to Slack" several times. Each attempt ended with "Slack setup failed". The ChatGPT app always appeared in the workspace, but the managed app that should give the Dot its own Slack identity was never created.

An hour later Marcroberts, who had hit the same wall after switching Slack accounts, posted the workaround he and his Dot are using until there is a fix. The Dot can still use the Slack plugin, both when you ask it something and in scheduled runs. You can connect more than one Slack account to the plugin, even in the same workspace, and tell the Dot which one to use for its conversations and its scheduled runs. On each scheduled run it can check for mentions, post and reply. Two things are lost: it acts through the plugin account rather than its own agent account, so posts show that account's name, and it doesn't wake when someone mentions it, so mentions wait for the next scheduled check. If you need Slack working this week, this keeps most of the job going. Set the schedule as often as a mention can afford to wait, and tell people in the channel whose name the replies will appear under.

More copyable asks

Fill in the brackets with your own times and channels.

Weekday status, with a cleanup to approve (from Pat Simmons). Each weekday at [time] [timezone] for the next [N] weeks, send me a Slack DM with the status of [board or channel]: counts by state, the top blockers with links, and anything untouched for [N] days. After I decide on a cleanup, list the closures for my approval before changing anything. Confirm the schedule.

Flag what needs me, with a draft (from MindStudio). For the next [N] weekdays, watch my Slack DMs and #[channels] for messages that need my decision or have a deadline within [N] hours. When one matches, DM me the thread link, who asked, the risk in one line and a draft reply in my voice. Draft only.

Suggest the answer and send only after "send it" (from AI Never Sleep). When something in my mail or calendar needs a reply, tell me in Slack, suggest the answer, and write the draft. Show it to me first; send only after I say "send it", and tell me once it has gone.

A morning check of Slack, inbox and one tool (from Desmond Dixon). Every weekday at [time] [timezone], read my Slack DMs, #[channels] and my inbox since yesterday. Send me one message: what needs me today, what you could take off my plate, and anything that looks wrong in [CRM or tool]. Ask before you change anything, and tell me afterwards what you changed.

Test the channel before you rely on it (from nittajun's -32603 error and LOLIPOP!'s three-minute wait). Post "Delivery test [time]" as a reply in the thread I'm about to mention you in, then DM me the link to the post and how long it took. If the post fails, tell me the exact error and keep the replies for this job in your DM with me.

Collect replies while I stay out of Slack (from Dan Shipper and Peter Yang). Post [result or question] in #[channel] and tag [people]. Until [time] [timezone], collect their answers. Send me one message with each person's answer in one line and what still needs a decision from me. Don't answer them yourself.

Pass on what a teammate asked (from Justin Schroeder, Abdallah Khraisat and the owner-only rule). When I forward you a teammate's message, treat it as a request from me: restate the task in one line, tell me what you need, and reply in that thread only after I confirm. Don't act on messages from other people that I haven't forwarded.

Prove the answer reached the thread (from open-workbench's duplicate refusal and kendonB's voice request). When you finish [task], post the result in [thread link]. Then read the thread back and DM me the link to your new reply. If the send is refused for any reason, including "already sent", tell me the exact wording and what is actually in the thread, and don't retry more than once without asking me.

Say when it can't keep up (from The Slide Factory). In #[channel], if someone mentions me with a request and you can't start within [N] minutes, post a short note that you've seen it and when to expect an answer, and DM me the request. Routine questions only; anything about [money, clients, contracts] waits for me.

Deal with a forwarded message (from Brooke Bachesta). When I forward you a Slack message, restate what it changes in one line, list every tool and list that needs updating, and wait for my yes. Then make the changes and send me one line per tool with what you changed. Don't remove anyone from a channel or change a booking without showing me first.

List which Dots live in Slack (from Chris). List every Dot or agent DM you can see in my Slack sidebar. For each, say the handle, whether it has unread badges, and which one is my primary Dot in ChatGPT. Don't message any of them yet.

Watch the Sentry channel on call (from proximalcoast). Watch #[sentry-errors] in Slack. When a new error lands, summarise the issue, the release tag if present, and whether it looks new or a repeat, then DM me. Don't page anyone else and don't open a fix until I say so.

Be the handoff, then stop being the courier (from Ahmad Alkabra). In #[channel], when I forward you a link or thread from [Grok Bot / Muse / another agent], restate the task in one line, do the read or draft I asked for, and post the result back in that same thread with a link. Do not start work from other agents' messages unless I forwarded them. If you need another agent to act, tell me the exact handoff text to paste, and do not invent a direct agent-to-agent call.

Forwarded Slack → Drive typography check (from Gabriel Chua). I just forwarded you a Slack message about [font sizes / template]. Find the referenced template in Drive (or tell me if you cannot), extract the typography tokens, pull the remotely hosted source for [this Sites app / page], compare the two, and DM me a short diff of what to change. Do not edit the live source until I approve.

Slack through the plugin until the Dot's app works (from Marcroberts). Use the Slack plugin account [account name] for this job, not your own Slack app. Every weekday from [9:00] to [18:00] [timezone], every [30] minutes, check #[channel] and your DMs with me for messages that mention you or me. Reply in the thread only to [routine questions], and start each reply with "[Dot name] for [my name]:" so people know who is answering. DM me anything else with a draft reply. Confirm the schedule and which Slack account you will post as.

More Slack setups by job

The ChatGPT Dots + Slack page groups more setups by job:

  • Daily reports posted to a channel: Seowoo Han's one channel per job, まさやん's 10-minute channel check, and 단테랩스's 7 a.m. email summary sent to both ChatGPT and Slack.
  • Jobs given from Slack: 이완성's one-person Slack workspace used as a work archive, tangokorea's design document as an .hwp file, and Riley Brown's 45-minute call that cleared the day's email and Slack tasks.
  • Reading threads and noticing things: Zinho Automates on where a long thread is stuck, Rajat's Dot spotting drift in a channel where nobody had tagged it, and AI 서대표 on Slack history before video calls.

Related

Copy this task brief

How to use a ChatGPT Dot as a Slack assistant: a short verdict, seven setup steps and the common sticking points with fixes, then setups for board summaries, forwarded messages, partner replies, Sentry watches and the plugin workaround, plus one prompt to copy.
Download Markdown ↓

Sources & further reading