GPT DotFIELD GUIDE
Home/Workflows
Workflows

How to set up ChatGPT Dots for meetings: a brief before every call, scheduling rules, calendar-change alerts and follow-ups (25 real setups, OpenAI Dots)

Connect every calendar plus the mail or Slack where meetings get agreed, make sends and invite edits ask first, run one brief by hand, then add scheduling rules and a change watch. Copyable message, common fixes and 25 real ChatGPT Dots (OpenAI Dots) meeting setups.

GPT Dot · Updated

The short version: how to set up a Dot for your meetings, from the brief before the call to scheduling, calendar changes and follow-ups

In one line

A ChatGPT Dot (OpenAI Dots) is good at the work around a meeting: a short brief before the call, spotting clashes and moved meetings, offering times that follow your rules, and finding what you promised afterwards. It works best when it reads every calendar you keep plus the mail or Slack where meetings get agreed, and when sends, invites and calendar edits wait for your yes. This page is the setup; the meeting prep use case goes deeper on the brief itself.

Set it up in this order

  1. Create or open your Dot (getting started), then connect Google Calendar plus the mail, files and chat where your meetings are actually arranged: Dots + Google Calendar, Dots + Gmail, Dots + Slack, and Dots + Microsoft Teams or Google Drive if your agendas live there. Each app is a separate connection (Connect computers and apps).
  2. Add custom rules before the first real job. Set sending mail, sending invites and changing or deleting events to Ask before taking action or Hand off to you; a plugin can also be set to read without write (Dots privacy FAQs).
  3. Run a small test that names every calendar: "What's my next meeting with [name] across my work and personal calendars, and which email thread is it about?" One hands-on test found the Dot read only the main calendar until the ask said "all calendars" (eln hands-on, Japanese).
  4. Run one full brief by hand with the copyable brief on this page, and say the shape you want (one page, cards, or a draft you can approve). Open every source link and tighten the format before you schedule anything.
  5. Give it your scheduling rules: which calendars count, travel time around in-person meetings, hours you don't take calls, and that it offers two times and asks before replying. That is how Shingo Irie and つるモンCEO run theirs (cases below).
  6. Ask for a change watch. Tell the Dot to message you when a meeting moves, is cancelled, or no longer matches what the latest email says, and to check every calendar for clashes. Learn says a Dot can follow up on its own as things change, or start work at a time or on a supported event you name (Tasks and memory).
  7. Schedule the brief only after one good run. Say what to check, when (with time zone and end date), which changes deserve a notification and where to deliver, and have the Dot repeat it back. Then find the task under Recent activity in your Dot's profile or in the Scheduled section, where you can pause it or change its time (Getting started with your dot).
  8. For notes without a bot joining the call, use the Meetings plugin (beta) in the Mac desktop app on Pro or Business. Tell everyone you are taking notes first: the consent reminder is only shown to you. The notes, summary and action items land on a ChatGPT Space page your Dot can work from (The Meetings plugin in ChatGPT).

Common blockers and what fixed them

  • The brief missed a meeting. The Dot read one calendar. Name every calendar in the ask and have the brief end with what it read and what it couldn't see.
  • The brief is a wall of text. Diana got three cards with "To confirm" items only after she said she was a visual person. Put the format in the first ask.
  • An invite edit broke something. Katie Fifer's Dot broke a Zoom link while it updated an invite. Keep invite edits behind Ask before taking action, and ask it to keep the meeting link and attendees exactly as they are.
  • A clear "delete" or "send" ran at once. In the eln hands-on test, "delete that event" ran without a confirmation screen even after the calendar permission had been changed to ask before changes, and "send that draft" went out within a minute. Ask for drafts and proposals, and give the final send yourself.
  • Your calendar is the thing that's wrong. Mark Graban's luncheon moved to a Thursday by email while his calendar still said Friday; his Dot compared the two and flagged it in time. A reminder alone would have reminded him on the wrong day, so ask the Dot to compare event emails with the calendar, not only to read the calendar.
  • A calendar change asked for during a call didn't happen. Voice requests have failed to reach the task for some users; check the calendar after the call and repeat the request in text if nothing changed (voice calls).
  • The task says completed but no brief arrived. A completed run doesn't by itself prove the result was delivered, so compare the first few deliveries with the task's last run (Tasks and memory).
  • The follow-up came back as chat text. Ask for it as a draft in your mail drafts, with owners and dates taken from the notes.
  • Meetings notes are missing voices or never appear. Check both microphone and system audio permissions on the Mac; on Business, ChatGPT Space and the Meetings plugin must both be enabled for the workspace. The audio is deleted once notes are ready and can't be replayed.

What it can do and what it can't yet

