PlaybookPrompts

Customer Support

Macros, triage, escalation, refund decisions.

Prompts for support teams: response templates that don't sound canned, tone re-anchoring after a hostile message, refund/credit decision frameworks, KB drafting.

Customer Support supporttone

Rewrite a canned support reply to sound human

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

2 variables • 2 suggested tools
Customer Support triageclassifier

Triage incoming tickets across urgency, intent, and team

Tier-1 triage is high-volume and low-leverage. This prompt produces a classifier you can use to route tickets before a human sees them.

2 variables • 2 suggested tools
Customer Support refundpolicy

Apply a structured refund/credit decision framework

Refund decisions are inconsistent across agents. A written framework + a model that applies it produces consistent outcomes you can defend to the customer.

1 variable • 2 suggested tools
Customer Support kbdocs

Generate a KB article from clustered support tickets

If you're answering the same question 10 times a week, write the KB article once. This prompt drafts one from real ticket excerpts.

3 variables • 2 suggested tools
Customer Support de-escalationtone

Re-anchor tone after a hostile customer message

When a customer sends an aggressive or threatening message, your reply sets the emotional trajectory of the entire conversation. This prompt helps you draft a response that acknowledges frustration without matching it or caving unnecessarily.

3 variables • 3 suggested tools
Customer Support incident-commsoutage

Write a proactive outage notification for affected customers

Getting ahead of an incident with a clear, honest outage notification reduces inbound ticket volume and builds trust. This prompt structures a message that covers what happened, who is affected, and what comes next—without vague filler.

5 variables • 4 suggested tools
Customer Support qacoaching

Give a support rep specific coaching on a weak ticket reply

Generic QA feedback ('be more empathetic') does not change behavior. This prompt produces specific, actionable coaching notes tied to exact lines in a rep's reply, making it useful for weekly 1:1s or async review.

3 variables • 3 suggested tools
Customer Support feature-requestssaying-no

Decline a customer feature request without losing goodwill

Saying no to a feature request is one of the most common and most mishandled support tasks. A poorly written decline feels dismissive; an over-promised one creates future problems. This prompt helps you draft a reply that is honest, warm, and closes the loop cleanly.

4 variables • 4 suggested tools
Customer Support handoffvip-accounts

Summarize a VIP account history for a support handoff

When a high-value account gets transferred between agents or escalated to a senior rep, a messy handoff wastes time and frustrates customers who have to repeat themselves. This prompt produces a tight, scannable account summary from raw ticket and note data.

4 variables • 4 suggested tools
Customer Support toneanalysis

Extract the real issue from an angry customer email

Hostile emails often bury the actual problem under frustration. This prompt strips away the emotional noise so a rep can respond to what the customer actually needs, not just how they said it.

2 variables • 3 suggested tools
Customer Support apologyemail

Write a genuine apology that avoids legal admission

Support reps often freeze when an incident needs a real apology but legal exposure is a concern. This prompt produces empathetic language that acknowledges impact without conceding fault prematurely.

4 variables • 4 suggested tools
Customer Support escalationinternal

Write a concise internal escalation brief for leadership

When a ticket needs to go up the chain fast, reps waste time writing lengthy summaries. This prompt produces a tight brief that gives leadership exactly what they need to make a decision or take action.

3 variables • 3 suggested tools
Customer Support policyplain-language

Rewrite a support policy excerpt in plain customer language

Pasting raw policy text into a customer reply damages trust and creates confusion. This prompt rewrites legal or internal policy language into clear, direct customer-facing explanations that still hold the policy's intent.

3 variables • 4 suggested tools
Customer Support troubleshootingtechnical-support

Build a branching troubleshooting script from a bug report

When a recurring bug has multiple causes, reps waste time asking the same scattershot questions. This prompt turns a known issue into a structured decision tree reps can follow without guessing.

3 variables • 4 suggested tools
Customer Support ticket-closureemail

Close a resolved ticket with a non-robotic sign-off

Ticket closures are the last impression a customer has of a support interaction, yet most read like automated form letters. This prompt writes closures that feel like a real person wrapping up a real conversation.

5 variables • 3 suggested tools
Customer Support macrosops

Audit a macro or saved-reply library for outdated entries

Macro libraries quietly go stale as products change, and reps don't always know which canned replies are safe to use. This prompt systematically flags entries that need updating, killing, or splitting.

3 variables • 4 suggested tools
Customer Support expectation-settingdelay

Set realistic expectations when a resolution will take time

When a fix requires engineering or a third party, reps often go silent or overpromise. This prompt writes honest, credible holding replies that keep customers calm without making commitments the team can't keep.

6 variables • 4 suggested tools
Customer Support follow-upticket-management

Draft a follow-up when a customer goes silent

A ticket stalls when the customer stops responding mid-resolution. This prompt writes a follow-up that prompts a reply without sounding passive-aggressive or automated.

4 variables • 4 suggested tools
Customer Support technical-supportplain-language

Translate a technical error message into plain customer language

Reps often paste raw error messages or engineer notes into replies, which confuses customers and erodes trust. This prompt turns technical output into a clear, actionable customer-facing explanation.

3 variables • 4 suggested tools
Customer Support compensationgoodwill

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

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.

3 variables • 4 suggested tools
Customer Support callbackscoaching

Prepare a support rep for a difficult customer callback

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.

5 variables • 4 suggested tools
Customer Support auto-replyhigh-volume

Rewrite an auto-reply for a high-volume support event

Generic auto-replies during outages or product launches frustrate customers who know something unusual is happening. This prompt writes an auto-reply that acknowledges the event and sets real expectations.

4 variables • 4 suggested tools
Customer Support churn-riskretention

Identify churn-risk signals in a support ticket thread

Support reps often handle tickets that contain early churn signals buried in the language — and miss them. This prompt scans a thread and surfaces those signals with a recommended response adjustment.

3 variables • 4 suggested tools
Customer Support known-issuestatus-update

Write a known-issue status update for waiting customers

When a bug or outage is known but not yet fixed, support teams need to update waiting customers without overpromising a timeline. This prompt drafts a credible, calm update that holds customers without losing them.

5 variables • 4 suggested tools
Customer Support faqonboarding

Build a new-customer FAQ from recurring support questions

New customers ask the same questions in their first 30 days, and support teams answer them repeatedly. This prompt turns a list of those recurring questions into a structured FAQ that can live in onboarding emails or a help center.

4 variables • 4 suggested tools