PlaybookPrompts

Prepare a support rep for a difficult customer callback

Customer Support callbackscoachingescalation

Reps walking into a callback with an angry or high-stakes customer often don't have a clear plan. This prompt builds a quick call brief with talking points, anticipated objections, and guardrails.

Prompt
You are a support team lead preparing a rep for a difficult inbound or outbound callback. Here is the context:

Customer name: {{CUSTOMER_NAME}}
Account tier or status: {{ACCOUNT_TIER}}
Summary of the issue and complaint history: {{ISSUE_AND_HISTORY}}
What the company can and cannot offer as resolution: {{RESOLUTION_OPTIONS}}
Any known sensitivities or prior escalations: {{KNOWN_SENSITIVITIES}}

Produce a callback brief with these sections:
1. Situation summary (3 sentences max) — what happened, why the customer is upset, what they want.
2. Opening line — how the rep should start the call to establish calm and signal they've done their homework.
3. Key talking points — 3 to 5 bullet points covering the resolution path and what to emphasize.
4. Anticipated objections — list 2 to 3 likely pushbacks and a one-sentence response to each.
5. Hard limits — what the rep must not agree to on this call, and what to say if the customer pushes past those limits.
6. Escalation trigger — the specific condition under which the rep should offer to bring in a manager.

Edge cases: If resolution options are genuinely unclear, note that in the brief rather than inventing offers the rep cannot honor.
Variables to fill in
  • {{CUSTOMER_NAME}}
  • {{ACCOUNT_TIER}}
  • {{ISSUE_AND_HISTORY}}
  • {{RESOLUTION_OPTIONS}}
  • {{KNOWN_SENSITIVITIES}}

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_NAME}}{{ACCOUNT_TIER}}{{ISSUE_AND_HISTORY}}{{RESOLUTION_OPTIONS}}{{KNOWN_SENSITIVITIES}}.
  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.