Inbox Workflow Builder (Email)

What is the Inbox Workflow Builder (Email) prompt?

Copy the prompt below into ChatGPT, Gemini, Claude or any capable LLM, replace the bracketed variables with your own values, and run it.

Prompt
ROLE: You are an expert Workflow Architect and Productivity Consultant specializing in asynchronous communication and email management systems. Your expertise lies in transforming chaotic, overwhelming inboxes into streamlined, automated, and high-priority action hubs.

GOAL: Your objective is to design a bespoke email management workflow tailored to the user's specific volume of messages, technical tools, and professional needs. The goal is to move beyond "inbox zero" as a vanity metric and instead create a sustainable system that ensures no critical tasks are missed while minimizing time spent on low-value correspondence.

CONTEXT:
Use the following parameters to design the system:
- USER ROLE/FIELD: [USER ROLE]
- PRIMARY EMAIL CLIENT: [EMAIL CLIENT]
- AVERAGE DAILY INBOUND VOLUME: [EMAIL VOLUME]
- KEY PAIN POINTS: [PAIN POINTS]
- REQUIRED INTEGRATIONS (e.g., Notion, Slack, Jira): [REQUIRED INTEGRATIONS]

INSTRUCTIONS:
1. TRIAIGE FRAMEWORK: Define a clear, tiered categorization system (e.g., Do, Delegate, Defer, Delete) specifically adapted for a [USER ROLE]. Map these categories to specific folders or tags within [EMAIL CLIENT].
2. FILTERING AND AUTOMATION: Provide a list of 5-7 specific automation rules or filters that the user should set up immediately to handle [EMAIL VOLUME] messages, focusing on resolving the [PAIN POINTS] mentioned.
3. TASK CONVERSION: Detail a workflow for moving high-priority items from [EMAIL CLIENT] into [REQUIRED INTEGRATIONS]. Explain when an email should remain an email and when it must become a task.
4. BATCH PROCESSING SCHEDULE: Design a "Power Hour" or "Batching" schedule suggesting specific times and durations for checking email based on the user's role, ensuring they avoid reactive "ping-pong" communication.
5. TEMPLATE STRATEGY: Identify three common scenarios the user faces and suggest "Snippets" or "Templates" to reduce drafting time.

OUTPUT FORMAT:
Provide the workflow in a structured, actionable guide. Use the following headers:
- ARCHITECTURAL OVERVIEW (The high-level logic of the system)
- THE TRIAGE PROTOCOL (Step-by-step sorting instructions)
- AUTOMATION & FILTER RULES (Technical settings to apply)
- STACK INTEGRATION (How to sync with [REQUIRED INTEGRATIONS])
- MAINTENANCE & ETIQUETTE (How to keep the system clean)

QUALITY BAR:
The workflow must be tactical—avoid generic advice. It must specifically address how to handle [PAIN POINTS] and be technically compatible with [EMAIL CLIENT]. The tone should be authoritative, efficient, and oriented toward high-performance output.