ChatGPT Now Has Always-On Agents Called ‘Dots’ β€” 10 Jobs to Hand Them Today

By the end of this list you will have ten bounded jobs ready to hand to ChatGPT's new always-on agents, called Dots, with the exact handoff line and best connector for each one.

A dot runs on its own cloud computer and browser, separate from yours unless you connect it. It reaches over 4,000 apps through OpenAI's plugin ecosystem, including Slack, Microsoft Teams, Google Drive and iMessage.

Dots ship with ChatGPT Pro, Business Premium and Enterprise. The first dot is included at no extra cost on Pro and Business Premium.

Enterprise users get it when a workspace admin enables it. It is not available in the EEA, Switzerland or the UK at launch.

Every job below follows one test: what the dot reads, groups and drafts alone versus what waits for your click. The review minutes are the slow part, so each entry gives three times separately.

JobBy hand (min)Dot's own timeReview and edit (min)Best tool
Overnight Slack triage2590 sec7Dot + Slack connector
Monday standup notes3070 sec5Dot + Teams + Jira
Weekly competitor brief9012 min15Dot in agent mode
Pricing-page change watch202 min2Dot + proactive research
60-page PDF decision memo1202 min10Dot + PDF upload
Figma to prototype24020 min30Dot + Codex
Drive cleanup453 min8Dot + Google Drive
Kickoff brief from Drive5090 sec10Dot + Google Drive
Unsent invoice check1545 sec3Dot + accounting + Drive
Duplicate bug clustering402 min6Dot + issue tracker + Slack
The ten jobs, timed: by hand vs. the dot's own run vs. the reader's review.

1. Overnight Slack triage into one bug ticket

Overnight Slack triage into one bug ticket

The worst part of 6 a.m. is not the messages. It is holding four versions of the same outage in your head while you scroll for the one that names the customer. A dot can read that channel for you and stop short of posting.

Before you set it up: Dots come with ChatGPT Pro, Business Premium and Enterprise. Pro and Business Premium include the first dot in the plan price, Enterprise users wait for an admin to switch it on, and one dot is all anyone gets at first.

The EEA, Switzerland and the UK are excluded at launch, and the first dot has to be created on the desktop app or a desktop browser, then reached from web, mobile, Slack or Teams.

The rule that decides everything: an idle dot reads with read-only access, so it cannot post to #eng-alerts or open the Jira ticket itself.

Custom Rules set that write to allow, to wait for your approval, or to block. Auto-review handles anything touching accounts or sharing data, and password changes stay with you.

Prompt to copy

Read #eng-alerts since 6 p.m. yesterday, group messages by incident, pick the one with the most customer reports, and draft a Jira bug with title, steps to reproduce, affected customers and links to the Slack threads. Do not post or create it; return the draft.

A dot with the Slack connector reads the thread and drafts in 90 seconds. By hand the same scroll takes 25 minutes before the standup even starts.

You spend 7 minutes checking the incident, the affected customers and the links, and chats with the dot skip your usage limits entirely. The draft, thread links attached, is waiting in ChatGPT or Slack for one click.

πŸ’‘ Tip: Conversations with a dot do not count against ChatGPT usage limits, but tasks it runs through Codex or ChatGPT Work do. Keep the Slack job on the dot itself.

🌱 GROWING TIP

Create once, reach it everywhere

The first dot must be created in the ChatGPT desktop app or a desktop browser, but after that you reach it through ChatGPT on desktop, web and mobile, or through Slack and Microsoft Teams. Create it on your laptop, then approve its drafts from your phone.

2. Monday standup notes from Teams and Jira

Monday standup notes from Teams and Jira

Prompt to copy

From Teams #team-updates and the Jira board for Project Atlas, pull every update since Friday 5 p.m. Return five standup bullets: shipped, slipped, blocked, needs decision, and who owns the next step. Link each bullet to its source.

That wording is the whole standup in five lines. Read one busy channel and stop at a draft, then repeat it across two sources on a schedule, and you have a note you can read aloud.

