ChatGPT Work Tutorial
6 Role-Based Workflows, Prompt Templates & Automation Recipes (2026)

ChatGPT Work pays off when it removes a workflow you already resent doing manually — not when you read another launch recap. If you know what Work is but wonder what to do with it Monday morning, this guide gives you copy-paste prompts for sales, marketing, finance, operations, product, and engineering; Plan Mode checklists; Scheduled Tasks recipes; and usage optimization tactics. For the July 9 launch timeline, feature overview, and Claude Cowork comparison, see our ChatGPT Work launch and Codex merge guide.

01 Three Principles Before You Copy a Prompt

OpenAI's onboarding advice is direct: start with a task you already know well — month-end variance analysis, a campaign brief, or sales meeting prep. Before pasting any template below, internalize three rules that separate productive Work sessions from wasted quota.

• Describe outcomes, not steps: Work mode plans its own path. Say "Build a weekly pipeline PPT from @Salesforce deals in the last 30 days, flagging at-risk opportunities" — not "Open Salesforce, export, then…"
• Connect tools first: Plugins are Work's data layer. Authorize Gmail, Slack, and Drive before starting; pin sources with @AppName.
• Plan Mode is your brake: For high-stakes deliverables — external emails, financial reports, client documents — review and approve every step before execution begins.

The universal 5-step workflow

Every role follows the same loop:

1. Connect plugins
2. Write goal and output format
3. Review Plan Mode
4. Steer mid-flight if output drifts
5. Accept deliverable and iterate

Work Mode prompt formula

[Role] + [Data sources @plugins] + [Task] + [Output format] + [Constraints] + [Acceptance criteria]

Example skeleton:
You are [role]. Pull [data type] from @Salesforce and @Gmail for [time range].
Complete [action]. Output as [Google Docs / Excel / PPT / Sites].
Constraints: [do not modify source data / two decimal places / no external email].
On completion: [Slack notify me / save to folder].

Plan Mode review checklist

• Are data sources correct — right account, right month?
• Any high-risk actions: send external email, delete, overwrite files?
• Does output match your team's template?
• Can any steps be removed to save usage?
• Do you need a human approval checkpoint?

02 Pain Points: Why Teams Stall After Launch

Most teams install ChatGPT Work, run one demo task, then revert to manual workflows. The friction is predictable:

• Wrong mode selection: Using Work for quick Q&A burns quota; using Chat for multi-app deliverables leaves you doing the last mile manually.
• Unconnected plugins: Work cannot pull CRM, email, or file data until the plugin directory is authorized — yet many prompts assume integrations already exist.
• Step-by-step prompting: Micromanaging execution steps defeats Work's planner and inflates token consumption.
• Skipped Plan Mode on high-stakes tasks: Financial reports and client deliverables sent without review create rework and compliance risk.
• Premature automation: Scheduling tasks before validating output quality leads to silent failures and surprise usage bills.
• Desktop vs web mismatch: Local file workflows fail on web; background Scheduled Tasks fail when a laptop sleeps.

The fastest path to ROI is not more launch coverage. Pick one task you know intimately, run it three times, tune the prompt, then automate it.

03 Mode and Environment Decision Matrix

The unified ChatGPT desktop app ships three modes. Picking the wrong one wastes usage and time.

Environment choice matters as much as mode choice:

04 Six Role-Based Workflows with Prompt Templates

Templates below draw on OpenAI's official cases, early tester feedback (Zapier, Nvidia, Virgin Atlantic), and the Workspace Agent Cookbook. Replace @plugin names with your actual stack.

Sales

Scenario A — Daily meeting briefs (scheduled). Pain point: reps spend 1–2 hours daily assembling customer background, recent news, and meeting agendas. Work scans tomorrow's calendar, pulls CRM notes, searches news, and archives briefs.

Create a scheduled task running every weekday at 4pm:

1. Check tomorrow's customer meetings in @Google Calendar (exclude internal-only)
2. For each customer meeting:
   - Pull 30-day account notes and interaction history from @SharePoint / @Salesforce
   - Search 30-day public news and executive updates for that company
   - Write a 2-3 sentence background summary for each external attendee