It can:

  • Send a brief before each call at a lead time you choose, with sources and "unknown" where it isn't sure (David Yu, チャエン).
  • Find clashes across calendars, Slack and mail, and offer to fix them after asking (Dan Shipper, Katie Fifer, Mark Nguyen).
  • Offer times that follow your rules and ask before it replies (Shingo Irie, つるモンCEO).
  • Tell you when a meeting moves or the calendar no longer matches the mail (neco. host, Mark Graban).
  • Read a transcript or notes and find promises you made, then ask what's still missing (José Carlos Amorim, AI 서대표).

Not yet:

  • Join a call as a bot. The Meetings plugin takes notes without one, but only in the Mac desktop app for now; iOS, Android and Windows are coming, and on Enterprise it is in a limited alpha.
  • Get consent from other participants for you.
  • Promise an exact delivery minute. Schedule the brief a little before you need it.

One message to copy

For every external meeting on my [work] and [personal] calendars, send me a one-page brief [30] minutes before it starts: who I'm meeting, what changed since last time, three questions, and what I promised, with a source link next to each fact and "unknown" where you aren't sure. Also tell me right away when a meeting moves, is cancelled, overlaps something on another calendar, or no longer matches the latest email about it. After each meeting, list what I agreed to do and draft any follow-up for my review. Ask before you send anything, send or change an invite, or edit or delete an event. Time zone: [zone]. Run this until [end date] and deliver to [this chat / Slack channel]. First repeat back what you will check, when, and where you will deliver.

Real meeting setups, grouped by job

Each setup links to the person's own post, video or article; a few were first found through Made with Dots. Names and handles are as the source gives them.

The brief before the call

  • David Yu named his Dot Sam and made meeting prep its first job: two hours before every call, Sam sends a brief on who he's meeting and what they should cover (Instagram).

  • @thefakegeorgewilson set his Dot to check his calendar and email for anything he might have missed. It then reminded him on its own: it prepared a primer for a 3 p.m. meeting and set a reminder for 1 p.m. (Threads).

  • Benjamín Cordero ran a Dot for 72 hours. It prepared a meeting brief for him without being asked, and his review also covers where the Dot fell short of its promise (YouTube, Spanish).

  • Alycia Chapman got the offer instead of the order: ten minutes after another task, her Dot asked whether she wanted research notes for tomorrow morning's meeting (Instagram).

  • Adrián Lucena set up his Dot live on camera. Through his connected Gmail it found the email with the previous day's meeting notes, including the follow-up to call Sergi about a SaaS demo (Instagram, Spanish).

  • Taha El Harti put "prepping for a meeting" and "booking time in my calendar" among 12 live business tests. The overall score was 10.5 out of 12; the video description doesn't say which job failed (YouTube).

  • KOBA (@koba_syunske) wrote on Oct 7 that the launch of Dots and Pages finally gave him a real AI secretary. His Dot keeps watching his email, calendar, Slack and Teams, so the day's meeting materials are all ready when he wakes up, and messages that arrive while he's travelling and can't touch his PC are already sorted into tasks (Threads, Japanese).

  • Marcèles AI (@marcelesai), a Dutch creator, recorded how he works with his Dot: he says what he wants to achieve, gives context and lets it prepare the work. On camera it prepares and prioritises tomorrow's agenda and drafts an email reply for him to judge. His caption's advice: start with one concrete task, and agree what your Dot may do and when you want to look first (Instagram, Dutch).

  • Gayatri Agrawal (@gayatri.tech) showed her early-access Dot on launch day: it researched the people on an upcoming panel, drafted emails and built presentations in the background, then came back with updates or approval requests (Instagram).

  • チャエン (DigiRise) ties his sales brief to the calendar, not to a fixed hour. His Dot, which he named "Codexニキ", looks for external sales meetings in Google Calendar, skips internal and cancelled ones, and sends a brief to the Dot chat about 30 minutes before each meeting. For a 16:00 meeting, the notification arrived at 15:33. The brief covers the company, the contact's recent news, the history with his own firm, the latest news and what to confirm that day, drawn from connected email, Slack, CRM and public sources, and each section ends with its source links. His prompt says to mark anything unknown instead of guessing. After pasting it, he opens Scheduled to check which trigger, timing and destination the Dot actually saved. His short video on the same setup is on the use-case page (DigiRise blog, Japanese).

  • 伊藤貴將 (いとぱん) is hosting a PixVerse seminar on Oct 16. To prepare, he had his Dot, シバット, read the introduction deck from his previous event together with this event's plan, then sort out the questions he wants to ask the creators on stage. The ask he suggests trying first is the same shape: "Read this material and sort out what I want to confirm at the next meeting" (note, Japanese).

