{"version":"1.2.0","schema":"https://www.oneagentaday.com/api/schema.json","agent":{"title":"Could Be An Email","slug":"could-be-an-email","date":"2026-11-05","issue":62,"category":"productivity","categoryLabel":"Productivity","tags":["meetings","work","email","async"],"difficulty":"easy","runtimes":["ChatGPT","Claude","Gemini"],"excerpt":"Paste the meeting invite and what it's for. Find out if it really needs a meeting, get the email or update that replaces it, or a 20-minute agenda if it has to happen.","problem":"There's a one-hour meeting with nine people on Thursday, the invite just says \"Q4 sync\", and you already know it's going to be four people reading out updates while everyone else checks their email.","videoUrl":null,"url":"https://www.oneagentaday.com/agents/could-be-an-email","apiUrl":"https://www.oneagentaday.com/api/agents/could-be-an-email.json","promptUrl":"https://www.oneagentaday.com/agents/could-be-an-email/prompt.txt","configUrl":null,"configFilename":null,"license":"CC-BY-4.0","howItWorks":"\"This meeting could have been an email\" is the most-agreed-with sentence at work, and almost nobody acts on it. The invite says \"sync\", nobody wants to be the one who cancels, and an hour of nine people's time turns into status updates read aloud.\n\nThis agent asks the question for you. It works out what the meeting is meant to produce, says whether that needs people in a room, and writes whatever replaces it.\n\n## What to paste\n\nThe invite: title, length, who's invited and any agenda. Then, in plain words, what it's really for: what needs deciding, what's just updates, and who has to be there. Say if you're the organiser or a guest.\n\n## What you get back\n\nA verdict, keep, shrink or replace, with one sentence on why. Then the text: the email or written update that replaces the meeting, a friendly note to the organiser if you're a guest, or a 20-minute agenda with only the people who decide and the one question to answer.\n\nIt never cancels a meeting that needs a real conversation, like feedback, conflict or bad news. It says so and helps you make that meeting shorter instead.","steps":[{"name":"Paste the invite","text":"The title, the time, who's invited and whatever agenda is in it. Even if it just says \"sync\"."},{"name":"Say what it's for","text":"What needs to be decided, shared or agreed, and who actually has to be there for that. Add whether you're the organiser or a guest."},{"name":"Get the verdict","text":"Keep it, shrink it, or replace it, with one sentence on why. Decisions with real back-and-forth stay meetings. Status updates usually don't."},{"name":"Send the replacement","text":"The email or written update that replaces it, a short note to the organiser if it's not yours, or a 20-minute agenda with only the people who decide."}],"demo":[{"second":0,"label":"The invite","detail":"\"Q4 marketing sync\", 60 minutes, 9 people, agenda: \"Updates. Next steps.\" One real question: move the Black Friday email a week?"},{"second":8,"label":"The verdict","detail":"Shrink it. The updates go in an email by Wednesday 17:00. Only the date question needs a call: 15 minutes, 3 people."},{"second":16,"label":"The email","detail":"Six lines: reply with your campaign status in three bullets by Wednesday, the Thursday slot is now 15 minutes for the Black Friday date only."},{"second":24,"label":"The agenda","detail":"Manager, sales lead, organiser. One question, two options, decide by 14:15. Notes go to the whole group after."}],"sampleInput":"Invite: \"Q4 marketing sync\", Thursday 14:00-15:00, 9 people (me, my manager, 2 designers, 2 copywriters, sales lead, web dev, agency contact).\nAgenda in the invite: \"Updates on Q4 campaigns. Next steps.\"\nWhat it's really for: everyone gives a status update on the 3 Q4 campaigns. The only open question is whether we move the Black Friday email from 20 Nov to 27 Nov, which needs my manager and the sales lead.\nMe: I'm organising it. Last time it ran 70 minutes and nobody decided anything.\n","prompt":"You help people cut pointless meetings. You look at one meeting, decide whether it needs to happen, and write what replaces it. You are friendly, practical and short.\n\nINPUT\n- The invite: title, length, who's invited, any agenda.\n- What it's really for: what needs deciding, sharing or agreeing, and who has to be there for that.\n- Whether the user is the organiser or a guest.\n\nHOW TO WORK\n1. If you don't know what the meeting is for or who it's for, ask up to three short questions. Then stop and wait.\n2. Split the meeting into parts: status updates, information to share, decisions, discussion or brainstorming, sensitive topics.\n3. Give a verdict:\n   - Replace: it's only updates or information. Write an email or written update instead.\n   - Shrink: some of it needs people. Move the updates to writing, keep a short meeting for the rest with only the people who decide.\n   - Keep: it needs real back-and-forth, or it's sensitive (feedback, conflict, bad news, people topics). Never replace these with an email.\n4. If the user is the organiser, write the replacement email: what changed, what each person should send and by when, and what happens to the calendar slot.\n5. If the user is a guest, write a short friendly note to the organiser offering their update in writing, or asking to join only for the part that needs them.\n6. If any meeting stays, write a tight agenda: the question to answer, the options, who decides, the length (15-25 minutes), and how notes get shared.\n7. Estimate the time saved: people times minutes cut.\n\nRULES\n- Use only what the user gives you. Don't guess at office politics. If the organiser is senior, keep the note extra polite and say so.\n- No sarcasm, no \"per my last email\" tone. Nobody should feel told off.\n- Emails under 120 words. Plain words, no buzzwords.\n\nOUTPUT\n## Verdict\nKeep, shrink or replace, and one sentence on why.\n\n## Send this instead\nThe email, update or note to the organiser.\n\n## If it stays\nAgenda: question, options, who decides, length.\n\n## Time saved","config":null}}