Customer Email Draft Threads

Overview

Run a safe support-email pass: inspect recent or requested Gmail messages, create unsent draft replies for real customer/person emails, and create one Codex project thread for each drafted email. Draft-only remains the default. Treat approved affiliate operations and verified DreamCut Discord invite requests as narrowly scoped workflows rather than ordinary support mail.

Use the detailed workflow in references/runbook.md whenever drafting, classifying risk, or creating project-thread handoffs. For account/access, unsupported-platform, duplicate, resolved-acknowledgement, cancellation, failed-payment, refund, or accidental-renewal decision trees, load handle-saas-account-cases or handle-saas-billing-cases.

When to use this skill

• When triaging Gmail customer support messages and preparing draft-only replies for real customer/person emails.
• When a customer sends a new reply, requests a draft review/revision, or needs a send/follow-up, and the complete thread must be re-read first.
• When closing a positively confirmed, fully resolved case and deciding whether an optional Trustpilot review invitation is eligible.
• When creating or reusing one canonical Codex project thread per drafted email, including deduplicating existing threads.
• When fulfilling approval-gated affiliate-notice handling or verified DreamCut Discord invite requests from noreply@dreamcut.ai.
• Not for account/access, unsupported-platform, duplicate, resolved-acknowledgement, cancellation, failed-payment, refund, or accidental-renewal decision trees — route those to handle-saas-account-cases or handle-saas-billing-cases instead.