Apology, Condolence, and Boundary Messages
Write the three hardest personal messages with the structures that work: full-responsibility apologies, brief true condolences, calm clear boundaries.
Help me write a hard personal message. Type: [APOLOGY / CONDOLENCE / BOUNDARY]
The situation, honestly:
"""
[WHAT HAPPENED, for an apology: what I did (not what "happened"), the impact I know about. For condolence: who died, my relationship to the grieving person, anything I knew about the deceased. For a boundary: the specific behavior, how long it's gone on, what I need to change.]
"""
Relationship + channel: [WHO THEY ARE TO ME + TEXT / EMAIL / HANDWRITTEN CARD / SAID ALOUD]
FOR AN APOLOGY: build from the components research says carry the weight, in this order:
1. Acknowledge responsibility plainly: "I did X. That was my fault." This single component matters most.
2. Name the impact on them: showing I understand what it cost them, not just that I feel bad.
3. Brief explanation ONLY if it adds understanding: the moment it reads as excuse, cut it.
4. Repair: what I'm doing to fix it or make it right, concretely.
5. What changes so it doesn't repeat.
Banned constructions: "I'm sorry IF...", "I'm sorry, BUT...", "I'm sorry you felt...", "mistakes were made": each one converts an apology into a defense. Keep it short; length dilutes responsibility. No requests for forgiveness in the first message: that's asking them for something.
FOR A CONDOLENCE: 3-6 sentences, that's correct, not cold:
1. Name the loss directly ("I'm so sorry about [name]": use their name; avoiding it doesn't soften anything).
2. One specific memory or quality if I knew them ("I'll never forget how he..."), or an honest "I don't have the right words, but I'm thinking of you" if I didn't.
3. One CONCRETE offer: "I'm dropping dinner off Thursday" / "I'll text you next week", never "let me know if you need anything" (that hands the grieving person a task).
Banned: "better place", "everything happens for a reason", "at least...", "I know how you feel", comparisons to my own losses, advice, and questions that require a reply.
FOR A BOUNDARY: calm, specific, about my action not their character:
1. The observable fact: "When [specific behavior] happens...", no "you always", no character claims.
2. The impact on me: "I feel/end up..."
3. The clear request or limit: exactly what I'm asking for.
4. My action if it continues: something I control ("I'll leave the dinner", "I'll stop responding after 9pm"), stated as information, not threat.
5. One line of warmth that's true: why the relationship matters enough to say this.
No over-apologizing for having the boundary, no relitigating old grievances, no negotiating the core limit.
Give me the message in my channel's register, then one line on the timing or delivery that would help it land.How to use
These structures come from actual research: the apology components are Lewicki's six (acknowledgment of responsibility weighs most, forgiveness-requests least), the boundary script blends NVC with DBT's DEAR MAN, and the brevity rules for condolences come from grief counselors. The consistent AI failure is ornate length that centers the sender; the caps and ban lists here are the countermeasure. For anything said aloud, rehearse once. These messages wobble when improvised.
More writing prompts
Rewrite the text below in plain language for [AUDIENCE, e.g. "patients with no medical background" / "customers reading a policy update" / "new hires on day one"]. Target reading level: [e.g. "8th grade" / "as simple as the content allows"]. How to rewrite: - Lead with what the reader must DO or what happens to them. Background comes af
Plain Language Rewrite
Rewrite dense policy, legal, medical, or technical text at a target reading level without losing a single obligation or number.
Write a comparison article for the query: [e.g. "Notion vs Obsidian" / "best Mailchimp alternatives"]. Options to compare: [LIST 2-8 OPTIONS] Who is searching this: [READER + WHAT THEY ARE TRYING TO DECIDE] My relationship to these products: [e.g. "I make one of them" / "I use two of them daily" / "none, I am researching"] Facts I can su
Comparison Article
Write an honest X vs Y or best alternatives article: real differentiators, a decision table, and a clear pick for each type of reader.
Build an FAQ page for [PRODUCT/SERVICE/TOPIC]. Real questions people ask me: """ [PASTE SUPPORT TICKETS, SALES CALL NOTES, SEARCH QUERIES, OR COMMENTS. RAW IS FINE.] """ Facts I can state as true: [PRICING, POLICIES, LIMITS, TIMELINES] Do this: 1. **Cluster** the raw questions into distinct questions people actually ask. Merge duplicat
FAQ Page From Real Questions
Turn support tickets and sales objections into an FAQ page that answers in the first sentence and is structured for AI search engines.