3. Generate a 2-3 page brief per meeting, save as @Google Drive documents
4. Email me a summary via @Gmail with links to each brief

Output format: email subject "Tomorrow's Customer Meeting Briefs — [date]",
body as a table (Customer | Meeting time | Key topics | Brief link)

OpenAI internal reference: sales teams converted a Discovery conversation into a customized PoC proposal within 24 hours — a process that traditionally took weeks.

Scenario B — Live account command center (Sites + daily refresh). Pain point: account data scattered across CRM, email, and Slack. Work builds an interactive Sites dashboard with daily auto-refresh.

From all opportunities, contacts, and recent activity for [Account Name] in @Salesforce:

1. Build an interactive account command center (Sites) with:
   - Pipeline overview (stage, amount, expected close date)
   - Key signals from the last 7 days (email, meetings, support tickets)
   - Prioritized recommended next actions
2. Schedule daily refresh at 8am on weekdays
3. Slack me on major changes via @Slack DM

Constraints: do not auto-send any external email; amounts must match CRM source data.

Scenario C — Lead review and pipeline repair (Zapier-style workflow). Pain point: thousands of monthly leads with invisible follow-up gaps.

Analyze @Salesforce leads from the last 30 days, cross-referenced with @Gmail outreach.

Find:
1. Leads with no follow-up for 48+ hours (grouped by source)
2. Broken handoff points (where response rate drops sharply)
3. Estimated pipeline loss amount

Output:
- Excel detail table (Lead ID | Source | Last follow-up | Gap type | Recommended action)
- 1-page executive summary PPT highlighting seven-figure opportunity risk
- A repeatable weekly review workflow suitable for Scheduled Tasks

Marketing

Scenario A — Research to Brief to multi-market assets (end-to-end). Pain point: research, brief, and regional assets are usually split across people, losing context at every handoff.

Using uploaded research / @Google Drive materials:

Phase 1 — Brief:
- Extract target audience, core pain points, competitive positioning
- Output Campaign Brief (Google Docs) with messaging pillars and channel recommendations

Phase 2 — Assets:
- Based on the Brief, generate: 1 acquisition email, 3 LinkedIn posts, 1 landing page outline
- Save to @Google Drive "Campaign / [product name]" folder

Phase 3 — Regional adaptation:
- Adapt core assets for US, EU, and APAC (language, cultural references, compliance wording)
- Flag sensitive phrases requiring human review in each version

Pause after each phase for my approval before continuing.

Scenario B — Slack / Teams to meeting agenda sync (weekly scheduled).

Set a scheduled task running every Monday at 7am:

1. Summarize important discussions from the last 7 days in @Slack #product-launch
   and @Microsoft Teams "Go-to-Market" channel
2. Extract: decisions made, open questions, blockers needing alignment
3. Update the "Weekly Agenda" document in @Google Drive (preserve version history)
4. Post a summary of 5 bullets or fewer to @Slack #leadership

Constraints: cite only public discussions; do not leak messages marked confidential.

Finance

Scenario A — Month-end variance analysis (OpenAI-validated use case). Pain point: month-end close and forecast adjustments consume days of manual data hunting and spreadsheet work.

Complete [Month] budget variance analysis:

1. Pull actuals from @Google Drive "Finance / Actuals" and forecast from "Finance / Forecast"
2. Build a reconciliation workbook in @Google Sheets:
   - Summarize actual vs forecast variance by department
   - Flag line items with variance >5% or >$50K
   - Preserve all original formulas; do not overwrite source files
3. Draft narrative explanations (Google Docs) by Revenue / COGS / OpEx
4. Build a 5-8 slide management deck with charts matching the attached template style
5. List 3 judgment calls requiring human sign-off

Constraints: do not modify source data; cite source cell for every number.

OpenAI internal result: month-end close and forecast workflows compressed from days to hours.

Scenario B — Invoice vs payment register reconciliation.

You are an accounts payable specialist. Compare:
- Payment register: [@Google Drive link]
- Invoice list: [@Google Drive link]