Scheduling and calendar conflicts

  • Dan Shipper was rescheduling a flight when his Dot, Boo, warned him that the new flight time clashed with a meeting request in Slack he hadn't read yet (X post). Slack setup: Dots + Slack.

  • Katie Fifer (Technically Curious, written with Claire Morrison) had her Dot resolve two scheduling conflicts from her phone: it found them, emailed to sort them out, and updated the invites. A typical message from it reads "your call with Customer X now overlaps with your meeting with Michael. Should I email Michael to reschedule?" The same post records one miss: the Dot broke a Zoom link while updating a calendar invite (Substack).

  • Mark Nguyen (The Slide Factory) named his Dot Toby. On day one it read his connected Slack and calendar and found a Monday overlap, then another meeting conflict on Wednesday. His advice is to start with read-and-flag work before anything that sends on your behalf (review).

  • @trekedge handed all meeting scheduling to a Dot, which confirms each booking instead of leaving a hundred threads half-settled (X post).

  • つるモンCEO (@tsurumon_ceo), who runs two driving schools and a marketing-support company, turned his Dot into a scheduling secretary. In his Oct 6 reel he describes teaching it his scheduling rules: how each company's appointments are handled, travel time around in-person meetings, offering several dates, and rescheduling. Fixed chat and Facebook Messenger exchanges, and verbal agreements, now end up as calendar entries. He calls it still an experiment (Instagram, Japanese).

  • 入江慎吾 (Shingo Irie) published the setup he actually runs (note.com, Oct 6). When he asks "find my free slots", his Dot checks both his work and personal calendars and offers two options; when he answers "Friday is good", it always asks "May I reply with this date?" first. His Dot is the watcher (checks every 30 minutes on weekdays, a 4 p.m. sweep for anything missed), while the pre-meeting memos and minutes go to Claude and Notion (note, Japanese).

  • Gurmeet (Gurmeet Builds AI), a former Shopify engineer, gave a Dot the customer workflow of a painting business: quotes, owner emails, customer replies with approval, and a booking handled end to end over email and calendar, tested live in the video. He also notes that some browser-based tasks took more than two minutes (YouTube, Oct 7).

More on Katie's and Toby's first days, beyond meetings: daily ops catch-up.

Notes, follow-ups and handoffs

  • José Carlos Amorim (@josecarlosamorim.ai) reviewed a week with his Dot (Oct 6). It read the transcript of a 2-hour-20-minute class he had taught at the weekend, found a promise he had made in the middle of it, checked his calendar and email, and came to ask him for the time and link of the next class. He hadn't asked for that review (Instagram, Portuguese).

  • AI 서대표 (@AISeoceo) ran a Dot in real work for three days with only Gmail, Google Calendar, Drive and Slack connected. Before video meetings its brief includes his Slack history with the attendees. When a holiday abroad meant he couldn't make the next day's meeting, he only asked it to understand the context and pass on what the team needed: it opened a Slack thread with his teammates itself, confirmed the meeting time and the decision taken, reported back and saved it to memory. He also gave it a people-and-relationships "brain", so when a YouTube shoot appears on the calendar it checks whether the person in charge of filming needs to be there (YouTube, Korean).

  • Diana (AI Agents Library) tested her Dot, Sparky, on her own accounts on Sep 30 and Oct 1. Asked to prepare her for a real editorial planning meeting, it found the participants, background, earlier decisions and open issues, and she scored it 9 out of 10. The first answer was a wall of text, though. After one sentence, "I am a visual person", it switched to three cards with a business question under each, source links, and unresolved items marked "To confirm" instead of filled in. A visual page it had promised was still being built when she checked back. Turning a real meeting record into decisions, owners, dates and a follow-up message scored 7 out of 10, her lowest result. It invented no commitments, but the follow-up arrived as more chat text rather than a draft she could approve, so she had to ask for the draft explicitly. Once she said to send it, it sent at once (review).

Calendar changes around the meeting

  • Meetul Jain posted a screen recording: on command his Dot added a team dinner for Oct 5 at 8 p.m. IST, moved it to Oct 11, and drafted an email to the team that it left unsent (Instagram).

  • Soyoung (@dailyprompt_) tested whether spoken requests really land in the apps. Her Dot added a manuscript-delivery event to Google Calendar, sent a thank-you test email after a meeting through Gmail, and sent an iMessage from her Mac, and she checked each result in the app itself (Threads, Korean). Calls work too: see voice calls.

  • A host of neco.🐈‍⬛ 焚き火をみながらAIの話 (YouTube AI morning live, 2 Oct, Japanese) described what the host's Dot caught the day before. A meeting with the host's boss had been moved by 30 minutes, and the host hadn't noticed until the Dot sent a message saying it was letting them know just in case. Several meetings ran back to back before it, so without that message the host would have gone in with the prep undone. The Dot also noticed that a change on the host's company calendar now clashed with an entry on a side-business calendar; it said the clash was probably fine but asked for a check. After the host changed an office booking, it pointed out that the booking wasn't on the calendar and offered to add it. The co-host has asked their own Dot for a reminder the day before and on the morning of anything on the calendar that means going out (YouTube, Japanese, from 57:11).

  • Mark Graban gave his Dot, Dottie, access to his email and calendar. A luncheon he was hosting in San Antonio had moved from Friday to Thursday, 15 October, but his calendar still said Friday. On the Monday night, without being asked, Dottie compared the event information with his calendar and flagged the mismatch. He corrected the calendar, cleared a conflicting lunch and still had time to change his travel. His point: a calendar reminder would have faithfully reminded him about the wrong day (LinkedIn).

