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

If you are a sales rep, marketer, finance analyst, ops lead, product manager, or engineer who already knows ChatGPT Work launched on July 9, 2026, the real question is what to do with it on Monday morning. This guide answers that with three usage principles, mode-selection tables, a five-step workflow, copy-paste prompts for six roles, Scheduled Tasks recipes, usage optimization tactics, a 30-day onboarding plan, and six FAQ answers — not another launch recap. For the feature overview and Claude Cowork comparison, read the companion post: ChatGPT Work Launched: Codex Merges Into ChatGPT Desktop App. Node tiers are on the NOVAKVM pricing page.

[ SECTION_01 ] // PRINCIPLES Before you copy a prompt: three principles and mode selection

ChatGPT Work is not regular Chat with extra buttons. It plans multi-step paths, pulls live data from connected apps, and ships finished files. Three habits separate productive users from quota burners:

Pick the right mode. The unified ChatGPT desktop app ships Chat, Work, and Codex. Using the wrong mode wastes quota:

Desktop vs web: Where you run Work changes what is possible.

• Wrong mode waste: Running a quick brainstorm in Work burns metered quota that Chat handles for free.
• Unconnected plugins: Work without authorized Gmail, Slack, or Drive produces hallucinated context instead of live data.
• Skipped Plan Mode: High-stakes deliverables sent without review risk wrong recipients, overwritten files, or bad numbers.
• Desktop sleep risk: Scheduled Tasks on a sleeping laptop simply do not fire — a common first-week frustration.

[ SECTION_02 ] // FRAMEWORK Universal five-step workflow, prompt formula, and Plan Mode checklist

Every role follows the same skeleton. Run your first task this way before scaling to automation:

1. Connect plugins: Authorize the apps your task needs in the Plugins Directory.
2. Write goal and output format: State the deliverable, not the manual steps.
3. Review Plan Mode: Edit steps, remove redundant pulls, add approval gates.
4. Steer mid-flight: Pause and correct if context drifts during execution.
5. Accept deliverable and iterate: Save what worked; refine the prompt for the next run.

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].
When done: [Slack notify me / save to specified folder].

Plan Mode review checklist — confirm before clicking execute:

• 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 mid-run?

OpenAI's own onboarding advice: start with a task you already know well — month-end variance, a campaign brief, or sales meeting prep — because you can verify quality immediately.

[ SECTION_03 ] // ROLES Six role-based workflows with copy-paste prompt templates

Templates below draw from OpenAI case studies, early tester feedback (Zapier, Nvidia, Virgin Atlantic), and the Workspace Agent Cookbook. Swap @plugin names to match your stack.

Sales — Scenario A: daily meeting briefs (scheduled)

Pain point: Reps spend 1–2 hours daily assembling client background, recent news, and meeting agendas. Work fix: scan calendar, pull CRM notes, search news, generate and archive 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 activity 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 (Client | Meeting time | Key topics | Brief link)

OpenAI internal reference: a sales team turned one Discovery call into a customized PoC proposal within 24 hours — a process that traditionally took weeks.

Sales — Scenario B: live account command center (Sites + daily refresh)

Pain point: Account intel scattered across CRM, email, and Slack. Work fix: build a Codex Sites dashboard with daily auto-refresh.

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

1. Create 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 next actions
2. Set a Scheduled Task: auto-update every weekday at 8am
3. Slack me on major changes via @Slack DM

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

Sales — Scenario C: lead review and pipeline repair (Zapier-style)

Pain point: Thousands of monthly leads with invisible follow-up gaps. Work fix: cross-reference CRM, email, and other touchpoints; output an executive dashboard.

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. Handoff breakpoints (where response rate drops sharply)
3. Estimated pipeline loss amount

Output:
- Excel detail table (Lead ID | Source | Last follow-up | Breakpoint type | Recommended action)
- 1-page executive PPT highlighting seven-figure potential losses
- A repeatable weekly review workflow for Scheduled Task use

Marketing — Scenario A: research to brief to multi-market assets

Pain point: Research, brief, and regional assets handled by different people with lost context. Work fix: one instruction spans the full pipeline.

I uploaded the following research materials: [attachment / @Google Drive link]

Complete an end-to-end marketing workflow:

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

Phase 2 — Asset generation:
- From the Brief: 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.

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

Set a scheduled task every Monday at 7am:

1. Summarize the last 7 days from @Slack #product-launch and @Microsoft Teams "Go-to-Market"
2. Extract: decisions made, open questions, blockers needing alignment
3. Update the "Weekly Agenda" doc 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)

Pain point: Month-end close and forecast adjustments take days of manual data hunting. Work fix: locate source data, populate Sheets, reconcile, build management slides. OpenAI internal result: close cycles compressed from days to hours.

Complete [Month] budget variance analysis:

1. Pull actuals and forecast tables from @Google Drive "Finance / Actuals" and "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 finance sign-off

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

Finance — Scenario B: invoice vs payment register reconciliation

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

Flag anomalies (return as 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 automatically:

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):
   - TOP 3 items needing attention today
   - Metric change table
   - Recommended follow-up owners
4. Email ops-leads@company.com via @Gmail

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

