Triage a 25-email Monday-morning inbox with AI: classify by urgency, summarize the two threads too long to read, and draft replies in three different tones — then prove every draft against the thread facts before anything gets "sent". Sixty minutes, free tools, and a triage habit you will keep.
Priya Nair is the office and admin manager at Meridian Facility Services Pvt Ltd, a fictional 200-person facilities company in Pune. She was off Friday. It is now 9:05 on Monday, her inbox shows 25 unread messages, and her first meeting is at 10:00. Two of the emails are long, tangled threads — a customer complaint and a vendor negotiation — and somewhere in the pile there is at least one thing that is not what it claims to be. Your job is to get Priya to a fully triaged inbox, with every reply drafted, edited into her voice, and fact-checked, in under an hour.
Here is Priya's unread list — sender, subject, and the first line of each message. Paste-ready.
01 | Anil Deshpande (Ops) | Weekly ops sync moved? | Can we shift Tuesday sync to 3pm...
02 | billing@sparkletclean.example | Payment overdue - FINAL | Your account is 45 days overdue...
03 | Ritu Sharma (HR) | New joiner desk allocation | Two joiners on the 14th, need desks...
04 | IT Helpdesk <it-support@meridian-facilties.example> | Password expiry - verify now | Your password expires today, click...
05 | Vikram (CEO office) | Board visit on the 19th | CEO wants walkthrough plan by Wed...
06 | Sunita Rao <sunita.rao@trentwoodhotels.example> | RE: RE: RE: Deep-clean complaint - Site 4 | This is the third time I am writing...
07 | facilities-newsletter@fmtoday.example | URGENT: Webinar seats filling! | Join our facilities trends webinar...
08 | Mohan (Security) | CCTV AMC renewal quote | Vendor quote attached, expires Fri...
09 | Deepa (Accounts) | GST invoices for July - missing 3 | Need invoices 2039, 2041, 2044...
10 | Rajesh Kulkarni <r.kulkarni@apexsupplies.example> | RE: RE: Revised rates - housekeeping consumables | As per our discussion, sharing...
11 | Anita (Reception) | Visitor badge printer jammed | Printer down since Friday evening...
12 | training@skillbridge.example | Your certificate is ready | Download your fire-safety cert...
13 | Anil Deshpande (Ops) | Fwd: AC servicing schedule | FYI - vendor confirmed for the 12th...
14 | Sunita Rao <sunita.rao@trentwoodhotels.example> | Escalation copy: deep-clean complaint | Copying my regional head on this...
15 | noreply@lunchbox-cafe.example | New menu this week! | Try our new thali combos...
16 | Ritu Sharma (HR) | Fire drill compliance sign-off | Need your sign-off by EOD Tuesday...
17 | Kiran (Admin exec) | Leave request - 15th to 17th | Family function, applying for 3 days...
18 | procurement@meridianfs.example | PO-1187 approved | Your PO for pantry supplies approved...
19 | Rajesh Kulkarni <r.kulkarni@apexsupplies.example> | Gentle reminder - revised rates | Awaiting your confirmation since...
20 | Shweta (Site 2 lead) | Water leakage - block B | Seepage near server room, need vendor...
21 | jobs@quickhirenow.example | 500 candidates waiting for you! | Hire facility staff in 24 hours...
22 | Deepa (Accounts) | RE: GST invoices - one received | Got 2039, still need 2041 and 2044...
23 | Anil Deshpande (Ops) | Site 4 supervisor change | Moving Prakash to Site 4 from the 11th...
24 | Vikram (CEO office) | RE: Board visit - parking | Also block 4 parking slots for the 19th...
25 | survey@meridianfs.example | Quarterly employee survey | 5 minutes, closes on the 15th...
The two threads that need summarizing before anyone can reply:
THREAD A - "Deep-clean complaint - Site 4" (Trentwood Hotels, our client)
28 Jul, Sunita Rao: Deep-clean of banquet hall was scheduled for 26 Jul.
Team arrived 3 hours late and left carpet shampooing unfinished.
29 Jul, Priya Nair: Apologies - confirming with the site team, will revert.
30 Jul, Prakash (Site 4): Team was late due to transport strike. Carpet job
finished next morning 7am before hotel opened. Photos attached.
30 Jul, Sunita Rao: Finished or not, my banquet manager lost half a day.
I want a credit on the August invoice. We were billed Rs 14,800 for this
deep-clean under invoice INV-2041.
01 Aug, Meridian billing (auto): Reminder - INV-2041 (deep-clean, Site 4,
Rs 14,800) due 15 Aug.
04 Aug, Sunita Rao: Third time writing. No response since Thursday. I expect
a full credit of Rs 18,400 against INV-2041, or we review the contract.
Copying my regional head.
THREAD B - "Revised rates - housekeeping consumables" (Apex Supplies, vendor)
12 Jun, Rajesh Kulkarni: Requesting a call to discuss revised rates -
raw material costs are up 9 percent.
13 Jun, Priya Nair: Call done today. Summary: we agreed you will send a
revised rate card for REVIEW. No commitment given. Any revision applies
only from the NEXT quarter after written approval.
27 Jul, Rajesh Kulkarni: As agreed on our 3 June call, sharing the revised
rate card. Kindly note the new rates apply from 1 June as discussed.
Invoice for June-July difference (Rs 42,300) attached.
02 Aug, Rajesh Kulkarni: Gentle reminder. Awaiting confirmation since last
week. We have been servicing Meridian for 6 years and this delay in
approving a small adjustment is disappointing.
Set up the triage. Open your chat AI and paste the 25-line inbox list with this prompt: "You are helping an office manager triage email. Classify each message into: URGENT-TODAY, THIS-WEEK, DELEGATE, FYI-ARCHIVE, or SUSPICIOUS. Give a one-line reason per message. Present as a table." Do not paste the threads yet — triage works on the manifest alone.
Audit the AI's triage before trusting it. Read every classification and reason. The AI is guessing from subject lines, exactly as a rushed human would — and a rushed human gets at least two of these wrong. Check specifically: does anything flagged urgent actually deserve it, and is anything dangerous sitting in a harmless-looking category? Correct the table yourself and note each correction — you will need the list at the end. Ask the AI to re-print the corrected table.
Summarize Thread A. Paste the complaint thread with: "Summarize this client complaint thread in 5 bullet points: what happened, what the client wants, what our team says happened, current risk level, and any facts that do not add up." That last clause matters — you are explicitly inviting the AI to spot inconsistencies rather than smooth them over.
Verify the summary against the thread. Take each bullet and find the exact line in the thread that supports it. Two things to check by hand: every rupee amount, and every date. If the AI's summary states what the client is asking for, confirm that number appears in the thread — and confirm it is consistent within the thread. Write down anything that conflicts. Do the same paste-summarize-verify pass for Thread B, asking specifically: "List every date and every amount mentioned, with who said it."
Draft the client reply — apologetic but precise. Prompt: "Draft a reply to Sunita Rao. Tone: apologetic, professional, de-escalating. We accept the team arrived late. We will discuss a credit but must confirm the correct invoice amount first — do not commit to a specific credit figure. Under 150 words. Do not invent any facts not in the thread." Read the draft. If it commits to any amount, or apologizes for something the site team disputes without acknowledging their account, fix it.
Draft the vendor reply — firm, not rude. Prompt: "Draft a reply to Rajesh at Apex Supplies. Tone: firm and factual. Point out exactly what our 13 June email agreed: revised rates were for review only, no retroactive application, changes only from next quarter after written approval. Decline the June-July difference invoice. Keep the relationship door open. Under 150 words." Check the draft quotes the real call date and terms from Thread B — not the vendor's version.
Draft the internal replies — warm and quick. In one prompt, ask for three short replies: to Vikram (board visit — confirm plan by Wednesday, ask about parking count), to Shweta (water leakage — treat as today's priority, name the next step), and to Kiran (approve leave, one warm line). Internal notes should sound like a colleague, not a press release — if any draft says "I hope this email finds you well," delete that line.
The 60-second check, then close the sprint. For each of the five drafts in your outbox doc: read it aloud once, verify every number and date against the source thread, confirm the tone matches the recipient, and confirm it makes no promise Priya is not authorized to make. Finally, ask the AI: "Turn what we just did into a reusable triage prompt I can paste every Monday." Save that prompt — it is the real take-home.
Never let an AI draft commit money, dates, or apologies-with-admissions on your behalf — instruct it up front what it may not promise, then check that it obeyed.
A completed sprint has all of the following:
AI turns a 25-email pile into a 60-minute sprint — but the value is in the audit, not the drafts. Classify with AI, verify with your own eyes, and never let a model commit an amount, a date, or an admission you have not checked against the thread.