Use a dot with the Microsoft Teams and Jira connectors wired in.

The dot returns the five bullets in 70 seconds, with a ticket or message behind each claim. Assembling the same note by hand eats 30 minutes of your Monday morning.

You still spend 5 minutes checking owners and anything marked needs decision. Expect a blank row for any channel it cannot see: private Teams channels and restricted Jira projects stay invisible until you grant access.

πŸ’‘ Tip: Run it once manually before scheduling. If the dot returns empty bullets for blocked, check the connector permissions first.

Dot terms in plain English

πŸ€– TERM Dot An always-on agent inside ChatGPT that runs on its own cloud computer and browser.
πŸ“œ TERM Custom Rules Per-action settings that allow, require approval for, or block what the dot can do.
πŸ‘€ TERM Auto-review The check that covers actions which could affect accounts or share information.

3. Weekly competitor brief from ten sites

Weekly competitor brief from ten sites

A dot can invent a quote or a link, so open every source in a competitor brief and check any price against the page itself.

Done safely, a dot in agent mode visits the ten sites you name and returns a one-page brief with a source link and a direct quote for each claim.

Prompt to copy

Visit these ten competitor sites: [list]. For each, note any change since last Monday in pricing, headline, new feature, or hiring. Return a one-page brief with a source link and a direct quote for every claim. Mark anything you could not verify as UNVERIFIED.

Internal sources fix your inside view; the drafting then turns outward, where the dot has to visit the pages. By hand the scan runs 90 minutes.

The dot spends about 12 minutes in agent mode, and your review takes 15, the largest review bill among the read-and-draft jobs.

The two times: 90 minutes by hand against 12 minutes running and 15 minutes checking. You get a one-page brief to trim and send, with the unverified items already flagged rather than mixed in.

Dot setup at a glance

πŸ’» Create on

ChatGPT desktop app or browser

πŸ“± Reach it via

ChatGPT web, mobile, Slack, Teams

πŸ”Œ App reach

4,000+ through plugins

πŸ’΅ Included on

Pro and Business Premium

🌍 Not available

EEA, Switzerland, UK at launch

First dot

You initially get one dot, included at no extra cost on Pro and Business Premium.

4. Pricing-page change watch

Pricing-page change watch

A dot can watch one named pricing page every weekday and report only what moved. Proactive research is read-only: no logging in, no buying, no editing the page.

The catch is that a change behind a cookie banner or an A/B test can stay invisible, so the reader confirms each diff on the live page.

Setup takes one sitting.

The prompt, pasted into ChatGPT on desktop after connecting your browser: "Every weekday at 7 a.m., open [pricing page URL], capture the plan names, monthly prices and included limits, and compare them with yesterday's snapshot. If anything changed, return a diff with the old and new text and the time you checked. Do not log in or buy anything."

The times: 20 minutes a week by hand, 2 minutes per dot run, 2 minutes to review and edit.

A short diff waits in ChatGPT or Slack before the standup, with yesterday's snapshot as the comparison, so the reader only reads on days something actually changed.

5. 60-page PDF into a decision memo

60-page PDF into a decision memo

Yes, and it does it in about two minutes of dot time. A two-minute check works on a page you can see; a 60-page PDF needs the same discipline at a larger scale, because the page number is the thing being checked.

Attach the file to a dot in ChatGPT on desktop and hand it the job. Two hours of reading shrinks to two minutes of summarization and 10 minutes of checking.

Prompt to copy

Read the attached 60-page PDF. Return a one-page decision memo: the recommendation, three numbers that support it, two risks, and the page number for each number and risk. Quote the exact sentence for each citation. If a number is not stated, say NOT IN REPORT.

The catch: a dot can read across merged table cells and carry the wrong number forward, and page citations drift in a scanned file.

Every figure and page number gets opened against the PDF, so the 10 review minutes are spot-checks, not a glance. When the quote lines up, the number is safe to use.

What lands is one page: the recommendation, the supporting figures, the risks, and a quote beside each citation. The reader stops reading 60 pages and starts checking 10 minutes of receipts, which is a shorter and more honest path to a confident decision.

