Le Trieur de Boîte de Réception : Transformez une Pile d'E-mails Non Lus en Liste d'Actions Priorisée
Pourquoi ce prompt est important
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.
À quoi nous l'utilisons
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.
Résultat
| 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 plupart des prompts de tri d'e-mails échouent pour la même raison : ils demandent à l'IA de deviner l'urgence uniquement à partir de l'objet, produisant une liste où tout semble également important. Ce prompt corrige cela en imposant une limite stricte : pas plus de trois éléments ne peuvent être classés "Répondre Aujourd'hui" sauf si l'e-mail indique explicitement une échéance du jour même ou bloque le travail de quelqu'un d'autre, et chaque exception doit être justifiée en une phrase.
La structure en quatre catégories (Répondre Aujourd'hui, Répondre Cette Semaine, Déléguer, Archiver) reflète la façon dont un assistant exécutif expérimenté pense réellement, pas la façon dont une appli de messagerie trie par date. La catégorie "Déléguer" inclut une option de repli [ASSIGN TO: ___] car les modèles d'IA reconnaissent bien qu'un e-mail doit aller à quelqu'un d'autre, mais ne sont pas toujours certains de qui exactement.
Les newsletters et les fils en copie uniquement sont envoyés à l'Archive sans analyse, volontairement. Dépenser de l'effort de raisonnement à décider si une newsletter marketing est "urgente" gaspille l'attention du modèle sur des e-mails qui n'allaient jamais être retenus.
L'exigence de brouillon de réponse pour les éléments à traiter aujourd'hui est limitée à 60 mots précisément parce qu'un outil de tri doit faire gagner du temps, pas créer une deuxième tâche de rédaction.