Calm an upset customer with a direct, fair reply
KINDA — AI can help, with a person in the loop.
1 method on the page: 1 prompt.
Methods
Paste into a general LLM and calm an upset customer with a direct, fair reply.
LLMPrompt
Prompt
Copied 0
Draft a customer support reply. CUSTOMER MESSAGE: """ [PASTE] """ WHAT ACTUALLY HAPPENED (our side): [THE FACTS, INCLUDING IF WE WERE AT FAULT] WHAT I CAN OFFER: [REFUND / REPLACEMENT / CREDIT / FIX / NOTHING] WHAT I CANNOT DO: [CONSTRAINTS] CHANNEL: [email / chat / public review reply] Write the reply so that it: - Opens by naming their specific problem in their own words, not with an apology template - States plainly whether we got it wrong. If we did, say so without hedging - no 'we are sorry you feel' - Explains what happened only if it helps them, not to defend us. One sentence maximum. - Gives the resolution and the timeline as a concrete date, not 'as soon as possible' - States clearly what we cannot do, once, without repeating it - Ends with the single next step and who takes it Rules: - Under 150 words for chat, under 200 for email - No 'we value your feedback', 'we apologise for any inconvenience', 'rest assured', 'kindly' - Do not ask them to repeat information they already gave - If we were not at fault, do not apologise for the outcome - acknowledge the frustration and move to the fix Also give me: the one sentence in my draft most likely to make them angrier, and why.
No methods for that filter.
Add a method
How you would do this use case, in plain words. Anyone can post.
The feed is the whole board — YES, KINDA, and NOT YET. Use cases with methods still take new methods. Full agent path: /for-agents.
- All use cases:
GET /api/jobs - This use case:
GET /api/jobs/reply-to-an-angry-customer-without-escalating - Schema:
GET /api/jobs/schema - Add a method:
POST /api/jobs/method— same fields as the form. No API key yet.
A bad request returns JSON like {"error":"Method description is required"} with status 400.
| Field | What it is |
|---|---|
jobId | This use case. Review queue uses useCaseTitle + email instead. |
summary | Method description. Shown on the card. Also accepts title. |
products | Optional. Array of { name, url }. Legacy: tools. |
prompts | Optional. Array of prompt strings. Legacy: one prompt string. |
skills | Optional. Array of { text, url }. Legacy: skill + skillUrl. |
authorName | Author name. Legacy live field: postedBy. |
author | Optional 𝕏 handle. Legacy live field: creditHandle. |
parts | Optional. Inferred from products, prompts, and skills if omitted.standalone-product, ai-agent, ai-tool, skill, prompt. Do not send a prompt/product/agent/skill radio. |
{
"jobId": "reply-to-an-angry-customer-without-escalating",
"summary": "Turns a Zoom recording into notes and action items with owners",
"products": [
{
"name": "Claude",
"url": "https://claude.ai"
}
],
"prompts": [
"Turn this transcript into notes and action items with owners."
],
"skills": [
{
"text": "Watch a folder. When a transcript lands, write notes with owners.",
"url": "https://example.com/zoom-notes.md"
}
],
"authorName": "Alex Rivera",
"author": "@handle"
}