Best PromptsSupport prompts
Ticket data: """ [PASTE 20-100 REAL TICKETS OR THEIR SUBJECTS AND FIRST MESSAGES. RAW IS BEST.] """ Build a support macro library from the tickets above. Product: [WHAT IT DOES] Our voice: [e.g. "warm and plain-spoken, never corporate" / "precise and technical, our users are engineers"] Policies I can state: [REFUNDS, SLAS, DATA HANDLIN
Support Macro Library
Turn your most common tickets into a reusable macro library with tone rules, escalation triggers, and honest wording for the bad news.
Businessintermediate
Customer feedback: """ [PASTE REVIEWS, SUPPORT TICKETS, NPS COMMENTS, CALL NOTES, CANCELLATION REASONS, OR APP STORE REVIEWS. INCLUDE SOURCE AND DATE PER ITEM IF YOU HAVE THEM.] """ Analyze the feedback above. Product and who uses it: [PRODUCT + SEGMENTS] What we plan to build next: [ROADMAP, so you can tell me whether the feedback supp
Voice of Customer Analysis
Mine reviews, tickets, and call notes for what customers actually struggle with, separating loud complaints from widespread ones.
Businessintermediate
Write a reply to the customer message below. Customer message: """ [PASTE THEIR MESSAGE] """ What actually happened (internal view): [THE FACTS: what went wrong, what's known, what's unknown] What I can offer within policy: [REFUND / REPLACEMENT / CREDIT / FIX ETA / NOTHING YET: the real options] What I cannot promise: [POLICY LIMITS, e
Customer Support Reply
Draft a support response that addresses the customer's specific issue, gives a concrete next step with a timeframe, and stays within policy.
Businessbeginner