Help me triage and manage this Outlook email workload without hiding commitments, exposing unnecessary personal information, or assigning work unfairly. [EMAIL THREADS OR MESSAGE SUMMARIES] [MY ROLE AND TEAM RESPONSIBILITIES] [CURRENT PRIORITIES AND DEADLINES] [TEAM AVAILABILITY AND OWNERSHIP RULES] [COMMUNICATION PREFERENCES] Read the messages as an operations coordinator. Distinguish: decisions already made, requests awaiting a response, tasks with an explicit owner, tasks with an implied owner, deadlines, blockers, and FYIs. Do not treat the loudest sender or most recent message as the highest priority.
Produce: 1. A triage table with priority (today, this week, monitor, archive), sender/thread, required action, owner, due date, and reason. Mark a due date as “not stated” when it is not explicit. 2. A commitments register listing every promise, decision, and dependency found in the threads. Separate confirmed commitments from assumptions. 3. Draft replies for the three highest-priority threads. Each should state the decision or next step, a named owner, a realistic date, and one direct question only when a decision is blocked. Keep the tone aligned to my preferences. 4. A short delegation plan that assigns work according to stated team roles and capacity. If ownership is unclear, propose an owner and label it as a proposal rather than a decision. 5. Outlook actions: folders or categories, flags, and calendar holds that would prevent a missed follow-up. Before answering, check that no task was assigned solely because of seniority, gender, or an unstated assumption, and flag any commitment that cannot be verified from the supplied messages. Ask up to three clarifying questions only if a required input is missing.
Fill in
| Placeholder | What to enter | Example |
|---|---|---|
| [EMAIL THREADS OR MESSAGE SUMMARIES] | Paste relevant emails or summaries with names and sensitive details removed if needed. | Client asks for revised onboarding date by Friday; product says an API fix may ship Tuesday; finance asks who will approve the discount exception. |
| [MY ROLE AND TEAM RESPONSIBILITIES] | Describe your role and who owns which types of work on the team. | I lead customer operations. Priya owns implementations, Marcus owns technical escalations, and Dana approves commercial exceptions. |
| [CURRENT PRIORITIES AND DEADLINES] | List active projects, immovable dates, and work that takes precedence. | Quarter-end renewals close September 30; two implementation managers are out Thursday and Friday. |
| [TEAM AVAILABILITY AND OWNERSHIP RULES] | State capacity limits, leave, decision-makers, and any assignment rules. | Do not assign Priya new launches this week; Dana must approve discounts over 10%; client commitments require written confirmation. |
| [COMMUNICATION PREFERENCES] | Describe the tone, reply length, and escalation style you want to use. | Direct and calm; use short paragraphs, bullets for next steps, and no apology unless we made an error. |
How to use
- Paste only the threads needed to make a decision, including prior messages that establish ownership or a deadline.
- Compare the commitments register with your calendar and project tracker before sending any draft.
- Confirm proposed owners with the relevant manager when the email trail does not establish authority.
- Follow up with: “Rewrite the client reply to acknowledge the risk, offer two feasible paths, and avoid promising the API fix.”
Variations
Inbox reset
Use this for a large backlog rather than a few active threads.
Create an Outlook inbox-reset plan from these message summaries: [INBOX SUMMARIES]. My responsibilities are [ROLE]. My next two weeks of deadlines are [DEADLINES]. Classify each item as reply, delegate, schedule, reference, or archive; identify hidden commitments and produce a 90-minute first-pass sequence. Draft only replies that can be sent with the facts provided. Do not archive messages containing an unresolved decision, customer promise, invoice, or legal issue. Check for duplicate threads and unstated deadlines.
Meeting follow-up
Use this after a meeting with scattered email decisions.
Convert these meeting notes and follow-up emails into a clear action email: [NOTES AND THREADS]. Recipients and roles: [RECIPIENTS]. Produce a message with decisions, actions, owner, due date, and open questions, followed by an internal tracker table. Preserve disagreements accurately and do not convert a suggestion into an approved decision. Flag actions without a named owner or date. Ask up to three questions only if a required decision is missing.
Manager escalation
Use this when a thread is blocked or a deadline is at risk.
Draft an escalation update about [BLOCKED WORK] using these email facts: [THREAD]. The decision-maker is [DECISION-MAKER], and the deadline is [DEADLINE]. Write a 150-word maximum email that states the impact, what has been tried, the decision needed, options with tradeoffs, and the latest safe decision date. Do not blame individuals or claim certainty not supported by the thread. Check that the requested decision is specific and actionable.
Tips
- Preserve the message that created a commitment; a polished summary is not a substitute for the source when a client disputes scope or timing.
- Use categories for workflow state such as Waiting, Delegated, and Decision Needed, not vague labels such as Important.
- Place a calendar hold for the date you need to follow up, not only for the due date promised to someone else.
- A reply that says “I’ll look into it” creates an obligation; replace it with a next action and date when possible.
FAQ
Can I paste client emails into an AI tool?
Follow your company’s data-handling policy first. Remove confidential account data, personal data, credentials, and contractual terms unless the approved tool is authorized for them.
How should AI decide email priority?
Priority should reflect customer impact, explicit deadlines, irreversible decisions, and dependencies—not sender rank or inbox order.
Should every email get a reply draft?
No. Many messages need a task, calendar hold, or archive decision rather than a new message that extends the thread.