Flag the following anomalies (return as a table):
| Issue type | Vendor | Invoice # | Amount | Recommended action |
- Amount difference >2%
- Missing tax ID
- Duplicate invoice number
- Vendor name mismatch

Do not initiate payments; output review table for human verification only.

Operations

Scenario A — Daily dashboard morning briefing (scheduled).

Every weekday at 6:30am:

1. Visit [internal dashboard URL / @SharePoint report page]
2. Compare to yesterday's snapshot; extract significant changes (>10% swings or new red indicators)
3. Generate a 1-page morning brief (Google Docs):
   - Today's TOP 3 items to watch
   - Metric change table
   - Recommended follow-up owners
4. Email [email protected] via @Gmail

If the dashboard is unreachable, stop and notify me in Plan Mode — do not fabricate data.

Scenario B — Customer feedback clustering to product priorities.

Monitor 14-day feedback from:
- @Slack #customer-feedback
- @Gmail label "NPS-Detractor"
- @Google Drive "Support Tickets Export"

1. Cluster feedback into 5-8 themes with representative quotes
2. Rank by frequency x impact x implementation effort
3. Output a prioritized product review doc (Notion / Google Docs format)
4. Schedule weekly Friday refresh for this document

Constraints: anonymize all customer references; no customer names in output.

Product

Scenario A — Launch readiness review (Jira + GTM cross-check, Nvidia-style). Pain point: launch requires checking engineering progress, marketing plans, and support docs — manual and error-prone.

Launch readiness review for [Product / Feature name]:

1. From @Jira: pull Epic / Story completion status and open blockers
2. From @Google Drive "GTM Plans": check milestone status for this launch
3. From @Slack #product-launch: extract unresolved discussions from the last 7 days
4. Output a Launch Readiness report (Google Docs):
   - Readiness score (Red / Yellow / Green)
   - Blocker list (Owner | Due date | Risk level)
   - Recommended Go / No-Go judgment with rationale

Do not auto-update Jira status; flag high-risk items for human decision.

Engineering — Work + Codex in the Same App

Engineering workflows split cleanly: Codex handles code; Work handles cross-team documents. Both modes live in the same desktop app — no tool switching required.

Scenario A — PR review to release notes to team announcement.

In Codex mode:
1. Review PR #123 in [repo/name], focusing on [security / performance / test coverage]
2. Leave line-by-line review comments in the PR sidebar
3. If approved, draft release notes

Switch to Work mode:
4. Format release notes for @Confluence
5. Draft @Slack #engineering announcement (do not auto-send)

Scenario B — Multi-repo weekly engineering summary.

In Codex mode, across [frontend-repo] and [backend-repo]:
1. Summarize this week's merged PRs and open P0/P1 issues
2. Generate engineering weekly report in Markdown

Switch to Work mode:
3. Convert to Google Docs and insert burndown chart from @Jira
4. Schedule automatic generation every Friday at 5pm

05 Scheduled Tasks, Usage Optimization & Pitfalls

Scheduled Tasks recipe library

OpenAI recommends four high-frequency automation patterns. Adapt triggers and outputs to your stack.

Scheduled Task prompt pattern

Set Scheduled Task:
- Frequency: [daily / every Monday / 1st of month / when @Slack keyword appears]
- Time: [timezone + specific time]
- Action: [workflow description]
- Notification: [Slack channel / email / none]
- Human approval: [which steps require my approval first]

Safety checklist before going unattended

• Minimal plugin scope — connect only necessary tools
• No auto-external-send unless explicitly intended
• Output archive path set to avoid accidental overwrites
• Enterprise: agent network policy confirmed with admin
• Run 2–3 manual single executions before scheduling

Usage optimization: do more for less

ChatGPT Work shares a metered usage pool with Codex. The same workflow can cost 5x more depending on design.

Seven cost-saving tactics:

1. Draft in Chat first, then hand a tight brief to Work
2. Trim Plan Mode steps, especially duplicate data pulls
3. Reuse template documents in Scheduled Tasks for cache discounts
4. Request concise outputs — table plus 3 bullets beats a narrative report
5. Split large projects into phases to avoid expensive re-runs
6. Free users: test small desktop tasks before scaling automation
7. Enterprise: set workspace, group, and individual limits in Admin Console