πŸ’‘ Tip: Ask the dot to quote the exact sentence, not just the page number. A quote is faster to verify than a paragraph.

6. Figma design into a working prototype

Figma design into a working prototype

Four hours by hand, 20 minutes for the dot in Codex, 30 minutes to review: a finished Figma design becomes a clickable prototype in one sitting.

That is a summary turned into work that runs, and it spends Codex usage rather than counting against chat limits.

The catch: generated code still needs a review for security, accessibility and broken states before anyone outside sees it.

The handoff line puts it in a new branch and leaves deployment off, then asks for the three riskiest parts by name.

Opening that branch and clicking every screen is the 30-minute review.

Prompt to copy

Use this Figma export and build a responsive React prototype with the three screens shown. Match spacing and type, add hover and empty states, and put the code in a new branch. Do not deploy. Return the branch name, a file list, and the three riskiest parts for me to review.

7. Shared drive cleanup into a naming scheme

Shared drive cleanup into a naming scheme

A tidy folder and a naming rule you can reuse, with every shared link still working. That is the trade this job offers, and it comes with one condition: nothing moves until a person has seen the list and ticked it off.

The danger is not a wrong label on a file – it is a link someone bookmarked in 2023 that now points at nothing.

So the dot inventories first, proposes names built from client, date and document type, and returns a table of current name, proposed name and duplicate flag. Bulk renaming waits for a per-file approval, or runs on a copy.

Check the first ten yourself before you let it continue.

By hand the folder takes about 45 minutes. The office reads it in 3 minutes to build the list.

The review and edits are 8 minutes, mostly on the duplicate flags. That ratio is the whole argument: the dot does the sorting, you do the deciding.

Prompt to copy

Inventory the folder [path]. Propose a naming scheme of client-date-document type. Return a table of current name, proposed name, and duplicate flag. Do not move or rename anything yet. After I approve the table, move only the files I mark approved.

Best tool is a dot with the Google Drive connector, and the review minutes buy back roughly five times the sorting.

8. Project kickoff brief from a Drive folder

Project kickoff brief from a Drive folder

A pasted client file is a copy handed to the model – it lives in the chat. A dot pointed at a folder reads it where it sits, through the Google Drive connector, and only the files you name.

The catch is version drift. The dot may grab an outdated draft, or read a slide as a final decision.

Name the exact three files, then check every date and owner against them. Because it cannot call you to ask, anything unclear must land in the brief as a question, not a guess.

By hand a kickoff brief runs about 50 minutes. The dot reads and drafts in 90 seconds. The 10-minute review is where you fix the drift – checking names, deadlines and what the files do not actually say.

Prompt to copy

Read only these three files: [file 1], [file 2], [file 3]. Draft a one-page kickoff brief with goal, scope, out of scope, owners, milestones, and open questions. Put every fact under a source heading with the file name. Put anything not stated in the files under OPEN QUESTIONS. Do not invite anyone or create calendar events.

The bill: Pro at $500 a month includes the first dot, and this job adds no extra app cost. The 10 review minutes buy back 50. You leave with a one-page brief and its open questions already separated.

πŸ’‘ Tip: Name the exact three files in the handoff line. If you say the folder, the dot may read forty files you did not mean to share.

What the dot does alone vs. what waits for you

πŸ€–

Dot alone

  • Reads Slack threads and Teams channels
  • Groups messages by incident
  • Drafts a ticket or brief with links
  • Inventories files and proposes names
  • Runs read-only pricing checks
πŸ‘†

Waits for your click

  • Posting to #eng-alerts
  • Creating or closing a Jira ticket
  • Sending an invoice email
  • Moving or renaming files
  • Any password change

9. Unsent invoice into an approval-ready draft

Unsent invoice into an approval-ready draft

It finds the forgotten invoice in 45 seconds instead of the 15 minutes it takes to scroll the billing screen and cross-check contracts by hand.

Best tool is a dot with the accounting app connector plus Google Drive. It compares draft and unsent invoices against signed contracts, lists the late ones with the missing field, and drafts the email.

