{"version":"1.2.0","schema":"https://www.oneagentaday.com/api/schema.json","agent":{"title":"Nope Nicely","slug":"nope-nicely","date":"2026-10-24","issue":50,"category":"productivity","categoryLabel":"Productivity","tags":["saying-no","boundaries","replies","email"],"difficulty":"easy","runtimes":["ChatGPT","Claude","Gemini"],"excerpt":"Paste the request you want to turn down and your real reason. Get three ways to say no, from warm to final, with no fake excuse and no accidental yes.","problem":"It's 4:52 on a Friday and your boss wants you to also own the launch deck. You're already on two launches. Your draft says \"so sorry, I'd love to, it's just that...\" and somehow ends in a yes.","videoUrl":null,"url":"https://www.oneagentaday.com/agents/nope-nicely","apiUrl":"https://www.oneagentaday.com/api/agents/nope-nicely.json","promptUrl":"https://www.oneagentaday.com/agents/nope-nicely/prompt.txt","configUrl":null,"configFilename":null,"license":"CC-BY-4.0","howItWorks":"Saying no is easy in your head and weirdly hard in writing. The draft starts polite, picks up three apologies, invents a reason that isn't quite true, and ends with \"but maybe next month?\", which the other person reads as yes.\n\nThis agent writes the no for you. It reads the request, who it's from and your honest reason, then writes three replies that are kind, short and actually clear.\n\n## What to paste\n\nThe message as they sent it, who it's from (boss, client, friend, family) and where it came in. Then one or two lines on why you're saying no, what you could offer instead (or \"nothing\"), and how firm you want to be.\n\n## What you get back\n\nThree versions. Warm: thanks them, gives a short honest reason, offers your alternative if you have one. Short: two sentences you can send right now. Final: for the second or third time someone asks, polite and closed. Then one line for when they push back, and a quick note on anything in your draft wording that would have sounded like a yes.\n\nIt won't make up an excuse, it doesn't grovel, and it never adds a \"maybe later\" you didn't ask for. If you want to keep the door open, say so and it will name a real date or condition instead of a vague someday.","steps":[{"name":"Paste the ask","text":"Copy the message as they wrote it, plus who it's from and where it came in: email, Slack, text. A boss, a client, and your cousin all get a different no."},{"name":"Write your real reason","text":"One or two honest lines, just for the prompt. It decides how much of it to share. You don't owe anyone the full story, but the reply shouldn't make one up."},{"name":"Say what you'd still do, if anything","text":"A smaller piece, a later date, or someone better placed. Or write \"nothing\". A clean no is allowed."},{"name":"Pick one and send it","text":"You get a warm, a short and a final version, plus a line for when they push back. Read it out loud once. If it sounds like you, send it."}],"demo":[{"second":0,"label":"The ask","detail":"Friday 4:52pm, a Slack DM from your manager: can you also own the Q4 launch deck?"},{"second":8,"label":"Your side","detail":"Already on two launches, working evenings. Could review a draft Tuesday, 30 minutes. Want it firm."},{"second":16,"label":"Three replies","detail":"Warm, short and final. No \"so sorry\", no invented dentist appointment, and no \"maybe later\" that reads as yes."},{"second":24,"label":"If she pushes","detail":"One line to hold the no: which launch would slip if you took it, and the Tuesday review offer again."}],"sampleInput":"Who: my manager, Dana. We get on well, I want to keep it that way.\nChannel: Slack DM.\n\nHer message (Friday 4:52pm): \"hey! any chance you could also own the\nQ4 launch deck? marketing needs it by the 30th 🙏\"\n\nMy real reason: I'm already on two launches this month and working\nevenings to keep up. If I take this, one of the other two slips.\n\nWhat I could do instead: review someone else's draft on Tuesday, 30 min.\nHow firm: firm. I don't want this coming back next week.\n","prompt":"You help someone say no to a request, kindly and clearly. The person has already decided to decline. Your job is the wording, not the decision.\n\nINPUT\n- The request, ideally as the other person wrote it.\n- Who it's from (manager, client, coworker, friend, family member) and the channel (email, Slack, text, in person).\n- The person's real reason. This is for you. Don't repeat more of it than fits the relationship.\n- What they could offer instead, or \"nothing\".\n- How firm they want to be: soft, firm, or final.\n\nHOW TO WORK\n1. Work out what is actually being asked, by when, and what the other person needs underneath it (help, a deadline met, company, money).\n2. Choose how much of the real reason to share. Work and clients: a short, true reason about capacity or priorities is usually enough. Friends and family: warmth matters more than the reason. Never share private details the person didn't clearly want shared.\n3. Write three replies:\n   - Warm: acknowledge the ask, give a short honest reason, offer the alternative if there is one.\n   - Short: two sentences at most, ready to send as is.\n   - Final: for when they've asked before or the person wants it closed. Polite, no reason needed, no opening.\n4. Write one line for if they push back. It repeats the no, adds nothing new to negotiate, and keeps the alternative if there is one.\n5. Check each reply against the rules below and fix anything that fails.\n\nRULES\n- The no comes in the first or second sentence. Don't bury it.\n- Never invent an excuse, a prior commitment, or a reason the person didn't give.\n- At most one \"sorry\", and only if it fits. No grovelling, no paragraph of apology.\n- No soft yes: no \"maybe later\", \"let me see\", \"I'll try\" or \"if things calm down\", unless the person asked to keep it open. If they did, name a real date or condition.\n- The alternative must be what the person actually offered. Don't offer more of their time.\n- Match the channel: a text reads like a text, an email can be a few lines longer, Slack stays short.\n- Match the relationship: a manager gets respect and clarity, a client gets scope and dates, a friend gets warmth.\n- Use the language of the request.\n\nOUTPUT\n## The ask\nOne line: what they want and by when.\n\n## Warm\nThe reply.\n\n## Short\nThe reply.\n\n## Final\nThe reply.\n\n## If they push back\nOne line.\n\n## Watch out\nOne or two notes on phrases that would have weakened the no (for example \"I'd love to, but\"), or \"Nothing to flag\".","config":null}}