Back to cookbook

AI Prompt to Triage an Overflowing Email Inbox Into a Prioritized Action List

0 views Published

Make this prompt yours

Share

This inbox triage prompt turns a backlog of unread or unsorted emails into a short, prioritized list of what actually needs a reply, a task, or nothing at all. It's built for anyone who comes back from a few busy days, a vacation, or a packed meeting schedule to find a few hundred emails and no clear sense of where to start.

Instead of summarizing every message equally, the prompt asks the model to sort emails into clear buckets β€” urgent and needs a reply today, needs action but not urgent, informational only, and safe to archive or ignore β€” and to justify each placement in one line so you can sanity-check the sorting instead of blindly trusting it. This keeps the output usable: a flat 300-line summary is just as overwhelming as the inbox itself, while a ranked, bucketed list is something you can actually work through.

It's designed to work across ChatGPT, Claude, and Gemini using plain pasted email text or subject-line/sender/snippet exports, so it fits whatever way you're pulling emails out of your client. If you want a reusable version of this exact workflow, the Prompt Builder tool can turn this template into a saved, one-click prompt you run every time your inbox backs up.

Prompt template

Make this prompt yours

prompt-template
290 tokens
ROLE: You are an executive assistant triaging an email inbox for prioritized action. CONTEXT: - My role: [YOUR JOB TITLE / WHAT YOU DO] - What counts as urgent for me: [e.g. "anything from my manager or top 3 clients, anything with a deadline mentioned, anything about payment or contracts"] - What's safe to deprioritize: [e.g. "newsletters, automated notifications, FYI-only threads"] - Emails to triage (sender, subject, and a snippet of each): [PASTE EMAIL LIST HERE] TASK: Sort the emails above into exactly these four buckets: 1. Urgent β€” needs a reply or action today 2. Important, not urgent β€” needs action but can wait a few days 3. Informational β€” no action needed, just worth knowing 4. Safe to archive or ignore For each email, give: sender, a one-line reason for its bucket, and (for buckets 1 and 2 only) a suggested next action. CONSTRAINTS: - If you're unsure which bucket an email belongs in, place it in the more urgent bucket and flag the uncertainty rather than guessing down. - Do not invent context about a sender or email that wasn't provided. - Keep each reason to one sentence. OUTPUT FORMAT: Four headed sections (one per bucket), each with a short bulleted list of emails and their one-line reasons and next actions.

Want it sharper? Optimize this prompt with Prompt Optimizer, check it with the Prompt Debugger or shorten it with the Token Optimizer.

Example input

example-input
352 tokens
ROLE: You are an executive assistant triaging an email inbox for prioritized action. CONTEXT: - My role: freelance web designer managing 4 active clients - What counts as urgent for me: anything from an active client mentioning a deadline, payment, or a site that's down - What's safe to deprioritize: tool newsletters, automated billing receipts, generic marketing emails - Emails to triage (sender, subject, and a snippet of each): 1. Sarah Chen (client) - "Site is down!!" - "Hey, our homepage is throwing a 500 error, customers are emailing us. Can you look ASAP?" 2. Figma - "New features in your workspace" - "Check out what's new in Figma this month..." 3. Marcus (client) - "Invoice question" - "Got the invoice, just want to confirm the hours before I approve payment, can you send a breakdown?" 4. Newsletter - "5 design trends for 2026" - weekly design newsletter digest 5. Priya (client) - "Launch date" - "Just confirming we're still on track for the March 20 launch, let me know if anything's changed" 6. Stripe - "Your receipt for $12.00" - automated billing receipt TASK: Sort the emails above into exactly these four buckets: 1. Urgent β€” needs a reply or action today 2. Important, not urgent β€” needs action but can wait a few days 3. Informational β€” no action needed, just worth knowing 4. Safe to archive or ignore For each email, give: sender, a one-line reason for its bucket, and (for buckets 1 and 2 only) a suggested next action.

When to use it

  • You're returning from time off or a heads-down stretch and facing a large backlog of unread emails
  • You need to decide, in minutes rather than hours, which emails need a same-day reply versus which can wait or be ignored
  • You manage a shared or support inbox and want a first pass that groups messages by urgency before a human reads them in detail
  • You want a daily or weekly habit of clearing inbox clutter without reading every message in full

Best practices

  • Paste real content (subject, sender, and at least the first few lines) rather than just subject lines β€” urgency is often buried in the body, not the subject
  • Tell the model who you are and what counts as urgent for you (client emails, your manager, anything with a deadline) so the triage reflects your actual priorities, not generic guesses
  • Review the 'safe to ignore' bucket before deleting anything β€” ask the model to flag anything it's unsure about rather than force a decision
  • If you run this same triage every day, save the structure as a reusable prompt with Prompt Builder instead of rewriting the instructions each time

Common mistakes

  • Pasting dozens of emails with no indication of sender relationship or deadline, leaving the model to guess at urgency from tone alone
  • Treating the triage as a final decision rather than a sorted starting point β€” always skim the urgent bucket yourself before acting
  • Running triage on emails containing sensitive account numbers, passwords, or personal data without redacting them first
  • Asking for a full summary of every email instead of a prioritized action list, which produces just as much to read as the inbox did

FAQs

How should I format my emails before pasting them into an inbox triage prompt?

Include the sender, subject line, and at least the first few lines of the body for each email β€” a list of subject lines alone usually doesn't give the model enough to judge urgency accurately. If your email client lets you export or copy a list view with snippets, that's usually enough.

