El Clasificador de Bandeja de Entrada: Convierte un Montón de Correos Sin Leer en una Lista de Acción Priorizada
Por qué importa este prompt
Professionals spend roughly 28% of the workday on email, and it takes about 23 minutes to fully refocus after each interruption. Without triage, a same-day contract deadline can sit buried under CC threads and newsletters until the deadline has already passed — a missed signature on a $200K vendor contract costs far more than the 10 minutes triage would have taken.
Para qué lo usamos
You return from a week-long conference to 340 unread emails and a 9am meeting in two hours. You need to know which handful of emails actually require action before that meeting — not spend an hour reading all 340 in order.
Prompt
Role: Act as an executive assistant with 15 years of experience triaging high-volume inboxes for busy executives and founders. Context: - My role: [YOUR JOB TITLE / ROLE] - Today's top priorities: [LIST YOUR 2-3 MOST IMPORTANT TASKS TODAY] - Unread emails: [PASTE YOUR EMAILS BELOW — INCLUDE SENDER, SUBJECT LINE, AND THE FIRST 2-3 SENTENCES OF EACH] Task: Review every email I've pasted above and sort it into exactly one of four categories: Respond Today, Respond This Week, Delegate, or Archive/No Action Needed. For every email marked "Respond Today," draft a 2-3 sentence reply I could send with minimal editing. Constraints: - Do not mark more than 3 emails as "Respond Today" unless an email explicitly states a same-day deadline or blocks someone else's work — if you exceed 3, justify each one in one sentence - Flag any email where NOT responding today would delay another person's deliverable, even if the sender doesn't ask urgently - For "Delegate" items, name who it should go to based on context clues in the email, or write [ASSIGN TO: ___] if unclear - Ignore newsletters, automated notifications, and CC-only threads — sort these straight to Archive without analysis - Keep draft replies under 60 words each, in a tone matching [YOUR PREFERRED TONE: e.g. direct / warm / formal] Output Format: A table with columns: Sender | Subject | Category | Why | Draft Reply (only for Respond Today items) Followed by a one-line summary: total emails processed, how many need action today, and the single most time-sensitive item.
Resultado
| Sender | Subject | Category | Why | Draft Reply |
|---|---|---|---|---|
| Sarah Chen (Legal) | Contract redline — needs sign-off by EOD | Respond Today | Explicit same-day deadline blocks the vendor contract from closing | "Reviewed the redlines — section 4.2 looks good, but let's cut the indemnification cap in half before signing. Can we hop on a 10-min call at 2pm to finalize?" |
| Marcus Webb (Sales) | Client escalation — losing patience | Respond Today | Client threatening to churn; blocks Marcus from closing the renewal | "Marcus, sorry for the radio silence — I was at the conference. Let's get the client on a call tomorrow morning. I'll personally walk them through the fix. Can you set it up for 9am?" |
| Priya Patel (Eng) | Staging environment is down | Respond Today | Blocks the entire engineering team's testing for tomorrow's release | "Priya, escalate to DevOps on-call immediately if you haven't already — don't wait on me for this. CC me on the incident thread." |
| Finance Team | Q3 budget review — no rush | Respond This Week | Recurring request, no deadline mentioned, but needs your input before Friday's finance meeting | — |
| David (Board member) | Coffee next month? | Respond This Week | Low urgency, but a board relationship worth a timely reply | — |
| Ops Team | New expense policy — FYI | Delegate | Should go to your ops manager to implement, not something you need to personally review | [ASSIGN TO: Ops Manager] |
| 47 new notifications | Archive/No Action | Automated notification digest | — | |
| TechCrunch Daily | Today's top stories | Archive/No Action | Newsletter, no action needed | — |
Summary: 8 emails processed. 3 require action today — the staging outage is the single most time-sensitive item, since it blocks your entire engineering team's release timeline and should be handled within the hour, before the contract sign-off or client escalation.
La mayoría de los prompts de clasificación de correo fallan por la misma razón: piden a la IA que adivine la urgencia solo por el asunto, produciendo una lista donde todo parece igual de importante. Este prompt lo soluciona imponiendo un límite estricto: no más de tres elementos pueden caer en "Responder Hoy" a menos que el correo indique explícitamente un plazo del mismo día o bloquee el trabajo de otra persona, y cada excepción debe justificarse en una frase.
La estructura de cuatro categorías (Responder Hoy, Responder Esta Semana, Delegar, Archivar) refleja cómo piensa realmente un asistente ejecutivo experimentado, no cómo una app de correo ordena por fecha. La categoría "Delegar" incluye una opción de respaldo [ASSIGN TO: ___] porque los modelos de IA son buenos reconociendo que un correo debe ir a otra persona, pero no siempre están seguros de a quién exactamente.
Los boletines y los hilos solo en copia se envían al Archivo sin análisis, a propósito. Gastar esfuerzo de razonamiento decidiendo si un boletín de marketing es "urgente" desperdicia la atención del modelo en correos que nunca iban a calificar.
El requisito de borrador de respuesta para los elementos de Responder Hoy está limitado a 60 palabras precisamente porque una herramienta de clasificación debe ahorrar tiempo, no crear una segunda tarea de redacción.