PlaybookPrompts

Rewrite a canned support reply to sound human

Customer Support supporttone

Canned responses get read like canned responses. This prompt keeps the answer's content intact while removing tells.

Prompt
Rewrite this canned support response so it reads as written for this specific customer. Keep the technical accuracy and the policy. Remove canned tells ("thank you for reaching out", "we understand your frustration", "please don't hesitate").

Customer's message:
{{CUSTOMER_MESSAGE}}

Canned response:
{{CANNED_RESPONSE}}

Rules:
- Mirror the customer's tone unless they're abusive (then de-escalate).
- Lead with the answer, not the apology.
- Apology only if a mistake was actually on our side, and only once.
- End with a concrete next step or 'no action needed' — never 'let me know if you have any other questions.'
Variables to fill in
  • {{CUSTOMER_MESSAGE}}
  • {{CANNED_RESPONSE}}

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: {{CUSTOMER_MESSAGE}}{{CANNED_RESPONSE}}.
  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.