What these setups have in common

  • Lead time is set by where you read it. Two hours before every call (David Yu) leaves time to act; a primer plus a 1 p.m. reminder for a 3 p.m. meeting (@thefakegeorgewilson) splits prep from the nudge; KOBA simply finds everything ready when he wakes up.

  • Last time's record is the best input. Adrián Lucena's Dot started from the previous day's notes in Gmail, and José Carlos Amorim's found an unkept promise in a class transcript. Shingo Irie and Andrew Southworth describe the same move on the use case page.

  • Conflicts and bookings come from outside the calendar. Dan Shipper's clash sat in an unread Slack request, Mark Nguyen's surfaced from Slack plus calendar, and つるモンCEO's appointments start in Messenger chats. Connect the place where meetings get agreed, not only the calendar.

  • Teach it rules and people, not only events. Per-company rules and travel time (つるモンCEO) and a map of who does what (AI 서대표) let the Dot judge a meeting, not just list it.

  • Propose first, write second. Shingo Irie's Dot offers two slots and asks before replying; Katie's broken Zoom link is why invite edits should stay behind Ask before taking action until you trust the Dot with them.

  • Tie the brief to the event, and say what shape you want. チャエン's brief follows each external meeting instead of a fixed hour, so it lands about half an hour before the call whenever the call is. Diana got cards with "To confirm" items only after she said she wanted them. Put both in the first ask.

  • A moved meeting costs prep time, not just a slot. The neco. host's 30-minute shift mattered because of the meetings around it, and the clash sat between a work calendar and a side-business calendar. Ask the Dot to tell you as soon as a meeting moves, and to check every calendar you keep.

  • The calendar can be the wrong source. Mark Graban's email had the new date while his calendar kept the old one. Ask the Dot to compare the latest email about an event with the calendar entry.

What a useful result looks like

For a renewal call, the brief separates the customer's requested start date from the date your team actually committed to, with source links, and it doesn't send mail or edit the calendar event.

Three more copyable asks

Scheduling with your rules:

When someone asks me for a meeting by email, Slack or Messenger, check my work and personal calendars and suggest two times that follow these rules: [rules per company or client], at least [minutes] of travel time before and after in-person meetings, nothing after [time]. Show me the two options and the draft reply, and ask before you send anything or create the event. Time zone: [zone].

A promise sweep after a meeting or class:

Read the transcript or notes from [meeting or class, date]. List every promise I made to someone (what, to whom, by when) and quote the line it comes from. Check my calendar and email for whether each one is already scheduled or done. For anything still open, tell me what you need from me and draft the message for my review.

When a meeting moves, or the calendar no longer matches the mail (built from the neco. and Mark Graban cases):

Watch my [work] and [personal / side-business] calendars. When a meeting is moved or cancelled, or now overlaps something on another calendar, message me right away with the old and new times and anything I planned to prepare for it. If I book or change something by email or on a website and it isn't on my calendar yet, or an email gives a different date or time than the calendar entry, tell me and offer to fix it. Ask before you change or add any event. Time zone: [zone].

Run it once, then schedule

Paste the brief, request one full result, open every source link, and tighten the format. Then save a schedule that covers what to check, when it runs (with time zone and end date), which changes deserve a notification, and where to deliver results, and have the Dot confirm what it saved. A completed run doesn't by itself prove the brief arrived, so check the first few deliveries (Tasks and memory). If mornings are when you plan, the morning brief workflow can list the day's meetings first.

Related

Copy this task brief

Prepare a meeting brief for [event/title] at [date, time, time zone].
Use [event link], [document links] and [named email threads], plus the notes or transcript from the previous meeting if there is one.
Return a one-page brief with:
- Purpose and the decision this meeting should produce.
- Participants and their known roles from the supplied sources.
- What changed since the previous meeting.
- Three questions ordered by importance.
- A proposed 25-minute agenda.
- A follow-up table with action, owner, due date and source.
Distinguish recorded decisions from suggestions. Preserve exact dates and numbers.
Put source links next to the claims they support.
If you can't find something, say so instead of guessing.
Save to [destination] by [deadline].
After the meeting, I will provide notes; update the decision and action tables from those notes.
Download Markdown ↓

Sources & further reading