It cannot send – no standalone address – and money or account changes need your approval or are blocked. Check the amount, client and tax line.

Prompt to copy

Check the invoices in [accounting app] against the signed contracts in [Drive folder]. Find any invoice marked draft or unsent for more than 14 days. Return a table: client, amount, days late, contract link, and the missing field. Prepare the email draft but do not send it.

Three minutes of review leaves an approval-ready invoice with one human click to go.

10. Duplicate bug reports clustered for triage

Duplicate bug reports clustered for triage

Forty open bugs become six clusters with a lead ticket and its duplicates attached, ready to approve in the meeting.

The dot reads the queue, groups by symptom rather than title, and writes nothing. A wrong merge hides a real bug, so the reader keeps every close and merge click.

The job splits the same way a payment does: the dot does the reading and the comparing, the reader keeps the write. Custom Rules hold every ticket action to approval, and the dot closes, merges or comments on nothing until the reader says so.

Prompt to copy

Read all open bugs in the [project] queue from the last 30 days. Group them by symptom, not by title. Return clusters with a lead ticket, duplicate ticket IDs, the shared reproduction steps, and any cluster where the reports disagree. Do not close, merge or comment on any ticket.

Paste that into the dot set up with the issue-tracker connector and Slack. It returns in about 2 minutes what takes 40 by hand; checking the clusters where reports disagree, and the shared steps on each, takes 6 minutes.

A wrong merge is caught in review, not after release.

Quick check: 40 minutes by hand, 2 minutes for the dot, 6 minutes to review – the merge list waits for triage, and every disagreement stays visible instead of smoothed over.

πŸ’‘ Tip: Ask for clusters by symptom, not by title. Two bug titles can differ while describing the same crash.

Four checks before you trust a dot
πŸ”
Auto-review is not optionalActions that could affect accounts or share information go through Auto-review. Leave it on for any job that touches a shared drive or a ticket.
πŸ—‘οΈ
Memories go with the dotIts memories can only be deleted by deleting the dot, so decide what it reads before it reads it.
πŸ“ž
It cannot call youAs of launch, a dot cannot start calls or send from its own email address. Anything urgent still needs a human check.
⚠️
It still makes mistakesOpenAI warns that Dots can still make mistakes, so always review consequential work before it leaves your screen.

Frequently Asked Questions

Do I need to code to use a dot?

No. You create it in the ChatGPT desktop app, connect the apps you want it to see, and paste a plain-English handoff line. Only the Figma and Codex job involves code, and you review that branch before anyone else opens it.

How much does a dot cost?

The first dot is included at no extra cost on ChatGPT Pro and Business Premium. Enterprise users get it when a workspace admin enables it. OpenAI's Pro 500 plan costs US$500 a month as of November 2026 and carries the highest included usage allowance.

Can the dot send messages or post to Slack on its own?

Only if you allow it. While idle it has read-only tool access, so it cannot post or change app content. Custom Rules set each write to allow, require approval or block, and Auto-review covers actions that could affect accounts.

What about my company's private files?

Point the connector at the named folder instead of pasting files into a chat. Name the exact files in the handoff line, and never paste passwords, client files, or medical or financial records into a chatbot. On free and personal plans, chats may be used to improve the company's models unless you switch that off.

Is a dot available where I live?

Dots are not available in the European Economic Area, Switzerland or the UK at launch. Elsewhere, you need a Pro, Business Premium or Enterprise plan, and the first dot must be created in the desktop app or a desktop browser.

Start with the job that gives back the most minutes

The biggest gap between by-hand minutes and review minutes is the overnight Slack triage, followed by the weekly competitor brief. Both hand you a draft you can approve in under 15 minutes.

Set Custom Rules to require approval for anything that sends, posts or moves money before you add a second job. Then add the pricing-page watch, which runs in 2 minutes and asks for 2 minutes back.

One dot, tested on one job, reviewed honestly, beats ten jobs you never checked. Add the rest only as the approvals hold.

Leave a Comment