{"generated": "2026-10-03", "count": 89, "read_first": ["00-how-to-use", "01-principles"],"entries":[
{"id":"00-how-to-use","title":"How to use SmoothTalker (read this first)","category":"core","tags":["meta","process","guide"],"triggers":["reply to this","help me respond","how do I say","rewrite this","make this sound better","soften this","draft a message","what should I text"],"summary":"The operating procedure for turning any message request into a smooth, effective reply. Read before using any other entry.","updated":"2026-09-24","body":"# How to use SmoothTalker\n\nSmoothTalker is a library of conversation playbooks. Your job is to make the user's message land well: the other person feels respected, the user gets what they need, and the relationship is left better than before. \"Smooth\" means clear, warm and low-friction. It never means slippery, vague or manipulative.\n\n## The five-step procedure\n\n**1. Read the situation before writing anything.** Extract from the user's request:\n- Who is the other person and what is the relationship (boss, client, friend, partner, stranger, family)?\n- What is the power dynamic (they hold leverage, the user does, or equal)?\n- What is the channel (text/DM, email, voice, in person)? Shorter and warmer for DM, more structured for email.\n- What does the user actually want to happen after the message is read? One concrete outcome.\n- What is the emotional temperature right now (neutral, tense, hurt, urgent)?\n\nIf a critical piece is missing and it changes the answer, ask one short question. Otherwise assume the most common reading and proceed.\n\n**2. Pick the closest playbook.** Match the situation to an entry using its `triggers` and `summary`. If two apply (for example \"decline a request\" and \"set a boundary with family\"), read both and blend. Always keep `01-principles` in mind.\n\n**3. Build the message from the playbook's structure, in order.** Every playbook gives a numbered skeleton. Follow it step by step; do not skip a step because it feels optional. If a step needs a specific the user has not given (a number to counter with, a date, a reason), either ask one short question first or leave a bracket with guidance inside it, like \"[your counter, e.g. $1,900; check comparable listings]\". Fill everything else with the user's specifics: real names, the real reason, the real alternative. Generic messages read as insincere.\n\n**Use the playbook's examples as the quality bar.** Your output should be at least as specific, as short and as concrete as the closest example in the entry. If your draft is vaguer than the example, rewrite it.\n\n**4. Calibrate tone.** Use `02-tone-calibration`. Match the other person's register. Default to slightly warmer than the user's draft and noticeably shorter.\n\n**5. Run the final checks.**\n- One clear ask or one clear point. Not three.\n- No stacked apologies, no stacked hedges (\"just\", \"sorry to bother\", \"if that's okay\", \"no worries if not\" all in one message is too much).\n- The other person has an easy way to say yes and a face-saving way to say no.\n- Nothing that reads as passive-aggressive when read in a bad mood. Read it as the recipient would on their worst day.\n- It sounds like a human the user could plausibly be, not a customer service template.\n\n## What to give the user\n\nDefault: offer **two versions**, one warmer and one more direct, each ready to send. Label them in three words or fewer. Add at most one line of reasoning if the choice matters. If the user asked for a single message, give one.\n\nFor sensitive situations (conflict, bad news, money, romance) add one line on **what to do if the reply is negative**, because the follow-up is where most people lose the exchange.\n\n**Always end with one line naming the playbook(s) you used**, for example \"Playbook: landlord-tenant-and-service-providers\". This lets the user see the library is working and ask for a different one.\n\n## Style rules for the message itself\n- No em-dashes. Use a comma, a full stop or \"and\".\n- No \"I'll have to say no\", \"unfortunately\", \"I'm afraid\". State the position: \"I can't agree to X\" or \"I'd like to propose Y\".\n- Every request ends with something the other person can say yes to: a number, a date, a specific option.\n- Reasons about your value or the facts (market, record, agreement) beat reasons about your needs (budget, feelings).\n\n## The user's explicit intent always wins\nPlaybooks are advisory. If the user has stated what they want (\"say no flat\", \"one version only\", \"keep it cold\"), do exactly that, and add at most one line noting what the playbook would suggest instead, so they can change their mind. Never override a stated instruction with a playbook rule.\n\n**Never concede what the user said they will not concede.** If they said \"I won't lower the price\" and offered other levers (scope, timing, payment terms), every version must hold the price and trade only the levers they named. Check each version against the user's stated constraints before returning it.\n\n**Scale the apology to the offence.** A forgotten birthday gets one sentence of ownership, not a paragraph of self-criticism. If a draft makes the other person want to comfort the user, cut it.\n\n## When not to smooth\n\nIf the user is being wronged, harassed, or pressured, do not make them softer. Use the boundary and de-escalation playbooks to make them clear and calm instead. Smoothness serves the user's interests, not the other side's comfort."},
{"id":"01-principles","title":"The principles behind every smooth message","category":"core","tags":["principles","foundation","psychology"],"triggers":["why does this sound bad","make it more diplomatic","tactful","graceful","how to be persuasive","sound confident"],"summary":"Nine principles that explain why some messages land and others cause friction. Apply these when no playbook fits exactly.","updated":"2026-09-24","body":"# The principles behind every smooth message\n\nThese are the mechanics. Every playbook is an application of them.\n\n**1. Acknowledge before you redirect.** People cannot hear your point until they feel their point was heard. One sentence that accurately reflects what they said or feel buys you the right to say something different. Accurate matters: \"I know this is frustrating\" only works if it actually is.\n\n**2. Name the constraint, not the person.** \"I can't do Friday\" creates no enemy. \"You always pick bad times\" creates one. Put the obstacle outside both of you: the calendar, the budget, the policy, the timeline.\n\n**3. Give them an out.** Every request should have a graceful no built in. \"If this week is packed, next week works too.\" A person who can decline without guilt says yes more often, and says no without resentment.\n\n**4. Ask, don't assert, when you are not sure.** \"Did you get a chance to look at this?\" beats \"You haven't responded.\" A question lets them supply a reason that keeps their dignity.\n\n**5. Be specific.** Vague warmth (\"let's catch up sometime!\") reads as a brush-off. Vague requests (\"can you help with the thing?\") create work for the other person. Specific words signal that you actually thought about them.\n\n**6. Face the future, not the past.** Once a problem is acknowledged, spend words on what happens next, not on how it happened. Blame analysis is for you, not for the message.\n\n**7. Match their register, then lift it one notch.** Mirror their length, formality and emoji habits, then be slightly warmer or slightly clearer than they were. Big register jumps feel like a mask.\n\n**8. Shorter is kinder.** A long message signals anxiety and forces the reader to work. Say the thing, give one reason if needed, stop. Three sentences is a good default for text. Five for email.\n\n**9. Leave the door open, but close the loop.** End with either a clear next step or a clean ending. Messages that trail off (\"anyway, let me know or whatever\") transfer the burden of closing to the other person.\n\n## Two things that are not principles but people think they are\n\n- **Flattery is not warmth.** Compliments that are not specific and true are noise. Specific appreciation for a real thing is warmth.\n- **Hedging is not politeness.** \"I was just wondering if maybe you might possibly\" is not polite, it is anxious. Politeness is clarity plus consideration."},
{"id":"02-tone-calibration","title":"Tone calibration by relationship and channel","category":"core","tags":["tone","register","formality","channel","email","text","dm"],"triggers":["too formal","too casual","make it sound more professional","make it friendlier","is this too cold","is this too much","email vs text"],"summary":"How to set warmth, formality and length for the relationship and channel, with register markers per app (WhatsApp, iMessage, Slack, LinkedIn, email, Instagram, WeChat, Xiaohongshu) and the same message at three settings.","updated":"2026-09-28","body":"# Tone calibration\n\nTone has three dials: **warmth**, **formality**, **length**. Set them from the relationship and the channel, then check against the other person's last message.\n\n## By channel\n\n| Channel | Length | Formality | Notes |\n|---|---|---|---|\n| Text / DM (iMessage, WhatsApp, Instagram) | 1 to 3 sentences | Low | Contractions, first names, one emoji at most if they use them. No \"Dear\". No sign-off. |\n| Email | 3 to 6 sentences | Medium | Greeting, one-line context, the point, the ask, sign-off. Subject line does half the work. |\n| Voice message or phone script | Conversational | Low to medium | Write it to be spoken. Short clauses. Pause markers. |\n| Formal letter or platform review response | Structured | High | Full sentences, no slang, no exclamation marks. |\n\n## Register markers by app\n\nEach app has its own normal. Match it, then apply the mirror rule below.\n\n| App | Length | Greeting and sign-off | Markers that read as normal | Markers that read as off |\n|---|---|---|---|---|\n| WhatsApp | 1 to 3 lines; split long points into two messages | None, or their name | Voice notes, one emoji, \"haha\" | Blue-tick guilt (\"I can see you read it\"), paragraphs |\n| iMessage / SMS | 1 to 2 lines | None | Lowercase, no full stop at the end, reactions instead of \"ok\" | A full stop after a one-word reply (\"Fine.\") reads cold |\n| Slack / Teams | One message, not five in a row | \"Hey [name],\" or none | Threads for follow-ups, the ask in the first line, emoji reactions as acknowledgement | \"Hi\" then waiting for a reply before the question; @here for non-urgent things |\n| LinkedIn DM | 3 to 5 sentences | \"Hi [name],\" and first name at the end | Why you, why now, one specific ask | A pitch in the first message, \"I hope this finds you well\" |\n| Email | 3 to 6 sentences, one ask | \"Hi [name],\" / \"Thanks,\" or \"Best,\" | A subject line that says the point (\"Invoice 1042, due Friday\") | \"Dear Sir/Madam\" to a named person; five paragraphs for one question |\n| Instagram / TikTok DM | 1 to 3 lines | None, or their handle's first name | Warm and quick, one emoji, a question to keep it going | Copy-pasted business email, long price lists in the first reply |\n| WeChat (微信) | 1 to 3 lines; voice for close contacts only | 称呼 by role or name (王总, 李老师, 亲) | \"好的\", \"收到\" as acknowledgement, a polite emoji or 表情 with elders and clients | A 60-second voice message to a client or senior; a bare \"嗯\" or \"哦\" to someone senior |\n| Xiaohongshu (小红书) DM or comment | 1 to 3 lines | \"亲\" or none | Friendly, emoji-rich, a question back | Hard selling or external links in the first reply |\n\n## By relationship\n\n| Relationship | Warmth | Formality | Default opener |\n|---|---|---|---|\n| Close friend or family | High | Low | Their name or nothing |\n| Partner | High, careful | Low | Nothing; go straight in |\n| Colleague, peer | Medium | Medium | \"Hey [name],\" |\n| Boss or senior | Medium | Medium high | \"Hi [name],\" |\n| Client or customer | Medium high | Medium | \"Hi [name],\" |\n| Stranger, cold outreach | Medium | Medium | \"Hi [name],\" with immediate context |\n| Someone who is angry at you | High, calm | Slightly higher than usual | Their name, then acknowledgement |\n\n## The mirror rule\n\nRead their last message. Copy their length within about 50 percent, copy their formality, copy their punctuation habits (do they use periods at the end of texts? exclamation marks? emoji?). Then move one notch warmer or clearer. Never jump two notches. A \"Hey!! 😊\" reply to a one-line period-ended text reads as fake.\n\n## The same message at three settings\n\nSituation: telling someone you can't make a meeting they proposed.\n\n**Close friend, text:**\n> Ah I can't do Thursday, I've got a thing till 7. Friday or the weekend?\n\n**Colleague, chat:**\n> Thursday doesn't work on my end, I'm double booked. Could we do Friday morning instead?\n\n**Client, email:**\n> Hi Dana,\n> Thanks for suggesting Thursday. I have a conflict at that time, but Friday morning or any time Monday is open on my side. Would either of those work for you?\n> Best,\n> Sam\n\nNotice: the reason gets shorter as the relationship gets closer, the alternative gets more specific as the stakes rise, and none of the three apologise.\n\n## Common miscalibrations\n\n- **Over-formal with peers**: \"Per our discussion\" to a teammate. Sounds like a threat.\n- **Over-casual with a client after a mistake**: \"oops my bad!\" Sounds like you do not care.\n- **Emoji to someone who never uses them**: reads as trying too hard.\n- **Long message to a short question**: reads as defensive.\n- **Warm sign-off after a firm boundary**: \"Hope you understand!! xx\" undercuts the boundary. Use a neutral close."},
{"id":"03-anti-patterns","title":"Anti-patterns that make messages sound slimy, weak or hostile","category":"core","tags":["mistakes","passive-aggressive","hedging","cliche","corporate"],"triggers":["does this sound passive aggressive","does this sound rude","sounds fake","too salesy","too apologetic","sounds robotic","cringe"],"summary":"The specific phrasings that undo smoothness, grouped by what they signal to the reader, with replacements.","updated":"2026-09-24","body":"# Anti-patterns\n\nSmoothness fails in three directions: too slippery, too weak, too sharp. Each has tell-tale phrases. Remove them and replace as shown.\n\n## Too slippery (reads as fake or salesy)\n\n| Remove | Why it fails | Replace with |\n|---|---|---|\n| \"I hope this email finds you well\" | Everyone knows it is filler | Delete, or one specific line (\"Hope the launch went smoothly\") |\n| \"I'd love to...\" when you would not | False enthusiasm is detectable | \"I can...\" or \"Happy to...\" |\n| \"Amazing! So excited!!\" | Inflated affect | One honest positive word |\n| \"Quick question\" before a long one | Minimising the ask | State the ask plainly |\n| \"No pressure at all!\" repeated | Over-signalling creates pressure | Say it once, or give a concrete out |\n| \"Let's circle back / touch base / synergy\" | Corporate noise | Plain verbs: \"let's talk Friday\" |\n| Compliment then immediate ask | Transparent setup | Ask first, or make the compliment specific and separate |\n\n## Too weak (reads as anxious or low status)\n\n| Remove | Why it fails | Replace with |\n|---|---|---|\n| \"Sorry to bother you\" | Pre-apologising for existing | \"Hi [name],\" then the point |\n| \"I was just wondering if maybe\" | Triple hedge | \"Could you...\" |\n| \"If that's okay?\" after every sentence | Asking permission to speak | Once at the end, or not at all |\n| \"No worries if not!!\" | Undercuts your own request | \"If this week is full, next week works\" |\n| \"I know you're busy but\" | Tells them they should say no | Delete |\n| Three exclamation marks | Nervous energy | Zero or one |\n| \"Sorry\" more than once per message | Dilutes the real apology | Apologise once, then act |\n| \"Does that make sense?\" | Invites them to say no | \"Let me know if you want more detail\" |\n\n## Too sharp (reads as passive-aggressive or hostile)\n\n| Remove | Why it fails | Replace with |\n|---|---|---|\n| \"Per my last email\" | Everyone reads this as \"you idiot\" | \"Resending the details below\" |\n| \"As I mentioned\" / \"As you know\" | Implies they forgot or are stupid | Just restate it |\n| \"Friendly reminder\" | Never friendly | \"Checking in on...\" |\n| \"I'll wait\" / \"Thanks in advance\" | Presumes compliance | \"Would you be able to... by Friday?\" |\n| \"With all due respect\" | Signals disrespect | Delete; say the disagreement plainly |\n| \"Just to clarify\" when correcting them | Condescending | \"I think we may be reading this differently\" |\n| \"Fine.\" / \"Okay.\" / \"K\" | Cold shutdown | Either say what is wrong or a full sentence |\n| \"It's not my job to\" | True but weaponised | \"That sits with [team]; I can point you to them\" |\n| Ending a text with a period when they never do | Reads as anger | Match their punctuation |\n| \"?\" alone or \"??\" | Impatience | \"Did you get a chance to see this?\" |\n\n## Structural anti-patterns\n\n- **Burying the ask** in paragraph four. Put it in the first two lines.\n- **The sandwich that is all bread**: so much cushioning that the point is lost. One sentence of cushion is enough.\n- **Explaining the whole history** before making the point. They were there.\n- **Ending on a question you already know the answer to.** \"Is that okay?\" when it has to be okay.\n- **Sending when angry.** If the user is heated, offer a version that waits, or a version that only says \"I want to think about this and reply properly tomorrow.\""},
{"id":"04-phrase-bank","title":"Phrase bank by function","category":"core","tags":["phrases","openers","softeners","bridges","closers","templates"],"triggers":["how do I start","what's a good opener","how to end the message","sign off","transition","way to say","better way to say this","sounds weak"],"summary":"Reusable phrases grouped by what they do in a message, with notes on when each fits, and a replace-this-with-that table for the 30 most common weak phrases. Use as raw material, never verbatim in bulk.","updated":"2026-09-28","body":"# Phrase bank\n\nPick one phrase per function at most. A message built entirely of phrase-bank lines sounds assembled. Adapt to the user's voice.\n\n## Openers that create context fast\n- \"Following up on [specific thing] from [when].\"\n- \"Quick one about [topic].\"  (only if it is actually quick)\n- \"I've been thinking about what you said about [X].\"\n- \"Two things: [A] and [B].\"  (for multi-point messages, tell them the count)\n- \"Before I forget:\"  (casual, low stakes)\n- \"I owe you a reply on [X], sorry for the wait.\"  (one apology, then content)\n\n## Acknowledgement (before redirecting or disagreeing)\n- \"That makes sense, and...\"  (not \"but\")\n- \"I can see why you'd read it that way.\"\n- \"You're right that [specific true thing].\"\n- \"I hadn't thought about [X], that's fair.\"\n- \"I know this isn't the answer you were hoping for.\"\n- \"I get that this is urgent on your side.\"\n\n## Softeners that keep the point intact\n- \"My honest read is...\"\n- \"I'd push back a little on...\"\n- \"Here's my hesitation:\"\n- \"Can I offer a different take?\"\n- \"I might be wrong on this, but...\"  (use once, only when actually uncertain)\n- \"Here's what I can do:\"  (after a no)\n\n## Making an ask\n- \"Could you [specific action] by [specific time]?\"\n- \"Would you be up for [X]?\"\n- \"What would it take to [X]?\"  (when they hold the leverage)\n- \"Is there a version of this that works for you?\"\n- \"I'd really value your read on [X].\"  (asking for input, not labour)\n- \"Can I get 15 minutes this week?\"  (name the cost)\n\n## Giving an out\n- \"If this week is packed, next week is fine.\"\n- \"Totally fine to say no.\"  (once)\n- \"If it's easier, I can [alternative].\"\n- \"No need to reply if you're good with it.\"\n- \"Whichever is easier for you.\"\n\n## Declining\n- \"I'm going to pass on this one.\"\n- \"I can't take this on right now.\"\n- \"That's not something I can do, but [alternative].\"\n- \"I'm at capacity through [date].\"\n- \"I'd rather be upfront than let you down later:\"\n- \"Not this time, but please keep me in mind.\"\n\n## Bridges to next steps\n- \"So the next step on my side is [X]; on yours, [Y].\"\n- \"I'll send [X] by [when] and we can go from there.\"\n- \"Let's lock a time: [two options]?\"\n- \"Leaving this with you; no rush.\"\n\n## Closers\n- Text: nothing, or \"talk soon\", or their emoji habit\n- Warm email: \"Thanks again,\" / \"Appreciate you,\" / \"Talk soon,\"\n- Neutral email: \"Best,\" / \"Thanks,\"\n- After a boundary or a no: \"Thanks for understanding,\" (neutral, not \"Hope that's okay!!\")\n- After bad news: \"I'm around if you want to talk it through.\"\n- After an apology: \"Thanks for your patience,\" (not another sorry)\n\n## Words that quietly improve a message\n- \"and\" instead of \"but\" after an acknowledgement\n- \"when\" instead of \"if\" for things that will happen (\"when you get a chance\")\n- \"I\" statements for feelings, \"we\" statements for plans, \"you\" statements only for appreciation\n- The person's name once, early\n- A specific date instead of \"soon\", \"later\", \"sometime\"\n\n## Replace this with that\nThe 30 weak phrases that most often sink a draft. Swap them on the final check.\n\n| Weak | Stronger | Why |\n|---|---|---|\n| Just checking in | Following up on [X]: could you [ask] by [date]? | Names the thing and the ask |\n| Sorry to bother you | Quick question about [X]: | Apologising for existing lowers the ask |\n| I was just wondering if maybe | Could you | One clear verb |\n| No worries if not! | Either way is fine, just let me know by [date] | Keeps the out, keeps the deadline |\n| I hope that makes sense | Tell me if anything's unclear | Invites questions without doubting yourself |\n| Does that make sense? | What do you think? | Asks for their view, not approval |\n| I'm sorry, but | I understand, and | \"But\" erases the first half |\n| Per my last email | As mentioned on [date], [restate the point] | Same fact, no edge |\n| As I said before | To recap: | Summarises without scolding |\n| To be honest | (delete) | Implies the rest was not |\n| Unfortunately, we can't | We can't do X; we can do Y | Leads with the alternative |\n| I'm afraid that | (delete, state it) | Hedge with no content |\n| I'll have to say no | I'm going to pass on this one | Owns the choice |\n| I'll try to | I will / I can't | Commit or decline |\n| ASAP | by [day, time] | A date gets met; ASAP gets argued |\n| Whenever you get a chance | by Thursday if you can | Soft and specific |\n| Let me know if you have any questions | Happy to walk you through it on a call | A real offer beats a reflex line |\n| Hope you're well! (in a complaint) | (start with the point) | Warmth that clashes with the content reads as sarcasm |\n| I just feel like | I think | Owns the view |\n| You always / you never | The last three times, [specific] | Facts invite a fix; absolutes invite a defence |\n| You need to | Could you | A request, not an order |\n| Calm down | I can hear this is frustrating | Names the feeling instead of dismissing it |\n| With all due respect | (delete, then disagree plainly) | Signals disrespect |\n| No offense, but | (delete) | Guarantees offence |\n| Thanks in advance | Thanks, [name] | Presumes the yes |\n| Let's circle back | Let's pick this up on [date] | A date, not a loop |\n| Going forward | From [date] | Specific start |\n| Sorry for the late reply!!! | Thanks for your patience | One line, no grovel, then the answer |\n| Feel free to reach out | Reply here or call me on [number] | Tells them how |\n| Hope this helps! | (delete, or name the next step) | Ends on the action |"},
{"id":"05-reply-to-a-pasted-message","title":"Replying to a message the user pastes in (point-by-point replies)","category":"core","tags":["reply","pasted message","point by point","email thread","multi-point","respond to this"],"triggers":["reply to this email","respond to this message","they wrote this","here's what they said","answer each point","reply to this thread","what do I say back to this"],"summary":"The procedure for answering a specific message the user shares: sort their points, own what is yours fully, correct what is wrong with facts once, and end with a clear next step.","updated":"2026-09-24","body":"# Replying to a pasted message\n\nUse this whenever the user gives you the other person's actual words. It sits on top of whichever situational playbook applies (angry customer, criticism, negotiation, boundary).\n\n## Procedure\n\n**1. Extract every point the other person made.** List them privately. People feel unheard when one of their three points is ignored, even if the other two are answered well.\n\n**2. Sort each point into one of three buckets** using the user's context:\n- **Ours**: the user is at fault. Own it fully, no \"but\", give the fix and a time.\n- **Theirs or shared**: the other person contributed (late assets, missed info). State the fact once, neutrally, with a date if possible. Then take responsibility for the part that is the user's (usually \"I should have flagged it\").\n- **Misunderstanding**: the point is factually wrong. Correct it once with evidence (where it was said, when), without tone. Never \"as I already told you\".\n\n**3. Open by reflecting the whole complaint accurately** in one or two sentences, in the other person's terms. This is what makes them keep reading.\n\n**4. Answer the points in the order they raised them**, each in two or three sentences. Label them if there are three or more (\"On the timeline:\", \"On the colours:\").\n\n**5. Close with where things stand and one concrete next step**, with dates. Then a single line of intent: \"I want to make this right.\" No second apology.\n\n**6. Check:** every point addressed; nothing conceded that the user said they will not concede; brackets for any date or fact the user did not give; the reader can act on it without asking a follow-up.\n\n## Register\nMatch the length and formality of the pasted message, then be slightly calmer than they were. If they were hostile, you are the adult in the room: warm, precise, unhurried.\n\n## Example shape (client email with three complaints)\n\n> Hi Dana,\n> You're right to be disappointed: the launch slipped, the homepage colours are wrong, and a cost you weren't expecting has come up. I'm sorry.\n> On the colours: my mistake, no excuse. Corrected homepage to you by [tomorrow 10am].\n> On the timeline: the brand assets arrived on [date], eight days after we needed them for a 10th launch. I should have flagged the knock-on then, and I didn't.\n> On the font licence: it's in the proposal from [date], section [X]. I should have called it out more clearly before now.\n> Where we are: colours fixed by [time], launch on [date]. I want to make this right.\n> [name]\n\n## Avoid\n- Answering the easiest point and skipping the hardest.\n- A wall of text; use short labelled paragraphs for three or more points.\n- Relitigating who said what. One fact, one date, move on.\n- Ending without a next step.\n- Two apologies."},
{"id":"06-situation-router","title":"Situation router (which playbook to open)","category":"core","tags":["meta","routing","index","decision-tree"],"triggers":["which playbook","I'm not sure what this is","help me with a message","I need to send something","what do I say here","not sure how to respond"],"summary":"A decision tree from the user's situation to the one or two playbook ids to open. Use when the triggers of the individual entries do not match cleanly.","updated":"2026-09-27","body":"# Situation router\n\nAnswer three questions, then open the entry named. When two branches apply, open both and blend. Entry ids are the file names without `.json`.\n\n## Question 1: Is the user replying to something, or starting?\n\n**Replying to a pasted message:** open `05-reply-to-a-pasted-message` first, then continue below with what the message is asking for.\n\n**Starting the conversation:** continue below.\n\n## Question 2: What is the user trying to do?\n\n### Say no\n- To an invitation, event, wedding, trip: `decline-invitation` (as the host saying no plus-ones, no kids, or cutting the list: `wedding-and-event-host-messages`)\n- To a favour, loan, request for time or help: `decline-request`\n- To a client asking for more work, a change, a rush: `say-no-to-client-scope`\n- To a customer asking for a refund, exception, custom order, feature: `say-no-to-a-customer-request` (refunds specifically: `handle-refund-request`)\n- To a job offer, or telling a candidate no: `decline-offer-or-candidate`\n- To a meeting, a \"quick call\", a recurring sync: `decline-meeting-or-protect-time`\n- To a boss's ask (stay late, take on more, an unrealistic deadline): `push-back-on-boss`\n- To a romantic advance or a second date, early dating: `romantic-let-down`\n- To an ex who wants to talk or get back together: `respond-to-an-ex-or-breakup-message`\n- To a relative's pressure (marriage, kids, money, career): `family-pressure-and-nosy-questions`\n- To a repeated intrusion on time, space, or feelings: `set-boundary`\n\n### Ask for something\n- Money owed to the user: `chase-late-payment` (between friends: `money-between-friends`)\n- A favour, a small ask: `ask-for-favor`\n- Help at work, or handing work to someone: `ask-colleague-for-help-or-delegate`\n- More time on a deadline: `ask-for-extension`\n- Time off, sick day, leave: `ask-for-time-off-or-sick-leave`\n- An introduction or referral: `request-intro-or-referral`\n- A reference, recommendation, testimonial from a person: `ask-for-reference-or-recommendation` (writing one for someone else: `write-a-recommendation-or-reference`)\n- A teacher or school to act on a concern, meet, or reconsider a decision: `messages-to-teachers-and-schools`\n- A review or testimonial from customers: `ask-for-review-or-testimonial`\n- A better price or a waived fee, as the buyer: `ask-for-a-discount-as-a-customer`\n- Higher pay or a higher price, as the seller or employee: `negotiate-price-or-salary` (a raise or promotion in your current job: `ask-for-a-raise-or-promotion`)\n- Someone to stop or change a behaviour: `ask-to-change-behavior` (a roommate, or chores, bills and guests in a shared home: `roommate-and-shared-living`; a neighbour, or escalating to the building or council: `neighbour-disputes`)\n- A decision from a group: `group-chat-coordination`\n- Someone to fix a problem they caused (landlord, contractor, shop): `landlord-tenant-and-service-providers` or `complain-as-customer`\n- A co-parent to agree a swap, a handover time or a shared cost: `co-parenting-and-ex-logistics`\n- A decision from someone senior, or a stuck problem unstuck: `escalate-an-issue`\n\n### Apologise or own something\n- Personal, including a reply that is days or weeks late: `apologize`\n- At work: `admit-mistake-at-work`\n- As a business, in public: `public-apology-from-a-business`\n- For being late, flaking, cancelling: `handle-no-show-or-lateness` (moving a plan in advance: `cancel-or-reschedule`)\n\n### Deliver news\n- Bad news to a person: `deliver-bad-news`\n- News to a team the user manages (someone leaving or joining, a reorg, layoffs, a missed target, a new policy): `team-announcements-as-a-manager`\n- Personal news, good or hard: `share-personal-news`\n- A price increase or policy change to customers: `price-increase-and-customer-announcements`\n- An order problem: `shipping-delay-or-out-of-stock`\n- Resigning or leaving a group: `leave-or-quit-gracefully`\n- Moving out of a rental, ending a lease early, or a landlord not renewing: `give-notice-to-a-landlord-or-tenant`\n- Availability while away: `out-of-office-and-away-messages`\n\n### Respond to heat\n- Angry customer: `respond-to-angry-customer`; public negative review: `respond-to-negative-review`\n- Criticism aimed at the user: `respond-to-criticism`\n- Passive-aggressive tone: `respond-to-passive-aggressive`\n- An argument in progress: `de-escalate-argument` (two other people fighting, with the user in the middle: `mediating-between-two-people`)\n- Unsolicited advice or opinions (on parenting, work, plans): `respond-to-unsolicited-advice`; relatives quizzing you about life milestones: `family-pressure-and-nosy-questions`\n- A disagreement the user wants to voice: `disagree-without-conflict`\n- A message that might be a scam or a hacked account: `suspicious-or-scam-message`\n\n### Connect or warm up\n- First message to a stranger (dating, someone you admire, a community): `first-message-to-stranger`; a business pitch (sales, partnership, press): `cold-outreach`; an intro through someone you know: `request-intro-or-referral`\n- Introducing yourself: `introduce-yourself`\n- Small talk, keeping a chat alive: `small-talk`\n- Someone the user has not spoken to in a long time: `reconnect-after-silence`\n- Dating, from asking out to the text after date one: `ask-someone-out-and-early-dating`\n- Thanks, praise, receiving praise, or a compliment that is really a hit-on: `give-and-receive-compliments` (a thank-you note or card for a gift, host, mentor or favour: `thank-you-notes`)\n- A recruiter wrote: `respond-to-recruiter`; after a rejection: `respond-to-job-rejection`\n\n### Support someone\n- A death: `condolences-and-support`\n- Someone just told the user about a diagnosis or health scare: `respond-to-difficult-health-news`\n- A hard time that is not a death: `check-in-on-someone-struggling`\n\n### Follow up\n- No reply yet: `follow-up-unanswered`; a client who went silent: `handle-being-ghosted-by-client`\n- After an interview or meeting: `follow-up-after-interview-or-meeting`\n\n### Give feedback\n- To a colleague or report: `give-feedback-to-colleague`\n- To a friend, partner, family: `give-feedback-kindly`\n- Something embarrassing they have not noticed (food in teeth, body odour, a typo in their post): `tell-someone-something-awkward`\n\n### Sell or serve\n- A DM asking about a product: `reply-to-customer-inquiry-dm`; adding to an order without pushing: `upsell-without-pushiness`\n- The first message after someone buys, books or signs up: `customer-onboarding-and-welcome`\n- A brand reaching out to a creator: `creator-brand-deal-reply`\n\n### End something\n- A relationship: `respond-to-an-ex-or-breakup-message` (only a few dates in: `romantic-let-down`)\n- A conversation that will not end: `end-conversation-gracefully`\n\n## Question 3: What is the temperature?\n\nIf the user is angry, hurt, or writing at night, first offer the one-line pause from `respond-to-criticism` (\"I don't want to answer this while I'm upset, I'll reply tomorrow\") and then the drafts. If the other person is in a different culture or language, also open `mixed-language-and-cultural-notes`. If nothing above fits, build the message from `01-principles` and say which principles you used."},
{"id":"admit-mistake-at-work","title":"Admitting a mistake at work","category":"work","tags":["mistake","error","own it","boss","client","accountability"],"triggers":["I made a mistake at work","tell my boss I messed up","own up to an error","I broke something","missed a deadline","sent the wrong thing"],"summary":"How to report your own mistake so you come out of it looking reliable: fast, factual, with impact, fix and prevention already in hand.","updated":"2026-09-24","body":"# Admitting a mistake at work\n\n## Goal\nYour manager or client learns it from you first, with the fix already in motion, and concludes you are someone who handles problems, not someone who causes them.\n\n## Structure\n1. **Headline the mistake in the first sentence.** No preamble.\n2. **Impact, factual.** What it affected, who, how much.\n3. **What you've already done.**\n4. **What you're doing next, with a time.**\n5. **Prevention**, one concrete change.\n6. **Stop.** No grovelling, no self-flagellation.\n\n## Principles\n- Speed is everything. A mistake reported in an hour is a blip; the same mistake discovered by someone else a week later is a trust problem.\n- One clean apology. Then all forward.\n- No \"but\". Context can come after ownership, in one clause, framed as information.\n- Do not blame tools, colleagues, or workload in the first message.\n- Bring a fix, even a partial one. \"I don't know how to fix this yet, but here's what I'm checking first\" counts.\n- Scale the channel: small mistake, chat message; big mistake, call then written summary.\n\n## Examples\n\n**Sent the wrong file to a client, message to boss:**\n> Heads up: I sent the client the internal pricing sheet instead of the customer version at 10:40. I've already emailed them asking to disregard it and sent the correct one, and called Dana to explain. No response yet. I'm sorry; this was a naming mix-up on my end. I've renamed the internal file with an INTERNAL prefix so it can't happen again. I'll let you know as soon as Dana replies.\n\n**Broke something in production:**\n> I pushed a change at 14:05 that broke checkout for about 12 minutes. It's rolled back and checkout is working; I'm pulling the numbers on affected orders now and will have them by 15:00. Root cause was a missing null check that the tests didn't cover. I'm adding that test today. Sorry, this one's mine.\n\n**Missed a deadline, to a client:**\n> Hi Mark,\n> I owe you the report today and I'm not going to hit that. I'm sorry. It will be with you by 10am tomorrow. The delay is on my side, not a problem with the data. I should have flagged it yesterday when I saw it slipping, and I'll do that in future.\n> Jess\n\n**Made an error that cost money:**\n> I need to flag a mistake. I booked the venue for the 18th instead of the 8th and the deposit of $2,000 is non-refundable. I've called them and they're checking if they can move it; I'll know by end of day. If not, I'll cover the difference for an alternative venue and I'm working on options now. I'm sorry; I misread the date and didn't double-check it.\n\n**Small mistake, keep it small:**\n> My mistake on the numbers in that email, corrected version below.\n\n## Avoid\n- \"I just wanted to let you know that there may have been a small issue...\"\n- \"In my defence...\"\n- \"It wasn't entirely my fault.\"\n- Apologising in every message afterward.\n- Waiting until you have a full fix before saying anything.\n- Hiding it and hoping.\n\n## If your boss reacts badly\n> That's fair. I'd feel the same. I'll keep you updated every step until it's resolved.\nThen do exactly that."},
{"id":"apologize","title":"Apologising properly","category":"personal","tags":["apology","sorry","mistake","hurt","late","missed"],"triggers":["how to apologize","I messed up","I was late","I forgot","I hurt them","say sorry","make it up to","sorry for the late reply","took me weeks to reply"],"summary":"The four-part apology that actually repairs things, with examples from minor lateness and slow replies to real hurt, by text or voice, and what never to include.","updated":"2026-09-28","body":"# Apologising\n\n## Goal\nThe other person feels that you understand what you did, that you own it, and that it is less likely to happen again. Forgiveness is their choice, not the message's goal.\n\n## Structure (all four, in order)\n1. **Name the specific thing.** \"I'm sorry I missed your call and didn't text back until today.\" Not \"sorry about earlier.\"\n2. **Own it without a \"but\".** No \"but I was busy\". If there is context they need, it goes after ownership, in one clause, framed as explanation not excuse.\n3. **Acknowledge the impact on them.** \"That left you waiting and probably wondering if I'd flaked.\"\n4. **What changes.** A concrete fix, or a concrete future behaviour. Or simply \"It won't happen again\" if that is true.\n\nOptional: **one make-good** if proportionate.\n\n## Principles\n- Scale the apology to the offence. Over-apologising for small things makes the other person manage your guilt.\n- \"I'm sorry you feel that way\" is not an apology. \"I'm sorry if\" is not an apology.\n- Do not ask for forgiveness in the same message. It turns the apology into a request.\n- Say it once. Repetition makes it about your discomfort.\n\n## Examples\n\n**Late to meet a friend, text:**\n> Sorry I kept you waiting 25 minutes, I should have texted the moment I knew I was running behind. Drinks are on me tonight.\n\n**Forgot something important:**\n> I completely dropped the ball on your birthday and I'm sorry. No excuse, I just didn't put it in my calendar and it slipped. That's not the kind of friend I want to be. Can I take you out this weekend, properly?\n\n**Hurt someone with what you said:**\n> I've been thinking about what I said on Sunday about your job. It was unfair and it came out as contempt, which isn't what I feel. I can see it stung. I'm sorry. I'd like to hear how it landed for you, when you're up for it.\n\n**Missed a deadline, work:**\n> I missed the Friday deadline on the report and I'm sorry, that put you in a bad spot with the client. It's done now and attached. Going forward I'll flag on Wednesday if anything is at risk so you're never surprised.\n\n**Small thing, keep it small:**\n> Oops, my bad, sending now.\n\n**Replying days or weeks late (one line of ownership, then the answer):**\n> Sorry for going quiet, this one got buried. Yes to Saturday, and I'll bring dessert.\n> Apologies for the slow reply, Mark. The answer is yes: we can start on the 14th, and I've attached the revised quote.\n\n**Voice note or call, for real hurt (spoken, short clauses):**\n> Hey, it's me. I've been thinking about Sunday. What I said about your job was unfair, and I'm sorry. You don't need to call back. I just didn't want it sitting there.\n\n## Avoid\n- \"I'm sorry, but...\"\n- \"I'm sorry you feel...\"\n- \"Mistakes were made.\"\n- Explaining at length. The longer the explanation, the more it reads as self-defence.\n- Asking \"are we okay?\" in the same message. Give them room.\n\n## If they are still upset\n> That's fair. I'm not going to argue with how you feel about it. I'm here when you're ready.\nThen actually leave space."},
{"id":"ask-colleague-for-help-or-delegate","title":"Asking a colleague for help, delegating, and saying \"I don't know\"","category":"work","tags":["ask for help","delegate","colleague","teammate","don't know","handoff","workload"],"triggers":["ask a coworker for help","delegate a task","hand this off","admit I don't know","ask my team to do","need help at work","ask for support from a colleague"],"summary":"Clear, respectful asks between colleagues: getting help without looking helpless, delegating without sounding like a boss, and admitting you don't know without losing standing.","updated":"2026-09-27","body":"# Asking a colleague for help, delegating, saying \"I don't know\"\n\n## Goal\nYou get the help, the handoff, or the honest answer you need, and you come out of it looking more capable, not less. The colleague finds it easy to say yes and easy to say \"not right now\".\n\n## Asking a peer for help\n\n**Structure:** what you've tried → the specific thing you need → the size of the ask → an out.\n\n> Hey Lee, I've been stuck on the export bug for an hour and I've checked the obvious things (config, permissions). Could you look at it with me for 15 minutes today? If you're heads-down, tomorrow's fine.\n\n> Could I borrow your eyes on this deck before it goes to Sara? Mainly slides 4 to 7, where I'm not sure the story lands. Ten minutes max.\n\n**Principles**\n- Show your work first. \"I've tried X and Y\" turns \"help me\" into \"help me finish\".\n- Name the time cost. People say yes to 15 minutes and dodge \"a quick chat\".\n- Give a deadline and an out.\n- Say thanks afterwards, specifically, and ideally where their manager can see it.\n\n## Delegating (to a peer, a junior, or across teams)\n\n**Structure:** the outcome → why them → what \"done\" looks like → deadline → what support you'll give → check they can take it.\n\n> Priya, I'd like you to own the onboarding email sequence for the launch. You've done the best work on the welcome flows, so it's a natural fit. Done means: five emails drafted and reviewed by marketing by the 20th. I'll do a first pass on your drafts whenever you want, and I'll clear it with Dan so it's on your plate officially. Can you take it on, given what you've got already?\n\n**Peer, no authority:**\n> Could you take the vendor calls this week? I'm on the audit until Thursday and you've got the relationship there. I'll pick up your Friday standup in return.\n\n**Cross-team:**\n> Hi Marcus, we need the API docs updated for the release and I think your team's the right owner since you built the endpoints. Target is the 15th. Is that doable, or should we talk about what would make it possible?\n\n**Principles**\n- Describe the outcome, not the steps. People own outcomes; they resent step lists.\n- Say why them. It's not flattery, it's context.\n- Ask, and mean it. If they say they can't, negotiate scope or date.\n- Delegating and then micromanaging is worse than not delegating.\n- Take responsibility upward. If it fails, that's yours.\n\n## Saying \"I don't know\"\n\n**The formula:** I don't know + what I'll do about it + when.\n\n> I don't know off the top of my head. Let me check and I'll have an answer by 3.\n> Good question, I'm not sure. My guess is X but I don't want to give you a guess on this. I'll confirm today.\n> That's outside what I've worked on. Lee has; want me to loop them in?\n> I don't know, and I'd rather say that than make something up. What's the decision this feeds into? That'll help me get you the right thing.\n\n**Principles**\n- \"I don't know\" said fast and cleanly raises your credibility. Bluffing lowers it, later.\n- Always attach the next step.\n- In meetings, \"I'll find out\" beats a wrong answer every time.\n\n## Avoid\n- \"Sorry to bother you, I know you're busy, but...\"\n- Asking for help without saying what you've tried.\n- Delegating by dumping (\"can you just handle this?\").\n- Delegating in a group message so nobody owns it.\n- \"I think it's probably...\" when you don't know.\n- Apologising for not knowing.\n\n## If they say no or don't reply\nA no from a colleague is information, not rejection. If they are too busy, ask who else knows the area, or ask for five minutes instead of fifteen. If a delegated task gets pushed back, negotiate scope or date. If nobody replies, ask one named person directly instead of re-posting to the group.\n> No problem, I know you're under it. Is there anyone else who knows the export code, or a doc you could point me at?\n> Understood, the 15th isn't workable. What could you do by then if we trimmed it to the two main endpoints?\nIf it is still no, flag the constraint to your manager early."},
{"id":"ask-for-a-discount-as-a-customer","title":"Asking a vendor for a discount, price match or fee waiver","category":"personal","tags":["discount","price match","fee waiver","buyer","vendor","negotiation","perk"],"triggers":["ask for a better price","ask for a discount","price match request","can you waive the fee","ask the dealer for a lower price","ask the wedding vendor for a discount","ask for a loyalty discount","get a hotel upgrade","ask a SaaS company for a discount"],"summary":"How to ask any seller for a lower price or a perk: anchor on a real fact, name a specific number, make yes easy, and stay gracious if the answer is no.","updated":"2026-09-28","body":"# Asking a vendor for a discount, price match or fee waiver\n\n## Goal\nYou get a lower price, a waived fee or a perk, and the seller feels they did a reasonable thing for a reasonable person. If they say no, you have lost nothing and they still like you.\n\n## Structure\n1. **Signal you want to buy.** \"I'm ready to book.\" Sellers discount buyers, not browsers.\n2. **One anchoring fact.** A competitor's real quote, your volume, your history with them, paying upfront, flexible timing, an off-peak date, a fee you did not expect.\n3. **The specific ask.** A number, a percentage, a named perk, or \"match this quote\". Not \"can you do anything on price?\"\n4. **Make yes easy.** Say what happens the moment they agree: \"I'll pay the deposit today.\"\n5. **A face-saving out.** \"If that's not possible, I understand.\"\n\n## Principles\n- Facts beat feelings. \"Your competitor quoted $1,400\" works. \"Money's tight\" makes them uncomfortable and rarely moves the number.\n- Never invent a competitor quote. It is dishonest, and sellers know their market well enough to catch it. No quote? Get one, or use another lever.\n- Ask for a specific number, slightly ambitious, so they can meet you partway and feel they won.\n- If price is fixed, ask for perks: delivery, a longer warranty, an upgrade, an extra month, waived setup.\n- Ask the person who can say yes: a manager, owner or retention team.\n- Timing: end of month for dealers, off-season for wedding vendors, the renewal window for SaaS.\n- Keep it brief and pleasant; it is a normal ask.\n\n## Examples\n\n**Local shop, in person or DM:**\n> I'd like to take the two chairs and the side table together. Is there any room on price if I take all three today? I was thinking $520 for the set.\n\n**Competitor quote, email to a vendor:**\n> Hi Rachel, I'd like to go with you for the kitchen fitting. One thing: [other firm] quoted $6,800 for the same scope, and yours is $7,400. If you can meet them at $6,800, or get close, I'll sign and pay the deposit this week. If not, tell me what's different about yours.\n> Ben\n\n**Car dealer, email before visiting:**\n> Hi Marcus, I'm buying a [model] this month and yours is one of two I'm considering. Your listed price is $24,900. I can pay in full on Friday if you can do $23,500 out the door, including fees. If that works, I'll come in Friday morning to finish the paperwork.\n\n**Wedding vendor:**\n> Hi Ivy, we love your work and want to book you for 14 February. Our photography budget is $2,800 and your package is $3,200. Two things that might help: it's a Thursday, and we only need six hours rather than eight. Would $2,800 for six hours work? If yes, I'll send the deposit today.\n\n**SaaS renewal:**\n> Hi, our renewal is coming up at $4,200 for 12 seats. We've been on the plan three years and we're staying. Is there a loyalty or annual-prepay rate? I'd be looking for around $3,600, or the same price with four extra seats. I can sign this week if so.\n\n**Hotel, the day before arrival:**\n> We're arriving tomorrow for four nights and it's our anniversary. If any upgraded rooms are free, we'd be grateful for one. No problem at all if not.\n\n**Fee waiver, bank or utility:**\n> Hi, I've been charged a $35 late fee. I've had this card six years and this is the first late payment; it was a bank holiday and it cleared the next morning. Could you waive it this once? I've set up autopay so it won't happen again.\n\n**Landlord's agent, before renewing:**\n> Hi Dana, I'd like to renew for another year. The proposed rent is $1,950. Comparable two-beds in the building are listed at $1,850 on [site] right now, and I've paid on time for three years with no repair callouts. Would you renew at $1,850? I can sign this week if so.\n\n**Price match, retail:**\n> I'd like to buy this from you rather than online. [Retailer] has it at $189 today, here's the link. Can you match that? If yes I'll take it now.\n\n## Avoid\n- Inventing a competitor quote or a budget you do not have.\n- \"Can you do anything on price?\" with no number.\n- Threatening a bad review to get a discount.\n- Asking twice after a clear no.\n- Insulting the product to justify the ask.\n\n## If they say no\nThank them and either buy at their price or walk, no drama. \"Understood, thanks for checking. I'll go ahead at $7,400 then, could you send the deposit details?\" If they say no to price, try one perk before you close: \"If the price is firm, could you include delivery?\" If the gap is too large, walk and leave the door open: \"That's beyond me right now, but I appreciate your time. If anything changes on your side, I'd still like to work with you.\""},
{"id":"ask-for-a-raise-or-promotion","title":"Asking for a raise or promotion (in your current job)","category":"work","tags":["raise","promotion","pay rise","career","manager","performance review"],"triggers":["ask for a raise","how do I ask my boss for more money","ask for a promotion","I deserve a raise","email my manager about a pay rise","underpaid compared to my coworkers","follow up after asking for a raise","they said no to my raise"],"summary":"How to ask your current employer for more pay or a bigger role: pick the timing, book the meeting, bring evidence and one number, and follow up in writing whatever the answer.","updated":"2026-09-28","body":"# Asking for a raise or promotion\n\n## Goal\nYour manager leaves with a specific number or title, the evidence to defend it upstairs, and a date for an answer. You are writing their case for them.\n\nFor negotiating a new job offer, use `negotiate-price-or-salary`.\n\n## Structure\n1. **Book the conversation separately.** A short message asking for 20 to 30 minutes about your role and pay. Never ambush a one-to-one or a corridor chat.\n2. **Open with commitment.** One line that you like the work and want to grow here.\n3. **Evidence, three items maximum.** Outcomes with numbers or scope: what changed because of you, and what you now own beyond your job description.\n4. **The ask, as a specific number or title.** Anchored in the role and the market, not your personal costs.\n5. **Invite the path.** \"If that's not possible now, what would it take and by when?\"\n6. **Follow up in writing** the same day, with what was agreed and the date for an answer. \"I'll get back to you\" is fine; \"by when?\" is the follow-up.\n\n## Principles\n- Timing matters more than wording. Best moments: after a clear win, before budget planning, at review season, or when your role has already grown. Worst: the week of a layoff or a bad quarter.\n- Ask for a number, not \"a bit more\". A specific figure (or a salary band level) gives your manager something to take upstairs.\n- Market data and scope beat need. \"The role now includes managing two people\" works; \"rent went up\" does not, even when it is true.\n- A promotion is a title plus scope plus pay. Ask which of the three is on the table, and do not accept the title alone without talking about the other two.\n- Never bluff about an outside offer. If you have a real one, you may mention it once, calmly, and only if you would take it.\n\n## Examples\n\n**Booking the meeting (Slack or email):**\n> Hi Priya, could we find 30 minutes in the next couple of weeks to talk about my role and compensation? No rush on your side, I just want to give it proper time rather than squeeze it into our 1:1.\n\n**The opening and ask, in the meeting:**\n> I really like the work here and I want to keep growing in this team. Over the last year I've taken on the vendor contracts, cut onboarding time from three weeks to one, and I'm now training both new hires. Based on that and what similar roles pay, I'd like to move to £58,000. What would you need from me to make that case?\n\n**Asking for a promotion:**\n> I've been doing most of the senior-analyst scope since March: owning the quarterly model and reviewing the juniors' work. I'd like to be considered for the senior title in this cycle. Can we map out what's left to get there?\n\n**Pay gap with peers, factual:**\n> I've done some research and my salary looks below the band for this level, based on [source]. I'd like to understand how my pay was set and whether we can bring it in line.\n\n**Follow-up email after the meeting:**\n> Thanks for making time today. To confirm: you'll take the move to £58,000 to Marco and come back to me by 15 May. I'll send over the onboarding numbers by Friday in case they help.\n\n**After a \"not right now\":**\n> Understood, thanks for being straight with me. Can we agree the two or three things you'd want to see, and revisit in the September review? I'll put a note in both our calendars.\n\n**When budget is truly frozen:**\n> If salary is fixed this year, could we look at a title change, extra leave or a training budget in the meantime, and put the raise first in line for January?\n\n## Avoid\n- Comparing yourself to a named colleague (\"but Tom earns more\").\n- Personal-need reasons as the main argument.\n- Ultimatums you do not mean.\n- Apologising for asking, or opening with \"I know it's a bad time, but...\".\n- Asking by email only. Book the conversation, then confirm it in writing.\n\n## If it goes badly\nA no is information, not a verdict. Stay calm, ask what would change the answer, and get the criteria and a review date in writing. If you get a flat no with no path, or the path moves every time you reach it, that tells you the ceiling here: start looking quietly, and do not threaten to leave before you have somewhere to go. If the conversation turns tense, end it kindly and follow up in writing the next day.\n> Thanks for being honest. So I'm clear: what would need to be true for this to be a yes, and when can we look at it again?\n> I appreciate you raising it with Marco. Since the criteria have shifted since March, could we write down what's needed now so we're both working to the same list?"},
{"id":"ask-for-extension","title":"Asking for a deadline extension","category":"work","tags":["extension","deadline","more time","delay","late"],"triggers":["ask for more time","extend the deadline","won't make the deadline","need an extension","push the due date"],"summary":"How to ask for more time early, with a specific new date and a reason that is about quality or scope rather than excuses.","updated":"2026-09-27","body":"# Asking for a deadline extension\n\n## Goal\nThey grant it, and think better of you for asking early with a plan rather than missing it silently.\n\n## Structure\n1. **Ask early.** The moment you know. Not the day before.\n2. **The situation in one line.** Not a story.\n3. **The specific new date.** Not \"a bit more time\".\n4. **What they get for it**, if there is a quality argument.\n5. **An alternative** if the date is hard: partial delivery, reduced scope.\n6. **Ask, not tell**, unless it is a done deal.\n\n## Principles\n- Extensions asked for early are planning; extensions asked for late are failures.\n- Specific dates only. \"By Thursday 5pm\" not \"early next week\".\n- Offer a trade: partial now, complete later. Most deadlines are about something downstream; find out what.\n- One extension. If you need a second, you have a bigger conversation to have.\n- Do not over-explain. One sentence of reason.\n\n## Examples\n\n**Boss, chat:**\n> The Q3 analysis: I can have it Friday as planned but the supplier data only came in this morning, so it'd be thin. If I can have until Tuesday, it'll be the full picture. If Friday is a hard date for the board pack, I'll send a summary Friday and the full version Tuesday. Which do you prefer?\n\n**Client, email:**\n> Hi Rob,\n> I want to give you a heads-up early rather than late. The design round is taking longer than I scoped because the brand guidelines came in a week after we planned. I'd like to move delivery from the 12th to the 16th. If the 12th is tied to something on your side, tell me and I'll prioritise the homepage so you have that on time.\n> Thanks,\n> Ava\n\n**Academic / formal:**\n> Dear Professor Lin,\n> I'm writing to ask for a three-day extension on the essay due on the 20th, to the 23rd. I've had [brief reason] this week and I'd rather submit work I'm confident in than something rushed. I understand if this isn't possible.\n> Kind regards,\n> Sam\n\n**Personal favour deadline (returning something, finishing something for a friend):**\n> I said I'd have the photos to you by Sunday and I'm going to need until Wednesday; I want to do the edits properly. Is that okay or do you need them for something sooner?\n\n**When you're already late (see also admit-mistake-at-work):**\n> I've missed today's date and I'm sorry. It'll be with you by tomorrow noon. I should have flagged this yesterday.\n\n## Avoid\n- \"Is there any chance, if it's not too much trouble, I could maybe have a little more time?\"\n- A paragraph of reasons.\n- Asking the night before.\n- \"I'll try to have it by...\"\n- Asking for a vague amount of time.\n\n## If they say no\nTake it cleanly, do not re-argue, and switch to the trade. Ask what they need most by the original date, deliver that, and say exactly when the rest lands. If they go quiet, assume the original date stands and ship what you have with a note.\n> Understood, Friday stands. I'll send the summary and the first two sections by 5pm Friday and the full version Tuesday morning, unless you'd rather I hold everything for Friday and cut scope.\nIf they are annoyed you asked at all, one line and move on:\n> Fair, I should have caught this earlier. Friday it is."},
{"id":"ask-for-favor","title":"Asking for a favour so it is easy to say yes","category":"personal","tags":["ask","favour","request","help","imposition"],"triggers":["ask a favor","need help with","can I ask you","how to ask someone to","need a ride","ask for a hand"],"summary":"How to ask for help without sounding needy or entitled: make the ask specific, name the cost, and give a real out.","updated":"2026-09-27","body":"# Asking for a favour\n\n## Goal\nThey should be able to say yes in one word, or no without guilt, and either way feel respected.\n\n## Structure\n1. **Context in one line** (why you're asking them specifically, if there is a reason).\n2. **The ask, specific**: what, when, how long, what it involves.\n3. **Name the cost honestly**: \"it's about an hour\", \"you'd need a car\".\n4. **A real out.**\n5. **What you'll do in return, if natural.** Do not manufacture reciprocity.\n\n## Principles\n- Vague asks (\"could you help me with something?\") force them to say yes before they know what it is. That feels like a trap.\n- Pre-apologising (\"sorry to ask\") frames the request as an imposition. A clear ask with an out is not an imposition.\n- People like being asked for things they are good at. If that is why you are asking them, say so.\n\n## Examples\n\n**Ride to the airport, text:**\n> Any chance you could drop me at the airport Thursday around 6am? I know it's early. If it's a pain, I'll grab a cab, no problem at all. Coffee's on me either way.\n\n**Ask someone to read your work:**\n> You're the best editor I know, so I'm going to be cheeky: would you have 20 minutes this week to read a two-page draft? Honest notes only. If you're underwater, tell me and I'll ask someone else.\n\n**Ask to borrow something:**\n> Could I borrow your projector for Saturday night? I'd pick it up Friday and bring it back Sunday. If you need it that weekend, no stress.\n\n**Bigger ask, email:**\n> Hi Priya,\n> I'm applying for the residency in March and they want a reference from someone who's seen my work up close. You'd be my first choice, but I know it's a real chunk of time, probably an hour to write. The deadline is the 20th. If that's not doable, I completely understand and I'd appreciate a heads-up so I can ask elsewhere.\n> Thanks either way,\n> Leo\n\n## Avoid\n- \"I hate to ask but\"\n- Hiding the size of the ask.\n- Following up within 24 hours unless it's time-sensitive.\n- \"You owe me one\" energy.\n\n## Follow-up if no reply\nAfter 3 to 5 days: \"No worries if the airport thing doesn't work, just let me know by Tuesday so I can sort a cab.\"\n\n## If they say no or go quiet\nA no is the outcome you built the out for, so treat it that way. Thank them in one line, do not ask why, and do not ask a second time in a different shape. Silence after your one follow-up means no; sort your backup plan and drop it.\n> No worries at all, thanks for letting me know. I'll sort a cab.\n> All good, I'll ask around. See you Saturday.\nIf they say yes and then pull out late, absorb it without a guilt trip. \"Ah okay, no problem, I'll figure it out\" keeps the door open for the next favour, in either direction."},
{"id":"ask-for-reference-or-recommendation","title":"Asking for a reference or recommendation","category":"work","tags":["reference","recommendation","linkedin recommendation","former manager","professor","testimonial","case study"],"triggers":["ask for a reference","ask my old boss to be a reference","linkedin recommendation request","ask a professor for a recommendation letter","ask a client for a testimonial","case study quote","reference after years","they said no to being a reference"],"summary":"Asking a former manager, professor or client to vouch for you, making it a ten-minute job for them, and handling a long gap, a hesitation, or a no. Writing one for someone else: write-a-recommendation-or-reference.","updated":"2026-09-28","body":"# Asking for a reference or recommendation\n\n## Goal\nThey say yes in one reply, know exactly what to say and by when, and feel good about being asked. The request is a ten-minute job for them, not a homework assignment.\n\n## Structure\n1. **Context in one line.** What you are applying for, or why you need it.\n2. **The specific ask.** A phone reference, a written letter, a LinkedIn recommendation, a quote. Name it.\n3. **Make it easy.** Three bullet points of what you would love them to mention, the deadline, and an offer of a draft they can edit.\n4. **The exit.** \"If the timing doesn't work, no problem at all.\" Mean it.\n5. **After they agree:** send the details in one place. Who will contact them, when, the job title, the bullets.\n\n## Principles\n- A reference request is a favour with a deadline. State the deadline in the first message, not after they agree.\n- Bullets beat memory. They remember you were good; they do not remember the number you moved. Give them the number.\n- Offer a draft for written recommendations. Most people accept and lightly edit it.\n- Ask before you list them. Being called out of the blue about someone you have not spoken to in three years is a bad experience.\n- After a long gap, lead with the reconnection and a reminder of what you worked on together. Do not pretend no time has passed.\n- Do not stack asks. One reference, one deadline, one message.\n\n## Examples\n\n**Former manager, phone reference:**\n> Hi Marta, I'm in the final round for a product lead role at Corvid and they've asked for two references. Would you be willing to be one? It'd be a 15 minute call sometime next week. If useful, the things they care most about are the Atlas launch, how I handled the vendor switch, and cross-team work. If the timing's bad, no problem at all.\n\n**Professor, letter of recommendation:**\n> Dear Professor Okafor, I'm applying to the MSc in Data Science at Edinburgh, deadline 15 January. Would you be able to write a letter of recommendation? I was in your Statistical Inference course in 2024 and did my final project on survival models for churn, which you gave an A. I'm happy to send a short draft, my CV and the submission link to make it quick. Thank you for considering it.\n\n**LinkedIn recommendation, with a draft offered:**\n> Hi Sam, I'm updating my LinkedIn and would value a short recommendation from you, since we worked together on the Hollis migration. Three or four sentences is plenty. If it helps, I can send a draft you can edit or throw out. No rush, any time in the next two weeks would be great.\n\n**Client, case-study quote:**\n> Hi Dana, we're putting together a short case study on the Q2 rollout and a line from you would carry a lot of weight. Something like: \"[Company] cut our onboarding time from six days to two, and the team was easy to work with throughout.\" Feel free to edit, rewrite, or tell me it's not something you can do. Would you be okay with us using your name and title alongside it?\n\n**Asking after a long gap:**\n> Hi Tom, it's been a while, I hope things are good at Fenwick. I'm applying for a senior engineering role and thought of you, since you managed me through the platform rebuild in 2022. Would you be open to being a reference? Happy to catch you up over a quick call first so you're not going in cold.\n\n**Sending the details after a yes:**\n> Thank you, that means a lot. Here's everything in one place: the role is Senior Analyst at Corvid; Jess Lin (jess@corvid.com) will email you to arrange a call between the 8th and 12th; the points I mentioned were the Atlas launch, the vendor switch, and cross-team work. I'll let you know how it goes.\n\n## Avoid\n- \"Could you maybe say a few words about me sometime?\" with no role, no deadline, no format.\n- Sending the draft before they have said yes. Offer it, then send it.\n- Chasing more than twice.\n- Forgetting to close the loop. A one-line \"I got the job, thank you\" earns the next yes.\n\n## If they hesitate or decline\n\n**They hesitate (\"I'm not sure I'm the right person\"):**\n> That's fair. Would it help if I sent you a draft and the three points they'll ask about? If it still doesn't feel right, I'll ask someone else, no problem.\n\n**They decline:**\n> Understood, and thank you for telling me straight.\nDo not ask why. Ask someone else the same day. A reluctant reference is worse than a missing one.\n\n**Silence after two messages:**\nTreat it as a no. Move to your next name and, if you want the door open, send one line.\n> No worries if this got buried. I've asked someone else for this one, but I'd still love to catch up sometime."},
{"id":"ask-for-review-or-testimonial","title":"Asking a customer for a review, testimonial or referral","category":"commerce","tags":["review","testimonial","referral","google review","ask for feedback","case study","small business"],"triggers":["ask for a review","get a testimonial","ask customers to leave a google review","request a referral from a client","ask for a case study","how to ask for reviews"],"summary":"How to ask for reviews and testimonials at the right moment, make it a 60-second job, and never sound needy or transactional.","updated":"2026-09-27","body":"# Asking for a review, testimonial or referral\n\n## Goal\nThe customer does it in the next minute because it's easy and because they liked you. Nobody feels pestered.\n\n## Structure\n1. **Thank them for something specific** about the purchase or the project.\n2. **The ask, framed by its effect**: what a review does for a small business.\n3. **One link and a time estimate.** \"Two sentences, about a minute.\"\n4. **A genuine out.** \"Thank you either way.\"\n5. **For testimonials, a draft they can edit** so the work is already done.\n\n## Principles\n- **Timing:** ask right after a good moment (delivery arrived, project shipped, they said thanks). Not weeks later.\n- **One link, one platform.** Do not send three links.\n- **Tell them it's short.** \"Two sentences is plenty.\"\n- **Make the ask about the effect**, not about you: \"reviews are how small shops get found.\"\n- **Offer to draft** for testimonials; most people say yes and edit.\n- **Never incentivise reviews** on platforms that ban it (Google, most marketplaces). A thank-you after is fine.\n- **Ask once, remind once.** Then stop.\n\n## Examples\n\n**After a delivery, DM or email:**\n> So glad the lamp arrived safely! If you have a minute, a quick Google review would honestly make a difference; it's how people find us. Here's the link: [link]. Two sentences is plenty. Thank you either way.\n\n**After a service (hair, cleaning, repair):**\n> Thanks for coming in today, it was lovely to see you. If you're happy with the cut, a short review here [link] helps more than you'd think. No pressure at all.\n\n**Freelancer asking a client for a testimonial:**\n> Hi Rob, now that the site's live, could I ask a favour? A short testimonial, two or three sentences, would help me a lot with the next few clients. To make it painless, I've drafted one below you can edit or replace:\n> \"Nina rebuilt our site in six weeks; it's faster, looks better, and enquiries are up. She was easy to work with and hit every date.\"\n> If you'd rather write your own, even better. Thanks, Rob.\n\n**Asking for a referral:**\n> Hi Rob, quick ask: if you know anyone who's in the same spot you were six months ago, I'd be grateful for an intro. No need to sell me, just a \"you should talk to Nina\". And if nobody comes to mind, no worries at all.\n\n**Asking for a case study (bigger ask):**\n> The results on your project were the best I've had this year and I'd love to write it up as a short case study, with your approval on every word. It'd take about 20 minutes of your time on a call. Would you be open to it? Happy to anonymise if that's easier.\n\n**Reminder, once:**\n> Just floating this back up in case it got buried: [link]. Totally fine if it's not your thing.\n\n**After a customer leaves a review:**\n> Saw your review, thank you so much. It genuinely made my week.\n\n**Responding to \"I'll do it later\":**\n> Thanks! No rush. Here's the link again so it's easy to find: [link].\n\n## Avoid\n- \"It would mean the world to me\" (too much).\n- Asking before the product's arrived or the work's done.\n- Asking unhappy customers for public reviews (ask them for private feedback instead).\n- Multiple platforms in one ask.\n- Reminding more than once.\n- Offering discounts for reviews where it's against the rules.\n\n## If they ignore it or say no\nNo reply after the one reminder is a no; drop it and ask the next customer. If they decline outright, thank them and do not ask what stopped them. If they reply with a complaint instead, treat it as a support ticket, not a review request: fix the problem first.\n> Totally understood, thanks for letting me know. Enjoy the lamp.\n> Sorry, I didn't know about the flicker. Let me sort that first; could you send a quick photo?\nIf they leave a lukewarm public review, reply publicly with thanks and one line on what you'll do about it. See `respond-to-negative-review`."},
{"id":"ask-for-time-off-or-sick-leave","title":"Asking for time off or sick leave","category":"work","tags":["time off","vacation","sick leave","mental health day","bereavement","parental leave","leave early"],"triggers":["ask my boss for a day off","request vacation","text my manager I'm sick","calling in sick","mental health day","bereavement leave","tell my manager I'm pregnant","parental leave","leave early today","doctor's note"],"summary":"Requesting vacation, sick leave, a mental-health day, bereavement or parental leave with the right amount of detail (very little), a handover line, and what to say if the manager pushes back.","updated":"2026-09-27","body":"# Asking for time off or sick leave\n\n## Goal\nThe manager knows the dates, knows the work is covered, and can say yes in one word. You give enough information to plan around and nothing they have to hold in confidence.\n\n## Structure\n1. **The dates, first line.** \"I'd like to take 14 to 18 October off.\" Not \"I was wondering if it might be possible\".\n2. **One sentence on coverage.** Who has what, or what you will finish before you go.\n3. **The category, if it helps them.** Vacation, sick, bereavement, parental. Not the diagnosis, not the family story.\n4. **The ask, closed.** \"Can you approve?\" or \"I'll put it in the system today.\"\n5. **For same-day absence, skip steps 1 to 4 and send three lines:** not coming in, what is urgent today and who has it, when you will next check in.\n\n## Principles\n- Vacation is a notification with a courtesy question attached. You are entitled to it. Sick leave is a notification, full stop.\n- Detail is not a favour to your manager. \"I'm unwell\" is complete. \"Stomach thing, been up all night\" makes both of you uncomfortable and adds nothing.\n- Mental-health days are sick days. You do not need to label them differently unless your company culture rewards it.\n- Ask early for planned leave, ideally before anyone else books the same week. Ask the same morning for illness, before your start time if you can.\n- The handover line is what makes the yes easy. Write it before you write the request.\n- For parental leave, give the news and the rough timeline in the same message so your manager can start planning instead of guessing.\n\n## Examples\n\n**Vacation request, email or Slack:**\n> I'd like to take 14 to 18 October off, back on the 21st. The Hendricks deliverable is due the 11th so it'll be done before I go, and Priya has agreed to cover the Tuesday client call. Can you approve?\n\n**Same-day sick text to manager:**\n> I'm unwell and won't be in today. The only urgent thing is the 2pm review, I've asked Dan to run it and sent him the notes. I'll check messages once mid-afternoon and update you tomorrow morning.\n\n**Mental-health day, when you want to say so:**\n> I'm taking a sick day tomorrow, I need a day to reset. Nothing on my plate is blocking anyone before Thursday. Back Wednesday.\n\n**Bereavement leave:**\n> My grandfather died last night. I'll need to be out this week, likely through Friday, for the funeral and family. Ana has the Q4 numbers and knows where everything is. I'll confirm my return date by Wednesday.\n\n**Parental leave announcement:**\n> Some news: we're expecting, due mid-March. I'm planning to take [12] weeks from around the due date. I know that's a while away, so I'd like to start a handover plan in January. Can we book 30 minutes to talk it through next week?\n\n**Leaving early today:**\n> I need to leave at 3 today for a [school pickup / appointment]. I'll finish the draft before I go and I'm reachable on my phone if anything comes up.\n\n**Longer trip, asking well ahead:**\n> Heads up for planning: I'd like three weeks off, 2 to 20 June. That's before the summer release cycle, and I'd handle the Kestrel migration before I leave. Are those dates workable from your side?\n\n## Avoid\n- \"I was wondering if it would be at all possible, if it's not too inconvenient...\"\n- Medical detail. Symptoms, appointments, test names. None of it.\n- Asking for sick leave as a question. \"Would it be okay if I stayed home?\" invites a no to something that is not theirs to refuse.\n- Promising to work while sick. \"I'll be online all day\" turns sick leave into remote work with a temperature.\n- Apologising for being ill or for taking holiday you have earned.\n- Booking the flights before the dates are approved, then presenting them as fixed.\n\n## If they push back\n\n**Vacation dates are inconvenient:**\n> Understood. Which week nearby works better for the team? I can move it to the 21st if the launch is the concern, but I'd like to lock something in this week so I can book.\n\n**They ask for a doctor's note:**\n> Sure. Policy says a note is needed after [three] days, so I'll get one if I'm out past Wednesday. If you need one for a shorter absence, let me know and I'll ask the GP for a letter.\nIf the request is out of step with the written policy, ask them to point you to the policy rather than arguing. Check with HR if you cannot find it.\n\n**They ask what is wrong:**\n> Nothing I need help with, just unwell. I'll be back as soon as I'm fit to work.\n\n**Silence on a leave request:**\n> Following up on my leave for 14 to 18 October. Could you let me know by Friday? I'm happy to put it in the system now for you to approve there."},
{"id":"ask-someone-out-and-early-dating","title":"Asking someone out, texting after a date, keeping it going","category":"personal","tags":["dating","ask out","first date","after the date","texting","flirting","second date"],"triggers":["ask her out","ask him out","text after first date","what to text after a date","how to ask for a second date","keep the conversation going","flirty text","suggest a date","dating app conversation"],"summary":"The positive side of dating messages: a clear, low-pressure ask; the text after a date; keeping a conversation alive; proposing a second date without overthinking. The very first opener on an app: first-message-to-stranger.","updated":"2026-09-29","body":"# Asking someone out and early dating messages\n\n## Goal\nA clear invitation the other person can say yes or no to easily, and after a date, a short message that says you enjoyed it and whether you want more. It reads as confident and unbothered whichever way the answer goes.\n\n## The rule that runs through all of these\nBe specific and make the no easy. Confidence is a clear invitation with a real out, not a vague \"we should hang out sometime\" and not a five-paragraph text.\n\n## Asking someone out\n\n**Structure:** context → clear invitation with a specific plan → easy out.\n\n**Someone you know a bit (friend of friend, coworker's friend, class):**\n> I've really liked our chats at the climbing wall. Would you want to get a drink sometime, just the two of us? Thursday or Saturday if either works. No pressure at all if not.\n\n**Dating app, moving off the app:**\n> I'm enjoying this and I'd rather keep it going in person. Coffee or a drink this week? I'm free Wednesday evening or Sunday afternoon.\n\n**Someone you've met once:**\n> This is a bit forward, but I'd regret not asking: would you want to grab a coffee sometime? I'm Sam, we talked about terrible sci-fi at Nina's party.\n\n**Colleague (be careful; only if it's appropriate at your workplace):**\n> Outside of work, I'd like to take you for a drink. If that's not something you want, I'll never mention it again and nothing changes. If it is, Friday?\n\n**If they say no:**\n> No worries at all, thanks for being straight with me. See you around.\n\n## Text after a first date\n\n**Send that night or the next morning. Short. Specific. Say if you want to see them again.**\n\n> I had a really good time tonight. The story about your grandad's boat is going to stay with me. I'd like to do it again if you would.\n\n> Home safe. That was fun; you were right about the dumplings. Same time next week?\n\n**If you're not sure yet:**\n> Really enjoyed tonight, thanks for a good evening.\n(This is honest and keeps the door open without promising.)\n\n**If you don't want a second date:** see `romantic-let-down`.\n\n## Asking for a second date\n\n> Want to do it again? There's a night market on Saturday I think you'd like, or a walk and a coffee Sunday if you'd rather keep it low-key.\n\n## Keeping a conversation going (texting between dates)\n\n- Reference something they said. \"How did the presentation go?\" beats \"hey\".\n- Send things, not just questions: a photo, a link, a thought. \"This made me think of you\" is the best text there is.\n- Match their pace. If they reply in hours, don't reply in seconds every time.\n- Don't interrogate. Two questions max, then share something.\n- Know when to stop. A conversation that ends on a high beats one that fizzles.\n\n**Examples:**\n> Passed a shop with exactly the ugly lamp you described. I'm sorry I doubted you.\n> Random thought: you said you'd never been to the Lido. I have opinions about this. Want to fix it Sunday?\n> How was the dinner with your sister?\n\n## Flirting without being weird\nCompliment a choice or a quality, not a body part. Tease gently, then soften. Be the one who's clearly interested but not anxious.\n> You're a lot funnier than your profile let on.\n> Okay you've got good taste in coffee, I'm reluctantly impressed.\n\n## If they go quiet\nOne light message after a few days. Then let it go.\n> Hey, no pressure, just wanted to say I enjoyed meeting you. If you're up for another drink sometime, I'm around.\n\n## Avoid\n- \"We should hang out sometime.\"\n- Paragraphs.\n- Double and triple texting.\n- \"Why haven't you replied?\"\n- Asking for a second date before the first has ended.\n- Over-planning the first date. One drink, one hour, easy exit."},
{"id":"ask-to-change-behavior","title":"Asking someone to change a behaviour (friend, partner, family, housemate)","category":"personal","tags":["roommate","neighbour","noise","dishes","habit","complaint","request"],"triggers":["roommate never cleans","ask a friend to stop","tell them to stop","ask them to be quieter","they keep doing","it's annoying me","chores"],"summary":"Raising an annoying behaviour so they fix it rather than get defensive: specific, one thing, a shared problem with a concrete ask. Ongoing neighbour problems: neighbour-disputes. Family overstepping: set-boundary.","updated":"2026-09-29","body":"# Asking someone to change a behaviour\n\n## Goal\nThey change the specific thing, and the relationship is not damaged. Being right is not the goal.\n\n## Structure\n1. **Low-key opener** that signals this is small and friendly.\n2. **The specific behaviour**, observable, no character judgement. \"The dishes have been sitting two or three days\" not \"you're messy.\"\n3. **The effect on you**, brief, first person.\n4. **The concrete ask**: what you want instead, specifically.\n5. **Something that makes it easy to say yes** (flexibility, acknowledgement of their side).\n\n## Principles\n- One behaviour per conversation. A list becomes an attack.\n- Raise it early, when it is a small annoyance. Waiting until you're furious guarantees a bad conversation.\n- Frame the ask as a shared system, not a correction. \"Can we do X?\" beats \"Can you stop Y?\"\n- Do it in person or voice if you live together. Text for neighbours you barely know.\n- Assume they do not know it bothers you. They usually do not.\n\n## Examples\n\n**Roommate, dishes, in person or text:**\n> Hey, small thing: the dishes have been piling up for a few days at a time and it's stressing me out when I cook. Could we go with a \"same day\" rule? I'm happy to do the same and I'll hold myself to it.\n\n**Roommate, noise at night:**\n> Can I ask a favour? I've got early starts this month and the TV through the wall after 11 is keeping me up. Would headphones after 11 be doable? I'll do the same on weekends when you're sleeping in.\n\n**Neighbour you don't know, note or message:**\n> Hi, I'm in flat 4. Your music's been coming through pretty loud most nights after 10; I don't think you'd know from your side. Would you mind keeping it lower after 10 on weeknights? Thanks so much, and shout if anything from our side ever bothers you.\n\n**Friend who's always late:**\n> Can I be honest about something small? You're usually 20 or 30 minutes late and I end up sitting around. It's not a big deal, but could you text me when you're actually leaving? Then I'll time it right and neither of us is stuck waiting.\n\n**Partner, a habit:**\n> Can I bring up a tiny thing without it being a thing? When you leave your phone on loud at night it wakes me every time it buzzes. Could it go on silent after we're in bed?\n\n**Repeated after you've asked once:**\n> I mentioned the dishes a couple of weeks ago and it's slipped back. I'm not trying to nag; it genuinely affects me. Can we figure out something that'll actually stick? Maybe a rota, or I'll take dishes and you take bins?\n\n## Avoid\n- \"You always\" / \"you never.\"\n- Bringing it up in front of others.\n- Saving up five things.\n- Passive-aggressive notes or sighing.\n- Apologising for having the request.\n- Threats (\"or I'm moving out\") unless you mean it.\n\n## If they get defensive or nothing changes\nDo not match the heat. Restate the specific ask once, same friendly register, and let it sit. If they say \"you do it too\", agree where it is true and go back to the one thing. If it slips after a week, raise it again briefly rather than stewing.\n> I'm not saying you're messy, I'm just asking for same-day dishes. That's all it is.\n> Fair, I've left mine too. Can we both do same day from today?\nIf a neighbour ignores two polite notes, escalate in writing with dates (see `neighbour-disputes`). If a roommate ignores everything, the real conversation is whether the living setup works. See `set-boundary`."},
{"id":"cancel-or-reschedule","title":"Cancelling or rescheduling plans","category":"personal","tags":["cancel","reschedule","plans","bail","change plans"],"triggers":["need to cancel","can't make it anymore","reschedule","move our meeting","bail on plans","push back the dinner"],"summary":"How to cancel or move plans so it reads as a change of logistics rather than a change of heart, with different versions for last-minute versus advance notice.","updated":"2026-09-28","body":"# Cancelling or rescheduling\n\n## Goal\nThey know immediately, they know it is not about them, and they have a new time before they finish reading.\n\n## Structure\n1. **Lead with the change** in the first sentence.\n2. **One reason, short and true.** No reason at all for very casual plans.\n3. **Acknowledge the cost to them**, proportional to the notice.\n4. **Two concrete alternatives**, not \"sometime\".\n5. **For last-minute cancels: offer to cover a cost or make it up.**\n\n## Principles\n- The earlier you tell them, the shorter the apology needs to be.\n- Cancelling twice in a row requires you to be the one who reschedules and shows up.\n- Do not over-explain. \"Work thing came up\" is a complete sentence.\n- Tell them the moment you know. A cancel that arrives three hours after you decided is two offences.\n- If they have already paid or travelled for it (a booking, a babysitter, a train), offer to cover it.\n\n## Examples\n\n**Advance notice, casual:**\n> Need to move Thursday, something's come up. Could do Friday or Sunday afternoon?\n\n**Same day, friend:**\n> I have to cancel tonight, I've been hit with a migraine. I'm really sorry to do it on the day, I know you'd planned around it. Can I take you out next week, my treat? Tuesday or Thursday?\n\n**Reschedule with a client / professional:**\n> Hi Maria,\n> I need to move our 2pm on Wednesday, a conflict I can't shift has come up. Sorry for the short notice. I'm free Thursday 10 to 12 or Friday afternoon. If neither works, send me a couple of times and I'll make one fit.\n> Thanks for your flexibility,\n> Ben\n\n**Second cancellation in a row:**\n> I'm aware I've cancelled on you twice now and I hate that. This one's on me to fix: I've booked Saturday 1pm at [place]. I'll be there early.\n\n**Cancelling something you don't want to reschedule:**\n> I'm going to pull out of Sunday. Nothing dramatic, I just need a quiet weekend. Enjoy it, and let's find another time soon.\n\n**Voice note or voicemail (dentist, salon, a friend who prefers voice):**\n> Hi, it's Sam Lee, I've got an appointment Thursday at 10 with Dr Park. I need to move it, sorry for the short notice. Any morning next week works. My number is 07700 900 123, again 07700 900 123. Thanks.\n\n**Group plan, you're the one dropping:**\n> I've got to drop out of Saturday, sorry all. Don't change anything for me, have a great time.\n\n## Avoid\n- \"Would it be okay if we rescheduled?\" (you are not asking permission; you are informing).\n- A long medical/family story.\n- \"Rain check?\" with no date.\n- Cancelling with a vague \"not feeling it\" to someone who made an effort.\n- Cancelling via a third party.\n\n## If they're upset or stop replying\nA short, sharp reply (\"fine\") after a same-day cancel is fair. Do not argue with it or over-apologise; own it once, then act. Book the new time yourself and confirm it, so the burden of rescheduling is not on them.\n> I get it, and I'm sorry. I've booked Thursday at 7 at Marco's, my treat. If that doesn't work, tell me a night and I'll move it.\n> No reply needed now. If Sunday works I'll see you at 2; if not, just say and I'll find another one.\nIf this is the third cancel and they've stopped responding, the repair is showing up next time, not another message."},
{"id":"chase-late-payment","title":"Chasing a late payment","category":"work","tags":["invoice","late payment","chase","overdue","accounts","freelance"],"triggers":["invoice is overdue","chase payment","they haven't paid","remind client to pay","late invoice","payment reminder"],"summary":"A three-stage escalation for overdue invoices that stays polite while getting progressively firmer, with a final notice that does not burn the relationship, plus automated reminders for many customers.","updated":"2026-09-27","body":"# Chasing a late payment\n\n## Goal\nYou get paid, the relationship survives, and you sound like a business, not a friend asking for a favour.\n\n## Principles\n- Assume admin error until proven otherwise. Most late payments are someone forgetting to click.\n- Every message has: invoice number, amount, original due date, how to pay. They should be able to pay from the message.\n- Firmness increases with each message; warmth stays constant until the final notice.\n- Never apologise for chasing. Never \"sorry to bother you.\"\n- Cc accounts payable or the finance contact from message two onward.\n- Put a date on everything.\n\n## The escalation\n\n**Stage 1: due date passed, 3 to 5 days (gentle):**\n> Hi Sarah,\n> A quick note that invoice #1042 for $2,400 was due on the 10th and I haven't seen it come through yet. It may just be in the queue; if so, ignore this. Payment details are on the invoice, attached again for convenience.\n> Thanks,\n> Mia\n\n**Stage 2: two weeks late (direct):**\n> Hi Sarah,\n> Following up on invoice #1042 ($2,400, due 10 May), now two weeks overdue. Could you let me know when I can expect payment, or if there's an issue on your end I should know about? I've copied in accounts in case that helps.\n> Thanks,\n> Mia\n\n**Stage 3: 30 days late (firm, with consequence):**\n> Hi Sarah,\n> Invoice #1042 ($2,400) is now 30 days overdue. I need to receive payment by Friday 14 June. If it's not received by then, I'll pause work on the current phase and apply the late fee set out in our agreement. I'd much rather not do either, so please let me know today if there's a problem I can help resolve.\n> Regards,\n> Mia\n\n**Final notice (before formal action):**\n> This is a final notice for invoice #1042 ($2,400), 45 days overdue. If payment isn't received by [date], I'll refer the matter to [collections / small claims]. I'm still happy to resolve this directly; a call today would be enough.\n\n## Variations\n\n**Client says \"it's being processed\":**\n> Thanks. Could you confirm the payment date so I can plan around it?\n\n**Client disputes the amount:**\n> Happy to go through it. Which line are you querying? The rest of the invoice isn't in dispute, so could that portion be paid now while we sort the remainder?\n\n**Automated reminders for many customers (subscriptions, memberships, small invoices):**\nUse the same four stages on a schedule (due date, day 7, day 14, day 30) with the amount, a one-click payment link and a real reply-to address in every message. Each message is shorter than the last. After the final notice, stop emailing and switch to a pause of service or one personal message; a sixth automated reminder only teaches people to ignore you.\n> Hi Leo, your March payment of £29 didn't go through, usually an expired card. You can update it here in a minute: [link]. Your membership stays active in the meantime. Any questions, just reply.\n\n**Friend or informal client:**\n> Hey, the $600 for the design work was due last week. Can you sort it this week? Bank details are in the invoice.\n\n## Avoid\n- \"Just checking in!\"\n- \"I know things are busy but...\"\n- Emotional language (\"I'm really struggling because you haven't paid\").\n- Threats you will not follow through on.\n- Continuing to deliver new work while heavily unpaid.\n- Chasing in the same thread as friendly chat. Separate email, clear subject line: \"Overdue: Invoice #1042\".\n\n## If they go silent or push back\nSilence at stage 2 means stage 3 on the date you said. If they promise a date and miss it, reply the next morning with the next consequence. If they get hostile, stay factual: invoice, amount, date. Ignore the tone.\n> The payment date you gave was Friday and it hasn't arrived. Please confirm by 5pm Wednesday whether it's been sent. Work on the next phase is paused until then.\n> I understand you're frustrated. The amount and due date haven't changed. If cash flow is the issue, I can take $1,200 now and $1,200 on the 30th, in writing.\nIf the final notice date passes, do what you said."},
{"id":"check-in-on-someone-struggling","title":"Checking in on someone who is struggling","category":"personal","tags":["check-in","support","friend","burnout","breakup","depression","going-quiet"],"triggers":["friend is going through a hard time","check in on a friend","my friend went quiet","what to say to someone who is depressed","friend lost their job","friend got dumped","they said they're fine","offer help to a friend","friend is burnt out"],"summary":"Reaching out to a friend or relative who is having a hard time, from the first text to what to do when they go silent or say \"I'm fine\", with concrete offers instead of vague ones.","updated":"2026-09-28","body":"# Checking in on someone who is struggling\n\n## Goal\nThey feel seen without feeling like a project. The message asks nothing, makes replying optional, and leaves a door open for later.\n\n## First check-in\n1. **Say why you're writing, in one line.** \"I heard about the redundancy\" or \"You've been quiet and I've been thinking about you.\"\n2. **No questions that need a report.** \"How are you?\" asks them to summarise a bad month. Prefer \"no need to reply\" or a question with a small answer.\n3. **One concrete offer** (see below). Not a menu.\n4. **Release them.** \"No pressure to answer this.\"\n\n## When they don't reply\n1. Wait at least a few days. Silence is not rejection, it is often the only energy they have.\n2. Send something that needs zero response: a photo, a memory, a \"still here.\"\n3. Never mention the unanswered message. \"Did you get my text?\" turns your care into a debt.\n4. About once a week, not daily, unless you fear for their safety.\n\n## When they say \"I'm fine\"\n1. Take it at face value the first time. Pushing makes the next \"fine\" more defended.\n2. Leave the door propped: \"Okay. If fine stops being true, you don't need a reason to text me.\"\n3. If the behaviour and the word clearly disagree, name it once, gently, and stop.\n\n## Offering concrete help\n\"Let me know if you need anything\" hands them a task. Offer one specific thing with a time attached, that they only have to accept or decline: food, a lift, a walk, a school pickup.\n\n## Principles\n- Their pace, not yours. You are a lamp in the hallway, not a search party.\n- Presence beats advice. Do not fix, reframe, or find the silver lining.\n- Shorter is kinder. A long message asks for a long reply.\n- Consistent beats intense: three small texts in a month beat one essay.\n- Professional help gets one warm line, offered as an option, never as a verdict on them.\n\n## Examples\n\n**Friend went quiet:**\n> Hey, you've gone a bit quiet and I've been thinking about you. No need to reply to this. I'm around all weekend if you want company, or silence in the same room.\n\n**Job loss:**\n> Heard about Tuesday. That's rubbish and it's not a verdict on you. I'm making a big pot of curry Thursday, can I drop some at yours around 7?\n\n**Breakup:**\n> Sorry about you and [name]. I'm not going to ask how you're doing because I think the answer is obvious. Do you want to walk the dog with me Saturday morning, 10ish? Zero talking required.\n\n**Burnout:**\n> You've been running on empty for months and I can see it. I'm not going to tell you to rest, you've heard it. Can I take [the kids / the dog / the airport run] off your hands on Sunday so you get an actual day?\n\n**Depression, they've been withdrawn:**\n> Still here. No pressure, no questions. Sending a picture of the dog being an idiot. Text me one letter if you want me to come over.\n\n**Illness, longer haul:**\n> Thinking of you before the scan on Monday. I'll text at 3 just to say hi, you don't have to answer. And I've got Wednesday evening free if you want me to bring dinner and a bad film.\n\n**Pointing to professional help, one line:**\n> I'm always going to be here, and I also think you deserve more support than a mate with a curry. If you ever want a hand finding someone to talk to, I'll help you look, no judgment, just an offer.\n\n**After \"I'm fine\":**\n> Okay, I believe you. And if fine stops being true at 2am, you can text me without a reason. Same offer stands for the walk on Saturday.\n\n## Avoid\n- \"Everything happens for a reason\", \"at least\", \"you're so strong\", \"have you tried\".\n- Comparing to your own hard time unless they ask.\n- Sending a check-in and then going silent when they finally open up.\n- Naming a condition. \"You sound depressed\" is a diagnosis, and it is not yours to make.\n\n## If it goes badly\nIf they snap at you or push you away:\n> That's fair, I'll back off. The offer doesn't expire. I'm not going anywhere.\nThen do exactly that, without defending your intent. Reappear in a couple of weeks with something small.\n\nIf you are genuinely worried about their safety, say it plainly and stay on the line:\n> I'm worried about you and I'd rather ask than wonder. Are you safe right now? I can come over, or sit on the phone with you while you call [crisis line for their country].\nAsking directly does not put the idea in their head, and it tells them they can talk about it. If they say they might act on it, or you cannot reach them and fear for their life, call your local emergency number. That one is not yours to carry alone."},
{"id":"co-parenting-and-ex-logistics","title":"Co-parenting messages with an ex (schedules, handovers, money, new partners)","category":"personal","tags":["co-parenting","ex","kids","custody","handover","child support"],"triggers":["text my ex about the kids schedule","co parent keeps changing pickup times","ask my ex to pay half of school costs","tell my ex i have a new partner meeting the kids","my ex is late for every handover","co-parenting message without starting a fight","ex sends long angry texts about the kids","swap weekends with my ex"],"summary":"Messages to a co-parent about schedules, handovers, costs, school and new partners: brief, factual, about the kids, fine for a judge to read. The relationship itself: respond-to-an-ex-or-breakup-message.","updated":"2026-09-27","body":"# Co-parenting messages with an ex\n\n## Goal\nThe arrangement for the children works, and every message could be read by the children, a mediator or a judge without embarrassing you. Co-parenting messages are a business correspondence about the most important project you share. Warmth is optional; clarity and civility are not.\n\nThe relationship itself (getting back together, closure, belongings): `respond-to-an-ex-or-breakup-message`.\n\n## Structure\n1. **Brief greeting.** Name, no small talk required.\n2. **One topic per message.** The swap, the cost, the school trip.\n3. **The facts and the specific proposal**, with dates, times and amounts.\n4. **A clear question they can answer yes or no**, with the date you need it by.\n5. **Sign off neutrally.** \"Thanks\" is enough.\n\n## Principles\n- Brief, informative, friendly, firm. If a sentence is not needed to arrange the children's lives, cut it.\n- Keep the past out. No \"as usual\", \"once again\", \"you always\". Each message is about this weekend, not the marriage.\n- Put the children's needs first and name them concretely (\"Mia has her recital at 5\") rather than as leverage (\"the kids are upset because of you\").\n- Never send messages through the children, and never ask them to report back.\n- Write it, do not phone it, for anything that matters: changes, money, medical decisions. A shared calendar or co-parenting app makes a record without you having to keep one.\n- You do not have to reply to hostility, only to logistics. Answer the question in the message and ignore the rest.\n- Give reasonable notice and grant reasonable swaps. Flexibility you give is flexibility you are more likely to get.\n\n## Examples\n\n**Swap request:**\n> Hi Sam, could we swap weekends this month? I'd take the kids 14 to 16 and you'd have 21 to 23, because of my sister's wedding. Can you let me know by Wednesday?\n\n**Late handover, first time it becomes a pattern:**\n> Hi Alex, the last three handovers have been 30 to 45 minutes after 6. Leo gets unsettled waiting. Can we either stick to 6 or agree 6:30 as the new time? Either works for me as long as it's consistent.\n\n**Shared cost:**\n> Hi, the school trip to the science museum is £60, due by 10 March. Receipt attached. As agreed, could you send £30 by then? Thanks.\n\n**Medical or school update, just the facts:**\n> Mia saw the GP today for her ear. It's a mild infection, she's on antibiotics twice a day until Sunday. The bottle and instructions are in her bag. She's fine for school tomorrow.\n\n**New partner meeting the children:**\n> I wanted to let you know before it happens: I've been seeing someone for about six months, and I'm planning for them to meet the kids briefly at the park next month. I'll keep it low-key. If you have any concerns, I'm happy to talk them through.\n\n**Replying to a long angry message (answer only the logistics):**\n> Noted about Saturday. I'll have the kids ready at 10 as planned.\n\n**Setting a communication channel:**\n> To keep things simple, could we move all scheduling to the co-parenting app from now on? Then we both have the calendar and the costs in one place.\n\n## Avoid\n- Sarcasm, \"per my last message\", or anything you would not want read aloud in court.\n- Commenting on their parenting, new partner or lifestyle, unless it is a genuine safety issue.\n- Using the children as messengers or as arguments.\n- Replying at night or while angry. Draft it, sleep, send the shorter version in the morning.\n- Long messages mixing three topics. The hardest topic swallows the easy ones.\n- Withholding contact or information as leverage over money.\n\n## If it goes badly\nIf they respond with insults or history, do not match them. Reply only to the practical part, or wait until there is one. If they refuse a reasonable swap, accept it and plan around it; one refusal is not a pattern. If a pattern of lateness, missed payments or cancelled contact continues, keep a dated record and raise it through mediation or a family lawyer rather than escalating by text. If you ever believe a child is unsafe, contact the relevant authorities or emergency services directly; that is not a messaging problem.\n> I'm not going to go back over that. For Saturday: 10am at mine, as planned.\n> Understood, I'll keep this weekend as it is. Let me know if a different date works later in the month."},
{"id":"cold-outreach","title":"Cold outreach that gets a reply (sales, partnerships, press)","category":"work","tags":["cold email","outreach","sales","partnership","pitch","dm","press"],"triggers":["cold email","reach out to a company","pitch a partnership","contact a journalist","sales outreach","first contact with a prospect","dm a brand"],"summary":"The four-line business pitch to someone who does not know you: why them, what you have, proof, tiny ask. Sales, partnerships, press. Personal or social first contact: first-message-to-stranger.","updated":"2026-09-27","body":"# Cold outreach\n\n## Goal\nA reply. Not a sale, not a meeting; a reply. Everything is optimised for making the reply cheap for them.\n\n## Structure (four lines, under 100 words)\n1. **Why them, specifically.** One line proving this is not a blast. Reference their work, a recent post, a problem they have publicly.\n2. **What you have**, in one plain sentence. No jargon.\n3. **Proof**, one number or one name.\n4. **Tiny ask.** A yes/no question, or \"worth a look?\" Not \"hop on a 30-minute call\".\n\n## Principles\n- Subject line: specific and short. \"Idea for [their product]'s onboarding\" beats \"Partnership opportunity\".\n- No \"I hope this finds you well.\" No \"my name is X and I'm the founder of Y\" as the opener.\n- Write it for a phone screen. If the ask is not visible without scrolling, it is too long.\n- Give them a way to say no that is not silence: \"If it's not relevant, a 'no' is genuinely helpful.\"\n- Follow up twice, spaced a week apart, each with a new piece of value. Then stop.\n- One ask. Not \"call, or demo, or intro to your team\".\n\n## Examples\n\n**Sales, email:**\n> Subject: 40% of your checkout drop-off\n> Hi Lena,\n> I noticed [brand]'s checkout asks for an account before payment; that's typically where a third of mobile buyers leave. We built a guest checkout layer that [similar brand] used to lift conversion 18% in six weeks. Worth a 10-minute look? If not relevant, a \"no\" is genuinely useful.\n> Sam\n\n**Partnership, DM:**\n> Hi Priya, your newsletter's piece on solo founders' burnout was the most shared thing in our community last month. We run a 12k-member group for exactly that audience. I have one specific idea for a joint piece that'd be easy on your side. Open to hearing it in two lines?\n\n**Press / journalist:**\n> Hi Marcus, you covered the rise of agentic shopping in June and asked what happens when Amazon opts out. We just published data from 2,000 shoppers on exactly that; the headline is [one stat]. Happy to send the full dataset, no strings. Useful?\n\n**Follow-up 1 (a week later):**\n> Bumping this with one more thing: we just published [resource] that's relevant to what you're doing. No pressure on the original ask.\n\n**Follow-up 2 (final):**\n> Last note from me. If the timing's off, no worries at all; I'll leave it here. Door's open if it becomes useful.\n\n## Avoid\n- Long intros about yourself.\n- Multiple links.\n- \"Let me know if you have any questions.\"\n- \"I'd love to pick your brain.\"\n- Asking for 30 minutes.\n- Flattery without specifics.\n- Sending the same message to ten people at one company.\n\n## If they say no, or never reply\nNo reply after two follow-ups is a no. Do not send a third with \"just checking in\". A quick no is a gift; thank them and leave the door open in one line, without asking why. If they say \"not now\", ask when, set a reminder, and actually go away until then.\n> Thanks for the straight answer, genuinely helpful. If it ever becomes relevant, I'm easy to find.\n> Got it. Is Q1 a better time? I'll come back then and not before.\nIf they respond sharply (\"stop emailing me\"), reply once with \"Done, apologies\" and remove them from every list."},
{"id":"complain-as-customer","title":"Complaining to a business and asking for a refund (as the customer)","category":"personal","tags":["complaint","refund","customer","airline","restaurant","delivery","faulty","compensation"],"triggers":["ask for a refund","complain to the company","my order was wrong","flight was cancelled","they overcharged me","faulty product","get compensation","write a complaint email","bad service"],"summary":"How to complain so you actually get the refund or fix: specific facts, a clear ask, a deadline, and a tone that makes the agent want to help you.","updated":"2026-09-27","body":"# Complaining as the customer\n\n## Goal\nThe person reading it can solve it with the information in front of them, and wants to, because you were the reasonable one.\n\n## Structure\n1. **Order/reference number, date, what you bought.** First line.\n2. **What went wrong, factually.** One or two sentences.\n3. **What you've already tried** (if anything).\n4. **What you want**, specifically: full refund, replacement, partial credit, an apology.\n5. **A reasonable deadline.**\n6. **Polite close, name, contact.**\n\n## Principles\n- Front-line agents can help you more if you are pleasant. Anger goes to the bottom of the pile or gets the script.\n- Ask for one thing. \"A refund or a replacement, your choice\" is fine; a list of demands is not.\n- Say what would make you happy. They often do not know.\n- Keep the receipts: photos, screenshots, dates. Attach them.\n- Escalate only if the first ask fails. Then: \"I'd like this escalated to a manager\" and restate.\n- Mention your loyalty once if true (\"I've ordered from you for years\"). Not as a threat.\n\n## Examples\n\n**Wrong or damaged order, email or chat:**\n> Hi,\n> Order #58213, placed 4 June, arrived today with the blue jacket instead of the black one I ordered (photo attached). I'd like the black one sent out, and I'm happy to return the blue one with a prepaid label. Could you confirm by Friday? Thanks,\n> Sam Lee, sam@email.com\n\n**Faulty product, out of warranty edge:**\n> The kettle I bought on 10 January (receipt attached) stopped working this week, so just under a year. I'd like a replacement or a refund. I've tried a different socket and a reset. Let me know what you need from me.\n\n**Restaurant, after a bad experience (email to manager):**\n> Hi, we ate at your Clapham branch on Saturday, table for four at 7:30. Two mains came out cold and one was wrong, and it took 25 minutes to get anyone's attention. Your staff were polite but clearly overstretched. I'm not looking for a fight; I'd appreciate a partial refund on the mains and I'd like to know it's been noted. Receipt attached.\n\n**Airline / travel, cancellation:**\n> Booking ref ABC123, flight LHR to JFK on 14 May, cancelled 3 hours before departure. I was rebooked to the next day and incurred a hotel night ($180, receipt attached). I'm requesting the compensation due under [regulation, if applicable] and reimbursement of the hotel. Please confirm within 14 days.\n\n**Overcharged / double charged:**\n> I was charged twice for order #58213 on 4 June ($89.00 each, statement attached). Please refund the duplicate charge. Let me know if you need anything else from me.\n\n**Subscription you couldn't cancel:**\n> I tried to cancel my subscription on the 2nd (screenshot attached) and was charged on the 5th anyway. Please cancel it, refund the $29 charge, and confirm no further charges will be taken.\n\n**Escalation after a no:**\n> Thanks for your reply. I don't think that resolves it, since [one reason]. I'd like this escalated to a manager. To restate: I'm asking for [X]. I'd rather settle this directly than through [card dispute / ombudsman / review], and I'm confident we can.\n\n**In person / phone script:**\n> Hi, I've got a problem with an order and I'm hoping you can help me sort it. [Facts]. What I'd like is [ask]. Is that something you can do?\n\n## Avoid\n- \"This is the worst service I've ever had.\"\n- Threatening a bad review or social media in the first message.\n- ALL CAPS.\n- A full timeline of your emotional journey.\n- Asking for compensation wildly out of proportion.\n- Not including the order number.\n\n## If they refuse or go quiet\nOne escalation, then a different channel. If the first reply is a scripted no, send the escalation message above once. If that fails, or they stop replying for a week, stop writing to the same inbox: a chargeback, the regulator or ombudsman, a formal complaints address, or a public post, in that order of restraint. Tell them the step before you take it, once.\n> I've asked twice and not had a resolution. If I don't hear back by Friday I'll raise a chargeback with my card provider for the $89 duplicate charge.\n> Thanks for confirming your position. I'll take this to [ombudsman / dispute scheme] and reference this thread."},
{"id":"condolences-and-support","title":"Condolences (a death, a miscarriage, a loss)","category":"personal","tags":["condolence","grief","loss","death","sympathy","bereavement"],"triggers":["their parent died","sorry for your loss","what to write in a sympathy card","coworker's mum passed away","my friend's dog died","miscarriage","what do I say at a funeral"],"summary":"What to say when someone is grieving a death or loss: specific, short, present, with concrete help and no need to reply. A diagnosis: respond-to-difficult-health-news. A breakup or hard patch: check-in-on-someone-struggling.","updated":"2026-09-29","body":"# Condolences and support\n\n## Goal\nThey feel less alone and are not handed any work: no need to reply, no need to manage your feelings, no need to decide what help to ask for.\n\n## Structure\n1. **Say the thing directly.** \"I'm so sorry about your mum.\"\n2. **One specific memory or quality**, if you knew the person or the situation. Specific is what people keep.\n3. **One concrete offer**, or none. \"I'm dropping food on your porch Thursday, no need to answer the door.\"\n4. **Explicitly release them from replying.**\n\n## Principles\n- Short beats long. They are reading dozens of these.\n- Do not explain the loss (\"at least they're not suffering\", \"everything happens for a reason\", \"they're in a better place\"). Explaining is for you.\n- Do not ask \"how are you?\" as an opener. The answer is obvious and it forces performance.\n- \"Let me know if you need anything\" transfers the work to them. Offer something specific, or just be present.\n- Say the person's name. People fear their loved one being forgotten more than they fear being reminded.\n\n## Examples\n\n**Death of a parent, text:**\n> I'm so sorry about your dad. I keep thinking about him teaching us all to skim stones that summer. I'm here for whatever you need, and I'll check in next week. You don't need to reply to this.\n\n**Death of a pet:**\n> I'm so sorry about Biscuit. Twelve years of that daft tail at the door. He had the best life with you. No need to reply, I'm just thinking of you.\n\n**Miscarriage (they told you directly):**\n> I'm so sorry. I'm not going to say anything except that I'm here, and I'll keep being here, and you don't have to be okay.\n\n**Colleague, peer (you don't control their workload):**\n> Raj, I'm so sorry about your dad. Don't give work a second thought; whatever lands on my side I'll cover. Thinking of you and your family, no need to reply.\n\n**Manager to report, card or email:**\n> I was very sorry to hear about the loss of your mother. Please don't think about work at all right now; we've got everything covered. Take whatever time you need. Thinking of you and your family.\n\n**Voice note, close friend (spoken, no need to call back):**\n> Hey, it's me. I just heard about your mum. I'm so sorry. You don't need to call me back, I just wanted you to hear my voice. I'll drop some food round on Thursday. Love you.\n\n**Weeks or months later (this matters more than the first message):**\n> Thinking about you today. No need to reply.\n\n## Avoid\n- \"Let me know if there's anything I can do.\"\n- \"At least...\"\n- \"I know exactly how you feel.\"\n- Comparing to your own loss in the first message.\n- Silence because you did not know what to say. A short imperfect message beats no message.\n\n## Follow-up cadence\nDay 1, then a week, then a month, then the anniversary. Most people disappear after the funeral; being the one who does not is the whole thing.\n\n## If they don't reply, or push you away\nNo reply is not a signal; it is grief. Keep the cadence going without ever asking why they went quiet. If they say \"I'm fine, I don't need anything\", take it at face value and stay lightly present anyway. If they snap at you, do not defend yourself and do not disappear.\n> No reply needed, just thinking of you. Soup's on your porch, it freezes fine.\n> That's okay, I'm not going anywhere. I'll check in next week.\nIf they ask clearly to be left alone, say \"Okay, I'll be here when you want me\", then send one line in a month."},
{"id":"creator-brand-deal-reply","title":"Replying to brand deals, collab requests and sponsorship offers (creators)","category":"commerce","tags":["creator","brand deal","sponsorship","collab","influencer","rate","negotiation","decline"],"triggers":["brand wants to collab","reply to sponsorship","they offered free product","my rate for a post","decline a brand deal","influencer negotiation","gifting\" offer"],"summary":"Creator replies to brand outreach: asking for details, stating rates, declining product-only deals, and negotiating usage rights, all while staying easy to work with.","updated":"2026-09-27","body":"# Replying to brand deals and collab requests\n\n## Goal\nYou come across as professional and easy, you get paid properly, and you decline mismatches without drama. Brands talk to each other; every reply is reputation.\n\n## Structure for a first reply\n1. **Thanks, brief and specific** (mention their product if you actually like it).\n2. **Ask for the details you need**: deliverables, timeline, budget, usage rights, exclusivity.\n3. **State your baseline** if they haven't given a budget: \"My rate for a single in-feed post starts at $X.\"\n4. **Easy next step.**\n\n## Principles\n- Always ask for the budget before quoting if you can. If they refuse, quote your rate confidently.\n- \"Gifting\" is a no unless you genuinely want the product and it costs you nothing to post. Say no to free-product-for-work kindly and clearly.\n- Usage rights and exclusivity are where the money hides. Ask every time.\n- Rates in writing, deliverables in writing, payment terms in writing. Nothing starts until the brief is agreed.\n- Decline mismatches fast. Do not string brands along.\n- Be the creator who replies within a day and delivers on time; that gets you re-booked more than follower count.\n\n## Examples\n\n**First reply to a vague \"let's collab\":**\n> Hi Sarah, thanks for reaching out, I've actually used the [product] for a while. To put together a proper proposal, could you share: what deliverables you're thinking (feed post, story set, reel), timeline, whether there's paid usage or exclusivity involved, and the budget range? Once I have that I'll come back within a day.\n\n**They ask for your rate:**\n> My rates start at $800 for one reel, $400 for a story set of three, with 30 days of organic usage included. Paid usage and exclusivity are priced separately. Happy to put together a package if you tell me what you're aiming for.\n\n**Declining a gifting-only offer:**\n> Thanks for the offer, I like what you're making. I don't do content in exchange for product, since the work's the same either way, but I'd be happy to talk about a paid post if that's in budget. If not, best of luck with the launch.\n\n**Declining a brand that's not a fit:**\n> Thank you for thinking of me. It's not the right fit for my audience, so I'll pass this time, but I appreciate the reach-out.\n\n**Negotiating when their budget is under your rate:**\n> I appreciate you being upfront on budget. $300 is below where I can do a reel, but I could do a story set of three for that, or a reel with a lighter brief. Would either work?\n\n**They want unlimited usage rights:**\n> I can include 90 days of organic usage in the base rate. Perpetual or paid-media usage I price separately, usually 30% of the content fee per additional 90 days. Let me know what you'd actually use it for and I'll suggest the simplest option.\n\n**Confirming a deal:**\n> Great, to confirm: one reel plus three stories, posted between the 10th and 20th, $1,100 total, 50% upfront and 50% on delivery, 90 days organic usage, no exclusivity. I'll send an invoice for the deposit and a brief for sign-off today.\n\n**Late payment from a brand:** see `chase-late-payment`.\n\n## Avoid\n- \"I'd love to work with you!!\" before you know the terms.\n- Quoting before you know deliverables.\n- Accepting product as payment for real work.\n- Vague \"let me think about it\" replies that never resolve.\n- Public callouts of brands for low offers.\n- Working without a written brief.\n\n## If they lowball, go quiet, or push back\nIf they counter below your floor after you have already offered a smaller package, decline in one line and leave it there. If a brand goes silent after you quote, one follow-up after a week, then move on; silence is a no.\n> Thanks for coming back. $300 isn't something I can do for a reel, so I'll pass this time. If the budget changes for a future campaign, I'd be glad to hear from you.\nIf they get sharp (\"other creators do it for free\"), do not argue the market:\n> That's fair, I'm just not the right fit for this one. Best of luck with the launch."},
{"id":"customer-onboarding-and-welcome","title":"Customer onboarding and welcome messages (after purchase, booking or sign-up)","category":"commerce","tags":["onboarding","welcome","new customer","client","booking","expectations"],"triggers":["welcome email for new clients","what to send after someone books","first message after a customer buys","new client onboarding email template","ask client for info before we start","welcome message for new members","thank you for your order message","set expectations with a new client"],"summary":"The first messages after someone pays or signs up: thank them, confirm what happens next and when, ask for exactly what you need, and name how to reach you. Pre-sale DMs: reply-to-customer-inquiry-dm.","updated":"2026-09-27","body":"# Customer onboarding and welcome messages\n\n## Goal\nThe customer feels sure they made a good choice, knows exactly what happens next, and sends you what you need without being chased. Most refund requests and angry emails start in the gap between paying and hearing anything useful.\n\nBefore they buy: `reply-to-customer-inquiry-dm`. When something goes wrong with the order: `shipping-delay-or-out-of-stock`.\n\n## Structure\n1. **Thank them by name**, for the specific thing they bought or booked.\n2. **What happens next, with dates.** The next two or three steps, not the whole process.\n3. **What you need from them**, as a short list with a deadline, and why.\n4. **How to reach a person**, and your typical reply time.\n5. **One small welcome touch** (a tip, a resource, what past clients found useful). Optional.\n\n## Principles\n- Send it fast. Within an hour of purchase for products, within a day for services. Silence after payment is the moment doubt starts.\n- Confirm the concrete details: date, time, address, what is included. A confirmation that makes them re-check is a failed confirmation.\n- Ask for everything you need once, in one list. Five separate emails asking for one thing each feels disorganised.\n- Set expectations honestly, especially on timelines and response hours. Under-promise slightly, then deliver.\n- Write as a person, not a system. Sign with a name.\n- Keep the first message short. A long welcome pack can be a link or an attachment; the message itself says what they must do now.\n- No upsell in the first message. Let them experience what they bought first.\n\n## Examples\n\n**Service business, after booking (email):**\n> Hi Hannah, thanks for booking your kitchen consultation. I'm looking forward to it. Here's what happens next: I'll visit on Tuesday 14 May at 10am to measure, and you'll have three layout options by 24 May. Before the visit, could you send me photos of the current kitchen and any inspiration images by Friday? Any questions, reply here or text me on 07700 900123. I usually reply within a few hours on weekdays. Maria\n\n**Freelancer, new client kickoff:**\n> Welcome aboard, and thanks for choosing us for the rebrand. To start on Monday I need three things by Thursday: your current logo files, access to the brand folder, and the names of the two people who'll approve designs. First concepts land on 3 June. I'll send a short update every Friday so you always know where things are.\n\n**Online shop, order confirmation:**\n> Thanks for your order, Sam! Your candles are being poured this week and will ship by Thursday; you'll get a tracking link the moment they leave. Any problem, reply to this email and you'll get me, not a bot. Jade, Wick & Oak\n\n**Membership or class, first message:**\n> Welcome to the studio, Aisha! Your first class is Wednesday at 6:30pm. Come 10 minutes early so we can show you around, and bring water and a towel (mats are here). If you need to change the booking, you can do it in the app up to 12 hours before.\n\n**Asking for missing information, gently:**\n> Hi Dev, quick nudge on the onboarding form. I need it by Wednesday to keep your launch on 12 June. It takes about 10 minutes, link here. If anything on it is unclear, tell me and I'll fill in what I can.\n\n**Setting availability and response-time expectations:**\n> One practical note: I work Monday to Thursday and reply to email within one working day. For anything urgent on launch week, text me and I'll pick it up the same day.\n\n## Avoid\n- \"Your order has been received\" and nothing else.\n- Asking for information piecemeal over several days.\n- Promising timelines you cannot keep, to sound impressive.\n- A no-reply address for a service where people will have questions.\n- A welcome message that opens with terms and conditions or penalties.\n- Upselling before they have received anything.\n\n## If it goes badly\nIf they miss the deadline for what you need, send one friendly reminder with the concrete consequence (\"otherwise launch moves to the 19th\"), not a warning. If they come back anxious before you have started, answer quickly and restate the next step and date; reassurance is usually about uncertainty, not about you. If you realise you set an expectation you cannot meet, tell them as early as possible with a new date, before they have to ask.\n> No problem at all. Just so you know, if I get the files by Monday we're still on track for the 12th; after that it moves to the 19th.\n> Quick heads-up: the first concepts will be with you on 5 June rather than the 3rd. I'd rather tell you now than let it slip quietly."},
{"id":"de-escalate-argument","title":"De-escalating an argument with a partner or friend","category":"personal","tags":["argument","fight","partner","de-escalate","conflict","repair"],"triggers":["we had a fight","they're mad at me","argument with my girlfriend","boyfriend is upset","cool things down","calm them down","make peace"],"summary":"How to lower the temperature of a live argument by text or in person, without capitulating or winning, so the real conversation can happen later. Two other people fighting: mediating-between-two-people.","updated":"2026-09-27","body":"# De-escalating an argument\n\n## Goal\nGet both of you out of fight mode. Not to resolve the issue, not to win, not to surrender. Resolution comes later, calmer.\n\n## Structure\n1. **Name what's happening, not who's wrong.** \"We're both heated.\"\n2. **Take responsibility for your part, specifically**, even if it's small. \"I got sharp with you.\"\n3. **Reflect their feeling accurately**, without agreeing with their argument. \"You feel like I wasn't listening.\"\n4. **Propose a pause with a return time.** \"Can we pick this up after dinner?\" A pause without a return time feels like abandonment.\n5. **One line of the relationship being bigger than this.**\n\n## Principles\n- Nobody has ever been calmed by \"calm down.\"\n- Being right is not available right now. Take it off the table.\n- Do not litigate facts mid-fight. \"That's not what I said\" restarts it.\n- Say less. Every sentence in an argument is ammunition.\n- If you need to leave, say when you'll be back. \"I need 20 minutes and then I'm coming back to this.\"\n- Do not text long paragraphs to an angry person. They read them as an essay against them.\n\n## Examples\n\n**Partner, text, mid-fight:**\n> I don't want to keep going like this over text. I'm sorry I snapped. Can we talk tonight when we're both home? I love you and I want to actually hear you.\n\n**Friend, they feel let down:**\n> I think I got defensive and that's not fair to you. You're right that I dropped the ball. Can I call you tomorrow and we sort it out properly?\n\n**In person, script:**\n> Okay. I'm getting heated and I don't want to say something I'll regret. I'm not walking away from this, I just need twenty minutes. I'll come find you.\n\n**When they're angry and you don't yet understand why:**\n> I can see you're really upset and I want to understand it. I'm not going to argue. Can you tell me what the worst part was?\n\n**When you were actually wrong:**\n> You're right. I was wrong about that and I'm sorry. Let me fix it.\n\n## Avoid\n- \"You're overreacting.\"\n- \"I'm sorry you feel that way.\"\n- \"Fine.\" / \"Whatever.\"\n- \"We've been over this.\"\n- Bringing up a previous fight.\n- Ultimatums in the heat of it.\n- Long texts. Three sentences maximum.\n\n## After the pause\nCome back on time. Open with: \"Okay, I've been thinking. Here's what I heard you say, tell me if I've got it wrong.\" Then listen before you respond. See `set-boundary` if the same fight keeps recurring.\n\n## If they refuse the pause or keep going\nIf they keep sending angry messages after you have proposed a pause, do not answer each one. One line, then silence until the return time. If they say \"no, we're doing this now\", you can still hold the pause without walking out on them: name the time and stay reachable.\n> I'm not ignoring you. I said 8pm and I mean it. I'll come find you then.\n> I know you're still angry. I'm not going anywhere, I just can't do this well right now.\nIf every argument ends with them refusing pauses and escalating, that is a pattern to talk about when calm. See `set-boundary`."},
{"id":"decline-invitation","title":"Declining an invitation without hurting the relationship","category":"personal","tags":["decline","no","invitation","social","plans"],"triggers":["can't make it","don't want to go","turn down invite","say no to party","skip the wedding","decline dinner"],"summary":"How to say no to an event or plan so the host feels the no is about logistics or capacity, not about them. A favour or loan: decline-request.","updated":"2026-09-29","body":"# Declining an invitation\n\n## Goal\nThe host should finish reading and think \"fair enough, they still like me\", not \"was it something I did?\"\n\n## Structure\n1. **Thank for the specific invite** (one clause).\n2. **Clear no** in the first two lines. Do not bury it.\n3. **One reason, short**, or none. A true simple reason beats a detailed excuse. Detailed excuses invite negotiation.\n4. **Signal the relationship** with a concrete alternative or a specific warm line.\n5. **Stop.** No second apology.\n\n## Principles that matter here\n- The longer the excuse, the more it sounds like a lie.\n- \"Maybe\" is crueller than \"no\" because it makes them plan around you.\n- If you would go if it were a different day, say so and propose one. If you would not go regardless, do not propose anything; just be warm.\n\n## Examples\n\n**Friend's party, text:**\n> Ah, I can't do Saturday, I've already got plans I can't move. Gutted to miss it. Let's do a proper catch-up the week after? I'll cook.\n\n**Wedding, message to a not-close friend:**\n> Thank you so much for inviting us, it means a lot. We can't make it on the 14th. We'll be thinking of you both and would love to take you out to celebrate once you're back.\n\n**Recurring thing you want to stop going to, no reason:**\n> I'm going to sit this one out. Have a great time and send me photos.\n\n**Work social:**\n> I'll pass on Thursday drinks this time, but enjoy. Count me in for the next one.\n\n## Avoid\n- \"I'll try to make it\" when you know you will not.\n- Listing your whole week.\n- \"Sorry sorry sorry\".\n- Cancelling on the day when you knew a week ago.\n\n## If they push\n> I really can't this time. Next one, I promise.\nRepeat once. Do not add new reasons; new reasons are new things to argue with."},
{"id":"decline-meeting-or-protect-time","title":"Declining a meeting or protecting your time","category":"work","tags":["meeting","calendar","decline","async","focus time","vendor","boundaries"],"triggers":["decline a meeting invite","too many meetings","can we do this async","leave a recurring meeting","quick call?","shorten the meeting","push it to tomorrow","say no to a vendor call","protect my focus time"],"summary":"Saying no to meetings, proposing async, shortening or leaving recurring ones, and turning down \"quick call?\" from strangers, with wording for juniors, peers and seniors.","updated":"2026-09-27","body":"# Declining a meeting or protecting your time\n\n## Goal\nThe meeting does not happen, or happens smaller, and the organiser still gets what they wanted from you. Nobody feels dismissed.\n\n## Structure\n1. **Name what they need**, not the meeting. \"You need a decision on the vendor\" or \"you want my read on the draft.\"\n2. **Decline the format, not the person.** \"I'll skip the call\" is about the call.\n3. **Give them the thing another way**: a written answer, a shorter slot, a named colleague, a date.\n4. **One line, no defence.** Reasons about the calendar invite debate; a plain alternative does not.\n5. **Close with the yes**: \"does that work?\" or \"I'll send it by 3.\"\n\n## Principles\n- Replace, don't reject. A decline with a working alternative is a favour to the organiser, because it gets them the outcome faster.\n- A meeting with no agenda is a question. Ask for the question, then answer it.\n- Juniors: decline the format and offer the deliverable. Do not say you are busy; say what you will send and when.\n- Seniors: say no plainly. Your no needs less padding than you think, and padding reads as indecision.\n- Recurring meetings die quietly. Nobody is offended when you leave one with a clean handover of what you contributed.\n- Strangers and vendors asking for \"15 minutes\" are asking for your attention, not your time. Written answers cost them effort, which is the filter.\n- Same-day requests are usually habit, not urgency. Ask once whether it truly cannot wait; most cannot answer yes.\n\n## Examples\n\n**Declining an invite, peer to peer:**\n> I'll skip this one. If you need my input on the pricing page, I can comment on the doc by Thursday morning. Does that cover it?\n\n**Proposing async instead, to a senior colleague:**\n> Happy to help on the Q4 forecast. Rather than a meeting, I can send you my numbers and the three assumptions behind them by end of day tomorrow, and we can do a 10-minute call only if something doesn't add up. Would that work for you?\n\n**Shortening a meeting (you are the organiser or a key attendee):**\n> Could we do this as 20 minutes instead of an hour? The only open point is the launch date; if everyone reads the two-pager first, we should get through it fast. I've updated the invite.\n\n**Leaving a recurring meeting, junior to manager:**\n> I'd like to drop out of the Tuesday sync from next week. My part is now covered by the status doc, which I'll keep updated before each meeting. If a topic needs me, ping me and I'll join for that slot. Okay with you?\n\n**Leaving a recurring meeting, senior to peers:**\n> I'm stepping out of the weekly ops review. Lena has full context and will represent our side. Reach me directly if something needs my sign-off.\n\n**Saying no to \"quick call?\" from a stranger or vendor:**\n> Thanks for reaching out. I don't take intro calls, but if you send a short note on what it does and rough pricing, I'll read it and reply if it fits what we're working on.\n\n**Pushing a same-day request to tomorrow:**\n> I can get this to you by 10am tomorrow with the numbers checked. If you need something today, I can send a rough version by 4, unchecked. Which do you prefer?\n\n**Declining a meeting from your own manager, offering the substance:**\n> I can't make 3pm today. I've put my update and the two decisions I need from you in [doc]; if you drop your answers there, I'll move on it this afternoon and we can skip the call.\n\n## Avoid\n- \"I'm swamped\" or \"my calendar is crazy\". Everyone's is; it invites \"just 15 minutes\".\n- Declining without saying what you will do instead. That is a wall, not an alternative.\n- Accepting and then not turning up. Decline early; a no on the day costs more than a no now.\n- Explaining your focus-time philosophy. Nobody asked, and it sounds superior.\n- \"Let me check and get back to you\" when you already know it is a no.\n- Silently ignoring a stranger's third follow-up when one clear \"not now\" would end it.\n\n## If they push back\nWhen they insist it has to be a meeting:\n> Sure, let's do it. Can you send me the one decision you need from me so I come prepared, and let's cap it at 20 minutes?\nWhen a vendor keeps chasing:\n> This isn't something we're looking at this year. Please take me off the follow-up list; if that changes, I'll get in touch.\nWhen your manager says the meeting matters:\n> Understood, I'll be there. To make it worth the hour, can we put the agenda in the invite?\nThen attend, contribute, and raise the format question again after two more sessions, with evidence."},
{"id":"decline-offer-or-candidate","title":"Declining a job offer, or rejecting a candidate","category":"work","tags":["job offer","decline","reject candidate","hiring","recruiter","turn down"],"triggers":["turn down the job","decline the offer","reject a candidate","tell them they didn't get it","withdraw from the process","decline recruiter"],"summary":"How to decline an offer so the door stays open, and how to reject a candidate so they leave with dignity and speak well of you.","updated":"2026-09-27","body":"# Declining a job offer, or rejecting a candidate\n\n## Goal\nWhichever side you are on, the other person hears a clear no early, feels treated as a person, and would work with you or recommend you later.\n\n## Structure\n1. **Specific thanks** for the time or the work.\n2. **The decision, plainly**, within the first three sentences.\n3. **One honest reason, or none.** Never a fabricated one.\n4. **One genuine positive** about them or the role.\n5. **Door open only if it is.**\n\n## Declining an offer\n\n**Goal:** they remember you as gracious, and would hire you again.\n\n**Structure:** thanks (specific) → clear decline → brief reason or none → warmth → offer to stay in touch.\n\n**Principles**\n- Decide quickly and tell them quickly. Holding an offer while you wait on another is fine for a few days; say so.\n- Do not lie about the reason. \"I've accepted another role that's a closer fit for what I'm looking for right now\" is honest and complete.\n- Do not use the decline to negotiate unless you actually would take it at a different number; if you would, say so plainly instead.\n- Thank the specific people who spent time.\n\n**Examples**\n\n*Accepted elsewhere:*\n> Hi Rachel,\n> Thank you for the offer and for the time you and the team put into the process; the conversation with Dev about the roadmap was one of the best interviews I've had. After a lot of thought I've decided to accept another role that's a closer fit for where I want to take the next few years. It wasn't an easy call. I'd love to stay in touch, and I'll be following what you build.\n> All the best,\n> Kai\n\n*Declining on compensation, honestly:*\n> I've really enjoyed the process and I'd like to be transparent: the gap on base is the one thing stopping me. If there's flexibility to get to [number] I'd accept today. If not, I completely understand, and I'll decline with genuine thanks.\n\n*Withdrawing mid-process:*\n> I want to let you know early rather than late: I'm withdrawing from the process. My circumstances have changed and it wouldn't be fair to keep taking your time. Thank you for the conversations so far.\n\n*Recruiter cold message:*\n> Thanks for reaching out. I'm not looking right now, but I'd be happy to hear from you in six months or so.\n\n## Rejecting a candidate\n\n**Goal:** they feel treated as a person, they know it is final, and they would apply again or recommend you.\n\n**Structure:** thanks → clear decision, early → one specific positive → one honest, useful reason if you can give one → door open (only if true).\n\n**Principles**\n- Tell them fast. Waiting weeks is the most common complaint.\n- Call finalists. Email everyone else, but personalised.\n- Be specific enough that it is clearly not a template.\n- Do not give feedback you cannot defend. If you cannot say it plainly, say less.\n- \"We'll keep your CV on file\" only if you will.\n\n**Examples**\n\n*Finalist, email after a call:*\n> Hi Mona,\n> Thank you for the time you put into the process, especially the case study, which was genuinely strong. We've decided to go with another candidate whose background is closer to the infrastructure side of the role. This was a close decision. If a role on the product side opens in the next year, I'd like to reach out, if you'd be open to it.\n> Best,\n> Theo\n\n*Early-stage, brief but human:*\n> Hi Sam, thanks for applying and for the thoughtful cover note about [specific]. We're not moving forward this time; the shortlist skewed toward candidates with [X], which isn't a comment on your ability. I hope you find the right fit soon.\n\n*After an interview that went badly:*\n> Thanks for coming in on Tuesday. We won't be taking it further. If it's useful: the role needs someone who can talk through trade-offs in real time, and that part of the conversation didn't land the way we needed. That's a skill that builds fast with practice. Best of luck.\n\n## Avoid\n- \"We had many strong candidates\" as the whole message.\n- Ghosting after an interview.\n- Feedback that is really just a list of what they lacked.\n- \"Unfortunately\" as the first word.\n- Leaving the door open when it's closed.\n\n## If they push back\nA declined offer sometimes brings a counter or \"what would change your mind\". Answer honestly once: a number, a change, or nothing. If nothing, say so and do not get drawn into a second round. A rejected candidate may argue or ask for more feedback: one more specific point if you have one, then repeat the decision kindly and close.\n> I appreciate the counter, and it's a real one. My decision isn't about the package, so I'm going to hold to it. Thank you again.\n> I understand it's disappointing. The decision is final, and the one thing I'd work on is [specific]. I meant what I said about the product role."},
{"id":"decline-request","title":"Declining a request or favour","category":"personal","tags":["decline","no","favour","boundary","request"],"triggers":["say no to a favor","don't want to help","can't lend","asked me to do something","how to refuse","turn down request"],"summary":"Saying no to a one-off request for help, money, time or effort, keeping their dignity and your limits intact. An event: decline-invitation. The same ask again and again: set-boundary.","updated":"2026-09-29","body":"# Declining a request\n\n## Goal\nA clean no that does not require a lie, a lecture, or a negotiation.\n\n## Structure\n1. **Acknowledge the ask** so they know you understood it (not that you agree).\n2. **The no**, plainly. \"I can't\" or \"I'm not able to\" or \"I'm going to say no to this one.\"\n3. **Optional single reason.** Only if it is true and not arguable (\"I'm at capacity\", \"I don't lend money to friends, it's a rule I keep for everyone\").\n4. **Offer a smaller yes if you genuinely have one** (a referral, a shorter version, a later date). If you do not, skip this step. A fake alternative is worse than none.\n5. **Warm neutral close.**\n\n## Principles\n- A no with a reason invites debate on the reason. A no with a rule (\"I don't do X\") is much harder to argue with.\n- \"Right now\" makes the no temporary. Only use it if it is.\n- Do not apologise for having limits. One \"sorry\" maximum, and only if you genuinely regret it.\n\n## Examples\n\n**Friend asks to borrow money:**\n> I'm going to say no on this one. I have a rule about not lending to friends, because I've watched it go badly for people I love. If it would help, I'm happy to sit down with you and look at options.\n\n**Colleague asks you to take on their work:**\n> I can see you're slammed. I can't take this on, I'm already past capacity through the end of the month. If it helps, I can walk you through how I set up the template so it goes faster.\n\n**Family asks you to host again:**\n> I love having everyone over, and I can't do it this year. Could we rotate and do it at yours, or split a place?\n\n**Someone asks for free professional advice/work:**\n> I'd rather be upfront than give you a half answer: this is the kind of thing I do professionally, so I can't do it for free. If you want to book a proper session, here's the link. Otherwise, [resource] is a really good starting point.\n\n**Stranger or acquaintance, low stakes:**\n> Not something I can help with, but good luck with it.\n\n## Avoid\n- \"I'll see what I can do\" when you already know.\n- Explaining your finances, your calendar, your mental health as justification. You do not owe it.\n- Ghosting the request. A no delivered quickly is a kindness; silence is not.\n\n## If they guilt-trip\n> I understand you're disappointed. My answer's the same.\nThen stop replying on that thread. Do not re-explain."},
{"id":"deliver-bad-news","title":"Delivering bad news","category":"personal","tags":["bad news","disappointing","cancel","rejection","difficult"],"triggers":["have to tell them","break the news","disappoint","let them know it fell through","tell them no","cancel on them"],"summary":"How to deliver news someone will not want, in a way that is clear early, kind throughout, and forward-looking at the end. Announcing to a team you manage: team-announcements-as-a-manager.","updated":"2026-09-28","body":"# Delivering bad news\n\n## Goal\nThey understand the news in the first two lines, feel it was delivered with care, and know what happens next.\n\n## Structure\n1. **One line of warning** so they brace: \"I've got some news you won't love.\"\n2. **The news, plainly, early.** Do not make them read three paragraphs to find it.\n3. **One sentence of why**, if there is a why they need. Not a defence.\n4. **Acknowledge what it means for them.**\n5. **What happens next / what you can offer.**\n6. **Availability**: \"I'm around if you want to talk.\"\n\n## Principles\n- Delay is cruelty. The kindest version is the fast one.\n- Do not soften the news into ambiguity. \"It might be tricky\" when you mean \"no\" makes them hope and then hurts twice.\n- Do not make them comfort you. Your feelings about delivering it are for someone else.\n- Deliver in the richest channel you reasonably can. Text for small things, call for big ones. If it has to be text, say you are happy to talk.\n\n## Examples\n\n**Plans fell through, text:**\n> Bad news: the cabin fell through, the owner double-booked. I'm really sorry, I know you'd cleared the weekend. I've found two other options nearby and I'll send them tonight. Still on if you are.\n\n**You can't pay someone back on time:**\n> I need to be straight with you. I can't pay you the £400 on Friday like I said. I can do £200 Friday and the rest on the 28th. I'm sorry for the change, I know you were counting on it.\n\n**Telling a friend you're not coming to their wedding abroad:**\n> I've gone back and forth on this and I don't want to keep you guessing: I'm not going to be able to make it to Portugal. It's the cost, honestly, and I'd rather tell you now than keep you hoping. I'm gutted. I'd love to do something to celebrate you both here before or after.\n\n**Telling someone a mutual friend is unwell, message:**\n> I wanted you to hear this from me rather than through the grapevine. Tom's been diagnosed with [X]. He's okay to talk about it and asked me to let people close to him know. Call me if you want to talk it through.\n\n**Phone call opener, when it is too big for a text:**\n> Have you got five minutes? I've got some news that isn't good, and I wanted to tell you myself. The house sale fell through this morning. Here's what happens next.\n\n**Email, project cancelled:**\n> Hi team,\n> I'll get straight to it: the Harbour project has been cancelled by the client as of this morning. This isn't about the quality of the work, which they were explicit about. I know several of you have put months into it and that's a hard thing to hear. I'll be meeting each of you this week to talk about what you move to next. My door's open before then.\n> Sam\n\n## Avoid\n- \"I don't know how to say this...\" followed by not saying it.\n- Burying the news after praise.\n- \"Everything happens for a reason.\"\n- Listing all the ways it is not your fault.\n\n## If they react badly\n> I get it. Take the time you need. I'm not going anywhere.\nDo not argue with the reaction."},
{"id":"disagree-without-conflict","title":"Disagreeing without starting a fight","category":"personal","tags":["disagree","pushback","opinion","argument","debate"],"triggers":["I don't agree","push back","they're wrong","tell them I think differently","disagree with friend","argue politely"],"summary":"How to state a different view so it is heard as a contribution rather than an attack, in personal and group settings.","updated":"2026-09-28","body":"# Disagreeing without conflict\n\n## Goal\nYour view is on the table, clearly, and the other person does not feel diminished for holding theirs.\n\n## Structure\n1. **Reflect the part of their view you can honestly agree with**, or the goal you share.\n2. **Signal the disagreement** (\"here's where I land differently\").\n3. **Your view, stated as your view**, with one reason.\n4. **Curiosity**: a genuine question about their reasoning, or an invitation to correct you.\n\n## Principles\n- \"And\" not \"but\" after the acknowledgement. \"But\" erases what came before.\n- Disagree with the idea, not the person. \"I see it differently\" not \"you're wrong.\"\n- One reason, your strongest. Three reasons sound like a case for the prosecution.\n- Offer your confidence level honestly. \"I'm fairly sure\" and \"I could be wrong here\" are both useful, if true.\n- In a group, disagree in a way that lets them save face in front of others. Or take it private.\n\n## Examples\n\n**Friend's opinion, casual:**\n> I actually see that film differently. I found the ending rushed, mostly because we never saw why she changed her mind. What made it work for you?\n\n**Group chat, someone says something you think is off:**\n> I'd gently push back on that one. I don't think the new bike lanes caused the traffic, the roadworks on Hill Street started the same week. Could be missing something though.\n\n**Partner, about a decision:**\n> I hear that you want to drive through the night, and I know it's the faster option. I'm not comfortable with it because we'd both be exhausted on the motorway. Could we stop halfway and leave early instead?\n\n**Someone senior, in a meeting:**\n> I want to make sure I understand the goal. If it's hitting the March launch, I'd suggest cutting the reporting feature rather than adding weekend work, because it's the piece with the most open bugs. Happy to be wrong on this.\n\n**Disagreeing with a plan everyone likes:**\n> I'm going to be the annoying one. I'm worried the venue has no step-free access, and two of the guests use wheelchairs. If we've already thought about it and I missed it, ignore me.\n\n## Avoid\n- \"With all due respect.\"\n- \"Actually,\"\n- \"I'm just playing devil's advocate.\"\n- Repeating your point louder when they do not agree the first time.\n- Piling on evidence. If one strong reason did not move them, five will not either.\n- Winning. Being right and losing the relationship is not smooth.\n\n## If it escalates\nIf they get heated, stop adding reasons and lower the stakes: name that you disagree, that it is fine to, and step off. If the disagreement matters for a decision (work, money, a shared plan), move from who is right to what you will do: agree a test, a trial period, or who gets the final call. If they keep returning to it, you do not have to keep defending your view; saying it once was enough.\n> I don't think we're going to agree on this one, and that's okay. I'd rather keep this easy between us than win the point.\n> We see it differently, and it's your call on this one. I've said my piece, I'll back whatever you decide."},
{"id":"end-conversation-gracefully","title":"Ending a conversation gracefully","category":"personal","tags":["exit","end conversation","wrap up","leave","goodbye","too long"],"triggers":["how to end the conversation","get out of this chat","wrap it up","stop texting","leave the conversation","they keep talking"],"summary":"How to close a text thread, a call, or an in-person chat without being abrupt or leaving it dangling.","updated":"2026-09-27","body":"# Ending a conversation\n\n## Goal\nThe other person feels the conversation was complete, not abandoned, and you are free.\n\n## Structure\n1. **Signal the ending** with a summary or a warm recap line.\n2. **Give a reason or none** (a reason is only needed if cutting off mid-flow).\n3. **A forward hook** if you want to talk again; a clean close if you do not.\n4. **Close.**\n\n## Principles\n- A conversation that trails off (\"anyway...\") makes the other person do the closing. Close it yourself.\n- Do not fake a reason to leave. \"I've got to run\" when you do not is a small lie that people can sense. \"I'm going to sign off\" needs no reason.\n- The last message should not be a question, unless you want it to continue.\n- On text, the final message is often just an emoji or \"talk soon\". Do not overthink it.\n\n## Examples\n\n**Text thread that has run its course:**\n> Okay, I'm going to head off. Really good to catch up, let's do it properly soon.\n\n**Ending without a future promise:**\n> Great talking. Take care of yourself.\n\n**Phone call, someone who keeps talking:**\n> I've got to jump off in a minute. Before I go, [one last thing]. Right, talk soon, bye.\nSay \"bye\" and hang up. You do not need them to say it first.\n\n**In person, party:**\n> I'm going to go say hi to [person] before they leave. Really good to meet you.\nOr: \"I'm going to grab a drink, can I get you one?\" (then do not come back).\n\n**Group chat you want out of:**\n> I'm going to duck out of this chat, my notifications are out of control. Message me directly any time.\n\n**Someone messaging late at night:**\n> Heading to bed. Talk tomorrow.\n\n**A conversation that got heavy and you're tired:**\n> I'm running out of steam and I don't want to give this less than it deserves. Can we pick it up tomorrow?\n\n## Avoid\n- \"Anyway...\" with nothing after it.\n- Replying with shorter and shorter messages until they get the hint.\n- Leaving on read after they asked something.\n- \"I'll let you go\" (it is you who wants to go; own it).\n- Multiple rounds of goodbye.\n\n## If they keep going, or take it badly\nIf they reply to your close with a new question, answer in one line and close again, without a question of your own. If they sound hurt (\"wow, okay\"), do not retract the exit; give warmth without reopening. On a call, restate that you are going and then go; the second goodbye is the one that counts.\n> Ha, quick one: yes, Tuesday works. Right, I'm properly off now, night!\n> Not a brush-off, I promise. I'm just done for the day. Talk properly this weekend?\nIf someone repeatedly ignores your exits, the conversation is no longer the issue; see `set-boundary`."},
{"id":"escalate-an-issue","title":"Escalating an issue","category":"work","tags":["escalation","skip-level","vendor","account manager","customer support","blocked","complaint"],"triggers":["escalate to my manager","go over someone's head","escalate to skip level","escalate with a vendor","escalate a support ticket","my ticket is being ignored","ask to speak to a supervisor","escalation email","nobody is responding"],"summary":"Escalating to a manager, a skip-level, a vendor or a support tier without burning the person you go past, with the heads-up, the escalation email itself, and what to send when it is ignored.","updated":"2026-09-28","body":"# Escalating an issue\n\n## Goal\nThe decision-maker gets the facts, the impact and the one decision you need, in under a minute. The person you escalated past hears it from you first and is not embarrassed.\n\n## Structure\n1. **Give the person a heads-up before you go around them.** One message: what you are escalating, why, and that it is about the timeline, not them.\n2. **Subject line that states the ask and the deadline.** \"Decision needed by Thu: vendor contract renewal.\"\n3. **Facts.** What happened, with dates. No adjectives.\n4. **Impact.** What it costs if unresolved: money, a date, a customer.\n5. **What you have already tried.** Two or three lines. This is what earns the escalation.\n6. **The specific decision you need, and by when.** One ask, one date.\n7. **Close with your recommendation.** Make the yes easy.\n\n## Principles\n- Escalate the problem, not the person. \"Open 11 days\" is a fact. \"Support is useless\" is a fight.\n- The heads-up is the whole difference between escalation and betrayal. Send it every time.\n- A skip-level is the last resort inside your company. Try your manager first, and say in the email that you did.\n- Give a real deadline tied to a real consequence. \"By Thursday, because the release ships Friday\" beats \"ASAP\".\n- Keep it under 150 words; it will be read on a phone between meetings.\n\n## Examples\n\n**Heads-up before escalating past a colleague:**\n> Quick note so it doesn't come from someone else: I'm raising the API timeout issue with Lena today, because we're at day 11 and the client's go-live is Friday. Not a comment on you, I know your queue is stacked. I'll keep you copied.\n\n**Escalation email to your manager:**\n> Subject: Decision needed by Thu: Hollis go-live\n> The Hollis integration has failed staging three times since the 14th (API timeouts, ticket #4471). Their go-live is Friday and the contract has a penalty clause if we miss it. I've worked with Ravi in platform daily and we've narrowed it to the auth service, but the fix needs a config change only Ops can make. I need you to approve Ops prioritising #4471 today, ahead of Q3 reporting work. My recommendation: approve, and I'll own communicating the slip on the reporting work.\n\n**Skip-level, after your manager has not acted:**\n> Hi Lena, I raised the Hollis go-live risk with Mark on the 16th and 19th and I know he's stretched with the reorg. We're now two days from a contractual deadline and I need a decision on Ops priority that Mark hasn't been able to get. Could you either approve the priority change or tell me who can? Mark is copied. Details below.\n\n**Vendor account manager:**\n> Hi Jordan, ticket #88210 has been open since 3 September with no update since the 10th. It's blocking our payroll export and our next run is the 27th. Support has asked for logs twice; we've sent them both times. Can you get an engineer assigned by end of day Wednesday and confirm here? If that's not possible, I need to know now so we can run payroll manually.\n\n**Customer support escalation, as a customer:**\n> This is my third contact about order #55120 (refund of $340, promised on 2 September). Case numbers so far: 55120-A and 55120-B. Please escalate to a supervisor or the refunds team and confirm a refund date. If I don't have a date by Friday, I'll raise a chargeback with my card provider.\n\n**Escalating to a support tier, technical:**\n> Requesting escalation to tier 2. Intermittent 502s on our production tenant since the 12th, roughly 3% of requests, reproduced with the curl command below. Impact: customer-facing checkout errors. Please assign an owner and share an ETA for first response.\n\n**Closing the loop with the person you escalated past:**\n> Update: Lena approved the Ops priority and the fix is in. I've made sure she knows the diagnosis was yours.\n\n## Avoid\n- Escalating with no ask. It gets filed, not actioned.\n- Copying half the company. Copy the people who can act and the one you went past.\n- Threats you will not carry out. If you say chargeback, be ready to file it.\n- Two problems in one email. One problem, one decision.\n\n## If it goes badly\n\n**The escalation is ignored:**\nWait one business day past your deadline, then reply on the same thread.\n> Following up, the deadline I mentioned was yesterday. Are you the right person for this decision, or should I take it to someone else? Either answer helps.\n\n**They say it is not a priority:**\n> Understood. So I can plan, can you confirm in writing that we're accepting the [Hollis penalty / payroll delay] as the cost? I want to make sure that's a decision and not a default.\n\n**The person you went past is upset:**\n> I hear that it landed badly. I sent you the heads-up first because I didn't want you blindsided. I'd rather work this out with you than around you. Can we talk for ten minutes?"},
{"id":"family-pressure-and-nosy-questions","title":"Family pressure and nosy questions","category":"personal","tags":["family","relatives","boundary","holidays","marriage","kids","deflection"],"triggers":["relatives keep asking when I'm getting married","family asking about kids","nosy aunt","holiday dinner questions","mum keeps asking about my weight","family pressure to move home","dad asks about my salary","relatives push religion","how to deflect family questions","parents pushing me to change careers"],"summary":"Warm lines for relatives who push on marriage, kids, career choices, weight, money, religion or moving home, a firmer version for repeat offenders, and when soft is right. Other repeated intrusions: set-boundary.","updated":"2026-09-29","body":"# Family pressure and nosy questions\n\n## Goal\nThe question stops without a scene. You keep your privacy, the relative keeps their dignity, and the table moves on. You are not trying to win, educate, or get them to agree that the question was rude.\n\n## Structure\n1. **Light acknowledgement.** A smile, a laugh, \"ah, the classic.\"\n2. **Short non-answer.** \"When there's news, you'll be the first to know.\"\n3. **Redirect immediately** to something they like talking about. The redirect is the deflection; steps 1 and 2 are just the runway.\n4. **If it comes back a second time**, repeat the same non-answer, nearly word for word. Consistency ends it. Variation invites a new angle.\n5. **If it comes back a third time, or with a dig attached**, move to the firmer version below.\n\n## Firmer version, for repeat offenders\n1. **Name it as a topic, not a person.** \"This one is off the table.\"\n2. **Say what you will do.** \"If it comes up again I'll go help in the kitchen.\"\n3. **Follow through** the next time, calmly, no announcement.\n4. **Stay warm on everything else.** The boundary is about one subject, not the relationship.\n\n## Principles\n- Do not explain. A reason (\"we're trying, actually\", \"I'm saving\") is an invitation to advise.\n- Humour works once. Repeated jokes read as nerves and keep the topic alive.\n- The same sentence every time. You are teaching them that the door does not open.\n- You can be private without being cold. Most relatives ask because they care, badly.\n- A cross-cultural note: in many families, a soft deflection is not avoidance, it is the normal and respectful way to close a topic, and a stated hard boundary can land as a rupture. If that is your family, treat deflection as the whole playbook and keep the firmer version as a last resort for someone who is genuinely hurting you, not someone who is merely annoying.\n\n## Examples\n\n**\"When are you getting married?\":**\n> Ha, you and my mother should form a committee. When there's news, you'll hear it first. Now tell me about the garden, Dad said you finally beat the slugs.\n\n**\"When are you having kids?\" (possibly painful, keep it short):**\n> That's between me and [partner], but I love that you're keen. Have you seen the photos from [cousin]'s trip? Pass me your phone.\n\n**Career, \"still doing that job?\":**\n> Still doing it, still like it. Not much to report. How's the knee, did the physio help?\n\n**Weight or appearance:**\n> I'm happy and healthy, and I'm not discussing my body at dinner. Can you pass the potatoes?\n\n**Money, \"how much are you making now?\":**\n> Enough to pay for lunch next time, which I'll do. How did the house sale go in the end?\n\n**Religion, \"you'll come back to church eventually\":**\n> I know it matters to you, and I'm grateful for that. It's not something I'm going to debate. Are you still doing the Tuesday choir?\n\n**Moving home, \"when are you coming back for good?\":**\n> I'm settled where I am for now, and I'll always come for the holidays. Let's make the summer one longer. When does the school break start for the kids?\n\n**Firmer version, by text after the third time:**\n> I know you mean well, and I need you to stop asking about [kids / marriage / my weight]. It's off the table. I'd love to talk about anything else on Sunday. See you at 1.\n\n## Avoid\n- Defending your choice with facts and studies. You are not on trial.\n- \"It's none of your business.\" True, and it makes the whole table tense. Save the sharp version for someone who has earned it.\n- Recruiting another relative to fight for you at the table. Handle it yourself, in one line, and let it drop.\n- Pre-empting the question in a long group message before the holiday. It usually makes things worse.\n- Answering the subtext (\"you think I've failed\") instead of the words.\n\n## If they push back\nIf the relative sulks, escalates or says you have changed, hold the line and stay kind:\n> I'm not upset with you and I'm not going to talk about that one. Come help me with the dishes.\n\nIf a parent takes the firmer version as rejection, address the relationship, not the topic:\n> Mum, I love you and I want the time we have together to be good. That's exactly why I'm asking for this one subject to rest.\n\nIf a relative is deliberately cruel rather than clumsy, you are allowed to leave the room. One line as you go, no explanation:\n> I'm going to step out for a bit. Back in ten."},
{"id":"first-message-to-stranger","title":"First message to a stranger (dating, networking, community)","category":"personal","tags":["cold message","first message","dating app","networking","dm","stranger","opener"],"triggers":["first message on hinge","message a stranger","opener","slide into dms","reach out to someone I don't know","message someone I admire"],"summary":"Personal first contact that gets a reply: dating apps, someone you admire, a community or event. Specific, short, easy to answer. A business pitch (sales, press, partnership): cold-outreach.","updated":"2026-09-29","body":"# First message to a stranger\n\n## Goal\nThey reply. That requires: it is clearly about them, it is easy to answer, and it does not ask for much.\n\n## Structure\n1. **Proof you looked**: reference one specific thing from their profile, post, work.\n2. **A reaction or question about that thing.** Open questions that are easy to answer.\n3. **Nothing about you** beyond a clause, unless it connects to their thing.\n4. **No ask** in the first message (dating), or a tiny, clear ask (professional).\n\n## Principles\n- \"Hey\" and \"how's it going\" put all the work on them. Give them something to grab.\n- Specific beats clever. A genuinely curious question about their thing beats a joke.\n- Short. Two to four sentences. A wall of text to a stranger is a red flag.\n- Compliments on appearance (dating) or achievements (professional) are the least interesting thing you can say; everyone says them.\n- One message. If no reply, one follow-up at most a week later, then stop.\n\n## Examples\n\n**Dating app, their profile mentions hiking in Scotland:**\n> Skye or the Cairngorms? I've only done one and I'm being told I picked wrong.\n\n**Dating app, a photo of them cooking:**\n> Okay that pasta looks better than any restaurant I've been to this year. Is it a recipe or a \"watched my nan\" situation?\n\n**Dating, after a match with a blank-ish profile:**\n> Your profile is mysterious, so I'll go first: I'm the kind of person who reads restaurant menus in advance. What's your equivalent?\n\n**Professional cold DM / email to someone you admire:**\n> Hi Rosa, your talk on onboarding flows at Config changed how we run our first-week emails; the \"delay the tour\" idea alone moved our activation rate. I'm building something similar for a nonprofit and had one specific question: how long did you wait before the first check-in email? Would you be open to a two-line reply? Totally understand if not.\n\n**Networking, someone at a company you're interested in:**\n> Hi Dev, I saw you moved to Larkfield Bank last year. I'm looking at a similar move and would love 15 minutes of your honest take on the culture, at a time that suits you. Happy to send questions in advance so it's quick.\n\n**Community (forum, Discord, hobby group):**\n> Your write-up on sourdough hydration was the first one that actually made it click for me. Quick question if you have a sec: do you drop to 70% for rye?\n\n**Someone you saw at an event:**\n> Hi, we didn't get to talk at the climate tech meetup, but I caught your question about grid storage and thought it was the sharpest one in the room. Up for a coffee if you're ever around Shoreditch?\n\n## Avoid\n- \"Hey\" / \"Hi\" / \"How are you\" alone.\n- Generic compliments.\n- Copy-paste openers (people can tell).\n- Asking for a call in a first professional message without offering to make it easy.\n- Explaining who you are for three sentences.\n- Asking two questions at once.\n- Negging, \"jokes\" at their expense, or anything that would be weird said aloud in a coffee shop.\n\n## Follow-up if no reply (professional only)\n> Bumping this once in case it got lost; no worries if you're not able to.\n\n## If they don't reply, or reply badly\nNo reply after one follow-up (professional) or none at all (dating) means no. Do not send a \"guess not\" or an \"okay then\"; that turns a non-event into a bad memory of you. A one-word reply on a dating app is a soft no; let it go. A curt professional reply that answers your question is a win, so thank them in one line and do not ask for more.\n> Thanks, that's exactly what I needed. Really appreciate you taking the time.\n> No worries, thanks anyway. Good luck with the launch.\nIf they tell you the message wasn't welcome, one line of apology and gone."},
{"id":"follow-up-after-interview-or-meeting","title":"Following up after an interview or meeting","category":"work","tags":["interview","meeting","follow-up","thank you","recap","next steps"],"triggers":["thank you after interview","follow up after the meeting","recap email","haven't heard back after interview","post-meeting email"],"summary":"Short follow-ups that add something: a specific thank-you after interviews, a recap with owners after meetings, and a polite check-in when the timeline slips.","updated":"2026-09-27","body":"# Following up after an interview or meeting\n\n## Goal\nThe other person has one specific reason to remember you, and everyone leaves with the same picture of what happens next. Every follow-up adds one thing; none of them just checks in.\n\n## Structure\n1. **Specific thanks or a one-line opener**, tied to something they actually said.\n2. **Add one thing**: a clarification, a decision, a resource, or the recap with owners and dates.\n3. **Say what happens next**, with a date where there is one.\n4. **One-line close** that reaffirms interest or invites corrections.\n\n## After an interview\n\n**Send within 24 hours. Three to five sentences.**\n\nStructure: thanks (specific) → one thing from the conversation that stuck with you → optional: one thing you'd add or clarify → reaffirm interest, one line.\n\n> Hi Elena,\n> Thank you for the conversation yesterday. The point about the team moving from quarterly to continuous releases stuck with me; it's exactly the kind of shift I'd want to be part of. One thing I'd add to my answer on incident handling: at [company] I also led the post-mortem process, which I didn't get to mention. I'm very interested in the role and happy to provide anything else that would help.\n> Best,\n> Chris\n\n**Checking in when they said \"by Friday\" and it's Wednesday of the next week:**\n> Hi Elena,\n> I hope the week's going well. You mentioned you'd have an update by last Friday; I wanted to check whether there's anything further you need from me. Still very interested.\n> Best,\n> Chris\n\n**After a rejection (this is how you get the next role):**\n> Thank you for letting me know, and for the process, which was genuinely well run. If it's possible, I'd value one line of feedback. Either way, I'd be glad to hear from you if something opens up in future.\n\n## After a meeting\n\n**Send the same day. Bullet points. Owners and dates on everything.**\n\n> Hi all,\n> Thanks for today. Quick recap so we're aligned:\n> - We're going with option B (phased rollout), starting with the UK.\n> - Priya: draft comms plan by the 14th.\n> - Me: updated timeline by Thursday.\n> - Open question: whether legal needs to review the T&Cs; Sam to confirm by Tuesday.\n> Shout if I've got anything wrong.\n> Lee\n\n**After a networking coffee:**\n> Really enjoyed this morning. The [specific thing they said] has been rattling around my head since. I'll send that article I mentioned. If I can ever be useful on [their thing], say the word.\n\n**After a sales / client meeting:**\n> Thanks for your time today. As discussed: I'll send the proposal for the phased approach by Friday, including the pricing for the reduced scope you asked about. The one thing I need from you is the current traffic numbers, whenever convenient. Looking forward to it.\n\n## Principles\n- Add something: a clarification, a resource, a decision. \"Just following up\" adds nothing.\n- The recap email is where decisions become real. Write the version you want to be true.\n- Keep the interview thank-you short; a long one reads as anxious.\n- One check-in on a slipped timeline, then wait.\n\n## Avoid\n- \"Just wanted to reach out and thank you for taking the time out of your busy schedule.\"\n- Restating your whole CV.\n- Multiple check-ins in a week.\n- Recaps with no owners or dates.\n\n## If they go silent or say no\nOne check-in on a slipped timeline, then wait two weeks and send a short closing note. If the answer is a rejection, reply once, ask for feedback, and stop; the graceful reply is what gets you remembered for the next opening. If a recap gets pushback (\"that's not what we agreed\"), do not argue in the thread. Correct the recap, thank them, and move on.\n> Hi Elena, I'll take the quiet as the timing not working out on your side. Thanks again for the process, and I'd be glad to hear from you if a similar role opens up.\n> Thanks for the correction, I've updated the notes: the UK pilot starts in Q1, not Q4. Shout if anything else is off."},
{"id":"follow-up-unanswered","title":"Following up on an unanswered message","category":"personal","tags":["follow-up","no reply","chase","nudge","reminder"],"triggers":["they haven't replied","follow up","nudge","chase","remind them","left on read","no response"],"summary":"How to nudge without sounding needy or annoyed, with a three-step escalation from casual bump to graceful exit. A client or prospect gone silent on a project or deal: handle-being-ghosted-by-client.","updated":"2026-09-27","body":"# Following up\n\n## Goal\nMake it easy for them to reply now, without making them feel bad for not replying earlier. Silence usually means busy or forgot, not rejection.\n\n## Structure\n1. **Assume the best out loud** (\"I know things are hectic\").\n2. **Restate the thing in one line** so they do not have to scroll.\n3. **Make the reply tiny**: a yes/no, a pick between two options, or \"even a 'not now' is helpful\".\n4. **Optional deadline** framed as helping you plan, not pressuring them.\n\n## Escalation ladder\n\n**Bump 1 (after 3 to 5 days), lightest touch:**\n> Bumping this in case it got buried. Thursday or Friday for the call?\n\n**Bump 2 (after another week), give a reason and an out:**\n> Hey, checking in on the draft I sent. If it's not a priority right now that's completely fine, I'd just like to know so I can plan around it.\n\n**Bump 3 (final), close the loop cleanly:**\n> Last nudge from me on this. I'll assume it's a no for now and stop pestering, but the door's open if it becomes useful later.\n\nThree is the maximum. After that, silence is the answer.\n\n## Examples\n\n**Friend who went quiet, personal:**\n> Hey, no agenda, just realised it's been a while. How are you doing?\n\n**After sending someone something they asked for:**\n> Did the file come through okay? Let me know if you need a different format.\n\n**Someone owes you an answer on plans:**\n> Need to lock the booking by tomorrow. Are you in or out? Either is fine, I just need to know.\n\n**Email, professional:**\n> Hi Marcus,\n> Following up on the proposal from the 12th. Happy to adjust scope or timing if that would help. If it's easier, a one-line \"not now\" is genuinely useful.\n> Thanks,\n> Jo\n\n## Avoid\n- \"Friendly reminder\" (never friendly).\n- \"Just checking if you saw my message?\" (they did).\n- \"?\" or \"??\" alone.\n- Restating the entire original message.\n- Following up with the same message twice.\n- Guilt: \"I guess you're too busy for me.\"\n\n## Reading the silence\nIf it is a friend and this happens repeatedly, the follow-up should eventually be about the pattern, not the message. See `reconnect-after-silence` and `set-boundary`.\n\n## If they reply with a no, or never reply\nA no after a bump is a success: you got an answer. Thank them in one line and do not reopen it. If they reply irritated (\"I saw it, I've been busy\"), do not defend the nudge; take the answer and give them room. If three bumps get nothing, send nothing more. A fourth costs you standing without changing the result, and if it is a friend, the next message should be about how they are, not about the thing.\n> Totally fine, thanks for letting me know. Door's open if it changes.\n> No problem, I'll leave it with you. Reply whenever it suits."},
{"id":"give-and-receive-compliments","title":"Giving and receiving compliments without awkwardness","category":"personal","tags":["compliment","praise","appreciation","thank you","gratitude"],"triggers":["respond to a compliment","how to compliment","say thank you","show appreciation","they praised me","thank someone properly","coworker keeps commenting on my looks","compliment feels like flirting"],"summary":"How to give a compliment that lands and receive one without deflecting, plus how to write genuine appreciation.","updated":"2026-09-28","body":"# Compliments and appreciation\n\n## Goal\nThe compliment lands as a gift, not a transaction: the other person feels seen for something they actually did, and when you are the one being praised, you accept it without shrinking or deflecting.\n\n## Structure\n1. **Name the specific thing** they did or chose, not a trait.\n2. **Say the effect it had on you**, one line.\n3. **Stop there**: no ask, no qualifier, no comparison.\n4. **When receiving: \"thank you\" plus one sentence that accepts it.** Credit others only after that.\n\n## Giving a compliment\n\n**The rule:** specific + effect on you. \"The way you handled that client call was so calm, I was taking notes\" beats \"you're great at your job.\"\n\n- Compliment effort and choices over innate traits. \"You clearly put real thought into the menu\" is better than \"you're so talented.\"\n- Do not attach an ask.\n- Do not qualify it (\"I don't usually say this but\").\n- To someone senior: keep it short and about a specific thing. Gushing reads as sucking up.\n- Written compliments are kept. Send the text.\n\n**Examples**\n> Your toast last night was the best I've heard at a wedding, it actually sounded like her.\n> The way you explained that in the meeting made something click that I'd been stuck on for weeks. Thank you.\n> I've noticed you always make new people feel welcome. It matters more than you probably think.\n\n## Receiving a compliment\n\n**The rule:** \"Thank you\" and a short sentence that accepts it. Do not deflect, minimise, or bounce it back immediately.\n\n- Deflecting (\"oh it was nothing\") rejects their judgement.\n- Immediate bounce (\"no, you're the one who's great\") makes it a transaction.\n- If you want to credit others, do it after accepting: \"Thank you. Priya did half of it, honestly, but I'm proud of it.\"\n\n**Examples**\n> Thank you, that means a lot coming from you.\n> Thanks, I worked hard on that bit, so I'm glad it showed.\n> That's really kind, thank you. I'm still learning but I'm getting there.\n\n**When a compliment is really a hit-on (a colleague, a client, someone you don't want to encourage):** keep it light, short and closed. Thank them briefly or not at all, steer back to the task, and give nothing to build on. If it repeats, say plainly that you'd rather keep things professional; if it continues after that, it is a workplace issue for your manager or HR, not a messaging one.\n> Ha, thanks. Anyway, about the Q3 numbers...\n> I'd rather keep comments to the work, thanks. So, Thursday's deck?\n\n## Writing genuine appreciation (thank-you message)\n\n**Structure:** what they did (specific) + what it meant / what it made possible + one line about them.\n\n**Examples**\n\n**After someone helped you move:**\n> Thank you for Saturday. You gave up a whole day and carried the worst of the boxes without a single complaint. I'd have been at it till midnight without you. Dinner's on me next week, no arguments.\n\n**Mentor or someone senior:**\n> I wanted to say thank you for the intro to Nadia. The conversation was exactly what I needed and I wouldn't have got in the room without you. I'll let you know how it goes.\n\n**Thank-you after a hard time:**\n> I don't think I said it properly at the time, but you showing up every week when Dad was sick is something I'll never forget.\n\n**Quick, casual:**\n> You're a legend, thank you.\n\n## Avoid\n- \"You're so lucky to be good at that\" (erases effort).\n- Compliment + request in the same breath.\n- \"No, you're amazing!\" ping-pong.\n- Thanking so profusely they have to manage your gratitude.\n\n## If it lands awkwardly\nIf they deflect your compliment (\"oh, it was nothing\"), do not argue them into accepting it. Repeat it once, shorter, and move on. If a compliment is misread as flirting or an angle, clarify in one plain line without apologising for having said it. If a thank-you message gets no reply, that is fine; appreciation does not need a receipt, and chasing one turns the gift into a demand.\n> I mean it, and I'll leave it there. Nice work.\n> No angle here, I just thought it was good and wanted to say so."},
{"id":"give-feedback-kindly","title":"Giving honest feedback kindly (personal and creative)","category":"personal","tags":["feedback","honest","critique","friend's work","opinion","review"],"triggers":["they asked what I think","give feedback on their writing","honest opinion","critique a friend's work","don't want to hurt their feelings","review their idea"],"summary":"How to tell someone the truth about their work, cooking, writing or idea in a way they can actually use, asked or not. At work: give-feedback-to-colleague.","updated":"2026-09-29","body":"# Giving honest feedback kindly\n\n## Goal\nThey come away with something they can act on and they still trust you. Kindness without honesty is useless; honesty without kindness is not heard.\n\n## Structure\n1. **Ask what kind of feedback they want**, if unclear: \"Do you want a cheerleader or an editor right now?\"\n2. **Start with what's genuinely working, specifically.** One or two things, real ones. This is calibration, not cushioning.\n3. **The main issue, one thing, framed as a question or observation.** \"The middle section lost me; I wasn't sure whose story it was.\"\n4. **A concrete suggestion if you have one.** Otherwise, just the observation.\n5. **Re-anchor on the goal**: \"I'm saying this because I think this could be really good.\"\n\n## Principles\n- Most people can absorb one significant critique per sitting. Pick the most important.\n- Describe your experience (\"I got confused here\") rather than pronounce a verdict (\"this is confusing\"). Experience cannot be argued with.\n- Specific praise makes specific criticism credible. Generic praise (\"it's great!\") makes everything else suspect.\n- If they did not ask, ask permission first. \"Want a couple of thoughts, or are you happy with it?\"\n- Skip what they cannot change now (their voice, the deadline that passed, the dress they are already wearing).\n\n## Examples\n\n**Friend's writing:**\n> I read it twice. The opening scene is properly good, I could see the kitchen. Where I got lost was the middle: three new characters arrive fast and I couldn't tell who to care about. If you cut one and gave the other two a line each that shows what they want, I think it'd snap into place. This is worth finishing.\n\n**Friend's business idea:**\n> I like the problem you're going after, it's real and I've felt it. My honest hesitation is the pricing: I'm not sure I'd pay monthly for it, though I'd pay once. Have you tested that with anyone yet? If it turns out I'm wrong, ignore me.\n\n**Someone's presentation, before they give it:**\n> The story in the middle about the customer is the strongest bit; I'd open with it. The first five slides are setup people already know. Also you say \"basically\" a lot when you're nervous; no one else will notice but you might.\n\n**When it's genuinely not good and they asked for honesty:**\n> You asked me to be straight so I will be. I don't think this version is there yet. The idea's strong; the execution feels rushed, mainly [one thing]. I'd rather tell you now than have you find out from someone who doesn't care about you.\n\n**When they didn't ask:**\n> Do you want thoughts, or are you done with it? Happy either way.\n\n**Cooking, someone proud of a dish:**\n> I love that Sunday chicken is your thing. Can I suggest one tweak? I think it'd be even better a bit juicier, maybe ten minutes less in the oven or brined overnight. Want to try it together next week?\n\n## Avoid\n- The compliment sandwich with a fake bottom slice (\"but overall great!!\"). They only hear the middle and distrust the bread.\n- \"It's fine.\"\n- Listing every small thing.\n- Feedback on the person (\"you're not a natural writer\").\n- \"I would have done it differently.\"\n- Delivering big feedback over text if they are anxious about it. Call.\n\n## If they get hurt or defensive\nDo not retract the point and do not add more to it. Reaffirm the goal, name that it is one reader's experience, and offer to leave it there. If they go quiet for a few days, send one warm line that is not about the work. If they push you to say it was good, hold: \"I think it can be, and it isn't yet\" is both honest and kind. If they say they only wanted support, take that at face value and be the cheerleader next time they ask.\n> I can hear that landed harder than I meant. It's one reader's take, and I said it because I think this is worth the work. Happy to drop it or go through it together, your call.\n> No need to reply to any of that. Coffee this week?"},
{"id":"give-feedback-to-colleague","title":"Giving critical feedback to a colleague or report","category":"work","tags":["feedback","colleague","report","performance","one-on-one","manager"],"triggers":["give feedback to my report","colleague keeps","tell a coworker","performance conversation","address a problem with a teammate","hard feedback at work"],"summary":"Critical feedback at work that changes behaviour without damaging trust: specific, private, timely, with a clear ask and a follow-up. Hygiene and other embarrassing things: tell-someone-something-awkward.","updated":"2026-09-29","body":"# Giving critical feedback at work\n\n## Goal\nThe behaviour changes and the person still feels respected and backed. Feedback that is not acted on was not feedback, it was venting.\n\n## Structure (for a conversation; write it out first)\n1. **Ask for the conversation**: \"Can I give you some feedback on X?\" Consent opens ears.\n2. **The specific observation.** What you saw, when. Not a pattern word like \"always\".\n3. **The impact.** On the work, the team, the client. Not on your feelings unless relevant.\n4. **Pause and ask.** \"What's your read on that?\" Then actually listen. There is often context.\n5. **The ask.** What you want to see instead, concretely.\n6. **Support and follow-up.** \"What would help?\" and a date to check in.\n\n## Principles\n- Private, always. Praise in public, correct in private.\n- Soon. Within days of the thing, not at the quarterly review.\n- One thing per conversation.\n- Behaviour, not personality. \"The report had three errors in the totals\" not \"you're careless.\"\n- Do not sandwich with fake praise. Real positive context is fine; a manufactured compliment before the point is transparent.\n- Say it plainly. Managers who hint are experienced as unclear, not kind.\n- Written follow-up after the conversation, short and neutral.\n\n## Examples\n\n**Missed deadlines, report:**\n> Can I give you some feedback? The last three deliverables have come in a day or two after the date we agreed. The effect is that Sana's team ends up scrambling and it's starting to show up in how they talk about us. What's going on from your side?\n> [listen]\n> Okay. Going forward I need the dates to hold, or a heads-up by the Wednesday before if something's slipping. What would make that easier?\n\n**Peer who talks over people in meetings:**\n> Hey, something I've noticed and I think you'd want to know: in the last couple of meetings you've jumped in over Maya and Lee a few times before they finished. I don't think you're doing it on purpose. It's meant a couple of good points got lost. Would you be up for leaving a beat after people finish? I'll do the same.\n\n**Quality issue, senior person to junior:**\n> The deck you sent had the wrong Q2 numbers on two slides and it went to the client before we caught it. That's the kind of thing we can't let out the door. I want to work out a check that catches it: what if you send me numbers slides an hour before anything external?\n\n**Attitude / tone issue (hardest one):**\n> I want to raise something that's a bit uncomfortable. In the planning meeting, when Tom suggested the phased approach, the response came across as dismissive, and I saw him shut down after that. I don't think that's what you intended. The effect is that people stop offering ideas. Can we talk about how that landed?\n\n**Written follow-up:**\n> Thanks for the conversation earlier. To capture it: we agreed deliverable dates hold, with a heads-up by the prior Wednesday if anything's at risk. Let's check in on the 20th. Let me know if I've missed anything.\n\n## Avoid\n- \"Some people have said...\"\n- \"You always / you never.\"\n- Feedback by email when it should be a conversation.\n- Piling several issues into one meeting.\n- Ending without a clear ask.\n- Not following up. Silence after feedback reads as \"it didn't matter.\"\n\n## If they push back or the behaviour doesn't change\nPushback with new context is useful: listen, then restate the ask if it still stands. Pushback that is only heat (\"that's unfair\", \"everyone does that\") gets a calm, short repeat and a close, not a debate. If nothing has changed by the check-in date, say so plainly, make the consequence clear, and put it in writing. Escalate through the right channel (your manager, HR) rather than having the same conversation a fourth time.\n> I hear that you see it differently. The ask stands: dates hold, or a heads-up by the Wednesday before. Let's see how the next two weeks go and talk on the 20th.\n> We agreed on the 6th that deadlines would hold, and the last two have slipped again. I need this to change now, and I'll be tracking it in our one-to-ones. What's getting in the way?"},
{"id":"give-notice-to-a-landlord-or-tenant","title":"Giving notice to a landlord or tenant (moving out, ending a lease early, not renewing)","category":"personal","tags":["notice","moving out","lease","tenancy","landlord","tenant"],"triggers":["write a notice to vacate letter","tell my landlord i'm moving out","how to break my lease early","give 30 days notice to landlord","email to landlord about ending tenancy","tell my tenant i'm selling the house","not renewing the lease message","ask landlord to let me leave early"],"summary":"Notice on a rental: a tenant moving out or asking to leave early, a landlord not renewing. Exact dates, in writing, with a handover plan. Rent rises, repairs, deposits: landlord-tenant-and-service-providers.","updated":"2026-09-27","body":"# Giving notice to a landlord or tenant\n\n## Goal\nThe notice is valid, the dates are clear, and the handover goes smoothly enough that the deposit, the reference or the next tenancy is not put at risk. Get the facts right first, then make it kind.\n\nRent increases, repairs and getting a deposit back: `landlord-tenant-and-service-providers`.\n\n## Structure\n1. **Check the lease and local rules first.** Notice period, how notice must be served (email, letter, a specific form), and whether it must end on a rent date.\n2. **State the notice plainly in the first sentence**, with the property address and the exact end date.\n3. **Reference the lease clause or notice period** you are relying on.\n4. **The practical plan:** final rent, viewings, key return, inspection, meter readings.\n5. **Ask for written confirmation.**\n6. **A warm close,** if the relationship allows it.\n\n## Principles\n- Put it in writing, in the form the lease requires, and keep a copy. A phone call or a text alone may not count as notice.\n- Give the exact date, not \"end of next month\". Check that it meets the notice period.\n- Rules differ a lot by country, state and tenancy type. When the lease is unclear or the stakes are high, check with a tenant advice service or a local housing body before sending.\n- Asking to leave early is a request, not a notice. Make it easy to say yes: offer to help find a replacement tenant, cover advertising or pay rent until someone moves in.\n- As a landlord, give more notice than the minimum when you can, the reason in one line, and practical help. A tenant who feels respected leaves the place in better shape.\n- Do not use notice as a threat in a separate dispute.\n\n## Examples\n\n**Tenant, standard move-out notice (email or letter):**\n> Dear Ms Harper, I'm writing to give notice that I will be leaving 14 Elm Road, Flat 2, with my tenancy ending on 30 June, in line with the one-month notice period in clause 8 of our lease. I'll pay June's rent as usual and return both sets of keys on the 30th. Could we arrange a check-out inspection that day? Please confirm you've received this notice. Thanks for two good years. Tom Reyes\n\n**Tenant, asking to leave early:**\n> Hi Mark, I've been offered a job in Leeds starting in August, which means I need to leave before the lease ends in December. Would you consider letting me end the tenancy on 31 July? I'm happy to pay rent until a new tenant moves in, help with viewings, and share the listing with people I know. I'd much rather sort this out together.\n\n**Joint tenancy, one person leaving:**\n> Hi Priya, Jess is moving out at the end of May, and Sam and I would like to stay. Can we add a new tenant to the lease in her place from 1 June? We have someone in mind and can send their details for your checks.\n\n**Landlord, not renewing (selling the property):**\n> Dear Chris and Ana, I'm writing to let you know that I've decided to sell the flat, so I won't be renewing your tenancy when it ends on 31 August. This is formal notice under the terms of your agreement. I know moving is a big disruption. I'll give at least 24 hours' notice for any viewings, and I'm very happy to write you a reference. Please let me know if you'd like to leave earlier, and I'll work with you on the dates.\n\n**Landlord, confirming the handover plan:**\n> Thanks for confirming the 30th. I'll meet you at 11am for the check-out, and we'll go through the inventory together and take meter readings. The deposit will be returned within the legal timeframe, minus any agreed deductions, and I'll send a written breakdown either way.\n\n## Avoid\n- Giving notice by text only, if the lease requires a letter or a form.\n- Vague dates (\"sometime next month\").\n- Threatening to withhold the last month's rent against the deposit, which many leases and laws do not allow.\n- As a landlord, entering the property for viewings without the notice the law or lease requires.\n\n## If it goes badly\nIf the landlord says your notice is invalid, ask them to point to the clause, check it against the lease and local rules, and if they are right, re-serve it correctly straight away rather than arguing. If they refuse an early exit, ask what would make it work (a replacement tenant, a fee) and get any agreement in writing. If a tenant does not leave by the end date, do not change locks or remove belongings; follow the legal process and get advice, since self-help evictions are illegal in most places.\n> Thanks for flagging that. I've re-read clause 8 and you're right about the rent date, so please treat this as notice ending on 31 July instead.\n> I understand you'd rather keep the lease as it is. Would you agree to release me if I find a replacement tenant who passes your checks? Happy to put that in writing."},
{"id":"group-chat-coordination","title":"Group chats: organising plans, chasing decisions, handling flakes","category":"personal","tags":["group chat","organise","plans","poll","flake","whatsapp group","coordinate","decision"],"triggers":["organise the group","nobody replies in the group chat","get everyone to decide","someone keeps flaking","plan a trip with friends","chase the group","pick a date","group won't commit"],"summary":"How to get a group to actually decide: fewer options, deadlines, a named default, and gentle ways to handle the person who always bails.","updated":"2026-09-27","body":"# Group chats: organising and deciding\n\n## Goal\nThe group reaches a decision that sticks, in the fewest messages, and nobody feels nagged or steamrolled.\n\n## Structure\n1. **Propose one concrete plan** (date, time, place), or two options at most.\n2. **Ask for a one-tap reply** (thumbs up, yes/no).\n3. **Set a deadline and say what happens by default** if people go quiet.\n4. **Confirm the decision in one message** once you have it, then move logistics to a smaller thread.\n\n## Why groups stall\nNobody replies because replying feels like committing, and everyone assumes someone else will. Fix: make the reply tiny, give a deadline, and name what happens if nobody answers.\n\n## Principles\n- **Propose, don't ask.** \"Saturday 7pm at Luca's, who's in?\" beats \"what does everyone want to do?\"\n- **Two options, max.** A poll with two choices gets answered; one with six gets ignored.\n- **Deadline with a default.** \"I'll book for 6 on Thursday unless I hear otherwise.\"\n- **Ask for a specific reaction.** \"Thumbs up if in\" makes it a one-tap reply.\n- **Name people when you need them.** \"@Sam @Priya you two haven't said\" is fine if warm.\n- **Move logistics to a smaller thread** once the plan is set.\n\n## Examples\n\n**Kick off a plan:**\n> Right, birthday dinner for Jo. Proposal: Saturday 14th, 7:30, Bar Italia. 👍 if you're in, 👎 if you can't, by Wednesday please so I can book. Silence means I assume yes and you're paying for a chair.\n\n**Chase a stalled decision:**\n> Gentle nudge: still need to lock the date. Two options: the 14th or the 21st. Thumbs on the one you prefer. Deciding tomorrow night.\n\n**Trip planning, first message:**\n> Trip: I'm proposing Lisbon, 10 to 14 October, budget around $600 each all in. This is a real proposal, not a wish; if three people say yes by Friday I'll book the flat. Say yes, no, or \"different dates\".\n\n**Someone keeps flaking, address in the group (light):**\n> @Tom you're on your third \"maybe next time\", we're starting a tally. Genuinely, come Saturday, it's not the same without you.\n\n**Someone keeps flaking, address privately (real):**\n> Hey, not a big deal but you've bailed on the last few things and I'm starting to plan around you not coming. If things are hard right now, tell me and I'll stop pestering. If you just don't fancy the group stuff, that's fine too, I'd just rather know.\n\n**Cutting through a long argument about where to eat:**\n> Okay, executive decision: Thai place, 7:30. Anyone who objects can pick next time.\n\n**Group chat that's become too noisy:**\n> Suggestion: let's keep this one for plans and start a separate chat for the memes. I keep missing actual info.\n\n**Leaving a plan you'd agreed to:**\n> I've got to drop out of Saturday, sorry all. Don't change anything for me. Next one, I promise.\n\n**Asking people to pay their share:**\n> Booking's done, $85 each. My link is [link]; no rush but before the 10th please so I'm not out of pocket for weeks.\n\n## Avoid\n- \"What does everyone think?\"\n- Open-ended questions with no deadline.\n- Re-asking the same question when nobody replied; change the question.\n- Passive-aggressive \"guess nobody's interested then\".\n- Making the decision, then reopening it because one person complained.\n- Chasing in the group when it's really about one person.\n\n## If nobody replies, or someone reopens it\nSilence past the deadline: do what you said you would and post it once. Do not re-ask. If someone complains after the decision, acknowledge it, hold the plan, and hand them the next one. If the thread turns into an argument between two people, message each of them directly rather than refereeing in the group. If a flake drops out late again, quietly stop planning around them; announcing it in the group only makes everyone else uncomfortable.\n> Deadline was tonight, so I've booked Bar Italia for 6 at 7:30. If you didn't say and want in, message me by tomorrow and I'll ask for an extra seat.\n> Fair, Thai isn't everyone's first pick. It's booked now, so you choose next time."},
{"id":"handle-being-ghosted-by-client","title":"Handling a client or prospect who went silent","category":"work","tags":["ghosted","client silent","prospect","no response","deal stalled","re-engage"],"triggers":["client stopped responding","prospect went quiet","deal went cold","haven't heard from the client","re-engage a lead","they ghosted me after the proposal","client not sending the files we need"],"summary":"How to re-engage a silent client or prospect without desperation, including a live project stalled waiting on their files or approval, and how to close the loop cleanly when it's over.","updated":"2026-09-27","body":"# Client or prospect went silent\n\n## Goal\nEither they re-engage because you made it easy, or you close the file cleanly and stop spending energy on it. Both are wins.\n\n## Principles\n- Silence after a proposal usually means: priorities shifted, budget got cut, they're embarrassed to say no, or your email is buried. Almost never personal.\n- Each follow-up should make replying easier than the last: fewer options, smaller ask.\n- Offer the no explicitly. People ghost because they hate saying no; give them a one-word way to do it.\n- Three touches, then a clean close. The close often gets a reply.\n- Add value in at least one follow-up. New information gives them a reason to reply that is not \"sorry I ignored you\".\n\n## The sequence\n\n**Touch 1 (one week after silence): assume buried.**\n> Hi Ravi, bumping the proposal from the 3rd in case it got lost. Happy to adjust anything. Would it help to have a 15-minute call to go through it, or would you rather I just answer questions by email?\n\n**Touch 2 (two weeks later): add value, shrink the ask.**\n> Hi Ravi, since I sent the proposal we've finished a similar project for [company] and I thought the results might be useful context: [one line]. Is this still something you're looking at this quarter? A quick yes / no / not yet is all I need.\n\n**Touch 3 (two weeks later): the clean close.**\n> Hi Ravi, I'll assume the timing isn't right and close this on my side so I'm not cluttering your inbox. If it comes back up, I'd genuinely like to help; just reply to this thread. Best of luck with [their project].\n\n## Variations\n\n**Existing client who's gone quiet mid-project:**\n> Hi Ravi, I haven't heard back on the draft from the 10th and I want to make sure we're still on track. If there's a hold-up on your side, no problem, just let me know so I can plan my schedule. If you'd like me to pause, say the word.\n\n**When you need a decision by a date:**\n> I'm holding time for this project in October, and I need to release it to someone else if we're not proceeding. Could you let me know by Friday either way?\n\n**Reply to a \"sorry for the silence\":**\n> No apology needed, I know how it goes. Where would you like to pick up from?\n\n## Avoid\n- \"Just checking in!\" with nothing else.\n- \"I've tried reaching you several times...\"\n- Guilt-tripping.\n- Following up daily.\n- A long re-pitch.\n- Leaving it open forever. Close it, it's healthier and often gets a reply.\n\n## If they reply with a no, or come back after the close\nA no is the second-best outcome: thank them, ask one question about why if the relationship is warm enough, and leave the door open. Do not counter with a discount you never offered before; it teaches them that silence gets a better price. If they resurface months after the close, skip the reproach entirely and re-scope from today's facts (your availability, current rates), not last year's proposal.\n> Thanks for letting me know, I appreciate the clear answer. If it's useful, one line on what tipped it would help me. Either way, good luck with the project.\n> Good to hear from you. Happy to pick this up. My availability and rates have moved since March, so let me send a fresh version this week."},
{"id":"handle-no-show-or-lateness","title":"Handling a no-show or lateness","category":"personal","tags":["no-show","late","flaked","cancel","reschedule","reliability","client"],"triggers":["friend keeps cancelling","they didn't show up","stood me up","I was late and missed it","I no-showed","friend is always late","client didn't turn up","vendor no-show","running late text","flaked on me again"],"summary":"Messaging someone who flaked, is running late, or keeps cancelling; owning it when you are the one who was late; naming a pattern without an ultimatum; and handling a client or vendor no-show.","updated":"2026-09-28","body":"# Handling a no-show or lateness\n\n## Goal\nThe plan gets rescued or rescheduled, the other person knows what you noticed, and nobody has to pretend it did not happen. Warm on the person, clear on the pattern.\n\n## They are running late or did not show (one-off)\n1. **Check they are okay.** One line, no sarcasm.\n2. **State what you will do.** \"I'll wait till 7:30\" or \"I'm heading off, let's rebook.\"\n3. **Give them a concrete next step** if you still want to meet.\n\n## You were late or did not show\n1. **Name it specifically.** \"I missed our 6pm\" not \"sorry about earlier\".\n2. **Own it without a \"but\".** Context, if needed, is one clause after the apology.\n3. **Acknowledge their cost.** Their time, their evening, the table they held.\n4. **Propose a fix with a date.** Do not ask them to do the rescheduling work.\n5. **One make-good if it fits.** \"Coffee's on me.\"\n\n## Friend who cancels last minute, repeatedly\n1. **Say you enjoy seeing them.** Real, not a softener.\n2. **Name the pattern with numbers.** \"Three of the last four.\"\n3. **Say the effect on you, one line.** \"I stop planning around it.\"\n4. **Ask what would actually work.** Shorter, closer, more spontaneous. Let them tell you.\n5. **No ultimatum.** You are adjusting how you plan, not threatening the friendship.\n\n## Professional no-show (client, vendor, contractor)\n1. **Factual and dated.** \"We had 10am today; I waited until 10:30.\"\n2. **Consequence, if there is one.** Fee, missed slot, delayed timeline. Stated, not threatened.\n3. **One rebooking option** with a specific time.\n4. **What happens if it recurs**, said once, calmly.\n\n## Principles\n- Sarcasm feels good for a minute and costs you the conversation.\n- Numbers beat adjectives. \"Always\" gets argued; \"three of the last four\" does not.\n- Say what you will do, not what they must do. That is the difference between a boundary and a demand.\n- A professional no-show is a business matter. Keep it in business language and put it in writing.\n\n## Examples\n\n**They're 20 minutes late, no word:**\n> Hey, all okay? I'm at the table by the window. I'll hang on till 7:30, after that let's do another night.\n\n**They no-showed, one-off:**\n> Missed you tonight, hope nothing's wrong. I'm free Thursday or Sunday if you want to try again, your pick.\n\n**You're running late:**\n> Running 15 minutes behind, my fault, left too late. Order without me and I'll catch up. There by 7:15.\n\n**You no-showed a friend:**\n> I completely missed our lunch today and I'm sorry. No excuse, I had the wrong day in my head. You held a table and gave up your break for it. Can I take you Friday, same place, my treat?\n\n**Friend who cancels last minute, naming the pattern:**\n> I love hanging out with you, and the last three plans have all been cancelled the day of. I'm not upset, I just want to find something that works. Would shorter and closer suit better, like a coffee near yours on a weekday? Or tell me what would.\n\n**Friend who is always late, before the next meet-up:**\n> Booking 7 for Friday. Fair warning, I'll order at 7:15 whether you're there or not, so I'm not sitting with an empty plate. See you then.\n\n**Client no-show, email:**\n> Hi [name], we had a call scheduled for 10am today and I waited until 10:30. No problem if something came up. I can offer Thursday at 2pm or Friday at 11am. Please note that a second missed session without 24 hours' notice is charged at the full rate, as per our agreement.\n\n**Vendor or contractor no-show:**\n> Hi [name], you were booked for 9am today and nobody arrived or called. I've taken the morning off for this. Can you confirm a new date by end of tomorrow? If I don't hear back I'll need to book someone else.\n\n## Avoid\n- \"No worries!\" when there are worries. It teaches them the flaking is free.\n- \"Typical\" or \"as usual\".\n- Asking \"why?\" They will give a reason and you will have to accept it.\n- Over-apologising when you were late by five minutes. Match the size.\n- Waiting silently for an hour then exploding. Set the limit early and out loud.\n\n## If it goes badly\nIf they get defensive about the pattern:\n> I'm not keeping score to punish you. I'd rather say it than quietly stop inviting you. Let's try the coffee idea and see.\n\nIf a friend keeps cancelling after you named it, stop making fixed plans and say so, once, without heat:\n> No stress at all. I'm going to stop booking things in advance for now, but if you're ever free last minute, text me and I'll come if I can.\n\nIf a client argues the no-show fee:\n> I understand it's frustrating. The policy was in the agreement you signed, and I apply it to everyone. Thursday at 2 is still open if you'd like it."},
{"id":"handle-refund-request","title":"Handling a refund, return or cancellation request","category":"commerce","tags":["refund","return","cancellation","policy","customer","small business"],"triggers":["customer wants a refund","refund request","they want to return it","cancel their order","refund policy","asking for money back","return outside the window","make an exception on a return"],"summary":"Saying yes fast when you can, saying no kindly when you must, and offering an alternative either way, without hiding behind policy.","updated":"2026-09-28","body":"# Handling a refund request\n\n## Goal\nWhether the answer is yes or no, the customer feels dealt with fairly and quickly, and would buy from you again. Policy is your reason, never your opening line.\n\n## The decision first\nAsk yourself: is the cost of this refund higher than the cost of this customer telling ten people you were difficult? Usually it is not. Say yes when you reasonably can.\n\n## Structure\n1. **Acknowledge the specific issue**, in their words.\n2. **The answer**: yes, no, or a middle option, in the first two lines.\n3. **If yes: exactly what happens and when.**\n4. **If no: one-line reason, then the alternative you can offer.**\n5. **Sign off warmly, no \"policy\" language.**\n\n## Examples\n\n**Yes, item arrived damaged:**\n> Oh no, I'm sorry the mug arrived cracked, that's not okay. I'll send a replacement today, no need to return the broken one. You'll have tracking by this evening. If you'd rather have a refund instead, just say.\n\n**Yes, changed their mind, within window:**\n> No problem at all! Send it back to [address] and I'll refund the full amount the day it arrives. Return label's attached. Sorry it wasn't right for you.\n\n**No, outside return window, offer alternative:**\n> Thanks for getting in touch. I can see the order was from March, and our returns close at 30 days, so I can't do a full refund on this one. What I can do is offer store credit for 50% of the price, or a 20% code for your next order. Would either help?\n\n**Outside the window, exception granted (without making it the new rule):**\n> Hi Jess, the window is 30 days and this is at 47, so normally this would be a no. Since you've ordered six times and never returned anything, I'll make an exception this once and refund in full. Label attached. Going forward the 30 days is firm, so there's no surprise next time.\n\n**No, custom / personalised item:**\n> I'm sorry it's not what you hoped for. Because this one was made to your spec I'm not able to refund it, since I can't resell it. If there's something specific that's wrong with it, I'd genuinely like to fix it, so tell me what's off.\n\n**Cancellation before shipping:**\n> Cancelled and refunded, you'll see it back on your card in 3 to 5 days. Sorry to see you go; if it was something we did, I'd love to know.\n\n**Service cancellation with notice policy:**\n> I can cancel Thursday's session for you. Because it's under 24 hours, the deposit isn't refundable, but I'm happy to move it to another day this month instead so you don't lose it. Want to do that?\n\n**Chargeback threat:**\n> I'd really rather sort this directly with you than through the bank, and I think we can. Here's what I can offer right now: [option]. If that doesn't work, tell me what would.\n\n## Principles\n- Speed defuses. Reply within hours.\n- Never open with \"Unfortunately\" or \"As per our policy\".\n- A partial yes (credit, exchange, discount) turns most nos into acceptable outcomes.\n- Do not ask them to prove things unless the amount justifies it.\n- Do not argue about whose fault it is.\n- Refund fast when you say you will. The delay is the real complaint.\n\n## Avoid\n- Copy-pasting the policy.\n- Making them fill in a form for a $20 item.\n- \"We apologise for any inconvenience.\"\n- Silence while you \"look into it\" for days.\n- Defending the product.\n\n## If they escalate, threaten a review or dispute the charge\nReply within hours, in the same calm tone, and restate the best offer you can make in one line. Do not match their heat and do not mention the review unless they do. If they file a chargeback, send the bank your records (order, tracking, messages) and stop negotiating in the thread. If they turn abusive, one line that ends it is enough, and you do not have to keep replying.\n> I understand you're frustrated and I'd still like to sort this. The offer is full store credit or a 50% refund, whichever suits you, and I can process either today. Let me know which.\n> I've set out the options I can offer. I'm going to leave it there, and the credit stays available if you want it."},
{"id":"introduce-yourself","title":"Introducing yourself (new job, new group, event, online community)","category":"work","tags":["introduce yourself","new job","first day","new team","community","hello","bio"],"triggers":["introduce myself to the team","first day message","hello to the group","new to the community","introduce myself in slack","say hi to new colleagues","write a short bio"],"summary":"Self-introductions that make people want to talk to you: short, one concrete thing about your work, one human thing, and an invitation.","updated":"2026-09-27","body":"# Introducing yourself\n\n## Goal\nPeople remember one thing about you and feel invited to reach out. Not a CV. Not a performance.\n\n## Structure\n1. **Name and role/reason you're here**, one line.\n2. **One concrete thing** about what you do or care about (not \"passionate about innovation\").\n3. **One human thing** that gives people a hook (a hobby, where you're from, an odd fact).\n4. **An invitation**: what you'd like to hear from them, or how to reach you.\n\n## Principles\n- Under 100 words for written intros. Thirty seconds spoken.\n- Specific beats impressive. \"I spent last year fixing our checkout flow\" beats \"I'm a results-driven product leader\".\n- The human thing is the part people remember. Pick one that invites conversation.\n- Say what you want. \"I'd love to hear what's annoying you about the current system\" makes people talk to you.\n- Match the room. A Slack intro is casual; a board intro is not.\n\n## Examples\n\n**New job, Slack or Teams:**\n> Hi all, I'm Maya, joining the platform team as an engineer today. Most recently I was at [company] working on payments infrastructure, so if anything payment-shaped is broken, I'm your person. Outside work I'm slowly restoring a 1970s bike and mostly failing. I'd love 15 minutes with anyone who wants to tell me what's annoying about the current system; DMs open.\n\n**First day, spoken to the team:**\n> Hi, I'm Maya. I've come from [company] where I spent three years on payments. I'm here to help with the platform rebuild. I'll spend the first couple of weeks mostly listening, so grab me if there's something you think I should know. I'm also new to the city, so restaurant recommendations welcome.\n\n**Online community / forum / Discord:**\n> Hey, I'm Sam, a self-taught designer working mostly on tiny apps for local businesses. I joined because I keep getting stuck on onboarding flows and this seems like the place people actually talk about it. I'll mostly lurk to start; if you have a favourite thread on onboarding, point me at it.\n\n**Networking event, spoken:**\n> I'm Sam, I do design for small shops, mostly the boring-but-important bits like checkout. What are you working on?\n\n**New to a parents' group, sports club, neighbourhood chat:**\n> Hi everyone, I'm Jo, we moved into number 14 last month with two kids (6 and 9) and a very loud dog, sorry in advance. Happy to help with anything neighbourly, and we'd love to know where the good playground is.\n\n**Short bio for a profile or panel:**\n> Maya Chen is an engineer on [company]'s platform team, where she spent three years making payments fail less often. Before that she was at [previous]. She lives in Bristol and is slowly restoring a bike that will never be ridden.\n\n**Meeting a client team for the first time:**\n> I'm Nina, I'll be leading the design work on this. I've done similar rebuilds for [two names] and the thing I care most about is that it's still easy to use in a year. I'll be asking a lot of questions this week; none of them are traps.\n\n## Avoid\n- \"Passionate about\", \"results-driven\", \"ninja\".\n- Listing every previous employer.\n- Self-deprecation past one line.\n- No invitation at the end (dead end).\n- Long paragraphs.\n- Jokes that need context.\n\n## If the intro gets no response\nA quiet channel is normal, especially in a big Slack workspace or a busy Discord. Do not re-post or ask whether anyone saw it. Within a day or two, reply to someone else's message or ask one specific question in a relevant channel; the intro did its job as background. If someone answers with a joke at your expense or a pointed question, take it lightly and answer the real question if there is one.\n> Quick one for the platform folks: which of the current on-call runbooks is the least trustworthy? Asking so I know where to start reading.\n> Ha, fair. The bike has been \"nearly done\" for two years. Anyway, what's the current pain point on checkout?"},
{"id":"landlord-tenant-and-service-providers","title":"Landlords, tenants, contractors and service providers","category":"personal","tags":["landlord","tenant","rent","repairs","deposit","contractor","plumber","quote","service provider"],"triggers":["landlord wants to raise rent","ask landlord to fix","get my deposit back","rent increase","contractor didn't finish","quote is too high","plumber overcharged","tell my tenant","dispute with landlord","repair request"],"summary":"Firm, documented, polite housing and home-service messages: pushing back on a rent increase, repairs, getting a deposit back, disputing a contractor. Ending a tenancy: give-notice-to-a-landlord-or-tenant.","updated":"2026-09-28","body":"# Landlords, tenants, contractors and service providers\n\n## Goal\nGet the outcome and keep the relationship workable; you will need this person again.\n\n## Principles\n- Written, always. If you call, follow up with \"confirming what we discussed\".\n- Facts, dates, amounts. Feelings weaken these messages.\n- Ask for a specific thing by a specific date.\n- Cite the agreement or law once, neutrally, not as a threat: \"Under the lease\" is enough.\n- Stay pleasant and precise; that person wins most disputes.\n\n## Rent increase, pushing back\n\n**Do not send a flat no**; it usually ends in non-renewal. If the user has not given the current rent, the proposed rent or comparable prices, ask or leave labelled brackets.\n\n**Structure (all four, in order):** thanks for notice → counter with a specific number → one or two factual reasons, not your budget (comparable listings, years in the unit, payment record, condition of the flat) → a concrete ask (sign for 12 months at that number, or a call this week).\n\n**Before sending:** check whether the lease allows an increase before renewal.\n\n> Hi Mark,\n> Thanks for letting me know about the increase to $2,100. I'd like to ask you to reconsider. Comparable units in the building list at $1,850 to $1,950, and I've paid on time for three years. I'd be glad to sign another 12 months at $1,900. Would that work? Happy to talk by phone.\n> Best,\n> Jess\n\n**If they hold firm:**\n> Understood. Could you meet me halfway at $2,000, with the bathroom fan repaired before the new term starts? I'd sign today on that basis.\n\n## Repair request (and follow-up)\n\n**First:**\n> Hi Mark, the kitchen tap has leaked since Monday and water is pooling under the sink. Could you arrange a plumber this week? I'm home after 5pm, or can leave a key. Photos attached.\n\n**Reminder, one week later:**\n> Following up on the tap leak from the 12th; it's now damaging the cabinet. Could you confirm a repair date by Friday? Or I can book a plumber and deduct it from rent, with your written okay.\n\n**Formal, after two weeks:**\n> This is a formal repair request for the kitchen tap leak first reported on 12 May. Under the lease, water and fixture repairs are the landlord's responsibility. Please confirm a repair date within seven days. I'd still prefer to sort this informally, so do call me.\n\n## Getting a deposit back\n\n> Hi Mark, I moved out on the 30th and left the flat clean with the keys as agreed; photos attached. Could you confirm when the $1,800 deposit will be returned? Under the lease it's due within 14 days. Thanks for three good years.\n\n**If they deduct unfairly:**\n> Thanks for the breakdown. I don't agree with the $400 for repainting: the walls are as they were at move-in, per the inventory photos and mine attached. Please return that portion. I accept the $80 cleaning charge. If we can't agree, I'll raise it with the deposit scheme, but I'd rather settle it directly.\n\n## Contractor: quote too high / work not finished / overcharged\n\n**Quote too high:**\n> Thanks for the quote. It's above my budget. Could we get it under $3,000, maybe by dropping the heated floor or using standard tiles? I'd like to work with you.\n\n**Work not finished:**\n> Hi Dave, the job was due to finish on the 20th and the bathroom tiling is still incomplete. Could you give me a completion date this week? I'll release the final payment once it's done, as agreed.\n\n**Overcharged:**\n> The invoice is $1,450 against the agreed $1,100. Could you walk me through the difference before I pay it? Happy to pay the agreed $1,100 today.\n\n## Landlord to tenant (the other side)\n\n**Rent increase notice, kind version:**\n> Hi Jess, rent will increase to $2,000 from 1 September, in line with the market and this year's higher building costs. You've been a great tenant and I'd like you to stay. Happy to talk it through.\n\n**Late rent, first message:**\n> Hi Jess, rent for May hasn't come through yet. Could you check on it? If something's changed, let me know and we can work it out.\n\n## Avoid\n- \"This is unacceptable.\"\n- Threatening legal action in the first message.\n- Withholding rent without written agreement or legal advice.\n\n## If they refuse, ignore you or get hostile\nMove one step up the ladder (request, dated reminder, formal notice), never two. If they are rude, answer only the facts. If they refuse outright, say calmly what you will do next (deposit scheme, tenancy board, small claims), then do it. Never threaten a step you would not take.\n> I'll treat the 14 days as passed on Friday. If the deposit hasn't been returned by then, I'll open a claim with the deposit scheme, which I'd rather avoid. Happy to talk before then.\n> I'll leave the tone to one side. The leak was reported on 12 May and is still unrepaired. Please confirm a date this week."},
{"id":"leave-or-quit-gracefully","title":"Quitting a job, or leaving a group or commitment gracefully","category":"work","tags":["resign","quit","leave","step down","notice","committee","volunteer"],"triggers":["how to resign","quit my job","resignation letter","leave the committee","step down","stop volunteering","leave the team","hand in notice"],"summary":"How to leave a job, a board, a group or a volunteer role so people remember the exit as clean and generous.","updated":"2026-09-27","body":"# Leaving gracefully\n\n## Goal\nEveryone you leave behind would work with you again. The exit is short, kind, and leaves nothing hanging.\n\n## Resigning from a job\n\n**Do it in person or by call first, then a short written note.** The written note is a record, not the conversation.\n\n**Structure (conversation):** decision, stated clearly → one line of reason or none → last day → what you'll do to hand over → thanks, specific.\n\n**Script for the conversation:**\n> I wanted to tell you directly: I've decided to leave, and I'm giving my notice today. My last day would be the 30th. I've accepted a role that's a step toward [X]. I want to make the handover as clean as possible, so I've started a doc of everything I own and I'd like to spend the next four weeks making sure nothing drops. I've really valued working for you, particularly [specific].\n\n**Written note (email, after the conversation):**\n> Hi Maria,\n> Following our conversation, this is my formal notice of resignation. My last day will be Friday 30 August. Thank you for the past three years, and especially for backing me on the platform project. I'll make sure the handover is complete before I go.\n> Best,\n> Dan\n\n**If you're leaving because of problems:** you do not have to say why. \"It's time for a change\" is complete. Save the honest feedback for the exit interview if you want to give it, and keep it factual.\n\n**If they counter-offer:** \"I appreciate that, genuinely. I've made my decision and I'd like to keep it clean. Thank you.\"\n\n## Leaving a committee, board or volunteer role\n\n> Hi all,\n> I'm going to step down from the committee at the end of this term. I've loved being part of it, and I need to free up some time for [X]. I'll finish the [thing I own] before I go and I'm happy to help whoever takes over get up to speed. Thank you for having me.\n\n## Leaving a group chat / social group / regular commitment\n\n> I'm going to step back from Thursday football; my schedule's changed and I keep letting you down on numbers. Thanks for having me, and I'll come to the end-of-season thing.\n\n> Ducking out of this group, my notifications are too much. Message me directly any time, I'm still around.\n\n## Leaving a friend group project or shared commitment (harder)\n\n> I need to be honest with you both: I can't keep up my part of the podcast and I'd rather say it now than fade out. I'll finish the two episodes I owe and hand over the editing files. I'm sorry to let you down on it and I really hope you keep going.\n\n## Principles\n- Tell the person most affected first, directly. Not via the group.\n- Give a date. Vague exits linger.\n- Offer a handover and mean it.\n- Do not use the exit to settle scores. You can be honest without being final.\n- Do not over-explain the reason. It invites negotiation.\n- The last two weeks are what people remember. Work them properly.\n\n## Avoid\n- Resigning by text or email only.\n- Announcing to the team before telling your manager.\n- \"I've been unhappy for a long time\" as the opener.\n- Burning the bridge, even a bridge you never plan to cross.\n- Letting things quietly drop instead of formally leaving.\n\n## If they react badly\nAnger, guilt or a hard sell to stay all get the same response: hold the decision, keep it short, and do not re-argue the reason. If your manager goes cold for the notice period, keep doing the handover visibly and put it in writing so the record is clean. If a group takes the exit personally, one warm reply, then let it settle. Do not answer hostility with a parting speech.\n> I understand this isn't the news you wanted, and I'm not going to change my mind. I do want the next four weeks to be useful, so tell me what you'd like prioritised in the handover.\n> I know it leaves a gap for the committee and I'm sorry for that. I'll finish the grant report and brief whoever takes it on. That's what I can do, and I'll do it properly."},
{"id":"mediating-between-two-people","title":"Mediating between two people (friends who fell out, two teammates in conflict)","category":"personal","tags":["mediate","conflict","friends","teammates","peacemaker","middle"],"triggers":["two of my friends are fighting and i'm stuck in the middle","help two coworkers who don't get along","my friends want me to pick a side","how to mediate between two team members","my sisters aren't speaking","both of them are venting to me about each other","get two people to talk again","i'm the manager and two people on my team are clashing"],"summary":"When two other people are in conflict and you are in the middle: stay neutral, stop carrying messages, and help them talk directly. Friends, family, or two people you manage. Your own argument: de-escalate-argument.","updated":"2026-09-28","body":"# Mediating between two people\n\n## Goal\nThe two people talk to each other instead of through you, and you keep both relationships. You are not the judge and not the messenger. Your job is to lower the temperature and make a direct conversation easier; whether they make up is theirs.\n\nYour own argument with someone: `de-escalate-argument`. Giving one of them feedback as their manager: `give-feedback-to-colleague`.\n\n## Structure\n1. **Acknowledge each person privately**, one at a time. Hearing them is not agreeing with them.\n2. **Say plainly that you will not take sides or pass messages.** Kindly, once, early.\n3. **Suggest they talk directly**, and offer to help set it up if they want that.\n4. **If you are asked to be in the room, set simple ground rules**: one topic, each speaks without interruption, aim for one agreement.\n5. **Step back.** Check in once later, and leave the outcome to them.\n\n## Principles\n- Neutral does not mean silent. You can care about both people and still refuse to rule on who is right.\n- Do not relay what one said about the other. Messages carried by a third person get sharper on the way.\n- Keep confidences. What A told you in private is not yours to use to persuade B.\n- Look for the shared goal: the friendship, the project, the family event. People agree on the goal long before they agree on the facts.\n- As a manager, you are not neutral about behaviour. You can stay neutral on the personal dispute and still set clear expectations about how people treat each other at work.\n- Your job has limits. If there is abuse, harassment or a safety issue, it is not a mediation; point them to the right help (HR, a professional, or authorities).\n\n## Examples\n\n**Friend venting about the other friend:**\n> That sounds really hurtful, and I'm glad you told me. I care about you both, so I'm not going to take sides or pass anything on. I do think it's worth saying this to Jess directly. Want to talk through how you'd put it?\n\n**Declining to be the messenger:**\n> I'd rather not carry messages between you two, it'll only get muddled. If you want her to know that, it's better coming from you. I'm happy to help you word it.\n\n**Being asked to pick a side:**\n> I'm not going to pick a side, because I don't think it would help either of you. I'm still your friend, and I'll still be hers. I'd really like you two to talk.\n\n**Offering to host a conversation (friends or family):**\n> I know things are tense between you and Mia. Would you both be up for a coffee with me there? No ambush, I'll tell her the same thing. Just a chance to hear each other out.\n\n**Ground rules at the start of a joint conversation:**\n> Thanks for coming, both of you. Let's keep it to the trip money, one person talks at a time, and let's try to leave with one thing we agree on.\n\n**Manager, two teammates clashing (to each, privately):**\n> I've noticed things have been tense between you and Sam, especially in the release meetings. I'm not here to decide who's right. I need the two of you to find a way to work together, and I'd like to sit down with both of you on Thursday to agree how handoffs will work. Anything you want me to know before then?\n\n**Manager, setting expectations after the joint meeting:**\n> Thanks both. To confirm what we agreed: Sam sends the build notes by 3pm, Alex reviews by noon the next day, and disagreements come to me rather than going into the team channel. Let's check in again in two weeks.\n\n## Avoid\n- \"Well, she told me you said...\"\n- Summarising each person's case to the other.\n- Taking a side quietly while claiming to be neutral.\n- Forcing a reconciliation on a timetable, or a group hug in public.\n- Discussing the conflict with mutual friends or the wider team.\n- As a manager, waiting until it spills into the team channel.\n\n## If it goes badly\nIf one person refuses to talk to the other, respect it and stop pushing; say the offer stands and leave it there. If either one turns on you for not taking their side, stay calm and repeat that you care about both of them. If a joint conversation blows up, pause it kindly and suggest trying again another day, or with a neutral professional such as an HR partner, a counsellor or a community mediator. At work, if the conflict keeps affecting the team, it becomes a performance matter; handle it with each person individually.\n> I get that you wanted me on your side, and I'm sorry that's hard. I'm still your friend. That hasn't changed.\n> Let's stop here for today. I don't think we'll get further right now, and that's okay. Can we try again next week?"},
{"id":"messages-to-teachers-and-schools","title":"Messages to teachers and schools (concerns, meetings, absences, disagreeing with a decision)","category":"personal","tags":["school","teacher","parent","child","education","absence"],"triggers":["email my son's teacher about bullying","how to email a teacher about a bad grade","ask the teacher for a meeting","absence note for school","my kid is struggling in class what do i say to the teacher","disagree with the school's decision","complain to the principal","message the teacher about homework being too much"],"summary":"A parent writing to a teacher or school: raising a concern, asking for a meeting, absence notes, questioning a grade or a decision, and escalating. Specific, collaborative, about the child.","updated":"2026-09-28","body":"# Messages to teachers and schools\n\n## Goal\nThe teacher reads you as a partner, not an opponent, and something specific happens next: a meeting, a plan, a change. Teachers get many messages from anxious parents; the ones that work are short, specific and assume good intent.\n\n## Structure\n1. **Who you are**: your name and your child's name and class.\n2. **What you have noticed, as facts**: what your child said or did, when, how often.\n3. **A question or a request**, not a verdict. \"Have you noticed anything similar?\" \"Could we meet?\"\n4. **What you are doing at home**, if relevant. It shows you are working together.\n5. **Thanks, and your availability.**\n\n## Principles\n- Start with the class teacher. Going straight to the head or the governors usually slows things down and costs goodwill.\n- Your child's account is real to them and partial. Ask what the teacher saw before concluding.\n- One concern per message. A list of grievances gets triaged; one clear concern gets action.\n- Write in office hours and expect a reply in a day or two. Do not message a teacher's personal phone or social accounts.\n- For bullying, safety or wellbeing, be specific about dates and what happened, and ask what the school's process is. These deserve a prompt reply, and it is fair to say so.\n- Keep a copy of what you send. If you need to escalate, you will want the dates.\n- Assume the teacher cares about your child. Most do, and the message lands better when you write as if they do.\n\n## Examples\n\n**Raising a worry about a child's wellbeing:**\n> Hi Ms Patel, I'm Leo's mum (Year 4). Leo has come home upset three times this week, saying some boys at lunch won't let him sit with them and call him names. I don't know the full picture, so I wanted to ask whether you've noticed anything. Could we have a quick chat this week? I'm free after 3:15 any day. Thank you.\n\n**Asking for a meeting about progress:**\n> Hello Mr Owens, I'd like to understand how Maya is getting on in maths. She's been finding the homework hard and getting upset about it. Could we find 15 minutes in the next week or two? I'm happy to do a call if that's easier.\n\n**Absence note:**\n> Hi, Aisha (7B) will be off today and tomorrow with a stomach bug. We expect her back on Thursday. Could she pick up any work she misses? Thanks, Sarah Khan\n\n**Questioning a grade, collaboratively:**\n> Hi Dr Lin, Jamie showed me the feedback on his history essay (C). He was surprised, since he spent a lot of time on it. Could you tell me what the main gap was, so we can work on it at home? Thanks for your help.\n\n**Homework load:**\n> Hi Mrs Garcia, a quick note that Ben has been spending over two hours a night on homework, often until 9:30, and he's getting quite tired. Is that what you'd expect for Year 6? If not, I wonder if something is taking him longer than it should.\n\n**Disagreeing with a decision (a detention, a placement):**\n> Thanks for explaining the detention. I've talked with Ruby, and I understand the rule. I do think the circumstances were unusual, since she was helping a friend who felt unwell. Could we talk briefly about it? I'm not asking you to overturn it, I'd just like us to be on the same page.\n\n**Escalating after no response or no change (to the head of year):**\n> Dear Mr Ahmed, I'm writing about the lunchtime bullying Leo has experienced since 3 October. I raised it with Ms Patel on 5 and 12 October (copies below) and it has continued. Could you let me know what the school's next steps are, and when we could meet?\n\n## Avoid\n- Opening with \"I'm very disappointed\" or \"I demand\".\n- Copying the head into the first message.\n- Criticising the teacher to your child, or quoting them to other parents.\n- Long histories. Dates and facts, then the ask.\n- Messaging at 11pm and chasing at 7am.\n- Discussing other children by name, beyond what is needed to describe what happened.\n\n## If it goes badly\nIf the teacher is defensive, go back to the shared goal: your child doing well in their class. If there is no reply after three school days, send one short follow-up; after that, go to the head of year or the school office, with dates. If a formal decision still seems wrong, ask for the school's complaints policy and follow it in writing. If you believe your child is unsafe, contact the school's safeguarding lead directly and say so in the first line.\n> I think we both want Leo to feel settled at lunch. What would you suggest we try first?\n> I haven't heard back about my message on the 5th, so I'm following up. Could you let me know when we might talk?"},
{"id":"mixed-language-and-cultural-notes","title":"Cross-cultural and multilingual notes","category":"core","tags":["culture","international","directness","formality","translation","non-native"],"triggers":["message a Japanese colleague","too direct for them","cultural difference","they're from","writing in my second language","translate this politely","non-native english"],"summary":"Adjustments to directness, formality and structure when the other person's cultural or linguistic defaults differ from the user's. General patterns, not stereotypes.","updated":"2026-09-24","body":"# Cross-cultural and multilingual notes\n\nThese are tendencies, not rules. Always weight the individual's own messages over their assumed background. The mirror rule in `02-tone-calibration` still comes first.\n\n## The main dial: directness\nCultures differ most on how explicitly a no, a disagreement or a request is stated.\n\n**Higher-directness defaults** (common in the US, Netherlands, Germany, Israel, Australia): a plain \"no\" or \"I disagree\" is normal and respected. Softening too much reads as evasive or unclear.\n\n**Lower-directness defaults** (common in Japan, Korea, Thailand, Indonesia, much of the Middle East, often the UK and Canada in polite registers): a no is often implied (\"that might be difficult\", \"let me think about it\"). A blunt no can read as rude; a blunt disagreement can cause loss of face, especially in front of others.\n\n**Practical adjustments**\n- Writing to a lower-directness reader: add one sentence of acknowledgement before the point, offer the no as a difficulty or alternative rather than a flat refusal, and never disagree in a group message. Take it private.\n- Writing to a higher-directness reader: cut hedges, put the ask in line one, and do not apologise for asking.\n- Reading a message from a lower-directness sender: \"we will consider it\" and \"it may be difficult\" often mean no. Do not push for a harder answer publicly; ask privately and gently.\n\n## Formality\n- Some cultures expect titles and surnames until invited otherwise (Germany, Japan, Korea, much of Latin America in business). When unsure, start formal and mirror their reply.\n- Age and seniority carry more weight in many East Asian, South Asian and African contexts. A junior person messaging a senior one should be warmer and more formal than they would be with a peer.\n- Emoji, exclamation marks and first names are safe with peers almost everywhere under 40; be more careful with seniors and first contacts.\n\n## Structure\n- Some readers expect relationship first, business second (much of Latin America, the Middle East, South Asia): a line asking after them or their family is not filler, it is the message working. Skip it and you sound cold.\n- Others expect business first (Germany, Nordics, US business email): the pleasantries can go after the point or be omitted.\n\n## Writing to a non-native speaker\n- Short sentences. One idea each.\n- Avoid idioms, sarcasm and jokes that depend on wordplay.\n- Say the ask plainly; indirect English (\"you might want to consider\") is often missed.\n- Dates in unambiguous form: \"14 March\", not 3/14.\n\n## When the user is writing in their second language\n- Do not \"correct\" their voice into corporate English. Keep it simple and natural.\n- Suggest the version that is easiest to say and to read, not the most sophisticated.\n- If they ask for a translation of a diplomatic message, translate the intent, not the words; softeners do not map one to one.\n\n## Avoid\n- Stereotyping an individual from their name or location.\n- Over-formality as a default; many people find it distancing.\n- Assuming English-language norms of directness are neutral. They are not."},
{"id":"money-between-friends","title":"Money between friends (splitting, owed money, chasing)","category":"personal","tags":["money","owed","split bill","debt","venmo","pay back","awkward"],"triggers":["they owe me money","ask a friend to pay me back","split the bill","who pays","awkward money","remind them to pay","chip in"],"summary":"How to raise money with friends in a way that treats it as logistics, not character: clear numbers, easy method, no moralising.","updated":"2026-09-29","body":"# Money between friends\n\n## Goal\nThe money gets sorted and nobody feels judged. Treat it as admin. The moment it becomes about character, it costs more than the money.\n\n## Structure\n1. **Casual opener.**\n2. **The number and what it was for**, factual.\n3. **The easiest way to pay**, stated.\n4. **Optional deadline framed around your needs, not their failing.**\n5. **Light close.**\n\n## Principles\n- Be specific and fast. The longer a debt sits, the more awkward it gets for both of you.\n- Send the number, not a hint. \"Whenever you get a chance\" is a hint; \"£42 for the tickets, here's my link\" is a request.\n- No shame, no story. They almost certainly forgot.\n- If it is a pattern with someone, stop fronting money for them. That is the fix, not a better reminder.\n- If you decide to let it go, actually let it go. Do not let it go and then resent it.\n\n## Examples\n\n**First reminder, casual:**\n> Hey, whenever you're near your phone: £42 for the gig tickets, my link's [link]. No rush, just so I don't forget.\n\n**Second reminder:**\n> Bumping the £42 for the tickets, I've got rent going out Friday so it'd be a help before then.\n\n**Larger amount, direct:**\n> Can we sort the £300 from the trip? I've been carrying it a while and it's starting to matter on my end. If it's easier in two chunks that's fine, just let me know when.\n\n**Splitting a bill when the pot comes up short:**\n> We're about £30 short on the bill. I had the pasta and a glass of wine, so I've put in £24. Can everyone check what they had and top up?\n\n**Proposing a split before a trip (prevents most problems):**\n> Let's do a shared pot for the trip, everyone puts in £200 up front and we settle at the end. Saves the awkward maths.\n\n**Someone asks you to cover them again:**\n> I can't front it this time, I'm keeping things tight this month. Can you book your own and we'll meet there?\n\n**Deciding to write it off:**\n> Don't worry about the £15, call it even for the lift last week.\n\n## Avoid\n- \"I hate to bring this up, but...\"\n- \"I'm not made of money, you know.\"\n- Bringing it up in front of others.\n- Sarcasm.\n- Vague hints (\"remember that thing I paid for?\").\n- Letting it sit for months and then dumping it all at once.\n- Sending a payment request app notification with a passive-aggressive memo.\n\n## If they get defensive or keep not paying\nIf they snap (\"it's only £42\"), do not explain your finances; agree it is small and repeat the request once. If a third reminder gets nothing, decide: write it off for real, or say plainly that you will not front money again. The pattern is the fix, not a sharper reminder. Never raise it in front of others or through a pointed payment memo, however tempting.\n> Yeah, it's not a lot, which is why I'd like to get it done. Link's above whenever you're ready.\n> I'll stop chasing the £42. Going forward I'll book and pay separately, no hard feelings, it's just easier for me."},
{"id":"negotiate-price-or-salary","title":"Negotiating price, rate or salary","category":"work","tags":["negotiate","salary","rate","price","offer","counter","raise"],"triggers":["negotiate salary","counter the offer","ask for more money","they lowballed me","negotiate the price","my rate is","haggle","negotiate my rate"],"summary":"How to ask for more without sounding entitled or apologetic: anchor with a number and a reason, stay warm, and leave room for them to say yes.","updated":"2026-09-27","body":"# Negotiating price, rate or salary\n\n## Goal\nYou get closer to your number and the other side still wants to work with you. The tone is collaborative: \"how do we make this work\" not \"give me more\".\n\n## Structure\n1. **Enthusiasm first, genuine and short.** They need to know you want this.\n2. **The gap, factually.** \"The offer is at X; based on [market/scope/my last role], I was expecting closer to Y.\"\n3. **Your number, specific.** Not a range (they will take the bottom). Slightly above what you would accept.\n4. **One reason**, the strongest, framed as value to them.\n5. **Collaborative ask.** \"Is there flexibility there?\" or \"What would it take to get to Y?\"\n6. **Optional: name what else could move** (start date, equity, title, scope, payment terms) so a no on money is not a dead end.\n\n## Principles\n- Never apologise for negotiating. It is expected; not negotiating is the surprise.\n- Silence after your number is fine. Do not fill it by lowering your number.\n- Anchor with a number; \"more\" is not a negotiation.\n- Reasons about your needs (rent, kids) are weak. Reasons about your value or the market are strong.\n- Be the person they want to say yes to. Warm, calm, unhurried.\n- Get it in writing before you decline anything else.\n\n## Examples\n\n**Job offer, email:**\n> Hi Jordan,\n> Thank you for the offer, I'm genuinely excited about the role and the team. I want to be straightforward about one thing: the base is at $95k, and based on the scope we discussed and what I'm seeing for comparable roles, I was expecting closer to $110k. Is there flexibility to get there? If base is fixed, I'd be open to talking about a signing bonus or an earlier review. Either way I'm keen to make this work.\n> Best,\n> Alex\n\n**Freelance rate, client pushes back:**\n> I understand the budget's tight. My rate is $120/hour and that's where I need to be for this kind of work. What I can do is scope it tighter: if we drop [X], I can bring the total under your number. Would that work?\n\n**Client asks for a discount:**\n> I don't discount the rate, but I'm happy to find a version that fits your budget. What if we phase it: [smaller scope] now at [price], and the rest when it makes sense?\n\n**Buying something, private seller:**\n> I'm interested and can collect this week. Would you take £350? I know it's under asking; that's what I can do in cash today.\n\n**Raise conversation, script:**\n> I'd like to talk about my compensation. Over the last year I've [two specific results]. I've looked at the market for this role and I'm below it. I'd like to move to [number]. What would it take to get there?\n\n**They say no:**\n> Understood. Can we agree a date to revisit, say six months, with clear goals attached? And in the meantime, is there movement on [other lever]?\n\n## Avoid\n- \"I was hoping for a little more, if possible?\"\n- Giving a range.\n- Justifying with personal expenses.\n- Ultimatums you will not follow through on.\n- Accepting on the call. \"Let me review the full package and come back to you tomorrow\" is always fine.\n- Negotiating twice on the same point after they have moved once.\n\n## If they say no or go quiet\nA flat no on money is rarely the end. Move to the other levers you named, and get a date. If they go silent after your counter, wait two working days, then send one short nudge that keeps the offer warm.\n> Thanks for looking into it. If the base can't move, could we agree a review at six months with the target in writing, plus the earlier start date? That gets me to a yes.\n> Just checking in on the compensation question so I can give you a firm answer by Friday. Happy to talk it through on a call if that's easier.\nIf they withdraw the offer over a polite counter, that tells you something useful."},
{"id":"neighbour-disputes","title":"Neighbour disputes (noise, parking, fences, shared walls, escalation)","category":"personal","tags":["neighbour","neighbor","noise","parking","fence","building"],"triggers":["neighbor keeps parking in my spot","note to my upstairs neighbour about noise","neighbour's dog barks all day","their tree is over my fence","complain to the building about a neighbor","neighbour ignored my note","write to the council about my neighbour","neighbor party every weekend"],"summary":"Raising an ongoing problem with a neighbour (noise, parking, fences, pets, shared walls), then escalating in writing to the building, landlord or council. A friend's or housemate's habit: ask-to-change-behavior.","updated":"2026-09-28","body":"# Neighbour disputes\n\n## Goal\nThe problem stops and you can still nod at each other by the bins. You may live next to them for years, so start friendly, specific and easy to agree to. If that fails, escalate calmly, dated and in writing.\n\nLiving with the person: `roommate-and-shared-living`. A habit of a friend or family member: `ask-to-change-behavior`.\n\n## Structure\n1. **Introduce yourself if you have not met.** Name and flat or house number. People are kinder to a face than to \"the neighbour.\"\n2. **Assume they do not know.** Most people have no idea how sound carries.\n3. **The specific issue, with times or examples.** \"Music after midnight on weeknights,\" not \"constant noise.\"\n4. **One small, concrete ask.** A time, a spot, a trim, a rug.\n5. **An open door.** \"Let me know if anything from our side bothers you too.\"\n\n## Principles\n- Knock or leave a friendly note first. Going straight to the landlord, the building or the council turns a fixable annoyance into a feud.\n- Pick a calm moment, not 2am and not while angry.\n- Ask for what they can actually do. Parents cannot stop a toddler running; they can add a rug or keep play away from your bedroom.\n- Speak only for neighbours who agreed. A letter signed by three named households carries more weight than \"everyone on the street\", and a claim others did not sign up to will come out.\n- Keep a simple log from the start: dates, times, what happened.\n- Know who actually decides. Parking may be the building's rules, trees and fences local law, noise the council. Check before you threaten anything.\n- Escalate one step at a time, and tell them before you do. Surprise complaints end relationships; announced ones often fix the problem.\n\n## Examples\n\n**First note, noise from upstairs:**\n> Hi, I'm Dana from flat 3, just below you. I'm not sure how much carries, but footsteps and music come through quite clearly after about 11 on weeknights. Would you mind keeping it down after then? A rug might help too. Thanks, and shout if we ever bother you.\n\n**Parking, in person or a note on the door (not the windscreen):**\n> Hi, I'm Tom from number 12. The bay by the gate is ours on the lease, and it's been taken a few evenings this week. Could you use the visitor spaces instead? Easy mistake, the markings are faded.\n\n**Dog barking while they're at work:**\n> Hi, I live next door at 8. Rufus barks a lot while you're out, often for an hour or so around noon. I figured you'd want to know.\n\n**Tree or hedge over the fence:**\n> Hi Mr Okafor, your oak is hanging quite low over our side now and dropping into the gutter. Would you be OK with us trimming back the branches over our fence line? We'll cover the cost and hand back anything you'd like to keep.\n\n**Follow-up when it keeps happening:**\n> Hi again, about the late music. It's been past midnight three times this fortnight (the 4th, 9th and 11th). Is there anything that would make 11 easier for you?\n\n**Telling them before you escalate:**\n> I've asked a couple of times about the noise after midnight and it's still happening most weekends. I'd rather sort it between us, but if it carries on I'll raise it with the building manager.\n\n**Written complaint to the building, landlord or council:**\n> I'm writing about ongoing noise from flat 5, above mine. Since March there has been loud music after midnight on at least 12 nights; my log with dates and times is attached. I raised it with the resident in person on 2 March and in writing on 20 March. Please let me know what the next step is.\n\n## Avoid\n- Anonymous notes. They read as hostile and cannot be answered.\n- Notes on a car windscreen or taped to a door where others can read them.\n- Retaliating with your own noise, blocking their car, or cutting their plants without asking.\n- Posting about them in the neighbourhood group chat.\n- Exaggeration (\"every single night\") that the log does not support.\n\n## If it goes badly\nIf they react angrily at the door, do not argue the facts on the doorstep. Say you will leave it with them and walk away; follow up in writing a few days later. If they ignore two polite messages, escalate one step (building manager, landlord, managing agent, then council or mediation service), with your log and copies of what you sent. Many areas offer free community mediation, which works better than it sounds. If you ever feel threatened or there is harassment, stop engaging directly and contact the police or your local authority.\n> I can see this has landed badly, that wasn't my aim. I'll leave it with you and we can talk another time.\n> Since our chat hasn't changed things, I've asked the building manager to help. It's not personal, I'd just like a fix that works for both of us."},
{"id":"out-of-office-and-away-messages","title":"Out of office and away messages","category":"work","tags":["out of office","auto-reply","vacation","leave","away message","small business","freelancer"],"triggers":["write my out of office","auto reply for vacation","parental leave auto-reply","on sick leave message","shop closed for holiday message","freelancer at capacity reply","whatsapp away message","sabbatical email","back from holiday reply to customer"],"summary":"Auto-replies for vacation, parental, sick and sabbatical leave, a shop closed for a holiday, a freelancer at capacity, plus the message to send a customer once you are back.","updated":"2026-09-27","body":"# Out of office and away messages\n\n## Goal\nThe sender knows in ten seconds whether to wait, go elsewhere, or escalate, and they do not feel brushed off. You get to be away without a pile of \"did you see this?\" follow-ups.\n\n## Structure\n1. **Dates.** When you left, when you are back, in the sender's terms (\"back Monday 12 October\").\n2. **What happens to their message.** Read on return, not read, or forwarded.\n3. **Who to contact instead**, with one route each: urgent versus everything else. Name a person, not \"the team\". Working solo with nobody covering? Say so, then either give one narrow emergency route you will actually check (\"text [number] if a live project breaks, I check once mid-week\") or say plainly that everything waits.\n4. **One line of warmth or context** if it fits you. Optional.\n5. **Nothing else.** No apology, no list of what you are doing on holiday.\n\n## Principles\n- Under 60 words for most. Auto-replies get skimmed on phones.\n- Be honest about whether you will read it. \"I'll reply when I'm back\" is a promise; only make it if you will.\n- Give the cover person a heads-up before you name them, and put their name in exactly one place.\n- Humour works when it is one line, self-directed, and does not delay the information. It fails when it is the whole message, mocks the sender, or forces them to hunt for the dates.\n- For sick leave and bereavement, give less detail, not more. \"Away for a few weeks\" is enough. Your colleagues can say more if they need to.\n- Small businesses: put the reopening date and how to order in the meantime. Customers mostly want to know if they can still buy.\n- Freelancers at capacity: an \"away\" reply is still a sales message. Give the next available date and make it easy to book it.\n\n## Examples\n\n**Vacation, standard:**\n> I'm away until Monday 12 October and not reading email. For anything urgent, Nadia Weiss (nadia@[company]) is covering. Everything else, I'll reply in the week I'm back.\n\n**Vacation, with humour that does not backfire:**\n> I'm out until 12 October, somewhere with patchy signal and excellent bread. Nadia (nadia@[company]) has my projects until then; I'll reply to everything else when I'm back.\n\n**Parental leave:**\n> I'm on parental leave until early February and won't be checking this inbox. For [product] questions, please contact Jordan Reyes (jordan@[company]). For everything else, hello@[company] will route you. Thanks for your patience.\n\n**Sick leave (keep it minimal):**\n> I'm on leave for a few weeks and not reading email. Please contact Amir Haddad (amir@[company]) for anything active. Messages here won't be forwarded, so do resend if it's important.\n\n**Sabbatical:**\n> I'm on sabbatical until March 2027 and this inbox is closed. Client matters: Priya Nair (priya@[company]). Speaking or press: office@[company]. If it can wait until spring, I'd love to hear from you then.\n\n**Small business closed for a holiday (email):**\n> We're closed for the holidays from 23 December, reopening Monday 5 January. Online orders still go through and ship from the 5th. Anything ordered before the 20th has already shipped. Thanks for a great year.\n\n**WhatsApp or Instagram away status for a shop:**\n> Closed for the holidays, back Tue 6 Jan. Order online any time at [link]; we'll reply to messages when we reopen.\n\n**Freelancer at capacity:**\n> Thanks for getting in touch. I'm fully booked until mid-November, so I can't take new work before then. If your timeline allows, reply with a line about the project and I'll hold a slot for the week of 17 November. If you need someone sooner, I'm happy to suggest a name.\n\n## Avoid\n- \"I have limited access to email.\" Either you read it or you do not.\n- Listing everyone in the department with a topic each.\n- \"Sorry for any inconvenience.\" Being away is not a fault.\n- Jokes about how much you hate work, or about the sender's timing.\n- Leaving the auto-reply on after you return.\n- Detailed medical or family information in a sick-leave reply.\n- Forgetting the date format: \"back on the 5th\" means nothing on the 27th of another month.\n\n## When you are back\nSend this to a customer who wrote during the closure, before they have to chase:\n> Hi Elena, thanks for your message on the 28th, and thanks for waiting while we were closed. I've checked and the order is in stock; it'll ship today and you'll have tracking by this evening. If anything else came up in the meantime, I'm here.\nIf you cannot fix it immediately:\n> Thanks for your patience over the break. I'm back today and I'm looking at this first thing; you'll have a proper answer from me by tomorrow noon.\nIf someone is annoyed they had to wait:\n> That's fair, a week is a long time to wait for a reply. I'm on it now and I'll have it sorted by [time]. Thanks for sticking with us."},
{"id":"price-increase-and-customer-announcements","title":"Announcing a price increase, delay, closure or policy change to customers","category":"commerce","tags":["price increase","announcement","delay","closure","policy change","customers","newsletter","small business"],"triggers":["tell customers prices are going up","announce a delay","we're closing","change our policy","notify customers","shipping delay email","raise my rates","tell clients my rate is increasing"],"summary":"Customer-facing announcements that keep trust: the news early and plain, the reason in one line, what stays the same, what customers can do, and a real person's name.","updated":"2026-09-27","body":"# Announcing a price increase, delay or change to customers\n\n## Goal\nCustomers feel informed and respected, not blindsided or spun. Most people accept a change; they do not accept feeling tricked.\n\n## Structure\n1. **The change, in the first sentence.** Date and amount.\n2. **The reason, one honest line.** Costs, wages, quality. Not a paragraph.\n3. **What isn't changing** (quality, service, the thing they love).\n4. **What they can do**: lock in the old price, cancel easily, get help.\n5. **Thanks, and a real name.**\n\n## Principles\n- Early. Give real notice (30 days is standard; more for big changes).\n- Plain. \"Prices are going up 8% from 1 March\" beats \"we're adjusting our pricing structure\".\n- No apology for a fair increase. \"Sorry\" makes people think you're doing something wrong.\n- Make the exit easy. Customers who can leave easily are more likely to stay.\n- Send it from a person, not \"The Team\".\n- Do not over-justify. Every extra reason invites debate.\n\n## Price increase\n\n**Small business, email to customers:**\n> Hi Sam,\n> From 1 March, our prices are going up by about 8%: the medium candle moves from $28 to $30, and the large from $42 to $45. This is the first increase in three years and it covers what wax and shipping now cost us. Nothing about how we make them changes. If you'd like to stock up at current prices, the old prices hold on the site until the end of February. Thank you for keeping a small business going.\n> Ana\n\n**Freelancer, to an existing client:**\n> Hi Rob,\n> I'm updating my rates for the new year. From 1 January, my day rate moves from $600 to $680. For you, I'll hold the current rate through March so it doesn't affect the project in flight. I'm grateful for the work we've done together and I'm looking forward to more of it.\n> Nina\n\n**Subscription service:**\n> Your plan is changing from $9 to $11 a month from your next billing date after 1 April. Since you've been with us a while, you'll stay at $9 until July. You can cancel any time from your account page, no hoops. Here's what the extra covers: [two lines].\n\n## Delay\n\n> Hi Sam, your order #4521 is going to arrive later than promised: the new estimate is 22 May, about a week late. A supplier issue on our side, not yours. If that doesn't work for you, reply and I'll refund it in full, no questions. Otherwise, I'll send tracking the moment it ships. Sorry for the wait.\n> Ana\n\n**Bigger delay, many customers:**\n> We've hit a manufacturing delay and orders placed since 1 May will ship around 10 June instead of the end of May. If you'd rather not wait, reply to this email for an immediate full refund. If you can wait, we'll add [small make-good] to your order. We'll email again the day it ships. Thank you for your patience, and I'm sorry.\n\n## Closure or ending a service\n\n> After six years, we're closing the shop on 30 September. It's a personal decision, and a good one for us, but we'll miss this. Between now and then: everything's 20% off, gift cards can be used until the 30th (email us if you can't make it), and we'll help you find a new supplier for anything you regularly order. Thank you for six extraordinary years.\n\n## Policy change (returns, hours, minimums)\n\n> From 1 June, our return window changes from 60 days to 30. Anything ordered before 1 June keeps the 60-day window. The reason: returns after a month were mostly worn items we can't resell, and it was costing more than we could absorb. Everything else about returns stays the same: free label, fast refund.\n\n## Avoid\n- \"Due to unforeseen circumstances.\"\n- \"We regret to inform you.\"\n- Hiding the number.\n- Sending it from \"no-reply\".\n- Blaming customers or \"some people\".\n- Burying the change in a newsletter.\n\n## If customers push back\nA few will reply annoyed or threaten to leave. Answer each one personally, restate the change once, do not re-argue the reason, and make leaving genuinely easy. Most people who are given a graceful exit stay.\n> Hi Sam, I understand, and I'd rather you told me than quietly went elsewhere. The new price is what it costs us to keep making these properly, so it stands. If it no longer works for you, I'll cancel today with no fuss, and you'd be welcome back any time.\nIf someone is rude, stay factual and short. One reply, then let it rest. Do not offer a secret discount to the loudest person; the others will hear about it."},
{"id":"public-apology-from-a-business","title":"Apologising publicly as a brand or small business","category":"commerce","tags":["public apology","brand","outage","incident","social media","reputation","small business"],"triggers":["apologise as a business","public apology post","we had an outage what do we say","bad batch apology email","employee was rude to a customer apology","we made a pricing mistake","data incident customer notice","our post was offensive apology","reply to angry comments under apology"],"summary":"A public apology that makes things better: what happened, who was affected, what you are doing, what you promise, and nothing you cannot back up. Formats for post, email and pinned comment.","updated":"2026-09-28","body":"# Apologising publicly as a brand or small business\n\n## Goal\nAffected customers feel told the truth and taken care of, and everyone else sees a business that owns its mistakes. A public apology is mostly information; \"sorry\" appears once, early.\n\n## Structure\n1. **What happened, plainly, first sentence.** \"Our site was down for six hours on Tuesday.\"\n2. **Who was affected and how.** Numbers if you have them.\n3. **Sorry, once, from a named person.**\n4. **What you have already done.**\n5. **What affected customers get and how**, automatic where possible.\n6. **What changes so it does not repeat.** One or two specifics, not a \"full review\".\n7. **How to reach a human.**\n\n## Principles\n- Speed over polish. A short honest post within hours beats a lawyered statement in three days.\n- Match the size. A wrong price needs three sentences. A data incident needs a full email and a pinned post.\n- Promise only what you can verify. \"Never again\" is unkeepable. \"A second check before prices go live\" is not.\n- Do not name or blame an employee publicly. Own it as the business.\n- For a data incident, check your legal obligations on notification timing and content in every region where you have customers before you post, and say plainly what data was and was not involved.\n\n## Examples\n\n**Outage, social post:**\n> Our checkout was down from 9am to 3pm today and about 1,200 of you couldn't place orders. Sorry, that's on us: a failed update, now rolled back. Anything ordered today ships free, code TODAY until Sunday. Charged without a confirmation? Email me at [address] and I'll sort it within the day. Jo, founder.\n\n**Bad batch, email to buyers:**\n> Subject: Your order from batch 0417 and what we're doing\n> Hi [first name],\n> The hot sauce you ordered between 2 and 9 April came from a batch that didn't ferment properly. It's safe, but it tastes flat and some bottles separate. I'm sorry. A replacement ships this week at no cost, no action needed. If you'd rather have a refund, reply \"refund\" and it's done. We now test every batch before bottling rather than every third one.\n> Kemi\n\n**Rude employee, reply to a public complaint:**\n> I'm sorry that's how you were spoken to on Saturday. That's not the standard here and I've dealt with it. I'm sending you a DM now to refund your visit and invite you back as my guest. Thank you for telling us rather than just not coming back. Ana, owner.\n\n**Pricing mistake, post:**\n> For about 18 hours yesterday our site showed the leather tote at $19 instead of $190. We've honoured all 340 orders placed at that price; they ship next week. Sorry to anyone who saw it change mid-checkout. A second sign-off now sits before any price goes live.\n\n**Data incident, email (check your legal obligations first):**\n> Subject: A security incident affecting your account\n> Hi [first name],\n> On 12 June we found that an unauthorised person accessed a database containing customer names, email addresses and order history between 3 and 11 June. It did not contain passwords or payment details, which are stored separately and were not accessed. I'm sorry. We closed the access within two hours, reset all internal credentials and brought in an outside security firm. Be cautious of emails claiming to be from us that ask for payment or login details; we never ask for those by email. Questions: reply here or call [number]. We'll update you by [date].\n> Marco, CEO\n\n**Social media misstep, pinned post:**\n> Yesterday's post was thoughtless and it hurt people. It's down. Sorry, no excuses: it shouldn't have been written or approved. From now on two people sign off on every post. Comments are open and we're reading.\n\n**Pinned comment under the apology:**\n> Affected and not heard from us by Thursday? Email [address] with your order number and I'll reply personally. Jo.\n\n## Replying to angry comments under the apology\nSilence under your own apology looks like you posted and ran. Reply to each specific comment briefly and move detail to DM: \"You're right, and I'm sorry. Sending you a DM now to fix your order.\" If a comment is wrong on the facts, correct once, calmly: \"The outage was six hours, not two days. Anyone who ordered that day gets free shipping, including you.\" If a commenter is abusive, one reply, then stop. Do not delete unless it breaks the platform's rules or yours.\n\n## Avoid\n- \"We apologise for any inconvenience.\"\n- \"Mistakes were made.\"\n- \"We take this very seriously.\"\n- \"Some customers may have experienced.\"\n- Blaming a vendor or platform in public.\n\n## If it goes badly\nIf the apology gets more heat than the original problem, do not apologise for the apology. Reply to comments with actions taken and let the fixes speak. If someone says \"words are cheap\", agree: \"Fair. Here's what's done so far: [two actions]. I'll post an update on [date].\" Then post it."},
{"id":"push-back-on-boss","title":"Pushing back on your boss","category":"work","tags":["boss","manager","pushback","workload","unrealistic","disagree with manager"],"triggers":["my boss asked me to","tell my manager no","unrealistic deadline","too much work","push back on my boss","disagree with my boss","overloaded"],"summary":"How to say no or \"not like this\" to a manager while sounding like someone who is protecting the outcome, not avoiding the work.","updated":"2026-09-27","body":"# Pushing back on your boss\n\n## Goal\nYour manager sees you as someone who raises problems early with options attached. Not someone who says no, and not someone who silently drowns.\n\n## Structure\n1. **Align with the goal.** \"I want to get this done well.\"\n2. **The constraint, factual.** \"Right now I have A, B and C due this week.\"\n3. **The trade-off, made visible.** \"If I take this on, one of them slips.\"\n4. **Options, two or three, with your recommendation.**\n5. **Ask them to choose.** This is the key move: you are not refusing, you are asking them to prioritise.\n\n## Principles\n- Never a bare no. Always \"here's what it would take\" or \"here's what has to give.\"\n- Bring the trade-off to them; do not make it yourself and hope they do not notice.\n- Raise it as early as possible. Pushback on day one is planning; pushback on the deadline is failure.\n- Be specific about time. \"This is a two-day job\" beats \"this is a lot.\"\n- Written follow-up after a verbal conversation, so the decision is on record.\n\n## Examples\n\n**Unrealistic deadline, chat or email:**\n> I can get this done, but not to the standard we'd want by Thursday. To do it properly is about three days. Options: I deliver a rough version Thursday and the polished one Monday; or I push the Marsh report to next week and give this my full time. My recommendation is the first. Which do you prefer?\n\n**Too much on your plate:**\n> Quick priority check. I've got the launch deck, the Q3 numbers and the onboarding doc all due this week and I can realistically do two well. Which one can move? My suggestion is the onboarding doc, since it's internal.\n\n**Disagreeing with a decision:**\n> Can I flag a concern before we commit? I think [decision] risks [specific problem] because [reason]. If we've already weighed that, I'll get on board. If not, [alternative] might get us the same result with less exposure.\n\n**Being asked to do something outside your role, repeatedly:**\n> I've been picking up the invoicing for a few months now and I'm happy to help in a pinch, but it's now about four hours a week that's coming out of [core work]. Can we either make it official and rebalance, or move it back to finance?\n\n**Pushback on a weekend request:**\n> I can't do this weekend, I've got commitments I can't move. I can start first thing Monday and have it to you by noon. If it truly can't wait, let's talk about what else comes off my plate.\n\n**Written follow-up after agreeing:**\n> Just confirming what we agreed: I'll deliver the rough version Thursday and the final on Monday, and the Marsh report moves to the 14th. Shout if I've got any of that wrong.\n\n## Avoid\n- \"That's not my job.\"\n- \"I'm too busy.\"\n- Saying yes and then missing.\n- Complaining about workload without a proposed fix.\n- Pushing back in front of their boss or the team.\n- Making the decision for them silently.\n\n## If they insist anyway\nSometimes the answer is \"all of it, by Thursday\". Do not argue a second time. Say what will slip, confirm it in writing, and deliver what you said you could. The written record is what protects you when the deadline hits.\n> Understood, I'll make Thursday the priority. To be clear, that means the Marsh report moves to next week and this version will be rough rather than polished. I'll send it by 4pm.\nIf the pattern repeats every week, raise it separately in a one-to-one as a capacity problem, not a single-task problem: \"Can we look at my load overall? I'm at about 130% and I'd rather we fix that than keep triaging.\""},
{"id":"reconnect-after-silence","title":"Reconnecting after a long silence","category":"personal","tags":["reconnect","old friend","lost touch","reach out","awkward"],"triggers":["haven't talked in years","reach out to old friend","reconnect","lost touch","awkward to message","been a while"],"summary":"How to message someone you have not spoken to in months or years without the awkwardness swallowing the message. Answering a message you left for days or weeks: apologize.","updated":"2026-09-28","body":"# Reconnecting after silence\n\n## Goal\nMake the gap a non-issue in one sentence, then give them something specific and easy to respond to.\n\n## Structure\n1. **Name the gap lightly**, once. Do not apologise for it at length; they went quiet too.\n2. **A specific reason you thought of them** (a memory, something you saw, a real update).\n3. **One easy question** about them, or one low-stakes invitation.\n4. **No pressure to reply fast.**\n\n## Principles\n- Most people are relieved, not annoyed, when an old friend reaches out. The awkwardness is mostly yours.\n- Do not open with a favour. If you need something, reconnect first, ask in a later message or say the ask plainly and separately.\n- Do not try to catch up on everything in the first message.\n\n## Examples\n\n**Old friend, text:**\n> It's been about two years, which is absurd. I walked past that ramen place we used to go to and thought of you. How are things? No rush, just wanted to say hi.\n\n**Former colleague, LinkedIn or email:**\n> Hi Ana, long time. I saw the news about your move to [company] and wanted to say congrats, it looks like a great fit. If you're ever up for a coffee, I'd love to hear how it's going.\n\n**Someone you drifted from after a falling out (no big conversation, just warmth):**\n> Hey. I've been thinking about you lately and hoping you're doing well. No agenda. If you ever want to grab a coffee, I'd like that.\n\n**Reconnecting because you need something (be honest):**\n> I'll be upfront that I'm reaching out because I could use your advice on [X], and I feel a bit sheepish since we haven't talked in ages. Either way, I've thought about you and hope you're well. If you have 20 minutes some time, I'd be grateful; if not, no hard feelings at all.\n\n## Avoid\n- \"Sorry I've been such a bad friend\" (makes them console you).\n- A wall of updates about your life.\n- \"We should catch up sometime!\" with nothing concrete.\n- Reconnecting only when you need something, without acknowledging it.\n\n## If they reply warmly\nSuggest one specific thing within two messages: a call this week, a coffee on a named day. Momentum dies otherwise."},
{"id":"reply-to-customer-inquiry-dm","title":"Replying to a customer inquiry in DMs (Instagram, WhatsApp, Messenger)","category":"commerce","tags":["dm","instagram","whatsapp","customer inquiry","small business","sales","creator"],"triggers":["customer dm","reply to inquiry","someone asked about price in dm","instagram message from customer","how much is this","is this available","respond to a lead in messages"],"summary":"Fast, warm, conversion-friendly replies to price, availability and how-it-works questions in DMs, written for small businesses and creators.","updated":"2026-09-27","body":"# Replying to a customer inquiry in DMs\n\n## Goal\nAnswer the question in the first line, then move them one step closer to buying or booking, without pressure. DMs are conversations, not tickets.\n\n## Structure\n1. **Answer first.** Price, availability, yes/no. Do not make them ask twice.\n2. **One useful extra** they did not ask but will want (sizes, delivery time, what's included).\n3. **The next step**, specific and easy: a link, a question that moves toward a decision, an offer to hold it.\n4. **Their name if you have it, no sign-off.**\n\n## Principles\n- Speed is the biggest lever in DMs. A fast \"yes, $45, here's the link\" beats a perfect reply an hour later.\n- Match their energy. If they wrote two words, don't write two paragraphs.\n- Never \"DM for price\" style evasions. Give the number.\n- Ask one question, not three. Each question is a hurdle.\n- If they go quiet after a price, one gentle follow-up in 24 to 48 hours, then stop.\n- Sound like a person. No \"Thank you for reaching out to us!\"\n\n## Examples\n\n**\"How much is this?\"**\n> Hi Jess! That one's $45, and it comes in the green and the oat colour. Free shipping over $60. Want me to send the link, or hold one for you?\n\n**\"Is this still available?\"**\n> Yes, still here! It's the last one in medium. I can hold it till tomorrow evening if you want; just say the word.\n\n**\"Do you do custom orders?\"**\n> We do! Custom pieces start at $120 and take about two weeks. Tell me roughly what you're thinking and I'll give you a proper quote.\n\n**\"Can you tell me more about the workshop?\"**\n> Of course. It's Saturday the 14th, 2 to 5pm, at the studio in Peckham. $80 includes all materials and you leave with a finished piece. Beginner-friendly, max eight people. There are three spots left; want me to save you one?\n\n**Service business, \"are you free next week?\"**\n> I've got Tuesday 10am or Thursday 2pm free next week. Either work? If not, send me a couple of times and I'll make one fit.\n\n**Follow-up after silence (once):**\n> Hey Jess, just checking whether you'd like me to keep holding the green one; totally fine if you've gone off it.\n\n**They ask for a discount:**\n> I don't discount individual pieces, but if you grab two the shipping's free, and there's a 10% code for newsletter sign-ups. Want it?\n\n**Question you can't answer immediately:**\n> Good question, let me check with the maker and come back to you by tonight.\n\n## Avoid\n- \"Thanks for reaching out! Please visit our website for more information.\"\n- Copy-paste templates that ignore their actual question.\n- Three questions in one reply.\n- Emoji overload.\n- Hard-sell pressure (\"only 2 left, buy now!!\").\n- Leaving inquiries unanswered for a day.\n\n## If they go quiet or get rude\nSilence after a price is normal; it is not a no. One follow-up (see above), then leave it. If they come back in a week, greet them as if no time has passed. If someone gets rude about the price or the wait, keep it short and polite, and do not defend the number.\n> That's the price for these; no hard feelings if it's not for you. Thanks for asking.\nIf they argue further or start insulting you, stop replying. You do not owe a debate in your inbox, and a calm last message is what any onlooker will see."},
{"id":"request-intro-or-referral","title":"Requesting an introduction or referral","category":"work","tags":["intro","referral","introduction","network","warm intro","recommendation"],"triggers":["ask for an intro","can you introduce me","referral for a job","ask them to recommend me","connect me with","forwardable email"],"summary":"How to ask someone to use their relationship for you: make it zero-effort with a forwardable blurb, give them an out, and report back.","updated":"2026-09-27","body":"# Requesting an introduction or referral\n\n## Goal\nYour contact can forward one message and be done. The ask costs them almost nothing and puts their reputation at minimal risk.\n\n## Structure\n1. **The ask, in the first line.** Who, and why them.\n2. **Why it's a reasonable intro** (what you offer the other person, not just what you want).\n3. **A forwardable blurb**, separate paragraph, written in third person or as a self-introduction they can paste.\n4. **A real out.** They may not be close enough, or may not want to spend the capital.\n5. **Promise to report back.**\n\n## Principles\n- Double opt-in: the best intros ask the other person first. Make it easy for your contact to do that by giving them the blurb.\n- Never ask for an intro to someone you could just email yourself. Use intros for people who would otherwise ignore you.\n- Be specific about the ask you'll make of the other person. \"A 20-minute call about X\" not \"pick their brain\".\n- Report back. People stop making intros for those who vanish afterward.\n- For referrals (jobs), make it explicit they can say no without explanation; their name is on the line.\n\n## Examples\n\n**Intro request, email or DM:**\n> Hi Jo,\n> Could I ask a favour? I'd love an intro to Dana Park at Helix. I'm building a tool for exactly the onboarding problem she wrote about last month and I think a 20-minute conversation would be useful for both of us. If you're not close enough for that to be comfortable, no worries at all, just say.\n>\n> If you're up for it, here's a blurb you can forward:\n>\n> \"Dana, I'd like to introduce Sam Lee. Sam runs Northstar, which builds guest-checkout tools for e-commerce, and has some interesting data on the onboarding drop-off you posted about. Sam's asked for 20 minutes to compare notes; happy to connect you if you're open to it.\"\n>\n> I'll let you know how it goes either way. Thanks, Jo.\n> Sam\n\n**Job referral, to a friend at the company:**\n> Hey, I'm applying for the senior designer role at your place. Would you be comfortable referring me? Totally understand if you'd rather not put your name on it; we've never worked together directly, so I won't take it personally. If yes, I'll send you the job link and a two-line summary to make it painless.\n\n**Asking a former manager for a reference:**\n> Hi Priya, I'm in the final round for a role at [company] and they've asked for references. Would you be willing to be one? They'd call for about 15 minutes, sometime next week. If you're not able to, no problem, I'd just appreciate a quick heads-up so I can ask someone else.\n\n**Reporting back (do not skip this):**\n> Quick update: Dana and I spoke on Tuesday, really useful, and she's introduced me to their platform lead. Thank you for making that happen; I owe you a coffee.\n\n## Avoid\n- \"Do you know anyone who could help me with...?\" (vague, makes them do the thinking).\n- Asking for multiple intros at once.\n- Not providing a blurb.\n- Following up on the intro with your contact more than once.\n- Asking for an intro and then not using it.\n- Forgetting to close the loop.\n\n## If they say no or don't reply\nA no on an intro is about their relationship with the other person, not about you. Thank them and keep the door open. If they do not reply at all, one nudge after a week, then find another route; two chasers makes them avoid you.\n> No problem at all, thanks for letting me know. If it ever feels like a better fit down the line, I'd still be glad of it.\n> Hi Jo, resurfacing this in case it got buried. Totally fine to say no, I just want to know whether to try another path.\nIf they make the intro and it goes nowhere, still report back. Silence after their effort is what stops the next intro."},
{"id":"respond-to-an-ex-or-breakup-message","title":"Breaking up by message, or responding to an ex","category":"personal","tags":["ex","breakup","relationship","closure","get-back-together","stay-friends","belongings"],"triggers":["break up with my boyfriend","break up with my girlfriend","end my relationship","break up over text","want to end it by message","my ex texted me","ex reached out","how to reply to my ex","ex wants to get back together","stay friends with my ex","get my stuff back from my ex","closing the door with an ex"],"summary":"Ending an established relationship by message, replying when an ex reaches out, declining a reunion, friendship, belongings. Early dating: romantic-let-down. Kids' logistics: co-parenting-and-ex-logistics.","updated":"2026-09-28","body":"# Breaking up by message, or responding to an ex\n\n## Goal\nYou say what you actually want, with no cruelty and no false hope. They know where they stand after one read.\n\n## Ex reaches out, you want to close the door\n1. **Acknowledge briefly.** \"Good to hear you're doing well.\"\n2. **State the position in one sentence.** \"I'm not in a place to be in touch.\"\n3. **No reason, or one clean reason.** Reasons are debate material.\n4. **A kind full stop.** Then do not reply to the reply.\n\n## Ex reaches out, you are open to it\n1. **Warmth, honestly sized.** Do not overplay it.\n2. **Name the limit up front.** Friendship, a coffee, a conversation about what happened. Say which.\n3. **One concrete next step** with a date, so it does not drift.\n4. **Keep it slow.** Nothing you would regret if they went quiet.\n\n## Breaking up by message (when a call is not possible)\n1. **Say it in the first two lines.** Do not build up to it.\n2. **One true reason, not a list.** Lists invite rebuttal.\n3. **Own your part**, if that is true. \"This is about what I want, not what you did.\"\n4. **Say what happens next.** Belongings, shared plans, whether you will talk again.\n5. **No \"let's stay friends\" unless you mean it now.**\n\n## Declining to get back together\nA clear no, not a negotiation, plus one line of respect. Do not list their faults and do not leave \"maybe someday\" hanging unless it is true.\n\n## Friends or not\nSay which you can honestly do, and when. \"Not now\" is a legitimate answer. \"Yes\" should come with a shape: occasional, in groups, no late-night messages.\n\n## Belongings\nLogistics only. Date, method, done.\n\n## Principles\n- Clarity is the kindness. Ambiguity keeps them checking their phone.\n- The longer the message, the more it reads as an argument. Aim for four to six lines.\n- Never apologise for the decision. Apologise only for a specific thing you did.\n- Do not reply late at night. Draft, sleep, send.\n- If they behaved badly, you can be clear without being warm.\n\n## Examples\n\n**Ex texts \"hey, been thinking about you\", closing the door:**\n> Hi. Hope you're doing well, honestly. I'm not in a place to be in touch and I'd rather say that than go quiet. Take care of yourself.\n\n**Ex texts after months, reopening carefully:**\n> It's nice to hear from you. I'm open to a coffee and a proper catch-up, as friends, no expectations either way. Are you free Saturday around 11 at [cafe]?\n\n**Breakup by message, call not possible:**\n> I need to say this now rather than wait until you're back in three weeks, and I'm sorry it's by message. I don't want to carry on the relationship. I've felt for a while that we want different things, and I've stopped being honest with myself about it. This isn't about anything you did. I'll pack your things and can drop them at [place] on [date], or your sister can collect them.\n\n**Declining to get back together:**\n> I've read your message a few times and want to give you a straight answer, not a maybe. The answer is no. It's not to hurt you, it's what I know about myself.\n\n**Agreeing to stay friends, with shape:**\n> I'd like to stay friends, and I think it works best as group things and daytime for a while. Come to [name]'s birthday on the 14th if you're up for it.\n\n**Not staying friends, kindly:**\n> I don't think I can do friends, at least not for a long time. That's about me needing distance, not about you. I hope you've got good people around you.\n\n**Belongings, plain logistics:**\n> I've got your books, the grey hoodie and the charger in a bag. I can leave it with [neighbour / at reception] on Thursday, or you can collect it Saturday 2 to 4. Which suits?\n\n**Ex who treated you badly, no warmth required:**\n> Please don't contact me again. I won't be replying.\n\n## Avoid\n- \"I still care about you but...\" It reads as a hook.\n- \"Let's see how things go\" when you know how things go.\n- Asking how they feel about it in the same message.\n- Blocking without a line, when a line is safe to send. One sentence spares them weeks of guessing. If they are unsafe, just block.\n\n## If they push back\nIf they argue or bargain, you do not need to answer each point.\n> I've heard you and I'm not going to argue it. My answer is the same.\n\nIf they keep messaging after you asked them to stop, send one final line, then mute or block:\n> I asked you not to contact me. I'm going to mute this now.\n\nIf you reopened the door and they are moving faster than you want:\n> I'm glad we're talking, and I want to keep it slow. Let's stick to Saturday and see how it feels."},
{"id":"respond-to-angry-customer","title":"Responding to an angry customer or client","category":"work","tags":["customer","complaint","angry","support","service recovery","escalation"],"triggers":["angry customer","customer complaint","they're furious","respond to a complaint","upset client","calm a customer down","service recovery"],"summary":"The service-recovery sequence: acknowledge, own, fix, follow up. With examples for justified and unjustified anger.","updated":"2026-09-29","body":"# Responding to an angry customer\n\n## Goal\nThe customer feels heard within the first two lines, sees a concrete fix, and ends up more loyal than before the problem. Anger is usually about not being heard, not about the original issue.\n\n## Structure\n1. **Acknowledge the specific problem and its impact**, in their words. No \"I understand your frustration\" boilerplate.\n2. **Own it plainly** if it is yours. No \"but\".\n3. **The fix, concrete, with a time.** What you're doing, by when.\n4. **Make-good if warranted**, proportionate.\n5. **Direct line**: your name, how to reach you.\n6. **Follow up when you said you would.**\n\n## Principles\n- Speed matters more than polish. A fast \"I'm on it, details within the hour\" beats a perfect reply tomorrow.\n- Say what you will do, not what you cannot do.\n- Never argue about whether they should be angry.\n- If they are wrong on the facts, correct gently after acknowledging, with evidence, not with tone.\n- If they are abusive, you can be firm. \"I want to fix this, and I need us to keep it civil to do that.\"\n- Take it off public channels quickly, but respond publicly first so others see you responded.\n\n## Examples\n\n**Justified complaint, email:**\n> Hi Mr. Okafor,\n> You ordered on the 3rd, were promised delivery by the 8th, and as of today you have nothing and no update from us. That's not acceptable and I'm sorry. Here's what's happening: I've located your order, it's shipping today by express, and you'll have a tracking number by 5pm. I've refunded the shipping cost in full. I'm Dana, I own this until it's resolved; reply to me directly or call 0161 496 0123.\n> Dana\n\n**Customer angry about something that is not your fault:**\n> I'm sorry you've had this experience, it sounds genuinely frustrating. Looking at the account, the charge came from PayFast, not from us, so I can't refund it directly, but I can do two things: send you the exact transaction reference to dispute it with them, and stay on this with you until it's resolved. Would that help?\n\n**Angry DM on Instagram (public-facing, keep short):**\n> I'm really sorry about this, it's not what we want for you. I'm sending you a DM right now to get the order details and sort it today.\n\n**Customer is wrong on the facts:**\n> I completely understand why you'd expect a refund here. I've checked, and the return window on this item was 14 days and it was returned on day 22. I can't refund it, but I can offer store credit for the full amount or an exchange. Which would you prefer?\n\n**Customer is abusive:**\n> I want to help you and I'm going to. I need us to keep this respectful so I can focus on fixing it. Here's what I can do right now: a replacement sent by express today, at no cost.\n\n**Follow-up after resolving:**\n> Just checking the replacement arrived and everything's working. If anything's off, I'm still here.\n\n## Avoid\n- \"I understand your frustration.\"\n- \"Unfortunately, our policy...\" as an opener.\n- \"We apologise for any inconvenience.\"\n- Asking them to repeat details you already have.\n- Promising a call-back time and missing it.\n- Explaining internal processes.\n- Defending the person who made the mistake.\n\n## If they stay angry\nSome people need to say it twice. Do not repeat your apology at length; restate the fix and the time, and ask what would make it right if the fix is not enough. If the demand is unreasonable, hold the line without the tone.\n> I hear you, and I'm still on it: the replacement ships today and I'll confirm tracking by 5pm. If there's something beyond that you need from me, tell me and I'll look at it properly.\n> I can't do a full refund and have you keep the item, but I can do a full exchange or a 50% refund today. Which works?\nIf they threaten reviews or lawyers, ignore the threat. Fix the thing and stay on the facts."},
{"id":"respond-to-criticism","title":"Responding to criticism","category":"personal","tags":["criticism","feedback","defensive","called out","blamed","accused"],"triggers":["they criticized me","someone called me out","got negative feedback","they blamed me","respond to complaint about me","feel attacked"],"summary":"How to respond to criticism, fair or unfair, without getting defensive: acknowledge what is true, ask about what is unclear, and hold your ground on what is wrong.","updated":"2026-09-24","body":"# Responding to criticism\n\n## Goal\nWhatever is true in the criticism, you own it. Whatever is unclear, you ask. Whatever is wrong, you say so calmly. The critic feels heard, and you have not shrunk.\n\n## Structure\n1. **Pause.** Do not reply in the first ten minutes if it stung.\n2. **Thank them or acknowledge the effort**, if it was offered in good faith.\n3. **Reflect the point in your own words** so they know you understood.\n4. **Sort it into three buckets** in your reply: what you agree with, what you want to understand better, what you see differently.\n5. **What you'll do next.**\n\n## Principles\n- The instinct to explain why it happened reads as an excuse. Explain only if asked.\n- \"You're right about X\" costs nothing and buys everything. Find the X.\n- You can accept a criticism without accepting the tone it came in.\n- For unfair criticism, you do not have to agree, but you do not have to fight either. \"I see that differently\" is complete.\n- Asking a question is stronger than defending. \"What would you have wanted me to do instead?\" moves it forward.\n\n## Examples\n\n**Fair criticism from a friend:**\n> That's fair. I've been flaky lately and I know it. Thanks for actually saying it instead of just going quiet. I'll do better, starting with Friday, which I will be at.\n\n**Criticism that is partly fair, work:**\n> Thanks for the straight feedback. You're right that the report went out late and that's on me. On the data question, I think there's a misunderstanding about the source; can we look at that together? I want to make sure I'm fixing the right thing.\n\n**Criticism you think is wrong:**\n> I appreciate you raising it directly. I see this differently: [one sentence]. I'm not trying to shut it down, I just don't want to agree with something I don't think is accurate. Happy to talk it through.\n\n**Criticism delivered harshly:**\n> I hear the point, and I'll take it on board. I'd ask that next time we talk about it before it gets to this level, because I'd genuinely rather fix things early.\n\n**Public criticism (group chat, comment):**\n> Fair point about [X]. Let me follow up with you directly so I don't clog the thread.\n\n**Criticism from a partner about a pattern:**\n> I don't love hearing this and I think you're right. I don't want to be the person who does that. Can you tell me next time it happens, in the moment, so I catch it?\n\n## Avoid\n- \"I'm sorry you feel that way.\"\n- \"But you also...\"\n- \"I was only trying to help.\"\n- Listing everything you did right.\n- Over-apologising to end the discomfort quickly.\n- Replying immediately when angry.\n\n## If you need time\n> I want to give this a proper response and not a defensive one. Can I come back to you tomorrow?"},
{"id":"respond-to-difficult-health-news","title":"Responding to someone's difficult diagnosis or health news","category":"personal","tags":["diagnosis","illness","health","cancer","support","hospital"],"triggers":["my friend just told me she has cancer","what to say when someone tells you their diagnosis","coworker told me he's sick","reply to my mom's test results","friend is in hospital what do i text","what not to say to someone with cancer","my friend has a chronic illness","dad's diagnosis text back"],"summary":"The first reply and the weeks after someone tells you about a serious diagnosis or health news: acknowledge, follow their lead, offer specific help, skip the questions and the advice. A death: condolences-and-support.","updated":"2026-09-27","body":"# Responding to difficult health news\n\n## Goal\nThe person feels heard, not managed. They should not have to reassure you, educate you, or answer a list of questions. Your reply says three things: I heard you, I care, and here is something concrete I can do, with no need to reply.\n\nAfter a death, use `condolences-and-support`. For someone who has gone quiet during a long hard time, `check-in-on-someone-struggling`.\n\n## Structure\n1. **Acknowledge the news plainly.** \"I'm so sorry you're dealing with this\" is enough. Do not look for the perfect line.\n2. **Thank them for telling you**, if they told you directly. It often took effort.\n3. **Follow their tone.** If they wrote it matter-of-factly or with a joke, you can be lighter. If they were scared, be steady.\n4. **One specific offer**, or a standing one with a date.\n5. **Release them from replying.**\n\n## Principles\n- It is their news to share. Do not pass it on, and do not ask \"who else knows?\"\n- Questions about prognosis, stage, survival odds or cause are for them to volunteer, not for you to ask. \"How did you find out?\" and \"Did you smoke?\" both land as judgement.\n- No stories about someone else with the same illness, especially ones that ended badly.\n- No cures, diets, articles or \"have you tried\". Their doctors have this; you are there for the person.\n- Avoid \"everything happens for a reason\" and \"stay positive\". They make fear feel like a failure.\n- Keep showing up. Messages dry up after the first week, which is when the hard part usually starts. Set a reminder to check in again.\n- A colleague's news at work stays professional: warmth plus practical flexibility, and privacy about the details.\n\n## Examples\n\n**Close friend, just told you:**\n> Oh, Jess. I'm so sorry. Thank you for telling me. I'm here for all of it, the scary bits and the normal bits. Can I bring dinner on Thursday? No need to reply tonight.\n\n**Parent sharing test results:**\n> Thank you for telling me straight, Mum. I'm coming up on Saturday, and I'd like to come with you to the next appointment if you'd like that. I love you.\n\n**They told you with humour:**\n> Only you could announce a tumour with a pun. I'm so sorry, and I'm fully on board for the gallows humour. Also on board for lifts to the hospital, just give me dates.\n\n**Friend in hospital:**\n> Just heard you're in. Thinking of you. I won't visit unless you say so, but I can feed the cat and bring whatever you need. Tell me one thing and I'll do it.\n\n**Colleague told you privately:**\n> Thank you for trusting me with that. I'm really sorry. Whatever you need on the work side, whether it's cover for appointments or just not being asked about it, tell me and I'll make it happen. It stays with me.\n\n**Chronic illness, a friend explaining why they keep cancelling:**\n> Thank you for telling me, that makes a lot of sense and I'm sorry it's been so hard. No explaining needed going forward. I'll keep inviting you, and \"not today\" is always a fine answer.\n\n**Check-in a few weeks later:**\n> Thinking of you today. No need to reply. I'm free Sunday afternoon if you'd like company, or a walk, or a film on the sofa.\n\n## Avoid\n- \"I know how you feel.\"\n- \"My aunt had that and...\"\n- \"Let me know if you need anything.\" Replace it with one real offer.\n- A list of questions about the medical details.\n- Sending articles, cures or supplement links.\n- Making your shock the centre (\"I can't stop crying, this is so hard for me\").\n\n## If it goes badly\nIf you said the wrong thing (asked about odds, told a bad story, sent advice), own it in one line and return to them: no long apology that makes them comfort you. If they do not reply for weeks, keep sending short, no-reply-needed messages; silence is usually exhaustion, not rejection. If they say they want space, respect it and ask if they would like you to check back in a month.\n> I've been thinking about what I said about my aunt, and it wasn't what you needed. I'm sorry. I'm here, and I'll follow your lead.\n> Still thinking of you. No need to reply, I'll keep sending the odd message unless you'd rather I didn't."},
{"id":"respond-to-job-rejection","title":"Responding to a job or pitch rejection","category":"work","tags":["rejection","interview","feedback","job search","pitch","hiring","gracious"],"triggers":["got rejected after the interview","reply to a rejection email","they went with someone else","ask for feedback after rejection","lost the pitch","client chose another agency","recruiter ghosted me","didn't get the job","respond to rejection"],"summary":"Closing a rejection so they remember you well, asking for feedback in the one way that gets answered, and what to send when they ghost instead of saying no.","updated":"2026-09-27","body":"# Responding to a job or pitch rejection\n\n## Goal\nThe person who rejected you finishes reading your reply thinking \"I hope we get to work with them later\". You get one useful piece of information if it exists, and you leave with your dignity and their number.\n\n## Structure\n1. **Thank them for the specific thing**, not \"the opportunity\". The time, the depth of the process, a conversation you actually enjoyed.\n2. **Accept the decision in one line.** No re-litigating, no \"I'm surprised\".\n3. **One small ask, optional.** Feedback, or to be kept in mind. Never both in the same message.\n4. **Make the ask easy to answer**: a narrow question, a stated time budget, and permission to skip it.\n5. **Close warm and short.** Name a future you would welcome.\n\n## Principles\n- Reply within a day. A rejection reply that arrives fast reads as composed; one that arrives a week later reads as brooding.\n- The single way to get real feedback is to ask a narrow question and make it cheap to answer. \"Any feedback?\" gets a template. \"Was there one thing that would have changed the outcome?\" gets a sentence, and a sentence is what you need.\n- Ask for feedback from the person you spoke with most, not the recruiter, unless the recruiter is all you have.\n- Hiring decisions are mostly about the other candidate, the budget, or timing. Take feedback as data, not verdict.\n- Bitterness leaks. If you cannot write it warm yet, wait a day, then write it.\n- Being kept in mind is real. Around one in ten hires at small companies comes from a previous runner-up. Make that easy by staying friendly and visible.\n\n## Examples\n\n**Gracious close that keeps the door open:**\n> Hi Priya, thanks for letting me know, and for how open the whole process was. I enjoyed the conversation with Tom about the migration, and I'd be glad to talk again if a similar role opens up. Good luck with the launch.\n> Sam\n\n**Asking for feedback after rejection (the version that gets answered):**\n> Thanks for the update, and no hard feelings. One quick question, only if it takes you under a minute: was there one thing that would have tipped it the other way? A single line is plenty, and it's fine to say you can't share. Either way, thank you for your time.\n\n**\"We went with someone else\" after a long process (four rounds, take-home task):**\n> Thanks for telling me directly. Four rounds plus the task was a real investment on both sides, so I'd value one specific thing from the panel, if you're able to share it. And I'd genuinely like to be considered for the next opening on the team. Congratulations on the hire.\n\n**Rejected by a client after a pitch:**\n> Thanks for the decision, Marcus, and for the clear brief throughout. If you're able, I'd like to know whether it came down to price, approach or fit, so I pitch better next time. One word is enough. If the project needs a second pair of hands later, I'm around.\n\n**Recruiter says the role was closed or paused:**\n> Understood, thanks for the heads-up. Would you keep me on your list for anything similar in [area], ideally in the next quarter? Happy to send an updated CV whenever useful.\n\n**Short reply to a template rejection (no relationship to protect):**\n> Thanks for letting me know. Best of luck with the search.\n\n**Responding to feedback that stings but is fair:**\n> That's useful, thank you for being straight with me. I'll work on [the specific point]. If the team is hiring again in six months, I'd like another shot.\n\n## Avoid\n- Asking why. \"Why\" makes people defensive; \"what one thing\" makes them helpful.\n- \"I'm surprised, I thought the interview went well.\" True or not, it sounds like a complaint.\n- Replying to all, or to the CEO, when the rejection came from a recruiter.\n- Explaining your circumstances, your other offers, or how much you wanted it.\n- Sending a rewritten application or a \"what if I did it at a lower salary\" counter.\n- Naming the person you assume they hired.\n\n## If they ghost instead of rejecting\nTwo touches, then let it go. After the date they gave you, wait three working days.\n> Hi Priya, checking in on the [role] decision, since you'd mentioned hearing back by the 20th. If it's a no, a one-line reply is completely fine and I'd appreciate the closure.\nOne week later, if still nothing:\n> I'll take silence as a no and close this on my end. Thanks for the conversations, and I'm open to talking again if things change.\nThen stop. Do not chase a third time. Log it, move on, and if they come back months later, you can still say yes."},
{"id":"respond-to-negative-review","title":"Responding to a negative review (public)","category":"commerce","tags":["review","negative review","google review","yelp","public response","reputation"],"triggers":["respond to a bad review","one star review","negative review reply","someone left a bad review","public complaint","respond on google"],"summary":"Public review replies are written for the next customer reading, not the reviewer: short, specific, non-defensive, with an offer to fix it offline.","updated":"2026-09-27","body":"# Responding to a negative review\n\n## Goal\nThe next hundred people who read the review see a business that listens and fixes things. The reviewer is the audience of one; the readers are the audience that matters.\n\n## Structure\n1. **Thank them for the specific feedback** (not \"for taking the time\").\n2. **Acknowledge the specific problem**, in your words, briefly. Do not repeat every complaint.\n3. **Own what's yours** in one line. If it is not yours, state the fact once, neutrally.\n4. **What you've changed or offered.**\n5. **Invitation to continue offline**, with a name and a direct contact.\n6. **Sign with a real name.**\n\n## Principles\n- Reply within 48 hours. Old unanswered reviews look worse than the review itself.\n- Under 120 words. Long replies look defensive.\n- Never argue, even when they are wrong. Correct facts once, calmly, then move on.\n- Never reveal the customer's private details in a public reply.\n- Do not offer compensation publicly (it invites more one-star reviews). Offer to \"make it right\" and do it in private.\n- Do not copy-paste the same reply across reviews. People check.\n- Tone: calm, human, slightly warmer than the review.\n\n## Examples\n\n**Legitimate complaint, restaurant:**\n> Thank you for this, Maria, and I'm sorry: a 40-minute wait for mains on a Tuesday isn't the standard we hold ourselves to. We were short two staff that night and handled it badly. We've changed how we manage the floor when that happens. I'd like to make it right; please email me at [address] so I can. Tom, owner.\n\n**Complaint that's partly wrong:**\n> Thanks for the feedback, Jake. I'm sorry the fit wasn't what you expected. One small correction for anyone reading: we do accept returns within 30 days, and I've messaged you directly to sort that out. If anything else was off, I'd like to hear it. Sara.\n\n**Unfair or hostile review:**\n> Thanks for the review. I'm sorry your experience didn't match what most of our customers describe. I'd genuinely like to understand what happened; I've reached out directly and I'm here at [address] if you'd like to talk. Dev.\n\n**Review about something out of your control (delivery courier):**\n> I'm sorry the parcel arrived late and damaged. That's the courier's failure, but you ordered from us, so it's ours to fix. A replacement is on its way and we've raised it with the carrier. Thank you for telling us. Ana.\n\n**Review that's actually about a different business:**\n> Hi Sam, thanks for the review; I think this may be meant for a different [business type] as we don't offer [X]. If I'm wrong, please email me at [address] and I'll sort it straight away. Lee.\n\n**Reviewer was rude to staff:**\n> Thank you for the feedback. I'm sorry you left unhappy. I've spoken with the team about the evening and I'm satisfied they handled a difficult situation professionally. If you'd like to discuss it further, I'm available at [address]. Jo, manager.\n\n## Avoid\n- \"We're sorry you feel that way.\"\n- \"This is the first time anyone has complained.\"\n- Quoting the customer's own words back at them.\n- Explaining internal problems in detail.\n- Pointing out that they have other bad reviews.\n- Legal threats.\n- Not replying.\n\n## If they reply and escalate\nReviewers sometimes edit the review or add a second, angrier one after your response. Reply once more, shorter, and then stop; a public back-and-forth loses you readers regardless of who is right. Move everything else to private.\n> I'm sorry it's still not resolved. I've sent you a direct message with my number so we can sort it today. Tom.\nIf the review is defamatory or clearly fake, do not say so in the reply. Flag it to the platform with evidence and leave your calm first response standing. Never respond from a personal account or ask friends to pile on."},
{"id":"respond-to-passive-aggressive","title":"Responding to a passive-aggressive message","category":"personal","tags":["passive-aggressive","snarky","sarcastic","dig","tone","cold"],"triggers":["they sent a passive aggressive text","snarky message","sarcastic reply","what did they mean by that","cold message","fine","respond to a dig"],"summary":"How to respond to snark or a cold message without taking the bait: reply to the content, name it only if needed, and stay warm.","updated":"2026-09-27","body":"# Responding to passive-aggression\n\n## Goal\nYou do not escalate, you do not grovel, and you give them an off-ramp to say what they actually mean.\n\n## The three options\n1. **Take it at face value.** Respond to the literal content, warmly, as if there were no dig. This defuses most cases because it denies the dig any oxygen.\n2. **Name it gently and ask.** \"I might be reading tone into this, but are you annoyed about something? Genuinely asking.\"\n3. **Move to a richer channel.** \"Can I call you? Text is making this weirder than it needs to be.\"\n\nUse 1 for one-off snark. Use 2 when it is a pattern or clearly about something real. Use 3 for people you care about.\n\n## Principles\n- Do not match the tone. Matching is what they are (often unconsciously) inviting.\n- Do not interpret the dig out loud (\"so what you're saying is I'm useless\"). You will be told you are overreacting.\n- Short and warm beats long and defensive.\n- If they are angry about something legitimate, the passive-aggression is the wrapper; deal with the contents.\n- Silence is a legitimate response to a pure dig with no content.\n\n## Examples\n\n**\"Must be nice to have time for the gym.\"**\nFace value:\n> It really is! I've been forcing myself. Want to come Thursday?\n\n**\"Fine.\" / \"Whatever you want.\"**\nName it:\n> That sounds like not-fine. What would you actually prefer? I'd rather know.\n\n**\"Thanks for finally replying.\"**\nFace value with a small own:\n> Sorry it took me a while, this week's been a lot. What's up?\n\n**\"I guess I'll just do it myself then.\"**\nName and offer:\n> Sounds like you're frustrated I didn't get to it. Fair. Do you want me to take it now, or has that ship sailed?\n\n**A sarcastic message in a group chat aimed at you:**\nFace value, briefly, then move on:\n> Ha, fair. Anyway, Saturday: who's in?\n\n**Cold email from a colleague (\"Per my last email...\")**\nWarm and factual:\n> Thanks for resending, I'd missed it. Answers below. Let me know if anything's still unclear.\n\n**Repeated pattern with someone close:**\n> I've noticed a few messages lately that feel a bit sharp and I don't want to guess at what's going on. If something's bothering you, I'd honestly rather hear it straight. If I'm imagining it, tell me that too.\n\n## Avoid\n- \"Wow, okay.\"\n- Sarcasm back.\n- A paragraph explaining yourself.\n- \"What's that supposed to mean?\" (invites a fight; use \"are you annoyed?\" instead).\n- Screenshotting it to others before talking to them.\n\n## If they deny it or get sharper\n\"I'm not annoyed\", in a tone that clearly is. Do not push for a confession; you named it, they declined, and that is their call. Take them at their word once and carry on warmly. If the digs continue, the second time you name the pattern rather than the message, and you make it a choice for them.\n> Okay, glad to hear it. So, Thursday still good?\n> This is the second time I've asked and got a sharp reply. I'm not going to keep guessing. When you want to talk about it properly I'm here, and until then I'm going to take messages at face value.\nThen do exactly that."},
{"id":"respond-to-recruiter","title":"Responding to a recruiter","category":"work","tags":["recruiter","linkedin","job search","headhunter","salary range","interview","decline role"],"triggers":["recruiter messaged me","reply to a recruiter","recruiter on linkedin","ask recruiter for salary range","not interested in the job","keep in touch with recruiter","recruiter went quiet","decline the role after the call","headhunter reached out"],"summary":"Replying to inbound recruiter messages, whether you are interested, not now, or not at all, plus getting the comp range before the call and following up when the recruiter goes quiet.","updated":"2026-09-27","body":"# Responding to a recruiter\n\n## Goal\nEvery recruiter who contacts you leaves with a clear answer and a slightly better opinion of you. The good ones come back with better roles. The ones you decline stop chasing.\n\n## Structure\n1. **Thank them in five words or fewer.** \"Thanks for reaching out.\"\n2. **Your answer, in the first two lines.** Interested, not now, or no. Do not bury it.\n3. **The one thing you need to move forward, if interested.** Usually the comp range, sometimes location or the team. Ask before booking a call.\n4. **A concrete next step.** A time window, a request to stay in touch, or a clean close.\n\n## Principles\n- Reply to everyone you might want to hear from again. A two-line no costs nothing and keeps the channel warm.\n- Ask for the range before the call. It is a normal question, and a recruiter who will not answer it is telling you something about the role.\n- \"Not now\" needs a reason with a date attached, otherwise it reads as a soft no and they stop writing.\n- You do not owe a reason for a no. \"Not a fit for me\" is a full sentence.\n- LinkedIn replies are three sentences. Email replies are five. Save the paragraph for the call.\n- Never bluff about competing offers or current comp. Recruiters compare notes.\n\n## Examples\n\n**Interested, asking for the range first, LinkedIn:**\n> Thanks for reaching out, this sounds interesting. Before we book a call, could you share the base range and whether the role is remote? If those line up I'm free Thursday or Friday afternoon.\n\n**Interested, email version:**\n> Thanks for the note. I'm open to a conversation. Two questions before we set a time: what's the compensation band for the role, and is it fully remote or hybrid out of the Austin office? If those work for me, I can do a 30 minute call Thursday between 2 and 5 or Friday morning.\n\n**Not now, keep in touch:**\n> Thanks for thinking of me. I'm six months into a new role and not looking, but I'd like to hear from you again around March next year. Happy to connect here in the meantime.\n\n**Not interested, LinkedIn length:**\n> Thanks for reaching out. This one isn't a fit for me, but feel free to keep me in mind for senior platform roles in the future.\n\n**Not interested, and you want them to stop:**\n> Thanks, but I'm not looking and I'd rather not be contacted about roles. All the best with the search.\n\n**Declining after learning about the role:**\n> Thanks for walking me through it yesterday. Having thought it over, I'm going to pass. The role is more people management than I want right now. I appreciated your time, and if something more hands-on comes up I'd be glad to hear about it.\n\n**Comp range is too low:**\n> Thanks for sharing the band. It's below what I'd need to move, my floor is [$165k base]. If there's flexibility on that I'm happy to talk, otherwise no hard feelings and please keep me in mind for roles at that level.\n\n**Following up when the recruiter goes quiet:**\n> Hi [Name], checking in on the [Company] role. We spoke on the 3rd and you mentioned an update by the end of that week. Is the position still open? If it's moved on, no problem, just let me know so I can plan accordingly.\n\n## Avoid\n- Ignoring the message. Silence is a no with none of the upside.\n- Sharing your current salary. Share your target, or ask for their range.\n- Booking the call before you know the range, the location and the level.\n- \"I'm not really sure, maybe, let me think about it\" with no date attached.\n- Long explanations of why you are happy where you are. One line.\n- Telling a recruiter you are \"open to anything\". You will get everything.\n\n## If they push back\n\n**They refuse to share the range before a call:**\n> I understand. To save us both time, my floor for a move is [$165k base]. If the role is in that range, let's book the call. If not, I'll pass for now.\n\n**They keep messaging after a no:**\n> As I mentioned, I'm not looking. Please remove me from your outreach list. Thanks.\nThen stop replying. Two clear messages is enough.\n\n**They go quiet after your follow-up:**\nSend one more, a week later, then assume the role is gone and move on.\n> Last check on the [Company] role. If it's closed out, no reply needed. Thanks for the conversation either way."},
{"id":"respond-to-unsolicited-advice","title":"Responding to unsolicited advice and opinions","category":"personal","tags":["unsolicited advice","opinion","parenting advice","deflect","redirect","coworker"],"triggers":["my mom keeps giving advice","don't want their advice","respond to opinion about my life","they keep telling me what to do","mil criticises how i parent","coworker comments on how i work","everyone has an opinion on my wedding"],"summary":"Receiving, deflecting or shutting down advice and opinions you did not ask for, from a light redirect to a firm close. Relatives quizzing you about marriage, kids or money: family-pressure-and-nosy-questions.","updated":"2026-09-29","body":"# Responding to unsolicited advice and opinions\n\n## Goal\nEnd the topic without a fight and without pretending to agree. Match the force of your response to how much it actually bothers you.\n\n## The ladder (use the lowest rung that works)\n1. **Receive and move on.** \"That's a thought, thanks.\" Then change the subject. Costs nothing.\n2. **Light deflect with humour.** Works with people you like.\n3. **Name your position, kindly.** \"I've got this one handled, but I appreciate you caring.\"\n4. **Close the topic.** \"I'm not going to discuss that, but I'd love to talk about [X].\"\n5. **Set the boundary.** See `set-boundary`.\n\n## Principles\n- You do not have to explain your choices to earn the right to make them.\n- Most unsolicited advice is love wearing bad clothes. Respond to the love, not the clothes, when you can.\n- A question is not an obligation. You can answer a different question.\n- Repeat the same short sentence rather than escalating your reasons.\n\n## Examples\n\n**\"You should really get out of renting and buy.\" (receive, position, close):**\n> Noted, thanks. I'll think about it.\n> I've looked into it and renting works for us right now, but I appreciate you thinking of it.\n> I know you mean well. I'm not looking for advice on this one right now.\n\n**Parent who won't stop advising on how you raise your kids:**\n> Mum, I love that you care about them this much. We're doing it the way that works for us, and I need you to trust that. If I want your take, I'll ask, and I will ask.\n\n**Friend giving relationship advice you didn't ask for:**\n> I hear you, and I know you're saying it because you care. I'm not looking for advice right now, just somewhere to vent. Can you just be on my side for a minute?\n\n**Coworker with opinions on your work style:**\n> Thanks for the input. I'll keep doing it this way; it's working for me and my results are where they need to be. Happy to compare notes if you're curious how.\n\n**Stranger / acquaintance comments on your body, food, appearance:**\n> I'm good, thanks.\n> I don't discuss that. So, how do you know Tom?\n\n**Someone who repeats the same advice every time you see them:**\n> You've mentioned this a few times. I've heard it, I've made my decision, and I'd really rather we talked about something else. Deal?\n\n## When the advice is actually good\n> Actually, that's fair. I hadn't thought about it that way.\nBeing able to say this makes your deflections credible the rest of the time.\n\n## Avoid\n- Over-explaining your reasons (each one is a new thing to argue with).\n- Sarcasm with people you'll see again.\n- \"Mind your own business\" unless you're done with the relationship.\n- Agreeing to end the conversation and then resenting it.\n\n## If they keep pushing or take offence\nIf they come back with \"I'm only trying to help\", agree with the intention and keep the position: \"I know, and I appreciate it. I've got this one.\" If it turns into a pattern that spoils every visit, move up the ladder to a clear boundary (`set-boundary`) in a calm moment, not mid-argument. If they are hurt that you did not take the advice, you do not owe them a reversal, only kindness.\n> I know you care, and I love that. I've made my decision, so let's leave this one."},
{"id":"romantic-let-down","title":"Turning someone down romantically","category":"personal","tags":["dating","rejection","not interested","let down","early dating","friend zone"],"triggers":["not interested in them","let them down gently","don't want a second date","reject politely","they asked me out","end things after a few dates","no spark after a few dates","turn down a date"],"summary":"Kind and unambiguous rejection in early dating: after a first message, after a date or two, or a few weeks in. Ending an established relationship is respond-to-an-ex-or-breakup-message.","updated":"2026-09-27","body":"# Turning someone down romantically\n\n## Goal\nNo ambiguity, no cruelty, no false hope, no lecture. They can walk away with dignity.\n\n## Structure\n1. **Appreciation, specific and brief.**\n2. **The no, clear.** \"I'm not feeling a romantic connection.\" Not \"I'm not sure\" or \"maybe later\".\n3. **No reason, or a reason that is about you/fit, not about their flaws.**\n4. **Warm close.** Do not offer friendship unless you mean it.\n\n## Principles\n- Ambiguity is the cruel option. \"Let's see\" makes them wait. A clean no is respect.\n- Do not list their faults. They did not ask for feedback.\n- Do not over-apologise. You are not doing anything wrong.\n- Scale the channel to the relationship: a message is fine for one or two dates; a call for a few weeks; in person for months.\n- Ghosting after a real date is the one thing to never do.\n- Do not respond to arguments about your decision. It is not a debate.\n\n## Examples\n\n**After one date:**\n> Thanks for last night, I had a nice time. I'm not feeling a romantic connection, so I don't think we should do a second date. Wishing you well.\n\n**After a few dates, message:**\n> I've really enjoyed getting to know you and I've been thinking about it: I don't feel this going where it should for me, and I'd rather be honest now than drag it out. You've been lovely. I'm sorry it's not the answer you wanted.\n\n**Someone asks you out and you're not interested:**\n> That's really kind of you to say, and I'm flattered. I don't see you that way, though, so I'll say no. Hope that doesn't make things weird.\n\n**Friend confesses feelings:**\n> Thank you for telling me, I know that wasn't easy. I don't feel the same way. I really value you as a friend and I hope we can keep that, but I understand if you need some space first.\n\n**Ending a short relationship (weeks to a few months), ideally a call, script:**\n> I want to be straight with you because you deserve that. I've realised I'm not in this the way I'd want to be, and it's not fair to either of us for me to keep going. This isn't about anything you did. I'm sorry.\n\n**Someone from an app before meeting:**\n> I've enjoyed chatting but I don't think we're a match. Good luck out there.\n\n**If they push for a reason:**\n> I don't think a list of reasons would help either of us. It's about fit, not about you being wrong.\n\n## Avoid\n- \"It's not you, it's me\" verbatim (cliche, reads as a lie even when true).\n- \"Maybe in the future.\"\n- \"You'll find someone great.\"\n- \"I'm not ready for a relationship\" if you are (they will find out).\n- Explaining at length.\n- Offering friendship as a consolation prize when you do not want it.\n- Replying to a hostile response. One line: \"I understand you're upset. I'm going to leave it here.\" Then done.\n\n## If they argue or keep messaging\nSome people answer a clear no with a case for why you are wrong, a request for one more chance, or a string of messages over several days. None of these need answering in kind. One calm line closing the door, then no more replies. Not replying is the message.\n> I've heard you and I'm not going to change my mind. I'm going to stop replying now, and I wish you well.\nIf they turn hostile, do not respond at all, and block if needed. Being kind first does not oblige you to absorb it. If they show up in person after being told no, tell a friend and treat it as a safety question, not a manners one."},
{"id":"roommate-and-shared-living","title":"Roommates and shared living (chores, bills, guests, noise, moving out)","category":"personal","tags":["roommate","flatmate","housemate","chores","bills","shared house"],"triggers":["my roommate keeps","flatmate won't clean","housemate never pays bills","roommate's partner basically lives here","tell my roommate I'm moving out","roommate is too loud at night","house chat about chores","split utilities with roommates"],"summary":"How to raise chores, bills, guests, noise and moving out with people you live with, as shared-house admin with a proposal, so the home stays livable while you sort it.","updated":"2026-09-28","body":"# Roommates and shared living\n\n## Goal\nThe problem gets fixed and you can still make toast in the same kitchen tomorrow. You cannot walk away from a roommate after a bad message, so every message is written for the next six months, not the next ten minutes.\n\n## Structure\n1. **Friendly, low-key opener.** Match how you normally talk in the house.\n2. **The specific issue, as a fact about the house**, not a verdict on the person. \"The bins went out late three weeks running\" beats \"you never do the bins.\"\n3. **A concrete proposal** (a rota, a split, a quiet-hours window, a guest rule). Arriving with a fix turns a complaint into a decision.\n4. **An easy way to adjust it.** \"Happy to tweak it if another setup works better.\"\n5. **Keep it short.** Long messages in a shared house get screenshotted and discussed without you.\n\n## Principles\n- Raise it early and small. Resentment that sits for two months comes out as a paragraph nobody deserves.\n- Speak for the house when it is a house problem, and for yourself when it is yours. Do not claim \"everyone's annoyed\" unless everyone agreed you could say so.\n- Money and chores go in writing (the house chat or a shared note). Feelings go in person or on a call.\n- Propose systems, not personalities. A rota, a shared bills app, or a quiet-hours rule does the nagging so you do not have to.\n- One issue per conversation. Stacking the dishes, the guest and the heating bill into one message reads as a case file.\n- Assume they have not noticed. Most roommate problems are about different baselines, not bad intentions.\n\n## Examples\n\n**Chores, proposing a rota in the house chat:**\n> Hey all, the kitchen's been getting away from us lately (me included). Want to try a simple weekly rota? I've made a draft: kitchen, bathroom, bins, hoovering, swap each Monday. Shout if you'd change anything, otherwise let's start this week.\n\n**One person not doing their share, privately:**\n> Hey, can I raise something small? The dishes have been piling up a few days at a time and I've ended up doing most of them. Could we agree nothing stays in the sink overnight? Happy to do the same.\n\n**Bills, a late payment:**\n> Hi Sam, the electricity bill came out on the 3rd, your share is £46. Can you send it over by Friday? I've set up Splitwise so it's all tracked from now on.\n\n**A partner who has effectively moved in:**\n> I really like Jo, and I get why they're here a lot. It's been 4 or 5 nights a week for a while now, which changes the bills and the bathroom queue. Can we either keep it to a couple of nights, or talk about Jo chipping in for utilities?\n\n**Noise, late at night:**\n> Hey, could we keep music and calls down after 11 on weeknights? I'm up at 6 for work and the walls carry more than you'd think. Weekends I'm not fussed.\n\n**Giving notice that you're moving out:**\n> Heads up, I've decided to move out at the end of March. I'll give the landlord proper notice this week and help find someone for my room if you'd like a say in who. Thanks for making this a good place to live.\n\n**Ending on good terms, deposit and handover:**\n> Before I go, can we do a quick walk-round on the 28th so we agree what state my room and the shared bits are in? I'll deep clean the bathroom and settle my share of the last bills by then.\n\n## Avoid\n- Passive-aggressive notes on the fridge or in the kitchen.\n- \"Some people in this house...\" in the group chat. Everyone knows who you mean, including them.\n- Raising it at 1am when you are woken up. Say \"could you turn it down, I'm sleeping\" then, and have the real conversation tomorrow.\n- Threatening to tell the landlord as an opening move.\n\n## If it goes badly\nIf they get defensive (\"I do loads, you just don't see it\"), do not argue the tally. Agree the goal and go back to the system: \"Fair, let's just put it on a rota so we both can see it.\" If a money issue drags past two reminders, move it to a written record and say plainly when the bill is due, because this is the item that can affect your deposit and credit. If nothing changes after a real conversation, check your tenancy: a joint tenancy may make you liable for their share, so contact the landlord or agent early and in writing, then decide whether it is you or them who moves.\n> Fair enough, I don't want to get into who did what. Can we just try the rota for a month and see?\n> I've asked a couple of times about the £46. I need it by the 15th, or I'll talk to the agent about how the bills are set up."},
{"id":"say-no-to-a-customer-request","title":"Saying no to a customer request without losing the customer","category":"commerce","tags":["decline","customer request","policy","feature request","custom order","exception","support"],"triggers":["say no to a customer","decline a feature request","can't do a custom order","discount code expired what do I say","request violates our policy","make an exception for a customer","tell a customer we don't do that"],"summary":"Declining a customer's request (a feature, a custom order, an expired code, a policy exception) so they stay a customer. Refunds and returns: handle-refund-request. A client's rush or extra work: say-no-to-client-scope.","updated":"2026-09-28","body":"# Saying no to a customer request without losing the customer\n\n## Goal\nThe customer gets a clear answer, understands it is not personal, and leaves with something: an alternative, a timeline, or a real explanation. A clean no keeps more customers than a vague maybe.\n\n## Structure\n1. **Thank them for the specific ask.** One line, no gush.\n2. **The no, plainly, in the first two sentences.** \"We can't do a custom size on this one.\"\n3. **The real reason in one line.** Cost, quality, capacity, fairness to other customers.\n4. **What you can do.** An alternative, a partial, a future date, or a referral to someone who does it.\n5. **Leave the door open** without promising: \"If that changes, I'll tell you.\"\n\n## Principles\n- Say \"can't\" or \"don't\", not \"unable to at this time\". Vague nos invite a second ask.\n- \"Policy\" is not a reason. Say what the policy protects: \"we close returns at 30 days because after that we can't resell the item\".\n- Offer what you can before they ask. Reactive concessions feel extracted; proactive ones feel generous.\n- If you bend the rule, decide fast and say it is an exception, so it does not become the baseline.\n- Bend for good reasons: a long-standing customer, your own mistake, a true edge case. Do not bend for volume of complaint. Rewarding pressure buys more pressure.\n- Tickets can run five sentences. DMs two or three.\n- Never say a feature is \"on the roadmap\" unless it is.\n\n## Examples\n\n**Feature request, support ticket:**\n> Hi Lena, thanks for the detailed suggestion about bulk export to CSV. We're not building it this year; the team is focused on the mobile app, and I'd rather tell you that than leave you waiting. What works today: the API can pull the same data (docs here [link]), and I can send a short script that does the export if that helps. I've logged your request so you'll get an email if it ships.\n> Omar\n\n**Custom order, DM:**\n> Thanks for asking! I don't do custom sizes on the ceramic planters, the kiln setup makes one-offs cost more than anyone would pay. The closest I have is the 22cm, which fits most windowsills. Send me a photo of the spot and I'll tell you honestly whether it'll work.\n\n**Expired discount code:**\n> Hi Sam, that code ended on 30 June, so it won't apply to this order. The SUMMER10 code is live until the 15th and takes 10% off. Here's the link with it applied [link]. If you already paid full price, reply with the order number and I'll refund the difference.\n\n**Request that violates policy (a second user on a personal plan):**\n> Thanks for asking rather than just doing it. I can't add a second login to a personal plan; it's one seat, and the team plan exists exactly for this. Team for two is $18 a month, $6 more than now, and I can apply the upgrade with the rest of this month free. Want me to do that?\n\n**Something you simply do not do, DM:**\n> I don't do wholesale, it's just me and a small kiln! For larger quantities, [maker] does similar work at volume and I'd happily introduce you.\n\n## Avoid\n- \"Unfortunately\" and \"I'm afraid\" as openers.\n- \"Our policy states.\"\n- Apologising more than once.\n\n## If they push back\nRestate the no in one line, repeat the alternative, and add no new reasons. \"I understand, and the answer's still no on the custom size. The 22cm planter is ready whenever you want it.\" If they threaten a bad review, hold the answer: \"That's your call. I'd still like to sort this with the alternative, and it's ready when you are.\" If they bring a genuinely new fact (the item was faulty, your site gave wrong information), reconsider on that fact and say so: \"That changes it. If the listing said custom sizes were available, I'll make one.\""},
{"id":"say-no-to-client-scope","title":"Saying no to a client (scope creep, unreasonable asks, bad fit)","category":"work","tags":["client","scope creep","freelance","no","out of scope","boundaries","agency"],"triggers":["client keeps adding things","out of scope","client asked for free work","tell a client no","turn down a project","scope creep","fire a client","client wants it rushed"],"summary":"How to hold the line with clients while staying the person they want to keep hiring: name the scope, price the extra, or decline the project cleanly.","updated":"2026-09-28","body":"# Saying no to a client\n\n## Goal\nThe client hears a professional managing a project, not a contractor being difficult. Every no comes with a path to a yes at a price, or a clean exit.\n\n## Structure\n1. **Positive acknowledgement of the request.** They are not wrong to ask.\n2. **The scope fact.** \"That's outside what we scoped in the [date] agreement.\"\n3. **The path.** Price for the extra, or a swap (\"we can do this instead of X\"), or a phase-two.\n4. **Ask for a decision.**\n\n## Principles\n- The tone is \"of course, here's what that costs\" not \"no, that's not included.\" Same content, very different relationship.\n- Do the free version of a thing once at most, and say you're doing it as a one-off. Silent free work becomes expected free work.\n- Put it in writing every time. A verbal \"sure\" becomes a dispute later.\n- If the client is a bad fit, decline early. A slow fade is worse for both of you.\n\n## Examples\n\n**Scope creep, email:**\n> Hi Tom,\n> Happy to add the second landing page. It's outside the original scope (three pages, per the March SOW), so I'd quote it as an add-on: $1,400 and about four working days. If you'd rather keep the budget flat, we could swap it in for the FAQ page. Let me know which you prefer and I'll update the schedule.\n> Best,\n> Nina\n\n**Client asks for \"a quick favour\" that isn't quick:**\n> I can do that. It's a couple of hours of work rather than a quick one, so I'll bill it at the usual rate unless you'd rather I skip it. Just say.\n\n**Rush request:**\n> Hi Dan, I can't turn this around by Friday. Done properly it takes six working days and I have two projects ahead of you. What I can do: deliver on Wednesday the 18th, or, if Friday is fixed, the first section by Friday and the rest the following week. Which is more useful?\n> Ruth\n\n**Client wants unlimited revisions:**\n> The package includes two rounds of revisions and we've used both. I want you to be happy with it, so here's the plan: I'll do one more round as a courtesy, and further rounds are $X each. Does that work?\n\n**Turning down a project (bad fit):**\n> Thanks for thinking of me for this. Having looked at it, I don't think I'm the right fit; the scope leans toward [X] and you'd get better results from someone who specialises there. I can recommend two people if that's useful.\n\n**Turning down a project (red flags), no explanation:**\n> Thank you for the opportunity. I'm going to pass on this one, but I appreciate you reaching out and wish you the best with it.\n\n**Ending an ongoing client relationship:**\n> I've valued working with you over the last year. I've decided to wind down this engagement at the end of the month so I can focus on [X]. I'll make sure everything is documented and handed over cleanly, and I'm happy to introduce you to someone who could take it on.\n\n**Client asks for a discount because they're \"a small business\":**\n> I understand, and I work with a lot of small businesses. My rates are set for the work rather than the client, but I can scale the scope to fit your budget. What's the number you're working with?\n\n## Avoid\n- Doing the extra work and then complaining about it.\n- \"I'll see what I can do\" when you mean no.\n- Apologising for having a scope.\n- Explaining your costs.\n- Ghosting a bad client instead of ending it.\n\n## If they push back on the price\n\"The last agency threw that in\" or \"it's only a small change\" means they want the work at zero. Stay pleasant, do not lower the quote, and put the choice back to them. If they go quiet, do not start the extra work hoping they will pay.\n> I get that it feels small from the outside; it's about four days of work at our end, so $1,400 is the fair number. The swap with the FAQ page is there if the budget's fixed. Just tell me which way you'd like to go.\nIf they get it done elsewhere, fine. If they keep testing the line every week, tighten the next SOW or end the engagement."},
{"id":"set-boundary","title":"Setting a boundary with family, friends or a partner","category":"personal","tags":["boundary","limit","family","overbearing","repeated","pattern"],"triggers":["set a boundary","my mom keeps","they always","stop asking me","too much","need space","they keep calling","overstepping"],"summary":"How to state a limit on a repeated pattern (calls, comments, visits, money, access to your home) clearly and kindly, hold it under pushback, and not over-explain. A one-off no: decline-request.","updated":"2026-09-29","body":"# Setting a boundary\n\n## Goal\nThe limit is clear, it is about your behaviour (what you will do), and it survives the first round of pushback.\n\n## Structure\n1. **Warm opener** that affirms the relationship.\n2. **The boundary as something you will do**, not something they must do. \"I'm going to stop answering calls after 9pm\" holds up better than \"you need to stop calling late.\"\n3. **One short reason, optional.**\n4. **What you're offering instead** (a time that works, an alternative).\n5. **Stop.** No paragraph of justification. Justification is an invitation to negotiate.\n\n## Principles\n- A boundary is a statement of what you will do. It is not a request for permission.\n- The first time you set it, expect pushback. The pushback is not a sign you were wrong.\n- Repeat the same sentence rather than adding new reasons. New reasons are new targets.\n- You can be kind and immovable at the same time. Warm tone, firm content.\n- Do not set a boundary you will not keep. Every broken boundary makes the next one weaker.\n\n## Examples\n\n**Parent who calls constantly:**\n> Mum, I love talking to you and I want to keep it that way. I can't do daily calls with work the way it is. I'm going to call you Sundays, properly, for as long as you like. During the week I'll text.\n\n**Friend who only calls to vent:**\n> I care about you and I've noticed our calls lately are mostly you going through a hard time, which I get. I don't have the capacity to be that person every time right now. I'm still here, and I'd love for some of our time to just be fun.\n\n**Relative who comments on your body / life choices:**\n> I know you mean well. I'm not going to discuss my weight, so if it comes up I'll change the subject. Everything else, I'm all yours.\n\n**Partner, needing space:**\n> I need some evenings that are just mine, not because anything's wrong with us but because I recharge alone. Can we say Tuesdays and Thursdays are mine, and I'll be fully present the rest?\n\n**Someone who keeps asking for money:**\n> I'm not able to lend money anymore, to anyone. That's a firm one for me. I'm happy to help in other ways, like looking at a budget with you.\n\n**Group / family chat, muting:**\n> I'm going to mute this chat during work hours. If something's urgent, call me.\n\n## When they push back\nSay the same thing again, shorter.\n> I understand you're not happy about it. Sundays is what I can do.\nThird time:\n> I've said what I can do. I love you. Talk Sunday.\nThen stop replying on that thread.\n\nIf they go cold, guilt-trip (\"after everything I've done\") or recruit others to pressure you, do not reopen the boundary to win them back. Stay warm about everything else and let the silence pass; most people adjust within a few weeks.\n> I know you're upset, and I love you. This part isn't changing. I'll call Sunday.\n\n## Avoid\n- \"I hope that's okay?\"\n- \"I'm sorry but...\"\n- \"You always...\" (turns a boundary into an accusation)\n- A list of reasons.\n- Setting the boundary in anger. Set it calm, hold it calm.\n- Threatening consequences you will not enforce."},
{"id":"share-personal-news","title":"Sharing personal news (good and bad)","category":"personal","tags":["news","announce","engagement","pregnancy","job loss","breakup","moving","diagnosis","announcement"],"triggers":["tell people I'm engaged","announce pregnancy","tell my family I got laid off","tell friends we broke up","announce I'm moving","share news","tell people about my diagnosis","group announcement"],"summary":"How to share big news with the right people in the right order and tone: individually to those closest, then a short group message, with cues for how you'd like people to respond.","updated":"2026-09-27","body":"# Sharing personal news\n\n## Goal\nThe people who matter hear it from you, in the right order, with a signal for how to respond.\n\n## Principles\n- **Order matters.** Closest people first, individually. Then the group. People are hurt by hearing big news in a group chat or on social media before you told them.\n- **Tell them how to respond.** \"No need to reply\" or \"I'd love to hear from you\" or \"please don't ask about X yet\" saves everyone guessing.\n- **Short.** Big news does not need a long message. The news, one line of feeling, one line of what's next.\n- **For bad news, decide what you want**: support, space, practical help, or just to have said it. Say which.\n- **For good news, be mindful of the reader.** A pregnancy announcement to a friend struggling with fertility deserves an individual, gentle message. A new job to a friend who just lost theirs, likewise.\n\n## Good news\n\n**Engagement, individual to close friend:**\n> Wanted you to hear it from me before it's anywhere else: we're engaged! It happened last night at the lake. I'm slightly in shock and very happy. Call you tomorrow with all of it.\n\n**Engagement, group:**\n> We're engaged! Happened Saturday, we're thrilled. No plans yet beyond a lot of cake. Thank you for being our people.\n\n**Pregnancy, to a friend who's had a hard time with it:**\n> I wanted to tell you this one directly and quietly, because I know it's not a simple thing for you: I'm pregnant, due in March. You don't have to say anything, and I don't need you to be anything but honest. I love you.\n\n**New job:**\n> Some news: I've accepted a role at [company], starting in June. It's a big step and I'm nervous in a good way. Thank you for listening to me agonise about it.\n\n## Hard news\n\n**Job loss, close friends:**\n> Bit of news: I was laid off yesterday, along with about a third of the team. I'm okay, mostly, a bit winded. I'll be looking for something new from next week, so if you hear of anything, send it my way. Don't need anything else right now, just wanted you to know.\n\n**Breakup, group of friends:**\n> Sharing this once so I don't have to keep saying it: Sam and I have split up. It's sad and it's the right thing. I'm okay. I'd love company over the next few weeks; I'd rather not do a post-mortem on it. Thanks for being there.\n\n**Diagnosis:**\n> I want to tell you something and I'd rather do it in writing so I can get through it: I've been diagnosed with [X]. The plan is [one line]. I'm okay to talk about it, and I'll tell you what I need as I work it out. For now, just knowing you know helps. No need to reply with anything wise; \"I'm here\" is plenty.\n\n**Moving away:**\n> Some news I've been sitting on: I'm moving to [city] in September. It's for [reason] and it's the right move, but I'll miss you properly. Let's do a lot of things before then.\n\n**Death in the family (letting people know):**\n> I'm letting people know that my dad died on Tuesday. It was peaceful, with us there. The funeral is on the 18th at [place]; details to follow. I'm not up to much conversation right now but I'm glad you know.\n\n## Responding to someone else's news\nGood news: specific joy, one sentence, then a question. \"Congratulations! I can hear how happy you are. When do you start?\"\nHard news: acknowledge, don't fix. \"I'm so sorry. Thank you for telling me. I'm here.\" See `condolences-and-support`.\n\n## Avoid\n- Announcing on social media before telling close people.\n- Burying big news in the middle of a chatty message.\n- Explaining the whole story in the announcement.\n- \"I know this is a lot\" (they can decide).\n- Apologising for having news.\n\n## If the response hurts\nSome replies will miss: a joke about the breakup, unsolicited advice on the diagnosis, a \"finally!\" on the engagement, or nothing at all from someone you expected to hear from. If it is worth addressing, usually one line does it, and silence often means they did not know what to say.\n> That landed a bit hard. I know you didn't mean it that way; I'm just still raw on this one.\n> I'm not looking for advice on the treatment right now, just company. Coffee this week?\nFor the friend who went quiet, reach out once, lightly: \"No need to have said anything, just wanted you to know I'd love to see you.\" Then let them come to you."},
{"id":"shipping-delay-or-out-of-stock","title":"Telling a customer their order is delayed, lost, damaged or out of stock","category":"commerce","tags":["shipping","delay","backorder","out of stock","lost parcel","order update","small business"],"triggers":["order is delayed tell the customer","item is out of stock email","backorder message","parcel is lost what do I say","package arrived damaged reply","tell customers about a shipping delay","sold out after they ordered","mass update to customers about delay","B2B delivery slipped"],"summary":"Order-problem messages that keep the sale and the trust: the news first, a firm new date, three options with a default, and one named person who owns it until it arrives.","updated":"2026-09-28","body":"# Telling a customer their order is delayed, lost, damaged or out of stock\n\n## Goal\nThe customer hears about the problem from you before they have to ask, knows what happens next and by when, and can choose between waiting, swapping or a refund in one reply.\n\n## Structure\n1. **Order number and the problem in the first line.** \"Your order #4521 is delayed\" beats \"an update on your order\".\n2. **The new date, or when you will know it.** \"I'll have a date by Thursday\" is a date.\n3. **One line of reason.** Supplier, courier, your mistake. No paragraph.\n4. **Three options with a default.** Wait (with tracking when it ships), swap for something in stock, or full refund. Say which happens if they do not reply.\n5. **A small make-good** if it is your fault and long enough to matter.\n6. **Your name and when they will next hear from you.**\n\n## Principles\n- Proactive beats reactive. A delay message sent the day you learn of it costs little. The same news after \"where is my order?\" costs the relationship.\n- One firm date beats a soft range. If you must give a range, give the later end and beat it.\n- Make refund the easiest option to pick. Customers who see an easy exit usually choose to wait.\n- \"Lost\" means the courier trace has expired, not that tracking has paused.\n- For damaged goods, ask for a photo and send the replacement. Do not make them return the broken item first.\n- B2B customers care less about apology than their downstream plan: give them what they need to tell their people.\n\n## Examples\n\n**Backorder, proactive email:**\n> Hi Priya,\n> Your order #4521 (the walnut desk tray) is out of stock, which we should have caught before the site took your order. The next batch lands on 14 October and yours ships the same day. Three options: wait and I'll add free express shipping; swap for the oak version, in stock and shipping tomorrow; or a full refund today. If I don't hear back by Friday I'll hold it for the 14th. Sorry for the mess.\n> Tom\n\n**Shipping delay, proactive DM (Etsy or Instagram):**\n> Hey! Quick heads up: the courier is running about four days behind in your area, so your order now looks like Tuesday rather than Friday. Tracking's in your messages. If Tuesday doesn't work, tell me and I'll refund it in full. Sorry for the wait, and thanks for ordering from a tiny shop.\n\n**Reactive, after \"where is my order?\":**\n> Hi Marcus, you're right to ask and I'm sorry you had to. Order #7710 left us on the 3rd and tracking stopped on the 6th, which usually means a sorting hub. I've opened a trace this morning. If it hasn't moved by Thursday I'll send a free express replacement, and if the first one turns up you keep both. I'll email you Thursday either way.\n> Elena\n\n**Item arrived damaged:**\n> Oh no, I'm sorry, that's not how it should have arrived. Could you send one photo of the damage and one of the box? Then I'll send a replacement straight away, no need to post the broken one back. If you'd prefer a refund, just say so.\n\n**Mass update, many customers:**\n> Subject: Your order will ship around 20 November\n> Hi [first name],\n> Orders placed since 1 November, including yours (#[number]), will ship around 20 November instead of this week. Our fabric supplier missed a delivery and the replacement arrives on the 18th. If you'd like to wait, we'll add a free tote and email tracking the day it ships. If you'd rather not, reply \"refund\" and I'll process it within one business day. This inbox goes to me, not a bot.\n> Hannah, owner\n\n**B2B, delivery slipped:**\n> Hi Dev,\n> PO 2291 (the 400 units for the March launch) is now due at your warehouse on 11 March instead of 4 March, a component shortage on our side. To limit the impact, I can split it: 150 units on the 4th as planned, the remaining 250 on the 11th, at no extra freight. If the full quantity on the 4th is essential, tell me by Wednesday and I'll see what I can pull from another line. Confirmed schedule tomorrow morning either way.\n> Sara\n\n## Avoid\n- \"Due to unforeseen circumstances.\"\n- \"Higher than usual demand.\"\n- \"Soon\", \"in the coming weeks\", \"as soon as possible\".\n- Blaming the courier or \"the system\" as the whole message.\n- Sending from no-reply.\n\n## If it goes badly\nIf they reply angrily, do not re-explain the cause. Confirm the action and date and offer the refund again: \"Understood, and I'm sorry. Your replacement ships today by express and you'll have tracking by 5pm. If you'd rather I refund it, say the word and it's done.\" If they go silent, do the default you promised. If a date slips a second time, refund the shipping unasked and give a date you are certain of."},
{"id":"small-talk","title":"Small talk that goes somewhere","category":"personal","tags":["small talk","conversation starters","networking","party","awkward silence","chit chat"],"triggers":["what to talk about","small talk","conversation starter","awkward silence","networking event","meet new people","break the ice"],"summary":"Openers, follow-ups and exits for small talk with strangers and acquaintances, built on curiosity rather than scripts.","updated":"2026-09-29","body":"# Small talk that goes somewhere\n\n## Goal\nBoth people leave the conversation a little lighter, with one thread worth picking up next time. The measure is whether they got to talk about something they care about, not how clever you were.\n\n## The mechanic\nSmall talk works when you ask about something they have a view on, then follow the thread they give you. It fails when you ask a question, get an answer, and ask an unrelated question. The second question should come from their first answer.\n\n## Openers by setting\n\n**Party / social, mutual host:**\n> How do you know Priya?\n> What's the story with the dog? (or the record collection, or the food: whatever is in the room)\n\n**Work event / networking:**\n> What are you working on at the moment that you actually care about?\n> What brought you to this one?\n> What's been the surprising part of nursing this year?\n\n**Waiting somewhere (queue, lobby, before a meeting):**\n> Is this your first time at one of these?\n> Any tips? I'm new to this.\n\n**Someone you vaguely know:**\n> Last time we spoke you were about to move to Leeds. How did it go?  (this one is gold; people remember you remembered)\n\n**Instead of \"what do you do\":**\n> What does a normal week look like for you?\n> What are you into outside of work?\n\n## Follow-ups that deepen\n- \"What's that like?\"\n- \"How did you get into that?\"\n- \"What's the part people don't understand about it?\"\n- \"Was that always the plan?\"\n- Reflect and ask: \"So you moved cities for it. Was that hard?\"\n\n## Sharing back\nGive a little of yourself after they share; a conversation that is all questions feels like an interview. \"That's funny, I had the same thing with...\" One sentence, then back to them.\n\n## Filling a silence\n> I've just realised I never asked what you're up to this weekend.\n> Okay, random question: what's the best thing you've eaten this month?\n> I'm terrible at small talk, so I'm just going to ask: what's the most interesting thing going on in your life right now?\n\n## Exiting\n> I'm going to grab a drink, it was really good to meet you.\n> I should go say hi to Tom before he leaves. Let's talk again.\n> I won't keep you, but I'm glad we met. Are you on LinkedIn?\n\n## Avoid\n- Weather, traffic, \"busy?\" as more than a warm-up.\n- Interrogation: three questions in a row without sharing.\n- Correcting them or one-upping their story.\n- Checking your phone.\n- Asking \"what do you do\" first at a social event; some people hate their job.\n- Topics that require a position: politics, religion, money, unless they go there first.\n\n## If it stalls or they're not interested\nSome people are tired, shy, or waiting for someone else. Two flat answers in a row is your cue: share one thing yourself to lower the pressure, and if it stays flat, exit warmly without making it a verdict on either of you.\n> I'll let you get back to it, nice to meet you.\n> I'm going to do a lap, but come find me if you want a break from the work talk.\nIf you said something that landed badly, fix it in one line and move on: \"That came out wrong, sorry. What I meant was...\" Do not apologise twice; it makes the moment bigger than it was."},
{"id":"suspicious-or-scam-message","title":"Replying to a suspicious or scam message","category":"personal","tags":["scam","phishing","hacked account","fraud","safety","verification","family"],"triggers":["is this a scam","friend asking for money on whatsapp","someone sent me a code request","bank text looks fake","delivery text with a link","wrong number text","job offer too good to be true","my aunt is being scammed","reply to suspicious message"],"summary":"Whether and how to reply to a message that may be a scam or a hacked account: verify through a channel you already had, do not engage, warn the real friend, and talk to a relative without shaming them.","updated":"2026-09-28","body":"# Replying to a suspicious or scam message\n\n## Goal\nYou lose nothing, the real person behind a hacked account gets warned, and any relative caught in a scam stays close enough to you to accept help. The scammer gets nothing, including your attention.\n\n## Core rule\n**Verify through a channel you already had, never through the one the message gives you.** Call the number saved in your phone, open the bank's app yourself, log in to the courier's site by typing the address. A scammer controls the message; they do not control your existing contacts.\n\n## Structure\n1. **Do not act inside the message.** No links, no codes, no \"confirm your details\", no replying to unknown numbers.\n2. **Check the channel.** Does the ask involve money, a code, urgency, secrecy or a link? Two of those is enough to treat it as a scam.\n3. **Verify outside it.** Phone call to a saved number, a question only the real person could answer, or the official app.\n4. **If real, help. If not, block, report, and warn the real person** through the verified channel.\n5. **Delete it.** Do not keep a thread open \"in case\".\n\n## Principles\n- Not replying is a complete response. Scammers work lists; a reply, even \"wrong number\", marks your number as live.\n- Never send a code. A real friend does not need your verification code for anything. This one rule stops most account takeovers.\n- Urgency is the tell. Anyone genuine can wait ten minutes for you to call them back.\n- Relatives who are being scammed are already ashamed. Shame makes them hide it. Your job is to be the person they can tell.\n- Your bank will never ask you to move money to a \"safe account\", and no courier withholds a parcel for a small fee by text.\n\n## Examples\n\n**\"Friend\" on WhatsApp asks for money or a code (do not reply there; call the real number):**\n> Hey, just got a message from your WhatsApp asking me for a code. I'm guessing that wasn't you? Ring me when you can.\n\n**Warning the real friend when you confirm the account is hacked (by phone, SMS or another app):**\n> Your Instagram is sending \"I need a favour\" messages to people. It's not you, right? Change the password and turn on two-step, and tell your followers from another account so nobody sends money.\n\n**\"Bank\" or \"delivery\" text with a link:**\nSend nothing. Open the bank app or type the courier site yourself. To report it, forward the text to your carrier's spam number or your bank's fraud line, then delete it.\n\n**Wrong-number opener from a stranger (\"Hi, is this David from the gym?\"):**\nSend nothing. If it is a real wrong number, they will find the right one. If you must, one line and then block:\n> Wrong number.\n\n**Too-good job offer by DM (\"$4,000 a week, no experience, reply YES\"):**\nSend nothing. Look up the company yourself and message its official careers address if curious:\n> Hi, I received a message claiming to be from your recruiting team about a remote position. Can you confirm whether it's genuine?\n\n**A relative's account seems hacked (message them on another channel you already had):**\n> Auntie, your Facebook is sending odd messages about a grant. I don't think it's you, so I've not replied. Can I call you tonight and we'll change the password together?\n\n**Telling a relative you think they are being scammed, without shaming them:**\n> Mum, I've been thinking about that man from the trading group you mentioned. Can I ask something, and I promise I'm not going to lecture: has he asked you to send money or keep it quiet? These people are professionals and they fool clever people every day. Whatever the answer is, we'll sort it out together.\n\n**Acquaintance says they sent money before realising:**\n> Don't beat yourself up, these are designed to work. Call your bank's fraud line right now and tell them exactly what happened; the sooner you call, the better the chance of a recall. Then report it to [national fraud service]. I'm around if you want company on the call.\n\n## Avoid\n- Clicking to \"just see\" what the link is.\n- Replying \"STOP\" to unknown numbers, which confirms yours is live.\n- Sending any code, even \"just this once\".\n- Arguing with, mocking or baiting the scammer.\n- \"How could you fall for that?\" to a relative. It ends the conversation and the next scam goes unreported.\n\n## If it goes badly\nIf the relative gets defensive:\n> You're right, it's your money and your decision. I'm not going to nag. I just want you to know that if anything about it starts to feel off, you can tell me and I won't say I told you so.\nThen check in again in a week. If they have already sent money, help them call the bank first and talk about it later. If a stranger keeps messaging after you ignore them, block and report; do not send a final reply."},
{"id":"team-announcements-as-a-manager","title":"Team announcements as a manager (reorg, someone leaving, missed target, new policy)","category":"work","tags":["manager","team","announcement","reorg","layoffs","policy"],"triggers":["announce to my team that someone is leaving","tell my team about the reorg","slack message to the team about layoffs","we missed our quarterly target how do i tell the team","announce a new return to office policy","message to team after bad news","how to announce a new hire to the team","all hands update wording"],"summary":"Announcing news to a team you manage: people leaving or joining, reorgs, layoffs, a missed target, a new policy. What changed, what it means for them, what happens next. One person's bad news: deliver-bad-news.","updated":"2026-09-27","body":"# Team announcements as a manager\n\n## Goal\nEveryone on the team knows what changed, what it means for their own work, and where to take questions, before the rumours fill the gap. People forgive bad news far more readily than they forgive finding out sideways or feeling spun.\n\nTelling one person bad news: `deliver-bad-news`. Telling customers: `price-increase-and-customer-announcements`.\n\n## Structure\n1. **Lead with the news** in the first sentence. No \"exciting updates\" preamble for something that is not exciting.\n2. **The reason, briefly and truthfully.** One or two sentences.\n3. **What it means for them.** Their work, their manager, their pay or their hours, whatever they will actually worry about.\n4. **What happens next**, with dates.\n5. **Where to take questions**, and a real offer of a 1:1.\n\n## Principles\n- Tell the affected people first, individually, then the team. Nobody should learn about their own job change from a group post.\n- Tell the team before the wider company when you can, and at roughly the same moment for everyone, so no one hears it from a colleague.\n- Match the channel to the weight. Hard news goes in a live meeting or call, followed by a written summary. Routine news can be a message.\n- Say what you do not know yet, and when you will. \"I don't know yet, I'll update you by Friday\" builds more trust than a vague reassurance.\n- Do not dress up bad news. \"Streamlining\", \"right-sizing\" and \"exciting journey\" land as insults on a hard day.\n- Respect the person leaving. Share only what they agreed you can share, and never hint at why.\n- Own the decision you are part of. \"Leadership decided\" distances you; if you agreed with it, say so.\n\n## Examples\n\n**Someone leaving (with their agreement on wording):**\n> Some news: Ana's last day will be 28 March. She's moving to a product role at a climate startup, and we're all a bit jealous. Ana, thank you for three years of making our releases calmer. Leo will pick up the billing integrations; I'll share a handover plan by Friday. Let's give her a proper send-off next Thursday.\n\n**New hire joining:**\n> Please welcome Tomás, who joins as a senior designer on Monday. He's coming from eight years in fintech and will own the onboarding flow. Say hi, and grab 15 minutes with him in his first week if you can.\n\n**Reorg, written follow-up after the meeting:**\n> As we discussed this morning: from 1 May, the support and success teams become one team under Priya. Your role, pay and day-to-day work stay the same for now. What changes is who you report to and our weekly rhythm. Priya and I will each hold 1:1s with everyone in the next two weeks. Questions to me or Priya anytime, including the awkward ones.\n\n**Layoffs, to the remaining team:**\n> This morning we let go of six colleagues across sales and ops, including Mark and Dee from our team. It's a hard day, and I want you to hear it from me directly. The reason is that revenue came in well below plan and we had to cut costs. No further cuts are planned for our team. I know that's hard to hear after today, so I'll be straight with you if anything changes. My door is open all day.\n\n**Missed target:**\n> We finished Q2 at 78% of our target. That's a miss, and I own my part in how we planned it. Two things drove it: the delayed launch and a slower renewal cycle. Here's what changes for Q3: fewer priorities, a mid-quarter check-in, and I'll share the revised plan on Monday. Good work doesn't disappear because a number was missed.\n\n**New policy people will not love:**\n> From 1 June, the company is moving to three office days a week, Tuesday to Thursday. I know this is a big change for some of you, especially anyone with a long commute or caring duties. If it creates a real problem for you, come and talk to me this week and we'll look at options together.\n\n## Avoid\n- Opening with \"exciting news\" when it is not.\n- Announcing a departure or reorg before telling the people it affects most.\n- \"Nothing is changing\" when something is.\n- Long paragraphs of context before the actual news.\n- Taking questions only in public. Some people will only ask privately.\n- Speculating about the person who left, or letting others speculate in the thread.\n\n## If it goes badly\nIf the thread turns angry or anxious, do not argue in public. Acknowledge the feeling in one line, answer the factual questions you can, and move the rest to 1:1s. If you got something wrong in the announcement, correct it quickly and plainly in the same channel. If you were asked to share something you believe is misleading, push back before the announcement, not after (see `push-back-on-boss`).\n> I hear you, and it's fair to be frustrated. I'll answer what I can here and I'm booking 1:1s with everyone this week for the rest.\n> Correction to my earlier message: the change starts on 1 June, not 1 May. Sorry for the confusion."},
{"id":"tell-someone-something-awkward","title":"Telling someone something awkward about themselves (hygiene, food in teeth, a typo, an open fly)","category":"personal","tags":["awkward","embarrassing","hygiene","body odour","typo","discreet"],"triggers":["how to tell someone they have body odor","tell a coworker they smell","friend has bad breath how do i say it","tell someone they have food in their teeth","there's a typo in their linkedin post should i tell them","how to tell my friend her fly is down","tell someone their post has a mistake","awkward thing to tell a colleague"],"summary":"Telling someone something embarrassing they have not noticed (body odour, food in teeth, a typo in their post), privately and kindly. Opinions on something they made: give-feedback-kindly.","updated":"2026-09-27","body":"# Telling someone something awkward about themselves\n\n## Goal\nThey find out privately, fix it, and are grateful rather than humiliated. The rule of thumb: if they can fix it in the next five minutes (food in teeth, an open fly, a typo), always tell them. If it is ongoing and personal (body odour, breath), tell them once, privately, and only if you are the right person.\n\nFor feedback on someone's work or behaviour, use `give-feedback-kindly` or `give-feedback-to-colleague`.\n\n## Structure\n1. **Private channel, right away.** A DM, a quiet word, a discreet gesture. Never in front of others or in a public reply.\n2. **Say it plainly in one sentence.** Euphemisms prolong the discomfort.\n3. **Normalise it.** One short line that it happens to everyone.\n4. **Give them an exit**, and move on. Do not linger, do not bring it up again.\n\n## Principles\n- Speed is kindness for quick fixes. Five seconds of awkwardness saves them an afternoon of embarrassment.\n- The more personal the issue, the more private and the more considered the message. Body odour and breath deserve a face-to-face word or a private message, not a note left on the desk.\n- Who says it matters. A close friend, a manager, or a trusted peer is better than a near-stranger. At work, persistent hygiene issues are usually for the manager, handled privately and with care.\n- Assume a reason you do not know about: a medical condition, a broken washing machine, a new medication, a hard stretch at home. Leave room for it without asking.\n- Say it once. If they fix it, it never happened.\n- Do not gather a group opinion first. \"We all noticed\" turns a kindness into a verdict.\n\n## Examples\n\n**Food in teeth or something on their face (quiet, in person):**\n> Quick one, you've got a bit of something in your teeth, left side.\n\n**Open fly or wardrobe issue, before a meeting:**\n> Heads up before you go in, your fly's down. Saved you!\n\n**Typo in a public post (DM, not a comment):**\n> Loved the post! Tiny thing, the second paragraph says \"pubic sector\" instead of \"public\". Thought you'd want to catch it before more people see it.\n\n**Wrong date on an event invite they sent out:**\n> Hey, just checking: the invite says Saturday the 14th, but the 14th is a Friday. Which one did you mean? Might be worth a quick correction.\n\n**Close friend, breath (in person or private text):**\n> This is a bit awkward, and I'm only saying it because I'd want you to tell me: I've noticed your breath has been a bit off lately. Could be nothing, but a dentist might know. Anyway, that's it, carry on!\n\n**Colleague you are close to, body odour (private, in person):**\n> Can I mention something a bit personal, just between us? I've noticed a bit of a smell sometimes in the afternoons. I'd want someone to tell me, so I'm telling you. No big deal, and I won't bring it up again.\n\n**Manager to a report, persistent hygiene issue (private meeting):**\n> I want to raise something a bit sensitive, and it stays between us. A few times recently there's been a noticeable body odour. I'm not assuming anything about why, and if there's something going on that we can help with, like a health issue or something at home, I'd like to know. Can we agree you'll keep an eye on it?\n\n## Avoid\n- Telling them in front of others, or replying publicly to their post.\n- Anonymous notes, gifts of deodorant, or \"hints\".\n- \"Everyone's been talking about it.\"\n- Long preambles that make them fear something far worse.\n- Laughing, or telling the story later.\n- Asking why it is happening.\n\n## If it goes badly\nIf they are embarrassed, lighten it and move on: say it happens to everyone and change the subject. If they get defensive or hurt, do not repeat the details or add evidence; say you only mentioned it because you would want to know, and drop it. If a work hygiene issue continues after one private conversation, it becomes a manager's issue to raise privately again, with an offer of support, not a peer's to keep repeating.\n> Honestly, it happens to everyone, I've done it twice this week. Right, coffee?\n> I didn't mean to upset you. I only said it because I'd want someone to tell me. That's all, I won't mention it again."},
{"id":"thank-you-notes","title":"Thank-you notes (gifts, hospitality, mentors, favours, late thanks)","category":"personal","tags":["thank you","gratitude","gift","card","host","mentor"],"triggers":["write a thank you note","thank you card message","thank them for the gift","thank you for having us","thank my mentor","thank you message for a favour","belated thank you","what to write in a thank you card"],"summary":"How to write a thank-you that feels personal: name the specific thing, say what it did for you, and look ahead. Covers gifts, hosts, mentors, favours, weddings and very late thanks.","updated":"2026-09-27","body":"# Thank-you notes\n\n## Goal\nThe person feels that you noticed exactly what they did and that it mattered. A good thank-you is short, specific and a little bit personal. The formula is easy; what makes it land is one concrete detail they could not have guessed you would mention.\n\nFor responding to praise, or quick appreciation at work, see `give-and-receive-compliments`.\n\n## Structure\n1. **Thank them for the specific thing**, by name. \"The blue linen tablecloth,\" not \"the lovely gift.\"\n2. **Say what it did for you or how you will use it.** One real detail.\n3. **Mention the person, not only the object or favour.** Their effort, their thought, the time they gave.\n4. **A forward line.** When you will see them, how you will pass it on, or what happens next.\n5. **Warm sign-off.**\n\n## Principles\n- Specific beats effusive. One real detail is worth three adjectives.\n- Send it soon. Within a few days for texts and emails, two weeks for cards. Late is still far better than never.\n- For money gifts, name what you will do with it rather than the amount.\n- If you did not love the gift, thank them for the thought and the care, honestly. Never invent enthusiasm you will have to keep up.\n- Handwritten for weddings, funerals, mentors, formal gifts and older relatives. A text is fine for friends, dinner and small favours.\n- Match the length to what they did. A lift to the airport gets two lines; a year of mentoring earns a paragraph.\n\n## Examples\n\n**Gift, from a friend (text):**\n> Thank you for the ceramic mug! It's already my morning coffee mug and I think of you every time I pick it up. Brunch soon? My shout.\n\n**Host after a dinner or weekend (text):**\n> Thanks so much for having us on Saturday. That lamb was ridiculous and the kids are still talking about the treehouse. Our turn next, how's the 20th?\n\n**Money gift, from a relative (card):**\n> Dear Aunt Mei, thank you so much for the birthday money. It's going towards the pottery course I've been wanting to take for ages, so you'll get a slightly wonky bowl out of it. Love, Lin\n\n**Wedding gift (card):**\n> Dear Sophie and Raj, thank you for the beautiful serving board. It had pride of place at our first dinner as a married couple. More than that, thank you for travelling so far to be with us; it meant a lot to see you there.\n\n**Mentor or former manager (email):**\n> I wanted to say thank you properly. The way you walked me through that first client pitch, and let me run the second one, is the reason I felt ready for this new role. I hope I get to do the same for someone one day. Coffee next time I'm in town?\n\n**Someone who did a big favour:**\n> Thank you for looking after Biscuit all week. Coming home to a happy dog and a note about his new favourite stick made my day. Please let me return the favour whenever you need it.\n\n**Very late thanks:**\n> This is embarrassingly late, but I didn't want it to go unsaid: thank you for the baby blanket. It's become Leo's favourite and it's in half our photos. We're so grateful.\n\n**A gift you didn't love:**\n> Thank you for thinking of me with the candle set, that was really kind, and it was lovely to see you at the party.\n\n## Avoid\n- \"Thanks for the gift\" with no detail. It reads as a template.\n- Over-apologising for lateness. One clause, then the thanks.\n- Mentioning the price or the amount of money.\n- Sliding in an ask at the end (\"also, could you...\").\n- Copying the same message to every guest. Change at least the specific line.\n- Promising to use something you will not use.\n\n## If it goes wrong\nIf you realise you have forgotten to thank someone for months, send it now with one line of ownership, not a paragraph; it will still be welcome. If you thanked the wrong person for a gift, correct it lightly and thank both. If you cannot remember who gave what, ask the organiser or check the cards before guessing, and send a general warm thanks to anyone you truly cannot place.\n> I've just realised I never properly thanked you for the housewarming plant, which is shameful given it's thriving. Thank you!\n> Small mix-up: I thanked Dan for your lovely book, when it was you. Thank you, I'm halfway through already."},
{"id":"upsell-without-pushiness","title":"Suggesting an upgrade, add-on or repeat purchase without being pushy","category":"commerce","tags":["upsell","cross-sell","add-on","repeat customer","recommendation","sales"],"triggers":["upsell","suggest an add-on","recommend the bigger package","get them to buy again","cross-sell","mention the premium option"],"summary":"How to recommend more in a way that reads as helpful advice, not a sales script: relevance, one option, honest framing, easy no.","updated":"2026-09-27","body":"# Suggesting more without being pushy\n\n## Goal\nThe customer feels advised, not sold to. Even if they say no, they trust you more.\n\n## The rule\nOnly suggest something that is genuinely better for them given what they've already told you. If you cannot say why it is better for them in one sentence, do not suggest it.\n\n## Structure\n1. **Confirm what they're getting** (so they feel handled).\n2. **The suggestion, framed around their situation.** \"Since you mentioned X...\"\n3. **One honest trade-off** (price, time). Honesty about the cost is what makes it advice.\n4. **An explicit easy no.**\n\n## Principles\n- One suggestion. A menu of add-ons feels like a checkout page.\n- Say when the cheaper option is fine. \"Honestly, for what you described, the basic one is enough\" builds the trust that sells the next thing.\n- Timing: after they've decided to buy, or after they've had a good experience. Not before the first yes.\n- Never manufacture urgency. Real deadlines are fine; fake ones are noticed.\n- For repeat purchases, a reminder with a reason beats a discount.\n\n## Examples\n\n**Add-on at point of sale, DM:**\n> Great, the medium tote it is. One thought since you said it's for a laptop: the padded insert is $18 and makes it a lot safer for daily commuting. Not essential, just say if you want it added.\n\n**Suggesting the bigger package, service:**\n> Based on what you've told me about the two-bathroom flat, the standard clean will work. If you want the inside of the oven and windows done too, that's the deep clean at $40 more; most people do that one first time and then standard after. Either's fine.\n\n**Honest downsell (this is what makes upsells work later):**\n> For a one-off event you don't need the pro plan; the basic one covers everything you listed. If you end up running these monthly, that's when the pro plan pays for itself.\n\n**Repeat purchase nudge:**\n> Hey Sam, it's been about three months since your last bag of the Ethiopian, which is roughly when people run out. Want me to send another? Same as before, or try the new Colombian?\n\n**Suggesting a related product after a good experience:**\n> So glad the serum's working for you. If you want to build on it, the moisturiser is the thing people pair with it most, but it's not needed; the serum does the heavy lifting on its own.\n\n**Premium tier, when they ask \"what's the difference\":**\n> The premium is $30 more and the real difference is [one concrete thing]. If [their situation], it's worth it. If not, the standard is genuinely fine and I'd rather you get what you'll use.\n\n**Client, scope expansion:**\n> Now that the site's live, the natural next step is the email flows; that's usually where the next revenue jump comes from. Happy to scope it if it's useful, or we can leave it here.\n\n## Avoid\n- \"Would you like to add...?\" scripts.\n- \"Customers who bought this also bought.\"\n- Fake scarcity.\n- Recommending the expensive one to everyone.\n- Multiple add-ons at once.\n- Following up on a declined suggestion.\n\n## If they say no\nA no to a suggestion is a complete answer. Confirm the original order, do not repeat the pitch, and do not add a \"just in case\" line. The next time they buy is where the trust you kept pays off. If they react badly to being sold to, own it in one line.\n> No problem, the standard tote it is. I'll have it out to you Tuesday.\n> Fair enough, that came across as a sell rather than a suggestion, and that wasn't the idea. Standard clean, Thursday 10am, confirmed.\nIf they say no and then ask about the add-on a week later, answer as if it is the first time. No \"I did mention that\"."},
{"id":"wedding-and-event-host-messages","title":"Wedding and event host messages (invites, plus-ones, no kids, gifts, dress code, cuts)","category":"personal","tags":["wedding","event","host","invitation","plus one","guest list"],"triggers":["how to word no plus one on wedding invite","tell guests no kids at our wedding","guest asked to bring someone to our wedding","how to ask for money instead of gifts","uninvite someone from my wedding","wedding dress code wording","remind guests to rsvp","we cut the guest list"],"summary":"Messages for the host of a wedding, party or big event: invitation wording, no plus-one or no kids, gifts, dress code, RSVP chasers, cutting or uninviting. Declining someone else's invite: decline-invitation.","updated":"2026-09-27","body":"# Wedding and event host messages\n\n## Goal\nGuests know exactly what is expected, feel welcome, and do not feel singled out by the limits. Rules for a big event are fine; they land well when they are stated once, warmly, for everyone, before anyone has to ask.\n\nDeclining an invitation you received: `decline-invitation`. A group chat for planning: `group-chat-coordination`.\n\n## Structure\n1. **Put the rule in the invitation or website**, framed as a fact about the event (\"an adults-only celebration\"), not a list of banned people.\n2. **When someone asks for an exception, thank them for asking.**\n3. **State the limit as applying to everyone**, with the plain reason in a few words (space, budget, numbers).\n4. **Add a warm line about them** and what you are looking forward to.\n5. **No negotiation.** One exception becomes five; decide in advance who, if anyone, is exempt.\n\n## Principles\n- A rule for everyone is easy to accept. A rule that seems aimed at one person is not, so apply limits by category (no plus-ones unless engaged or living together), and keep to the category.\n- Say it early. The invitation or website is the kindest place; a text a week before is the hardest.\n- Gifts are always optional. Mention preferences only where guests will look (website, card insert), never as a demand.\n- RSVP chasers are admin. Keep them short and give a real date and the reason (the caterer needs numbers).\n- Uninviting is rare and serious. Do it in person or by call if you can, give the real reason briefly, and take the cost on yourself.\n- Keep your partner or co-host aligned. Contradictory answers from two hosts are how guest-list feuds start.\n\n## Examples\n\n**Invitation wording, no plus-ones:**\n> We've kept the guest list small so we can celebrate with the people closest to us. Your invitation is for the names on the envelope; we hope you understand.\n\n**Invitation wording, adults only:**\n> We love your little ones, but we've chosen to make this an adults-only celebration. We hope it's a chance for a night off.\n\n**Someone asks to bring a new partner:**\n> Thanks so much for asking, and I'm glad things are going well with Sam. We've had to keep plus-ones to partners who live together to stay within numbers, so it's just you this time. I can't wait to see you there.\n\n**Gifts, card insert or website:**\n> Your company is the best gift. If you'd like to give something, a contribution towards our honeymoon would mean a lot, and there are details on the website.\n\n**Dress code, clear and specific:**\n> Dress code: cocktail. Think suits without ties, dresses or smart separates. The ceremony is on grass, so block heels or flats are a good idea.\n\n**RSVP chaser:**\n> Hi Laura, just chasing RSVPs for the 14th. Could you let me know by Friday if you can make it, and any dietary needs? The caterer needs final numbers on Monday.\n\n**Cutting the guest list before invites go out (to someone expecting one):**\n> I wanted to tell you myself rather than you wonder: we've had to cut the wedding right down to family and a few friends, so we couldn't invite everyone we'd hoped to, including you. I'm really sorry, and I'd love to take you for dinner when we're back.\n\n**Uninviting after invitations went out (rare, by call if possible):**\n> I owe you a hard message. After what happened with Mia, we've decided it's best that you don't come to the wedding. I know that's painful to hear, and I didn't make the decision lightly. I'd rather tell you straight than leave it unsaid.\n\n## Avoid\n- \"No ring, no bring\" and other jokes that make the rule feel like a jab.\n- Listing names of people who are or are not allowed.\n- Putting gift preferences on the main invitation card, or asking for cash as an expectation.\n- Making an exception for one guest and hoping nobody notices.\n- Uninviting by group message, or blaming it on \"the budget\" when it is a personal reason.\n\n## If it goes badly\nIf a guest pushes back on a limit, repeat it once, shorter, and do not add new reasons; new reasons are new targets. If they say they will not come without their partner or children, accept it warmly and do not bargain: \"I understand, we'll miss you.\" If family members start lobbying for someone, agree a single answer with your co-host and let one of you give it. If an uninvited guest threatens to turn up, tell the venue and a trusted person to handle it quietly on the day, and do not argue it again in writing.\n> I get it, and I'm sorry it's disappointing. We're keeping it the same for everyone. I really hope you'll still come.\n> That's completely your call, and we'll miss you. Let's celebrate properly together when things calm down."},
{"id":"write-a-recommendation-or-reference","title":"Writing a recommendation or reference for someone (LinkedIn, letter, reference call)","category":"work","tags":["recommendation","reference","linkedin","referee","endorsement","letter"],"triggers":["write a linkedin recommendation for my coworker","reference letter for a former employee","my old intern asked me to be a reference","what to say on a reference call","write a recommendation letter for grad school","give a reference for someone i have doubts about","character reference for a friend","recommend my nanny"],"summary":"Writing a recommendation or giving a reference for someone else: specific evidence, honest scope, and what to do when you have reservations. Asking someone to be your reference: ask-for-reference-or-recommendation.","updated":"2026-09-28","body":"# Writing a recommendation or reference\n\n## Goal\nThe reader believes you because you are specific, and the person is helped because the evidence fits the role. The kindest reference is a truthful one with the strongest true things first.\n\nAsking someone to be your referee: `ask-for-reference-or-recommendation`.\n\n## Structure\n1. **How you know them**: role, how long, how closely. This sets how much weight the reader gives you.\n2. **Two or three strengths, each with one concrete example.** A number, a project, a moment.\n3. **What they would be good at next**, tied to the role or programme they are applying for.\n4. **A clear endorsement** at the level you truly mean (\"without hesitation\", \"strongly\", \"for roles like X\").\n5. **An offer to talk**, with contact details, for letters.\n\n## Principles\n- Specific beats superlative. \"She cut our month-end close from nine days to five\" does more than \"exceptional\".\n- Ask them for a short brief: the role, the deadline, and two or three things they would like you to mention. Then write only what you saw and can stand behind.\n- Match length to format: LinkedIn is 3 to 5 sentences, a letter is under a page, a reference call is short answers with one example each.\n- If you cannot recommend someone, say no to the request early and kindly, rather than writing something lukewarm. A faint reference hurts more than no reference.\n- With reservations, narrow the scope instead of lying: recommend them for what they were good at and stay silent or factual on the rest. Never invent strengths, and never hide something serious that a reader has a right to know, such as a safeguarding concern.\n- Check company policy for former employees; some allow only dates and title.\n\n## Examples\n\n**LinkedIn recommendation, peer:**\n> I worked alongside Priya for three years on the payments team. She's the person everyone went to when an incident got messy: calm, fast, and clear in the incident channel. She rebuilt our alerting so false pages dropped by about 70 percent. Any team would be lucky to have her.\n\n**LinkedIn recommendation, former report:**\n> I managed Tom for two years. He joined as a junior analyst and within a year was running our quarterly forecast on his own. What stood out was his judgement: he knew when a number looked wrong and chased it down before it reached the board. I'd hire him again tomorrow.\n\n**Reference letter, opening and close:**\n> I'm pleased to recommend Ana Lopes for the MSc in Environmental Policy. I supervised Ana for 18 months as a research assistant at the city council, where she led the data collection for our air quality study across 40 schools...\n> I recommend Ana without hesitation, and I'd be glad to talk further: 07700 900456 or j.hart@example.org.\n\n**Reference call, a direct question about a weakness:**\n> Early on, she took on too much herself instead of delegating. By her second year she'd fixed that; she was running a team of three and the handoffs were clean.\n\n**Recommending someone for part of what they did (with reservations):**\n> I can speak to Sam's client work, which was excellent: he kept our two largest accounts through a difficult year. I worked less closely with him on internal projects, so I'll leave those to others.\n\n**Declining to be a reference, kindly:**\n> Thanks for asking me, I'm glad the search is going well. I don't think I'm the best person for this one, since we only worked together briefly on the launch. Someone who saw more of your day-to-day work will give you a stronger reference.\n\n**Nanny or tradesperson, personal reference:**\n> Maria looked after our two children for four years. She was reliable to the minute, the kids adored her, and she handled a broken arm at the park with total calm. We recommend her wholeheartedly.\n\n## Avoid\n- Superlatives with no evidence (\"amazing\", \"rockstar\").\n- A generic template with the name swapped in.\n- Coded faint praise (\"punctual and always well dressed\") instead of an honest no.\n- Stretching what you saw, or signing a draft they wrote that says things you do not believe.\n- Mentioning protected characteristics, health or family circumstances.\n\n## If it goes badly\nIf you realise after agreeing that you cannot write a strong reference, tell them now, privately, and help them find a better referee. If a reference call asks something you cannot answer honestly in their favour, answer briefly and factually, or say it is outside what you saw. If they ask to see what you wrote and you would not be comfortable showing them, rewrite it until you would.\n> I've thought about it more, and I don't think I'm the right referee for this role. I only saw a small part of your work. Could Dana be a better fit? I'm glad to tell her what I did see.\n> That's outside what I worked on with him, so I can't really speak to it. What I can say is that his client work was consistently strong."}
]}