A frustrated long-time customer. A shipment with damaged units. Draft a response that protects the relationship — without admitting fault you don't owe.
You are the Customer Service Manager at a manufacturing company in eastern North Carolina.
This morning, you opened your inbox to a sharp email from Carolina Equipment Supply, a customer of 10+ years. Their latest shipment arrived with 3 damaged units out of 50. They're asking for a full replacement shipment and a 15% discount on their next order.
You pulled the records. Your packaging passed inspection. Photos from the customer show crush damage consistent with freight handling — not a plant defect. The freight carrier is responsible, not you. But this customer has been with you for a decade and does roughly $180K a year in business.
| Your Role | Customer Service Manager |
| Customer | Carolina Equipment Supply |
| Customer Contact | Denise Whitaker, Purchasing Director |
| Order | PO #CES-2041, 50 units |
| Issue | 3 units damaged on arrival — crush damage, not defect |
| Customer Demand | Full 50-unit replacement + 15% discount on next order |
| Likely Cause | Freight handling (carrier: Reliance Logistics) |
| Relationship History | 10+ years, $180K annual spend, first damage claim |
| Your Goal | Replace the 3 damaged units, file a freight claim, preserve the relationship — without admitting plant fault or eating a 15% discount |
Open whichever AI tool you prefer and start a new conversation:
If your company has deployed an enterprise AI, sign in with your work account for better data protection.
Type this exact prompt and see what you get:
Now paste this into the same conversation:
Revise the draft by typing this follow-up in the same conversation:
Now flex the other direction. In the same conversation, type:
One more use of the same thread. Try this:
The first prompt is rarely the best one. Iteration is where quality lives.
Giving AI a role changes the output completely. "You are an experienced Customer Service Manager" outperforms "write an email" every time.
Context is king. The relationship history, the freight evidence, the annual spend — all of that made the draft land.
Tone is a prompt, not a rewrite. Warmer, firmer, more diplomatic — ask, and the AI adjusts.
Talk back to the AI. Don't start over. Revise it the way you'd revise a coworker's first draft.
When you do this with a real customer situation at your own company: use your company's enterprise AI tool if one is deployed, never paste customer names, PO numbers, pricing, or contract details into a free public tool, and always read the draft carefully before sending. AI gets things close, not perfect. You are still the author. AI is the assistant.