45 ChatGPT Prompts for Customer Support

Write a support response to: '[paste ticket]'. Customer is [sentiment]. Our policy: [describe]. Respond with empathy, acknowledge their concern, explain the solution, and end with a next step. Under 150 words.

Tip: Always acknowledge the emotion before jumping to the solution. People need to feel heard.

Create 10 response templates for common issues: password reset, billing question, feature request, bug report, cancellation, refund, upgrade inquiry, integration help, account access, shipping status. Human, not robotic, with placeholders.

Tip: Templates should be starting points, not copy-paste scripts. Always personalize.

Write a response to a customer threatening to leave for a competitor. They're upset about [issue]. Retention offer: [describe]. Acknowledge frustration, demonstrate loyalty appreciation, present the offer, commit to satisfaction.

Tip: Retention responses work best when they address the root cause, not just offer a discount.

Draft a bug report response for '[describe bug]'. Acknowledge, explain what's known, set realistic fix timeline, offer workaround if available, and thank them. Technically competent with genuine appreciation.

Tip: Bug responses should always include what you're doing about it, not just that you received it.

Write a feature request response for '[describe]'. Validate the request, explain current capability, suggest a workaround, describe how requests are prioritized, and invite more detail about their use case. No promises about future development.

Tip: Never promise features you can't guarantee. Make the customer feel heard.

Create a billing dispute response. Customer claims incorrect charge. Actual situation: [describe]. If at fault, own it completely. If correct, explain clearly with references. Either way, clear resolution and next step.

Tip: Billing disputes require extreme clarity. Break down charges line by line.

Write an escalation response for an issue needing manager/engineering. Explain why (reassuringly), what happens next, expected timeline, who will contact them, and follow-up method. Make escalation feel like premium treatment.

Tip: Frame escalations as 'bringing in our specialist' not 'can't help you.'

Draft a response to a 1-star review: '[paste review]'. Acknowledge the complaint publicly, apologize, offer to make it right, provide direct contact. Professional, empathetic, solution-oriented.

Tip: Public review responses are as much for people reading them as for the reviewer.

Write a response to a customer transferred 3 times. They're extremely frustrated. Original issue: [describe]. Sincerely apologize for the runaround, take full ownership, commit to personally resolving, provide a direct contact.

Tip: The most powerful thing: 'I will own this until it is resolved.'

Create a de-escalation response for a customer using hostile language about [issue]. Acknowledge frustration without matching energy, set professional boundary if needed, redirect to the problem, offer resolution path.

Tip: Match the emotion, not the behavior. Be empathetic while maintaining boundaries.

Write a bad news response: [describe news, e.g., discontinuation, price increase, feature removal]. Empathize with impact, explain honestly, describe alternatives, offer transition plan, and provide direct contact.

Tip: Bad news responses should lead with empathy and a clear 'why.'

Draft a response for a customer waiting [X days] beyond timeline for [issue]. Delay reason: [explain]. Apologize, provide transparent update, give realistic new timeline, offer delay compensation, commit to proactive updates.

Tip: When you've missed a timeline, provide proactive updates before the customer asks.

Write a response to a customer claiming you promised something you didn't. Handle diplomatically: don't accuse them, review what was communicated, offer to investigate, find middle ground. Include language for if you did make the mistake vs miscommunication.

Tip: Framing it as 'miscommunication' preserves dignity and the relationship.

Create a response for a genuine service failure with real consequences (lost data, missed deadline, financial impact). Full responsibility, immediate remediation, prevention steps, appropriate compensation. No deflection.

Tip: When you genuinely failed, full accountability earns more loyalty than any excuse.

Write a response when a customer wants to speak to a manager. Issue: [describe]. You can resolve it. Acknowledge request, explain your authority, describe the specific resolution, and let them escalate if they prefer.

Tip: Often they just want someone with authority to take action. Demonstrate that authority.

Draft a final response for a customer you cannot satisfy. Exhausted all options for [issue]. Summarize what was tried, explain limitations, express genuine regret, offer any remaining alternatives, close professionally.

