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

Before You Copy a Prompt: 3 Principles That Decide Success

ChatGPT Work is not a smarter chat box. It is an agent that plans its own path, connects to your tools, and delivers finished files. Most early failures come from treating it like Chat mode. These three principles separate productive runs from wasted usage:

Why Most First Attempts Fail (Pain Points)

1. 01

   Micromanaging steps: Writing 20 manual instructions defeats Work mode's planning engine and burns usage

2. 02

   Missing plugin auth: Tasks stall or hallucinate when Gmail, Slack, or CRM connectors are not authorized

3. 03

   Wrong mode selected: Using Chat for multi-app deliverables or Work for quick Q&A wastes quota

4. 04

   Skipping Plan Mode review: High-risk actions (send, delete, overwrite) slip through unchecked

5. 05

   Vague data sources: Saying "the CRM" instead of @Salesforce leads to wrong pulls

6. 06

   Desktop asleep during Scheduled Tasks: Local automation pauses when the laptop lid closes or the user logs out

Pick the Right Mode: Chat / Work / Codex

The new ChatGPT desktop app runs three modes. Using the wrong one wastes usage:

Desktop vs Web: Where to Run Your Workflow

6 Role-Based Workflows: Sales, Marketing & Finance

The templates below are adapted from OpenAI case studies, early tester feedback (Zapier, Nvidia, Virgin Atlantic), and the Workspace Agent Cookbook. Replace @plugin names with your actual stack.

Sales

Scenario A: Daily Customer Meeting Briefs (Scheduled)

Pain point: Reps spend 1–2 hours daily assembling client background, recent news, and meeting agendas. Work solution: 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 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 (Client | Meeting Time | Key Topics | Brief Link)

OpenAI internal reference: Sales teams turned a single Discovery call 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 intel scattered across CRM, email, and Slack. Work solution: Build a live 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 (emails, meetings, support tickets)
   - Prioritized recommended next actions
2. Set a Scheduled Task: auto-refresh every weekday at 8am
3. Slack me via @Slack DM when major changes occur

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

Scenario C: Lead Review & Pipeline Repair (Zapier-Style)

Pain point: Thousands of leads per month; follow-up gaps are invisible until too late.

Analyze @Salesforce leads from the last 30 days and cross-reference @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 (for Scheduled Task use)

Marketing

Scenario A: Research to Brief to Multi-Market Assets (End-to-End)

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

Complete the 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, generate: 1 acquisition email, 3 LinkedIn posts, 1 landing page copy 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 proceeding.

Scenario B: Slack / Teams to Meeting Agenda Sync (Weekly Scheduled)

Set a scheduled task running every Monday at 7am:

1. Summarize the last 7 days from @Slack #product-launch and @Microsoft Teams "Go-to-Market" channel
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)

OpenAI internal result: Month-end close and forecast adjustment compressed from days to hours.

Assist with [Month] month-end budget variance analysis:

1. Pull 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 (match attached template style)
5. List 3 key judgment calls requiring human finance sign-off

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

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 only for human verification.

Usage Optimization, Pitfalls & 30-Day Roadmap

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

Billing Logic (Simplified)

Seven Cost-Saving Tactics

1. 01

   Draft in Chat first, then hand a tight brief to Work

2. 02

   Trim Plan Mode steps, especially duplicate data pulls

3. 03

   Reuse template docs in Scheduled Tasks for cache discounts

4. 04

   Request concise outputs — table + 3 bullets beats a narrative report

5. 05

   Split large projects into phases to avoid expensive re-runs

6. 06

   Free users: test small desktop tasks before scaling automation

7. 07

   Enterprise: set workspace / group / individual limits in Admin Console

Pre-Launch Usage Test

1. Pick a real task you know the human time cost of (e.g., month-end 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. If too high, apply the seven tactics above and re-run to compare

Common Pitfalls & Troubleshooting

30-Day Onboarding Roadmap

Citable Hard Data

• Output token multiplier: Output costs roughly 6x input tokens in Work mode billing
• Cache discount: Repeated reads of the same document cost ~1/10 of fresh input
• Workflow cost variance: Identical tasks can consume 5x more usage depending on step count and output verbosity

Running Scheduled Tasks and Computer Use workflows on a personal laptop creates predictable friction: agents pause when the lid closes, memory pressure interrupts long runs, and parallel Work + Codex sessions compete for CPU and disk I/O. Cloud VMs and shared Macs often add latency and lack native plugin sandboxing. For teams that need 7x24 stable agent uptime, isolated automation environments, or simultaneous iOS CI/CD and AI workflows, NodeMini Mac Mini cloud rental — dedicated Apple Silicon hardware, SSH access, and auditable networking — is typically the more reliable production path. See rental plans for current pricing.

Sources: OpenAI Blog, OpenAI Cookbook — Sales Meeting Prep, ChatGPT Learn Changelog, SiliconANGLE. Features and pricing subject to OpenAI official announcements.