Dots coordinates meetings from a forwarded Gmail request
Eddie Soehnel reports a Dots meeting assistant that takes forwarded Gmail requests, coordinates by email and adds a Zoom bridge when needed.
Suggested prompt
Suggested prompt written by Agents In Use, not the source author. Replace bracketed inputs and review tool permissions first.
Read this scheduling request and the approved availability policy. Find suitable times, email the other participant to coordinate, and add a Zoom bridge when needed. Pause if the request involves a group or conflicting constraints.
Reach people exploring AI agents
See placements →Evidence at a glance
Sourced account- Source poster / publisher
- Eddie Soehnel (@edsoehnel)
- Original account
- Read the source ↗
- Published
- Source link checked
- Reported result
- Soehnel reports a working one-to-one scheduling assistant after several iterations. Group scheduling remained untested in his account.
- Human involvement
- The source does not say whether Soehnel approves outgoing coordination emails. The author had not tested group scheduling. The public repository is a reference toolkit with synthetic fixtures and no live account connection.
A linked account supports attribution. It does not mean we independently reproduced its result.
Report an issue with this case
Open correction emailOpens your email app with the case link included. Nothing is sent automatically.
How the agent did it
- Forward a meeting request, or write a new one, to the configured Gmail label.
- Let OpenAI Dot coordinate a time with the recipient by email.
- Add a Zoom bridge when the meeting needs one.
Eddie Soehnel says he built a working calendar-scheduling assistant over several months and iterations. The intake is a Gmail label: he forwards an incoming request there, or writes an email asking to schedule with someone. He says OpenAI Dot then takes over the coordination, emailing the other person and adding a Zoom bridge when needed. Soehnel has not tested group scheduling.
He published an open-source scheduling toolkit alongside the account. The repository’s README describes a Python reference implementation with policy evaluation, slot selection, an operation ledger and sample fixtures. It explicitly says the repository is not a hosted scheduler, has no live account connection and does not automatically authorize calendar or email changes. That public code is useful context, but it does not expose the author’s personal account configuration or independently prove the reported emails.
The source does not say whether Soehnel reviews each outgoing message before it is sent, so the handoff boundary is unclear. The practical pattern is to funnel scheduling requests into a dedicated mailbox label and have an assistant handle coordination and meeting logistics. It is not evidence that group scheduling, every time-zone edge case or a public reference toolkit is ready for unattended production use.
Prompt
Suggested prompt (written by Agents In Use, not the author's)
Source: X · Eddie Soehnel (@edsoehnel)
Frequently asked questions
How does a scheduling request reach the assistant?
Soehnel says he forwards an incoming email, or writes a scheduling request, into a Gmail-labeled inbox.
What does Dot do after receiving a request?
The author reports that it emails the invitee to coordinate and can add a Zoom bridge when needed.
Was group scheduling tested?
No. Soehnel explicitly says he had not tested group scheduling when he posted.
More details
Remaining steps
- Treat group scheduling as unsupported in this account; the author had not tested it.
About this account
The author says Dot takes a labeled request, emails the recipient to coordinate and adds a Zoom bridge when needed.
Firsthand X post captured directly with author and 2026-10-06 publication metadata; reopened on 2026-10-18 but X returned HTTP 403. Followed the post’s project link and read the current public repository README, which describes reference code with synthetic fixtures, no live account connection and no automatic external authorization. The reported personal deployment is not independently reproduced; outgoing-message approval is unspecified. Suggested prompt written by Agents In Use.
Credit: Eddie Soehnel (@edsoehnel)
Source published
Added to Agents In Use
Source checked
Tools and topics
OpenAI Dot · Gmail · Zoom · AI Calendar Scheduling Toolkit
Meeting scheduling · Gmail · Zoom
Editorial completeness: 100/100. Measures documented fields, not agent performance or verified outcomes.