Pre-launch usage test

1. Pick a real task you know the human time cost of (e.g., variance table, usually 2 hours manual)
2. Run once in Work with Plan Mode; note step count
3. Check consumption against your plan's included usage
4. Extrapolate daily / weekly / monthly cost
5. Optimize per tactics above and re-run to compare

Common pitfalls and troubleshooting

06 30-Day Roadmap, Key Stats & Setup Steps

30-day onboarding roadmap

Seven setup steps to run your first workflow

1. Install the desktop app: Download from chatgpt.com/download. Existing Codex users update in place — projects migrate automatically.
2. Confirm three modes visible: Top navigation should show Chat, Work, and Codex. Free users get all three on desktop.
3. Switch to Work mode: Click Work in the top bar to enter the agent interface.
4. Authorize plugins: In the Plugins Directory, connect Gmail, Slack, Google Drive, and your daily tools.
5. Pick one familiar task: Start with a workflow you can verify — variance analysis, campaign brief, or meeting prep.
6. Review Plan Mode before execution: Confirm data sources, output format, and no high-risk actions.
7. Iterate, then automate: Run manually 2–3 times, tune the prompt, then convert to a Scheduled Task.

Citeable technical facts

• Plugin ecosystem: ChatGPT Work launches with 1,400+ integrations across collaboration, storage, CRM, development, and creative tools.
• Codex user base: OpenAI reports roughly 5 million weekly Codex users, with over 1 million using it for non-coding work — validating cross-role Work adoption.
• Billing model: Work and Codex share a usage-metered pool with no separate monthly fee; output tokens cost roughly 6x input tokens, and cached reads cost about 1/10 of fresh input.
• Validated internal ROI: OpenAI's finance team compressed month-end close from days to hours; sales teams cut PoC proposal turnaround from weeks to 24 hours.

Primary reference sources; verify against official pages after release:

OpenAI Blog — ChatGPT for your most ambitious work

OpenAI Cookbook — Sales Meeting Prep Agent

ChatGPT Learn Changelog

SiliconANGLE — ChatGPT Work launch coverage

07 FAQ

Q: Which workflow should I try first?
A: The task you know best and can verify — month-end variance, campaign brief, or sales meeting prep. OpenAI recommends tasks where you can quickly judge output quality.

Q: How long should my prompt be?
A: 150–400 words focusing on data sources, output format, and constraints. Do not micromanage steps — that is Work mode's job.

Q: Do Scheduled Tasks run when my laptop is off?
A: Desktop tasks need the device online and logged in. For true background automation, use web Workspace Agents on Plus or higher plans.

Q: Work mode vs Workspace Agent?
A: Work is personal agent mode inside ChatGPT. Workspace Agents are team-built, admin-governed automations in Business and Enterprise with Admin Console controls.

Q: Can I use generated slides or reports externally as-is?
A: Treat them as 80% drafts. Always human-review numbers, names, and external statements.

Q: What can free users run from this guide?
A: Desktop Work with usage limits. Start with lightweight tasks like invoice reconciliation before scheduling long-running automation.

Last updated: July 11, 2026 | Features and rollout schedule subject to OpenAI official announcements.

ChatGPT Work removes repetitive cross-app labor — but Scheduled Tasks and Computer Use need a machine that stays awake. A sleeping laptop kills desktop automation; shared cloud desktops contend for resources; VM hypervisor overhead slows long-running agent throughput. Teams running Codex multi-repo projects or desktop Work automation at scale need dedicated Apple Silicon with native macOS toolchains. For production environments requiring zero hypervisor overhead, stable iOS CI/CD, and 7x24 AI Agent automation, ZUKCLOUD bare-metal Mac mini cloud nodes are typically the better choice: dedicated physical hardware, no virtualization tax, flexible day/week/month ordering. See our ChatGPT Work launch guide for the full feature context and Cowork comparison, and our Mac Mini M4 rent vs buy analysis for cost numbers.