ChatGPT Work in der Praxis
6 Rollen-Workflows, Prompt-Vorlagen und Automatisierungsrezepte

Create a scheduled task that runs every weekday at 4:00 PM.

1. Check my @Google Calendar for client meetings tomorrow (exclude internal meetings)
2. For each client meeting:
   - Pull account notes and interaction history from the last 30 days via @SharePoint / @Salesforce
   - Search for public news and executive updates about the company from the last 30 days
   - Write a 2–3 sentence background summary for each external attendee
3. Generate a 2–3 page brief for each meeting and save as @Google Drive documents
4. Send me a summary @Gmail with links to each brief

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

Based on all opportunities, contacts, and recent activity for [account name] in @Salesforce:

1. Create an interactive account command center (Sites) containing:
   - Pipeline overview (stage, amount, expected close date)
   - Key signals from the last 7 days (email, meetings, support tickets)
   - Recommended next actions (priority ranked)
2. Set a Scheduled Task to refresh the Site every weekday at 8:00 AM
3. DM me on @Slack when there are significant changes

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

Analyze new leads from the last 30 days in @Salesforce and their follow-up history, cross-referenced with sales correspondence in @Gmail.

Find:
1. Leads with no follow-up after 48 hours (grouped by source)
2. Break points in the follow-up chain (where response rate drops sharply)
3. Estimated pipeline loss in dollar terms

Output:
- Excel detail sheet (Lead ID | Source | Last follow-up | Break type | Recommended action)
- 1-page executive summary PPT highlighting seven-figure opportunity risk
- A weekly review process suitable for conversion into a Scheduled Task

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

Complete an end-to-end marketing workflow:

Phase 1 — Brief:
- Extract target audience, core pain points, and competitive positioning
- Output a Campaign Brief (Google Docs) with message 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 folder "Campaign / [product name]"

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

Pause after each phase and wait for my confirmation before proceeding.

Set a scheduled task to run every Monday at 7:00 AM:

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 that need alignment in the meeting
3. Update the "Weekly Meeting Agenda" document in @Google Drive (preserve version history)
4. Post a summary of 5 items or fewer in @Slack #leadership

Constraints: cite only publicly discussed content; do not leak messages marked confidential.

Help complete [month] budget variance analysis:

1. Pull corresponding tables from @Google Drive "Finance / Actuals" and "Finance / Forecast"
2. Create 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 a performance narrative (Google Docs) explaining likely causes by Revenue / COGS / OpEx
4. Build a 5–8 page management report PPT (with charts, following the attached template style)
5. List 3 key judgment calls that require manual finance sign-off

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

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

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

Do not initiate payments; output a review sheet for manual verification only.

Run automatically every weekday at 6:30 AM:

1. Access [internal dashboard URL / @SharePoint report page]
2. Compare against yesterday's snapshot; extract significant changes (>10% swing or new red indicators)
3. Generate a 1-page morning brief (Google Docs) structured as:
   - TOP 3 items to watch today
   - Metric change table
   - Recommended follow-up owners
4. Send via @Gmail to ops-leads@company.com

If the dashboard is unreachable, tell me during Plan Mode—do not fabricate data.

Monitor new customer feedback from the last 14 days across:
- @Slack #customer-feedback
- @Gmail label "NPS-Detractor"
- @Google Drive "Support Tickets Export"

1. Cluster feedback into 5–8 themes (with representative quotes)
2. Score priority by frequency × impact × implementation difficulty
3. Output a product evaluation backlog (Notion / Google Docs format)
4. Set a Scheduled Task to refresh the document every Friday

Constraints: anonymize feedback; do not include customer names.

Run a launch readiness review for [product/feature name]:

1. Pull associated Epic / Story completion status and open blockers from @Jira
2. Pull the corresponding GTM plan from @Google Drive "GTM Plans" and check key milestones
3. Extract unresolved discussions from the last 7 days in @Slack #product-launch
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.

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, generate a Release Notes draft

Then switch to Work mode:
4. Format Release Notes as a @Confluence page
5. Draft an announcement for @Slack #engineering (do not auto-send)

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 this week's burndown chart (pulled from @Jira)
4. Set a Scheduled Task to auto-generate every Friday at 5:00 PM

1. Pick a real task you already know the manual time for (e.g., month-end variance table, usually 2 hours by hand)
2. Run it once in Work mode with Plan Mode enabled; record step count
3. After execution, check consumption against your plan's included usage
4. Estimate: if run daily / weekly, is monthly consumption within budget?
5. If high → optimize per Section 5.2 and rerun to compare