سازنده اولویت‌بندی ایمیل: انبوه ایمیل‌های نخوانده را به یک لیست اقدام اولویت‌بندی‌شده تبدیل کنید
چرا این پرامپت اهمیت دارد
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.
ما از آن برای چه استفاده می‌کنیم
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.
پرامپت
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.
نتیجه
| 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.
بیشتر پرامپت‌های اولویت‌بندی ایمیل به یک دلیل مشترک شکست می‌خورند: از هوش مصنوعی می‌خواهند فوریت را فقط از روی موضوع ایمیل حدس بزند، که نتیجه‌اش فهرستی است که همه چیز در آن به یک اندازه مهم به نظر می‌رسد. این پرامپت با اعمال یک سقف سخت‌گیرانه این مشکل را حل می‌کند — حداکثر سه مورد می‌توانند در دسته «پاسخ امروز» قرار بگیرند، مگر اینکه ایمیل صراحتاً مهلت همان‌روزه اعلام کند یا کار شخص دیگری را مسدود کند، و هر استثنا باید در یک جمله توجیه شود. همین محدودیت است که کار واقعی را انجام می‌دهد.
ساختار چهار دسته‌ای (پاسخ امروز، پاسخ این هفته، واگذاری، بایگانی) دقیقاً همان‌طور فکر می‌کند که یک دستیار اجرایی باتجربه فکر می‌کند، نه آن‌طور که یک اپلیکیشن ایمیل بر اساس تاریخ مرتب می‌کند. دسته «واگذاری» شامل یک گزینه پشتیبان [ASSIGN TO: ___] است، چون مدل‌های هوش مصنوعی خوب تشخیص می‌دهند که ایمیلی باید به شخص دیگری برود اما همیشه مطمئن نیستند دقیقاً به چه کسی.
خبرنامه‌ها و رشته‌های فقط-CC عمداً بدون تحلیل مستقیم به بایگانی فرستاده می‌شوند. صرف تلاش استدلالی برای تصمیم‌گیری درباره فوریت یک خبرنامه بازاریابی، توجه مدل را روی ایمیل‌هایی هدر می‌دهد که هرگز قرار نبود انتخاب شوند.
الزام پیش‌نویس پاسخ برای موارد «پاسخ امروز» به شصت کلمه محدود شده است، چون ابزار اولویت‌بندی باید در زمان صرفه‌جویی کند، نه اینکه یک وظیفه نوشتاری دوم ایجاد کند.