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