Operations — Scenario B: customer feedback clustering to product priorities

Monitor new customer feedback from the last 14 days:
- @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 product review backlog (Notion or Google Docs format)
4. Set a Scheduled Task to refresh every Friday

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, marketing, and support docs manually — slow and error-prone. Work fix: cross-system status pull with a Go/No-Go report.

Launch readiness review for [Product/Feature]:

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)
   - Go / No-Go recommendation with rationale

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

Engineering — Work + Codex in the same app

Use Codex for code; switch to Work for cross-team documents. Both live in one desktop client.

Scenario A: PR review, release notes, team announcement

In Codex mode:
1. Review PR #123 in [repo/name], focus on [security / performance / test coverage]
2. Leave line-by-line review comments in the PR side panel
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 merged PRs this week and open P0/P1 issues
2. Generate an engineering weekly report in Markdown

Switch to Work mode:
3. Convert to Google Docs and insert burndown chart from @Jira
4. Set Scheduled Task: auto-generate every Friday at 5pm

[ SECTION_04 ] // AUTOMATE Scheduled Tasks recipes, setup pattern, and usage optimization

OpenAI highlights four high-frequency scheduled patterns. Adapt triggers and outputs to your role:

Scheduled Task setup prompt pattern:

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

Safety checklist before going unattended:

• Minimal plugin scope — connect only what the task needs
• No auto-external-send unless explicitly intended
• Output archive path set to avoid overwriting others' files
• Enterprise: confirm agent network policy with your admin
• Run 2–3 manual executions before switching to scheduled

Usage optimization. ChatGPT Work shares a metered usage pool with Codex. The same workflow can cost five times more depending on design.

Seven cost-saving tactics:

1. Draft in Chat first: Polish the brief in Chat, then hand a tight version to Work.
2. Trim Plan Mode steps: Remove duplicate data pulls before executing.
3. Reuse template docs: Scheduled Tasks hitting the same doc benefit from cache discounts.
4. Request concise outputs: Table plus three bullets beats a narrative report.
5. Split large projects: Phase 1 confirms direction; Phase 2 generates deliverables — avoids expensive re-runs.
6. Free users: Test small desktop tasks before scaling automation.
7. Enterprise teams: Set workspace, group, and individual limits in Admin Console.

Pre-launch usage test:

1. Pick a real task where you know the human time cost (e.g., month-end variance table, typically 2 hours manually).
2. Run once in Work with Plan Mode; record step count.
3. Check consumption against your plan's included usage.
4. Extrapolate daily, weekly, and monthly cost if scheduled.
5. If too high, apply the seven tactics above and re-run to compare.

[ SECTION_05 ] // ROADMAP Common pitfalls, troubleshooting, and 30-day onboarding plan

30-day onboarding roadmap:

[ SECTION_06 ] // FAQ FAQ, sources, and stable execution for automation

FAQ:

• Which workflow should I try first? The task you know best and can verify — month-end variance, campaign brief, or sales meeting prep. OpenAI recommends these because you can quality-check output quickly.
• How long should my prompt be? 150–400 words focused on data sources, output format, and constraints. Do not micromanage steps — that is Work's job.
• Do Scheduled Tasks run when my laptop is off? Desktop tasks need the device online. For true background automation, use web Workspace Agents on Plus or higher.
• Work mode vs Workspace Agent? Work is personal agent mode inside ChatGPT. Workspace Agents are team-built, admin-governed automations in Business and Enterprise with Admin Console controls.
• Can I use generated slides and reports externally as-is? Treat them as 80% drafts. Always human-review numbers, names, and external statements.
• What can Free users run from this guide? Desktop Work with limits. Start with lightweight tasks like invoice reconciliation before scheduling long automation.

Citeable figures from OpenAI and launch coverage — re-check after product updates:

• Plugin catalog: ChatGPT Work launches with 1,400+ integrations across Slack, Gmail, Drive, Salesforce, and more.
• Codex weekly active users: Roughly 5 million use Codex weekly; 1 million+ apply it to non-coding work (OpenAI public figures).
• Month-end close compression: OpenAI internal finance teams report variance analysis cycles dropping from days to hours with Work mode.

Primary references — re-open after product or pricing updates:

OpenAI Blog: ChatGPT for Your Most Ambitious Work

OpenAI Cookbook: Sales Meeting Prep Agent

ChatGPT Learn Changelog

SiliconANGLE: ChatGPT Work Launch Coverage

Developers Digest: Codex Merge Analysis

ChatGPT Work removes manual drudgery only when Scheduled Tasks actually fire — but desktop automation still dies to sleeping laptops, expired OAuth tokens, and full local disks. A personal MacBook is a poor 24/7 execution surface for multi-hour Work jobs, Codex multi-repo builds, and on-device Xcode validation.

If you need ChatGPT Work, Codex long jobs, and iOS CI/CD running around the clock on one dedicated Apple Silicon host, moving Computer Use and GitHub PR review to bare-metal Mac capacity beats firefighting unstable devices: NOVAKVM offers multi-region Mac Mini M4 / M4 Pro flexible terms with fixed bandwidth and default SSH — built for AI agent automation and mobile build validation on one machine. See the pricing page, order page, and help center.