ChatGPT for customer service

You are a calm, senior customer support agent. A customer is angry. Write a reply that (1) acknowledges their frustration in the first sentence, (2) takes responsibility without making excuses, (3) states the concrete next step, and (4) closes warmly. Keep it under 120 words, no corporate jargon. Here is their message: [paste the customer's message]

A customer asked how to do something in our product. Write a clear, friendly reply with numbered steps. Assume they are non-technical. End by offering to help if they get stuck. Product context: [describe what your product does]. Their question: [paste the question]

A customer requested a feature we can't build right now. Write a reply that thanks them specifically, explains we're not building it yet without over-promising, and asks one clarifying question about their underlying goal. Warm, honest, under 100 words. Their request: [paste the request]

A customer disputes a charge. Write a reply that stays neutral, restates the charge and what it was for, offers to investigate, and gives a clear timeline. Do not admit fault or promise a refund yet. Details: [paste their message and the charge details]

A customer is requesting a refund. Our refund policy is: [paste your policy]. Write a reply that is empathetic, states clearly whether the request fits the policy, and explains the next step. If it doesn't qualify, offer one good-faith alternative. Their message: [paste the message]

Rewrite this support reply to sound warmer and more human without adding length or losing any information. Keep it professional, drop any robotic phrasing: [paste your draft reply]

Tighten this support reply to half the length. Keep every fact and the next step, cut filler and hedging. Plain, direct language: [paste your draft reply]

Rewrite this reply in our brand voice. Our voice is: [e.g. friendly, plain-spoken, lightly witty, never salesy]. Keep the meaning identical. Reply to rewrite: [paste your draft]

This draft reply sounds defensive or blames the customer. Rewrite it so it takes ownership and stays on the customer's side, without admitting legal liability: [paste your draft]

Translate this support reply into [target language]. Keep it natural and conversational for a native speaker — not a literal translation — and preserve the warm, helpful tone. Reply: [paste your reply]

Write a short apology to a customer affected by a service outage. Acknowledge the impact, say what happened in plain terms, state what we're doing to prevent it, and avoid admitting legal liability. No jargon. Incident details: [paste what happened]

A customer says they're about to cancel. Write a reply that takes their concern seriously, asks one question to understand the real blocker, and offers a concrete path forward — without sounding desperate or discounting on reflex. Their message: [paste it]

Summarize this customer issue for our engineering team. Include: one-line summary, steps to reproduce, expected vs actual behavior, customer impact, and severity. Be factual and skip the pleasantries. Conversation: [paste the thread]

Write a brief, sincere apology for a delayed order. Give the new expected date if known, offer a small goodwill gesture, and make it easy for them to reply. Order details: [paste the details]

Write a public reply to this negative review. Stay gracious, address the specific complaint, avoid defensiveness, and invite them to continue privately. Under 80 words. Review: [paste the review]

Turn this one-off reply into a reusable saved reply (macro). Replace customer-specific details with clearly labeled placeholders like {{first_name}} and {{order_id}}, and keep the tone. Reply: [paste your reply]

Generate 5 saved replies (canned responses) for the most common questions a [type of business] support team gets. Each should have a short title and a reply with placeholders for personalization. Product context: [describe your product]

Write a clear, friendly canned response that walks a customer through resetting their password. Include numbered steps and what to do if the reset email doesn't arrive. Our reset URL is: [paste URL].

Write an auto-reply for inbound support emails received outside business hours. Set expectations on response time, point to our help center, and stay on-brand. Hours: [paste hours]. Help center: [paste URL].

Write a short in-app welcome message for someone who just started a free trial of [product]. One sentence of warmth, one clear first action to take, and one link to help. Under 60 words.

Turn this resolved support conversation into a reusable help center article. Use a clear title, a one-line summary, numbered steps, and a short 'If this didn't work' section. Strip out anything customer-specific. Conversation: [paste the thread]

Generate 15 frequently asked questions with concise answers for this product. Cover setup, pricing, security, and common confusion points. Write the answers in a friendly, plain voice. Product description: [paste it]

Rewrite this help article at roughly a 7th-grade reading level. Keep every step and fact, shorten sentences, and remove jargon. Article: [paste it]

Write clear step-by-step instructions for this task in our product. Number each step, start each with a verb, and note anything that commonly trips people up. Task: [describe the task]. Product context: [describe your product].

Write a 2-sentence TL;DR for the top of this help article so customers know in 5 seconds whether it's the right page. Article: [paste it]

Summarize this long support thread in 5 bullet points: what the customer wants, what's been tried, what's blocked, the current status, and the next step. Thread: [paste it]

Classify this support ticket. Return: category (bug / how-to / billing / feature request / account), priority (low / medium / high / urgent) with a one-line reason, and the right team to route it to. Ticket: [paste it]

Read this customer conversation and list every action item as a checklist, noting who owns each (us or the customer) and any due dates mentioned. Conversation: [paste it]

Analyze this customer message and return: sentiment (positive / neutral / negative), urgency (low / medium / high), and the single most important thing they need. One line each. Message: [paste it]

Write a short internal note handing this ticket to a teammate. Include: the customer's goal, what's already been done, the blocker, and exactly what the next person should do. No fluff. Conversation: [paste it]