Is it safe to paste email content into ChatGPT or Claude for triage?

Avoid pasting emails containing passwords, account numbers, or other sensitive personal data β€” redact or summarize those parts first. For routine work correspondence, most people find triage prompts like this useful, but check your employer's policy on pasting client or internal communications into AI tools if you're triaging a work inbox.

Can this prompt actually reply to emails for me, or just sort them?

As written, it only sorts and prioritizes β€” it doesn't draft replies. Once you have the prioritized list, you can ask the same model in a follow-up message to draft a reply for any specific urgent or important email.

Which Cuelara tool pairs well with this inbox triage prompt?

Prompt Builder β€” if you run this same triage routine regularly, it can turn this template into a saved, reusable prompt so you're not rewriting the instructions every time your inbox backs up.

Found this prompt useful? Share it.

Share

More in Productivity

Productivity

AI Prompt to Audit Your Calendar and Protect Deep Work Time

This calendar audit prompt turns a messy week of back to back meetings into a schedule with real blocks of deep work protected on the calend…

ROLE: You are a scheduling and time-management assistant helping a [JOB TITLE / ROLE] protect focused work time.

CONTEXT:
- Working hours: [START TIME] to [END TIME], [TIME ZONE]
- This week's meetings and recurring commitments: [LIST MEETINGS WITH DAY, TIME, DURATION, AND PURPOSE]
- Top 3 priorities for this week: [PRIORITY 1], [PRIORITY 2], [PRIORITY 3]
- Minimum deep work block needed: [E.G. 2 HOURS UNINTERRUPTED]

TASK:
1. Review the meeting list and flag which meetings are essential, which could be shortened, declined, or handled asynchronously, and why.
2. Identify any days with no meaningful block of uninterrupted time, and explain what's causing it.
3. Propose a revised weekly structure that protects at least [NUMBER] blocks of [DURATION] for deep work, placed during [PREFERRED TIME OF DAY, E.G. MORNING].
4. For each meeting you suggest cutting or shortening, give a one-sentence explanation I could use to justify the change.

CONSTRAINTS:
- Do not suggest moving meetings outside of [WORKING HOURS].
- Do not assume I can decline meetings with [NAMES OR ROLES THAT ARE NON-NEGOTIABLE].

OUTPUT FORMAT:
Return a day-by-day table (Day | Time Block | Activity | Type: Meeting/Deep Work/Admin) followed by a short list of specific meetings to renegotiate.

Make this prompt yours

Productivity

ChatGPT Prompt to Prepare Talking Points for a Difficult Workplace Conversation

This ChatGPT prompt helps you prepare talking points for a difficult workplace conversation β€” a tense one on one with a manager, a conflict…

You are an experienced workplace communication coach helping someone prepare for a difficult conversation.

Context:
- Who you need to talk to: [PERSON'S ROLE/RELATIONSHIP TO YOU]
- The situation: [DESCRIBE WHAT HAPPENED]
- Your relationship history with this person: [RELEVANT BACKGROUND]
- What you want to happen as a result of this conversation: [DESIRED OUTCOME]
- Your biggest worry about how this conversation could go wrong: [YOUR CONCERN]

Instructions:
1. Open with a one-sentence statement of shared goal or good intent, not a complaint.
2. List 3-5 key points to make, in the order they should come up, each as a short, specific statement grounded in facts rather than feelings.
3. Predict 2-3 likely objections or defensive reactions from the other person and draft a calm, non-escalating response to each.
4. Suggest one sentence to close the conversation that confirms the agreed next step.

Constraints:
- Keep language neutral and non-accusatory; avoid words like "always," "never," or "you clearly."
- Do not suggest ultimatums or threats.
- Keep each talking point under two sentences.

Output format:
Return the talking points as a numbered list under the headings: Opening, Key Points, Anticipated Pushback & Responses, Closing.

Make this prompt yours

Productivity

ChatGPT Prompt to Build a Weekly Time-Blocking Schedule From Your Task List

This time blocking schedule prompt turns a loose list of tasks, meetings, and deadlines into a structured weekly calendar with dedicated blo…

You are a productivity planner helping me build a realistic weekly time-blocked schedule.

CONTEXT:
Working hours: [E.G. 9 AM TO 6 PM, MONDAY TO FRIDAY]
Fixed commitments this week: [LIST MEETINGS/CALLS WITH DAY, START TIME, END TIME]
Tasks to schedule (with estimated duration): [LIST TASKS AND HOW LONG EACH TAKES]
Energy pattern notes (optional): [E.G. "SHARPEST IN THE MORNING", "LOW ENERGY AFTER 3 PM"]

TASK:
Build a day-by-day time-blocked schedule for this week that places every task and fixed commitment into a specific time slot.

CONSTRAINTS:
- Respect all fixed commitments exactly as given; never move or shorten them
- Group demanding, focus-heavy tasks earlier in the day when my energy notes say I'm sharpest then
- Leave at least a 10-15 minute buffer between blocks
- If the full task list does not fit within working hours, say so explicitly and list which tasks should move to another day or be cut, rather than compressing everything to fit

OUTPUT FORMAT:
For each day, list:
- Day and date placeholder (e.g. "Monday")
- Time blocks in order, each as [START-END]: [TASK OR COMMITMENT NAME]

After the schedule, add a short "Notes" section flagging any tasks that didn't fit and why.

Make this prompt yours