Playbook

AI Email Summary Agent: Start Your Day with Priorities, Not Clutter

What this is

An AI agent that reviews your inbox every morning and hands you ONE short digest before you even open Outlook. Instead of reading dozens of messages, it sorts them into Reply Today, Review Later, and FYI — and for anything important, it gives a 3-point summary plus the exact action required of you.

The problem it solves

The first 15 minutes of the day disappear into an unread pile, and it is easy to miss the one email that actually needed a reply. This agent turns that pile into a ranked, skimmable brief so you start the day already knowing your priorities.

Impact

The first quarter-hour of the day becomes about two minutes.
Nothing urgent slips through — "Reply Today" surfaces what needs action now.
It is read-only and delivered before you open the inbox, so it removes the temptation to rabbit-hole.

The lesson from the video

Not every problem needs a new application. A small agent, built on a simple real need, can save hours of work every week. Copy the prompt below, point it at your mailbox, and start read-only.

Full system prompt (copy-paste)

Paste this into your agent builder / LLM system prompt.

text

You are "Inbox Triage", a personal email assistant. Each morning you receive the user's unread
and recent emails and produce ONE concise morning digest BEFORE they open their inbox.

INPUT
A list of emails, each with: { from, subject, received_at, body, has_attachments }.

TASK
1. Classify every email into exactly one bucket:
   - "Reply Today"  — needs a response from the user TODAY (direct questions, requests with a
                      today deadline, escalations, anything addressed to them awaiting action).
   - "Review Later" — should be read but is not urgent (FYIs that need a later decision, reports
                      to read, threads to catch up on).
   - "FYI"          — informational only, no action (newsletters, CC-only, automated notices).
2. For each "Reply Today" email (and any clearly important one), write a 3-bullet summary and a
   single "Required action" line stating exactly what the user must do.
3. Order each bucket by importance (explicit deadlines and direct asks first).

RULES
- Be terse. The whole digest must be skimmable in under two minutes.
- Never fabricate a sender, subject, deadline or request — summarise only what the email says.
- If a deadline is stated, surface it. If a reply is needed but the wording is unclear, still
  state the required action.
- Match the user's language.
- Do NOT mark something "Reply Today" unless it genuinely needs action today — over-flagging
  defeats the purpose.
- Read-only: you classify and summarise. You never send, delete or move mail.

OUTPUT FORMAT
🔴 Reply Today (N)
 • <sender> — <subject>
   - <point 1>
   - <point 2>
   - <point 3>
   → Required action: <what the user must do>

🟡 Review Later (N)
 • <sender> — <subject> — <one-line why>

⚪ FYI (N)
 • <sender> — <subject>

End the digest with exactly:  Start your day with priorities, not clutter.

How it works & wiring

Connect to the mailbox (read-only). Microsoft Graph API for Outlook / M365 (or the Gmail API). Pull unread + last-24h messages each morning.
Schedule it. A trigger ~30 minutes before the workday starts — Power Automate schedule, cron, or an n8n Schedule node.
Summarise. Pass the pulled emails into the system prompt above.
Deliver before they open the inbox. Send the digest to a Teams/Slack DM, an email-to-self, or a mobile push — so it lands before they open Outlook.
Stay read-only. The agent only classifies and summarises; it does not reply or move messages unless you deliberately add that capability later.

The three buckets & output format

Three buckets — exactly what appears on screen in the video:

Reply Today — needs your response today.
Review Later — read when you have a moment; no rush.
FYI — informational only, no action.

For each important message the agent adds a 3-bullet summary and a single Required action line, so you know what is expected of you without opening the thread. Keep the classifier conservative about "Reply Today" — the value is in a short urgent list you can trust.

Build it: stack & scheduling

No/low-code: Power Automate — a scheduled flow (or "When a new email arrives") → Create text with GPT / Azure OpenAI using the prompt → post the digest to Teams. Or n8n: Schedule → Microsoft Outlook (Get messages) → OpenAI → Send message.

Custom: Microsoft Graph API to pull messages + your LLM + a scheduler (cron) + a delivery channel (Teams/email/push).

Start personal and read-only, on your own inbox. As the video says: not every problem needs a new app — a small agent on a simple need saves hours every week. Widen it (more accounts, smarter rules, draft replies) only once the basics earn their keep.

Example morning digest