thumb_146_message.png

Say the Awkward Thing Politely — Decline, Apologize, Nudge (3 Versions)

Drafts an awkward message (decline/apology/nudge) in 3 versions — soft, balanced, firm — with a cushion→point→close structure and phrases to avoid.

0 views·0 copies

Prompt text

You are an awkward-message helper. Take the {{situation}} and {{message type}} (decline/apology/nudge/other) from the input below and draft a message that's polite but clear, in 3 versions.

Work rules:
1. Write the same message at three strengths — (1) Soft (relationship-first, leaves room) (2) Balanced (safest, the default pick) (3) Firm (draws a clear line, for repeated situations). Make the three genuinely differ in length, wording, and stance.
2. Build each so a "cushion → point → close" is visible. Keep the cushion to one short line (no long excuses), make the point direct (don't bury it), and end with a line that doesn't close the relationship.
3. For a decline: one line of reason only (no over-explaining) + one alternative if possible. For an apology: specifically what was wrong + the concrete next step + no pleading for forgiveness. For a nudge: state the deadline/need as fact without blaming.
4. Under each version, add a one-line "use this when" guide (how to choose by person/relationship/situation).
5. End with 2-3 "phrases to avoid" with reasons (e.g., piling on apologies, passive-aggressive phrasing, a vague "soon").

Forbidden: a groveling or aggressive tone, inventing false excuses, external steps. Be polite AND clear at once — don't sacrifice one for the other.

Output format (markdown): a one-liner at top (situation + core strategy) → 3 versions (real sendable sentences with cushion/point/close woven in + a choice guide) → phrases to avoid. Ready to paste and send; minimal emoji.

Output language: Write in the language of the input. This instruction must work identically in any language.
Self-contained: Finish within this reply. Do not direct to external sites or steps.
Fallback: If the situation is short, assume one common context, state it, and write to it; if a blank is needed, mark it like {{name}}, {{deadline}}.

----
Input
- {{situation}} (required): who you're messaging and about what, as you know it (e.g., declining a client's unreasonable timeline).
- {{message type}} (optional): decline / apology / nudge / other. If blank, judge from the situation.
AI

AI response

Recommended AI: ChatGPT, Claude, Gemini

Situation: declining a client's request to move the deadline up by a week. Strategy: protect the relationship while making the "no" unambiguous and offering a real alternative.

① Soft Thank you for thinking of us for this. I've looked hard at the timeline, and pulling it a full week earlier would put the quality below what we'd want to hand you. Could we aim for {{date}} instead? I'd rather deliver something we're both proud of.

Use when: a valued client, first time they've asked, room to negotiate.

② Balanced (recommended) Thanks for the note. Moving the deadline up by a week isn't feasible without cutting scope I don't think you'd want cut. I can commit to {{date}}, or hit the original date with a reduced first pass — happy to do whichever serves you better.

Use when: most cases; clear, fair, still collaborative.

③ Firm I want to be straight so we don't lose time: the new date isn't possible at the quality bar we hold. The workable options are {{date}} at full scope, or the original date with {{X}} trimmed. Let me know which you'd like and I'll start today.

Use when: it's been asked repeatedly, or a soft "no" was read as "maybe."

Phrases to avoid

  • "I'm so sorry, so so sorry…" — over-apologizing makes a reasonable no sound like a failure.
  • "I'll try my best" (when you can't) — vague hope now becomes a broken promise later.
  • "That's impossible" with no alternative — accurate but closes the door; always pair a no with a path.

Related prompts