ChatGPT Prompts for Customer Support

Write a professional, empathetic customer support reply for the following ticket.

Product: [product name]
Issue category: [billing | technical | account | shipping | other]
Customer message: "[paste ticket text here]"
Account status: [free | paid | enterprise]
Previous interactions: [none | 1 prior contact | ongoing issue]

Requirements:
- Open with genuine acknowledgment of their frustration without being sycophantic
- Summarize the issue back to show you understood
- Provide a clear step-by-step resolution or next steps
- Set realistic expectations on timeline if escalation is needed
- Close with a warm, reassuring sign-off
- Tone: professional yet human — avoid robotic corporate language
- Length: 150-250 words

Draft an internal escalation email to pass a complex customer issue to a senior support agent or engineering team.

Customer name: [name]
Ticket ID: [ID]
Product area: [billing | API | UI bug | data loss | security | other]
Issue summary: [describe the problem in 2-3 sentences]
Steps already taken by first-line support: [list what has been tried]
Customer sentiment: [frustrated | urgent | calm | threatening churn]
SLA remaining: [X hours]
Desired outcome from escalation: [fix bug | refund | account recovery | explanation]

Write the email with:
- A concise subject line
- Priority level recommendation (P1/P2/P3)
- Clear context so the escalation team does not need to re-read the original thread
- Suggested owner or team to assign to

Generate a comprehensive FAQ document for our [product/feature name] based on the following context.

Product description: [brief description]
Common support topics we see: [list 5-8 recurring themes from tickets]
Target audience: [beginners | intermediate users | developers | enterprise admins]
Tone: [friendly and casual | professional | technical]

For each FAQ entry:
- Write a question exactly as a customer would phrase it
- Provide a clear, scannable answer (use bullet points where helpful)
- Flag any questions that require screenshots or video walkthroughs

Generate at least 10 FAQ entries organized into logical sections (Getting Started, Billing, Troubleshooting, Advanced Features).

Create a set of canned responses for our customer support team to cover the following scenarios.

Product: [product name]
Scenarios to cover:
1. Password reset instructions
2. Refund policy explanation (our policy: [describe policy])
3. Feature not yet available (roadmap response)
4. Billing charge dispute
5. Slow performance / outage acknowledgment
6. Account upgrade instructions
7. Cancellation confirmation with save attempt

For each canned response:
- Write a ready-to-send version (agents fill in [bracketed] variables)
- Keep each under 120 words
- Include a suggested subject line for email tickets
- Mark responses that need personalization with a [PERSONALIZE] flag

Write a de-escalation response for an angry or threatening customer message.

Customer message: "[paste the angry message here]"
Root cause of their frustration: [data loss | billing error | product not working | long wait time | other]
What we can actually offer: [refund | credit | priority fix | explanation | escalation to manager]
What we cannot offer: [describe limitations]

The response must:
- Never be defensive or make excuses
- Validate their feelings without agreeing that we were necessarily wrong
- Acknowledge the specific impact this had on them
- State clearly what we will do (not what we cannot do)
- Offer a concrete next step within a specific timeframe
- Avoid hollow phrases like "I apologize for the inconvenience"
- Tone: calm, firm, and genuinely caring

Analyze the sentiment and intent of the following customer support messages and produce a structured report.

Messages to analyze:
[Paste 5-20 customer messages, each on a new line, optionally prefixed with a ticket ID]

For each message, provide:
- Sentiment: Positive / Neutral / Negative / Highly Negative
- Primary emotion detected: frustrated | confused | urgent | satisfied | threatening | disappointed
- Intent: seeking help | requesting refund | reporting bug | threatening churn | complimenting | escalating
- Priority score: 1 (low) to 5 (critical) with reasoning
- Suggested response approach: [empathy-first | quick resolution | escalate | save attempt | thank and close]

End with a summary table and overall health score for this batch of tickets.

Write a help center knowledge base article for the following topic.

Article title: [e.g., 'How to Reset Your Password']
Product: [product name]
Target reader: [new user | experienced user | admin | developer]
Difficulty level: [beginner | intermediate | advanced]
Key steps involved: [list the main steps or concepts to cover]
Related articles to link to: [list article titles or URLs]

Article requirements:
- Start with a one-paragraph overview explaining what the article covers and who it is for
- Use numbered steps for procedural content
- Use bold for UI elements, menus, and button names
- Include a "Before you begin" prerequisites section if needed
- Add a "Troubleshooting" section with 3 common problems and fixes
- End with a "Next steps" section linking to related articles
- Target length: 400-600 words

Write a proactive outreach email to send to a customer who may be at risk of churning.

Customer segment: [trial user who hasn't logged in | paid user with declining usage | customer who filed 3+ tickets in 30 days | customer approaching plan limit]
Product: [product name]
Key value proposition: [one sentence on main benefit]
What we know about their usage: [describe their usage pattern or ticket history]
Offer we can make: [free consultation | extended trial | one-month credit | feature unlock | nothing]

Email requirements:
- Subject line: curiosity-driven, not salesy (write 3 options)
- Opening: reference their specific situation without being creepy about data usage
- Body: offer genuine value before any ask
- CTA: one clear, low-friction action (book a call, try a feature, reply to this email)
- Tone: human and conversational — written by a real person, not a robot
- Length: under 200 words

Write a customer response for a confirmed bug report.

Bug description: [describe the bug]
Impact on customer: [what they cannot do because of this bug]
Engineering status: [investigating | confirmed | fix in progress | fix deployed in next release]
Expected fix timeline: [X days | X weeks | unknown]
Workaround available: [yes — describe it | no]

Response requirements:
- Acknowledge the bug without making engineering promises you cannot keep
- If a workaround exists, explain it step-by-step
- Give an honest timeline if known, or explain why you cannot commit to one
- Explain what happens next (they will be notified when fixed? auto-credit? etc.)
- Offer a goodwill gesture if this is a critical bug affecting their workflow
- Do not use passive voice or blame the customer for finding the edge case

Write a follow-up message to send after a customer support ticket has been resolved.

Ticket type that was resolved: [billing | technical | account | general question]
Resolution provided: [brief description of what was fixed or explained]
Customer satisfaction during the interaction: [appeared happy | neutral | was frustrated but issue resolved]
Survey tool we use: [CSAT scale 1-5 | NPS 0-10 | simple thumbs up/down | Typeform link]
Survey link: [URL]

Message requirements:
- Short and respectful of their time (under 100 words)
- Reference the specific issue that was resolved so it doesn't feel generic
- Frame the survey as improving their experience, not as a corporate checkbox
- Make it easy to say no — don't guilt them into responding
- Include a warm sign-off with the agent's actual name
- Optional: add a P.S. with one helpful tip related to what they asked about