Tip: Closing unsolvable tickets with grace preserves the relationship.

Write a knowledge base article: how to [task] in [product]. Include: overview, step-by-step numbered instructions, screenshot descriptions, troubleshooting for common issues, and related article links.

Tip: Write KB articles at a 6th-grade reading level. If they need the article, they're frustrated.

Create a troubleshooting guide for [common issue]. Structure: symptom, 5 causes ranked most to least common, step-by-step fix for each, when to contact support, and diagnostic checklist.

Tip: Start with the most common cause. 80% of issues come from 20% of causes.

Write an FAQ section for [product/feature] with 12 questions. Cover: getting started, confusion points, billing, integrations, limitations, and security. Concise answers (3-5 sentences), plain language.

Tip: FAQ questions should use exact customer language, not internal jargon.

Create a getting started guide for new users. 5-step onboarding: account setup, first key action, core features, customization, advanced tips. Each: what to do, why it matters, 'you'll know it worked when' confirmation.

Tip: Give exactly one path to success, not a buffet of options.

Write release notes for [version/update]. Cover: new features with use cases, improvements, bug fixes, deprecated features, and known issues. Write for end users, not developers. Lead with what users care about.

Tip: Lead with the change that delivers the most user value.

Create a 'best practices' article about [topic related to product]. Include: 5-7 best practices with explanations, common mistakes section, example configurations, and power user tips. Actionable, not theoretical.

Tip: Best practices articles reduce support tickets by helping users set up correctly.

Write a comparison article: '[Our product] vs [manual process].' Compare: time, cost, accuracy, scalability, ease of use. Comparison table, real scenarios, honest about when our product isn't the best choice.

Tip: Honest comparisons are more trusted than one-sided feature lists.

Create API docs for [endpoint]. Include: URL and method, auth requirements, parameters with types, example request (curl and code), example response with field descriptions, error codes, and rate limits.

Tip: API docs with copy-paste examples get far fewer support tickets.

Create a support SOP for [scenario: refunds, outage comms, VIP escalations]. Include: when it applies, decision tree, required actions, response templates, who to notify, documentation requirements, and follow-up timeline.

Tip: SOPs should be short enough to reference during a live conversation.

Write a training guide for new agents on [inquiry type]. Cover: common scenarios, needed knowledge, example interactions (good and bad), escalation criteria, tools, and quality benchmarks. Include a first-week shadow checklist.

Tip: Pair training with real ticket examples annotated with what went well.

Create a customer feedback analysis template for monthly reviews. Categories: issue types, sentiment, feature requests, praise. Metrics: response time, resolution time, CSAT, volume by category. Insights format and action items for product/engineering.

Tip: The most valuable metric is insights surfaced for the product team from pain patterns.

Write an internal comms template for [outage / major bug / policy change]. Include: what happened, status, customer impact, approved messaging, what to tell customers, and next update timing.

Tip: During incidents, support needs one source of truth updated in real time.

Create a QA scorecard for evaluating support interactions. 10 criteria: greeting/empathy, issue identification, solution correctness, clarity, tone, personalization, efficiency, follow-up, KB usage, documentation. 1-5 scoring rubric.

Tip: QA scorecards should focus on behaviors agents can control, not situation-dependent outcomes.

Draft a macro library plan for [product] support. 20 most common ticket types. For each: macro name, trigger condition, template with placeholders, and automated actions (tags, assignments, status).

Tip: Well-built macro libraries reduce response time by 60% while maintaining personalization.

Write a customer success playbook for first 90 days post-purchase. Week 1: onboarding. Weeks 2-4: adoption. Month 2: expansion. Month 3: optimization. For each: milestones, proactive touchpoints, risk signals, intervention templates.

Tip: Proactive customer success in the first 90 days determines long-term retention.

Create a voice of customer report template for leadership. Sections: executive summary (3 bullets), ticket volume and trends, top pain points with verbatim quotes, ranked feature requests, churn risk signals, and recommended actions.

Tip: Include direct customer quotes. Nothing moves leadership to action faster than actual words.