PlaybookPrompts

Write a compensation offer that doesn't set a bad precedent

Customer Support compensationgoodwillretention

Offering a goodwill credit or discount is easy; wording it so customers don't treat it as a standing policy is harder. This prompt drafts the message so it reads as a one-time gesture, not a guarantee.

Prompt
You are a senior support writer. Draft a compensation message for a customer who experienced the following issue: {{ISSUE_DESCRIPTION}}.

Compensation being offered: {{COMPENSATION_DETAILS}} (e.g., $20 account credit, one free month, shipping refund).
Reason this is a one-time gesture rather than policy: {{REASON_NOT_POLICY}}

Write the message using these steps:
1. Open by acknowledging the specific inconvenience — not a generic apology.
2. State the compensation clearly: what it is, how the customer accesses or receives it, and when it expires if applicable.
3. Frame it as a goodwill gesture tied to this specific situation, without language that implies it will happen again ('we always do this', 'you're entitled to', 'per our policy').
4. Close by affirming the relationship without overpromising future performance.
5. Keep the tone warm but brief — under 150 words total.

Edge cases: If the customer has already received a compensation credit in the past 90 days, this prompt may not be appropriate — flag that for the rep to check before sending. Do not use this framing for legally required refunds, which should reference the actual policy.
Variables to fill in
  • {{ISSUE_DESCRIPTION}}
  • {{COMPENSATION_DETAILS}}
  • {{REASON_NOT_POLICY}}

How to use this prompt

  1. Copy the prompt above (Copy button on the top-right).
  2. Replace each {{VAR}} with your own value. Variables: {{ISSUE_DESCRIPTION}}{{COMPENSATION_DETAILS}}{{REASON_NOT_POLICY}}.
  3. Paste it into one of the recommended tools below.
  4. Iterate: tighten constraints in the prompt if the output is generic.

Why this prompt is structured this way

The prompt is split into explicit steps because LLMs do better when the path is named, not implied. Each variable forces specificity at the input layer — vague inputs get vague outputs.

Heads up: some of the links on this page are affiliate links — meaning we may earn a commission if you sign up after clicking, at no extra cost to you. We only recommend tools we'd put on our own stack. You can see our full affiliate disclosure here.

Pair this prompt with a tool

The PlaybookPrompts weekly

One short email per week. The five sharpest prompts we found, one tool worth your attention, one anti-pattern to avoid. Unsubscribe in one click.

Newsletter signup is not configured. Set PUBLIC_NEWSLETTER_USERNAME in the build env.