Same-Day Email Priority Triage
Rank incoming emails by same-day urgency, impact, deadlines, and response effort.
Customise & copy
Add the context you have. The prompt updates as you work.
Paste each email subject with its snippet or a short body excerpt.
List explicit deadlines, meetings, outages, launches, or other timing constraints.
Identify whether each sender is internal, external, a customer, a manager, a direct report, or a VIP.
For each email, state whether it needs a decision, information, approval, acknowledgement, or another action.
Live prompt
4 fieldsFilter and rank the incoming emails below to identify which require a response today. Do not ask follow-up questions. Assess each email using urgency, stated deadlines, business or operational impact, sender relationship, expected action, and estimated response effort. Do not invent facts; mark missing information as "Not stated". Incoming emails: {{email_batch}} Known deadlines or time-sensitive context: {{deadline_context}} Sender relationships: {{sender_relationships}} Expected action types: {{action_types}} Return only this fixed format: RESPONSE TODAY 1. [Email subject] Priority: Critical, High, or Medium Reason: [brief, specific justification based on urgency, impact, deadline, relationship, and action type] Estimated effort: [minutes or "Unknown"] Recommended action: [specific response action] 2. [Email subject] Priority: Critical, High, or Medium Reason: [brief, specific justification] Estimated effort: [minutes or "Unknown"] Recommended action: [specific response action] Continue numbering as needed. Rank highest priority first. DEFER OR NO SAME-DAY RESPONSE - [Email subject] — [brief reason it can wait or does not require a response today] If no emails require a response today, write "None" under RESPONSE TODAY. Include every email exactly once.
Proof before you use it
A real example
Tested on gpt-5.6-luna on 2026-09-10
{
"email_batch": "1. Subject: ICU ventilator maintenance alert\nSnippet: Engineering reports a fault on the backup ventilator assigned to Ward 4 and needs an operational decision.\n\n2. Subject: Quarterly nursing education survey\nSnippet: Please complete the optional survey when convenient this month.\n\n3. Subject: Vendor introduction for cafeteria redesign\nSnippet: The facilities vendor would like a discovery call sometime next quarter.",
"action_types": "Ventilator alert: decision and acknowledgement; nursing survey: information; vendor introduction: scheduling decision.",
"deadline_context": "The Ward 4 ventilator issue affects tonight's staffing plan and requires a decision before the 2:00 PM operations briefing. The survey closes at month-end. Cafeteria planning begins next quarter.",
"sender_relationships": "Biomedical engineering lead: internal operational partner; Nursing education coordinator: internal; Facilities vendor: external supplier."
}A small ritual that works
How to use it
- 01Paste email subjects and snippets into Email subjects and snippets.
- 02Add deadlines, meetings, outages, launches, or other time-sensitive context.
- 03Describe each sender relationship and expected action type.
- 04Review the ranked same-day responses and defer-or-no-response list.
Why it works
The prompt gives the task a clear decision rule: identify messages that require a response today, assess them against urgency, deadlines, operational or business impact, sender relationship, expected action, and effort, then rank them. It also separates same-day responses from items that can wait, which creates a practical action queue. The fixed format makes each item comparable by requiring a priority, evidence-based reason, effort estimate, and recommended next step. Its instruction to mark unknown information as "Not stated" helps limit unsupported assumptions, while the requirement to include every email exactly once supports complete coverage.
Where it fails
The structure depends on the supplied email snippets and context containing enough information to distinguish urgency, impact, relationships, deadlines, and required actions. Short, ambiguous, contradictory, or outdated inputs can make prioritization uncertain. The three-level priority scale may also be too coarse for teams that need more categories, explicit tie-breaking rules, ownership, escalation paths, or calendar-aware scheduling. Estimated effort is limited to minutes or "Unknown," so it does not capture dependencies, waiting time, or the effort of gathering missing information.
Customisation tips
Adapt the assessment criteria to the operating context. Add escalation rules for regulatory matters, security incidents, executive requests, customer commitments, or revenue-sensitive issues. If prioritization should reflect business policy, specify how deadlines, impact, sender relationship, and response effort should be weighted or used to break ties. Expand the required fields to include owner, due date, dependency, escalation channel, or a short reply template. Replace the current priority labels with the organization's terminology if needed, and adjust the response categories to distinguish acknowledgement, decision, delegation, scheduling, and no action.
Watch-outs
- Provide matching context for each email so relationships, deadlines, and action types can be associated with the correct subject.
- Keep deadline information current; the prompt uses timing context as a central prioritization signal.
- Do not treat sender seniority or external status as sufficient on its own; the required reason should connect the relationship to urgency, impact, or action.
- The prompt asks for a specific response action, so vague recommendations such as "handle this" reduce the usefulness of the structure.
Works in
Was this useful?
Submit your variation
If your version helps, it may be published with your name and a link back to you.
Want to make AI useful across your team? Explore Atul's training.