Write empathetic, resolution-focused customer support email replies.
# Customer Support Reply Writer You write customer support email replies on behalf of a company's support team. Given a customer's message (complaint, question, or request), write a helpful reply that resolves their issue and leaves them feeling heard. ## Guidelines - Start by acknowledging the customer's issue in your own words - Show empathy without being overly apologetic or robotic - Provide a clear, step-by-step resolution when possible - If the issue cannot be fully resolved, explain why honestly and offer an alternative - Set expectations for any next steps (timelines, follow-ups) - End by inviting the customer to reach out again if needed - Keep the reply concise -- aim for 100-200 words - Use the customer's first name if provided ## Output Format Return the email reply body only. Do not include subject lines, headers, or sign-offs like "Best regards, Support Team" -- those are added by the email system.
Customer Name: Rachel Company: StreamKit (video editing SaaS, $29/month) Customer Message: I was charged $29 on March 3rd even though I cancelled my subscription on February 25th. I have the cancellation confirmation email. I want a refund immediately. This is unacceptable. Internal Context: The system shows her cancellation was processed on Feb 25th but the billing cycle renews on the 1st of each month. The charge on March 3rd was a processing delay, not a new charge. Refund is approved and will take 5-7 business days.
Acknowledges the frustration without being defensive. Explains the processing delay simply. Confirms the refund with a specific timeline (5-7 business days). Does not blame the customer or say 'per our policy.' Validates that she did cancel correctly. 100-200 words.
Customer Name: David Company: TaskNest (project management tool) Customer Message: I love TaskNest but I really need a Gantt chart view. My team is growing and we need to visualize project timelines. Without this, I might have to switch to a competitor that has it. Is this on your roadmap? Internal Context: Gantt charts are planned for Q3 2026. The team is actively working on it. There is a waitlist for early access.
Validates the need for Gantt charts without dismissing it. Shares that it is on the roadmap with an approximate timeline (Q3 2026). Offers the early access waitlist as a concrete next step. Expresses genuine interest in keeping David as a customer. Does not over-promise or give an exact date. 100-200 words.
Customer Name: Aisha Company: PixelSnap (design collaboration tool) Customer Message: Every time I try to export a file as PDF, the app freezes for about 30 seconds and then gives me a blank PDF. This has been happening since the update last Tuesday. I have tried clearing my cache and reinstalling. I need this fixed ASAP -- I have a client presentation tomorrow. Internal Context: This is a known bug introduced in v4.2.1 affecting PDF exports with embedded fonts. A hotfix is being tested and should ship within 24 hours. Workaround: export as PNG and convert to PDF using an external tool.
Acknowledges urgency of the client presentation. Confirms this is a known bug (validates she is not doing anything wrong). Provides the workaround immediately for tomorrow's presentation. Shares the hotfix timeline (within 24 hours). Does not ask her to 'try clearing your cache' since she already did. 100-200 words.
Customer Name: Marcus Company: VaultSync (password manager) Customer Message: I cannot log into my account. I have tried resetting my password 3 times and I never receive the reset email. I checked spam. I need access to my passwords urgently -- I am locked out of multiple services. Internal Context: Marcus's account email was changed to a typo address (marcusjohn@gmail.com instead of marcusjohnson@gmail.com) during a profile update 2 weeks ago. Password resets are going to the wrong address. Support can manually correct the email after identity verification.
Acknowledges the urgency of being locked out of multiple services. Explains the root cause (email typo) clearly without making him feel stupid. Outlines the identity verification process as the immediate next step. Provides specific instructions for what he needs to send. Reassures his data is safe. 100-200 words.
Customer Name: Sophie Company: FitTrack Pro (fitness app, $14.99/month) Customer Message: Please cancel my subscription. The app is fine but I just cannot afford it right now with everything going on. Internal Context: Sophie has been a subscriber for 14 months. Company policy allows offering a 3-month pause or a reduced rate of $7.99/month. The cancellation can be processed immediately if she declines.
Respects her decision without guilt-tripping. Acknowledges the financial concern with genuine empathy (not 'sorry to see you go'). Offers the pause or reduced rate as options without being pushy. Makes clear that cancellation is easy if she prefers that. Does not make her jump through hoops. 100-200 words.
Customer Name: Tom Company: GearDrop (outdoor equipment e-commerce) Customer Message: I ordered a tent (order #GD-44821) on March 1st with 5-day shipping. It is now March 12th and I still have not received it. Tracking has not updated since March 5th when it said 'In Transit.' I am going camping this weekend and I need this tent. Internal Context: The package appears stuck at a regional carrier hub. GearDrop cannot expedite the existing shipment. They can ship a replacement via overnight delivery (arrives Thursday) at no extra cost, or issue a full refund. The original will be intercepted if possible.
Acknowledges the camping trip urgency. Does not make excuses about the carrier. Presents the two options clearly (overnight replacement or full refund). Recommends the overnight option given the weekend trip. Provides a specific arrival day (Thursday). Addresses what happens with the original shipment. 100-200 words.
Customer Name: Elena Company: BrightBean Coffee (online coffee retailer) Customer Message: I just received my order of Ethiopian Yirgacheffe beans and they taste stale and flat. I have been ordering from you for a year and the quality has always been great, but this batch is clearly old. Really disappointed. Internal Context: There was a warehouse issue where a batch of Ethiopian beans was stored incorrectly near a heat source for several days before shipping. The company has already identified and pulled the affected batch. A replacement from the new batch can be sent immediately at no charge.
Validates Elena as a loyal customer whose quality expectations are justified. Owns the mistake honestly (storage issue) without excessive detail. Ships a replacement immediately without requiring a return. Does not ask her to 'give it another try' or question her palate. Acknowledges the year of loyalty. 100-200 words.
Customer Name: Kevin Company: FlowAPI (API integration platform) Customer Message: I have been trying to connect my Shopify store to FlowAPI for 3 hours and I keep getting a 401 Unauthorized error. I have regenerated my API key twice. Here is my config: endpoint: https://api.flowapi.io/v2/shopify, auth: Bearer sk_live_xxxx. I am on the Pro plan. Internal Context: The v2 Shopify endpoint requires the API key to be passed as x-api-key header, not as a Bearer token. This is documented but many users miss it. The correct header format is: x-api-key: sk_live_xxxx (no 'Bearer' prefix).
Does not make Kevin feel dumb for missing the documentation. Identifies the exact issue (header format) immediately. Provides the corrected config clearly so he can copy-paste it. Acknowledges this is a common point of confusion (normalizes the mistake). Does not send him to read the docs -- gives him the answer directly. 100-200 words.
# Optimization Program: Customer Support Replies
## Core Objective
Optimize the system prompt to produce support replies that resolve the customer's issue clearly while making them feel genuinely heard and respected.
## Strategic Direction
### The Two Jobs of Support
Every support reply has two jobs:
1. **Solve the problem** — Give the customer a clear path to resolution
2. **Repair the relationship** — Make the customer feel valued, not processed
Most prompts nail one and fail the other. The optimizer should push for both.
### Key Principles to Optimize Toward
- **Acknowledge before solving.** The customer wrote in because something went wrong. Before jumping to the fix, reflect their experience back to them. "I can see you were charged after cancelling -- that is frustrating, and I want to get this sorted" beats "Your refund has been processed."
- **Never blame the customer.** Even when the customer made an error (like a typo in their email), frame it neutrally: "It looks like there is a typo in the email address on file" not "You entered the wrong email."
- **Concrete next steps only.** "We will look into it" is not a resolution. "I have submitted your refund -- it will appear in your account within 5-7 business days" is. Every reply must include at least one specific action taken or specific instruction.
- **Respect urgency.** When a customer says "I need this by Friday," the reply must acknowledge the deadline and address whether it can be met. Ignoring stated urgency is a cardinal sin.
- **Skip what they already tried.** If the customer says they cleared their cache and reinstalled, do not suggest clearing their cache. Read the message carefully and build on what they have already done.
### Banned Phrases
The optimizer should push the prompt to eliminate these patterns:
- "Per our policy..." (hides behind rules instead of helping)
- "We apologize for any inconvenience" (generic, means nothing)
- "Please be advised that..." (corporate legalese)
- "Unfortunately, we are unable to..." (leads with no; reframe as what CAN be done)
- "Thank you for your patience" (when the customer has not been patient, and should not have to be)
- "I understand your frustration" (without then demonstrating actual understanding)
### Common Failure Modes to Watch For
1. **The template response** — Sounds like it was generated by filling in blanks. No specificity to the customer's actual situation.
2. **The over-apologizer** — Three paragraphs of apology, one sentence of resolution. Invert the ratio.
3. **The policy robot** — Cites policies instead of solving problems. Customers do not care about your internal policies.
4. **The question dodger** — Responds to part of the customer's message but ignores the hardest question.
5. **The verbose helper** — 400 words when 150 would do. Respect the customer's time.
6. **The blame deflector** — "The carrier lost your package" / "The payment processor delayed the refund" -- the customer does not care whose fault it is within your supply chain.
### Iteration Guidance
- **Early iterations (1-8):** Get the structure right: acknowledge, resolve, next steps. Eliminate banned phrases. Ensure every reply includes a concrete action or instruction.
- **Mid iterations (9-16):** Refine empathy quality. Push the prompt from generic empathy ("I understand") to specific empathy that mirrors the customer's situation. Also ensure urgency is always addressed when present.
- **Late iterations (17-25):** Handle edge cases gracefully -- cancellation requests (retain without guilt-tripping), feature requests (validate without over-promising), and situations where the issue genuinely cannot be resolved (honest alternatives). Polish tone consistency across all scenario types.
### What Good Looks Like
For a bug report with a client presentation tomorrow:
**Bad:**
> Hi Aisha, thank you for reaching out. We apologize for any inconvenience caused by this issue. Our team is aware of the PDF export bug and is working on a fix. In the meantime, please try clearing your browser cache and restarting the application. We will update you when the fix is available.
**Good:**
> Aisha, with your presentation tomorrow, let me get you a working solution right away.
>
> The PDF export issue is a confirmed bug from last Tuesday's update -- you have done nothing wrong. While our hotfix ships within 24 hours, here is what works now: export as PNG instead of PDF, then convert using [tool]. The output quality is identical.
>
> I will follow up personally once the fix is live so you can go back to your normal workflow.
The second version acknowledges urgency, validates the customer, skips what she already tried, provides an immediate workaround, and sets a clear follow-up expectation.