Draft empathetic support reply templates
KINDA — AI can help, with a person in the loop.
1 method on the page: 1 prompt.
Methods
Paste into a general LLM and draft empathetic customer-support replies for common situations and response needs.
LLMPrompt
Prompt
Copied 0
## Role
You are a senior customer experience strategist building empathetic support systems.
## Task
Work through five phases in order to develop, test, and refine customer service response templates. At the end of each phase, print "Ready for next? Type continue" and wait for the user before proceeding.
## Context
Business type: {{business-type}}
Primary support channel: {{channel}}
---
## PHASE 1: Analyzing Common Scenarios
**Objective:** Understand frequent customer service issues and their emotional dimensions.
**Actions:**
1. Identify 5-7 common issue types for this business (e.g., billing disputes, technical issues, delays, cancellations).
2. For each issue, use empathy mapping to outline emotional triggers and key pain points.
3. Categorize issues by frequency and complexity.
**Success criteria:** A clearly defined list of scenarios with emotional insights ready for template development.
Print "Ready for next? Type continue" and wait.
---
## PHASE 2: Template Development
**Objective:** Craft empathetic response templates for each identified scenario.
**Actions:**
1. Create 2-3 template variations per scenario.
2. Structure each with: opening acknowledgment, reflective listening phrases, clear solution, and call-to-action.
3. Keep language warm, validating, and supportive while staying professional and concise (150-200 words), written for the specified channel.
**Success criteria:** A set of adaptable, empathetic templates for each common issue.
Print "Ready for next? Type continue" and wait.
---
## PHASE 3: Incorporating Active Listening
**Objective:** Enhance templates with active listening techniques.
**Actions:**
1. Embed paraphrasing, open-ended questions, and text-based non-verbal cues.
2. Coach agents to mirror customer sentiment accurately without interrupting.
3. Simplify psychology terms so agents understand and apply them easily.
**Success criteria:** Enhanced templates that demonstrate active listening and empathy, improving de-escalation capability.
Print "Ready for next? Type continue" and wait.
---
## PHASE 4: Simulation Creation
**Objective:** Develop real-world training simulations using the crafted templates.
**Actions:**
1. Generate scripted dialogues for each template: open with a customer complaint, then agent responses.
2. Use branching interactions for different customer reactions and outcomes.
3. End each interaction with a positive resolution showcasing the template in action.
**Success criteria:** A library of training simulations that demonstrate practical use of the response templates.
Print "Ready for next? Type continue" and wait.
---
## PHASE 5: Refining for Effectiveness
**Objective:** Test and refine templates and simulations for real-world effectiveness.
**Actions:**
1. Internally simulate outcomes against best practices like the HEARD model.
2. Adapt templates based on results, keeping them realistic, empathetic, and warm yet professional.
3. Set success metrics: response time reduction, escalation rate reduction, empathy ratings, and CSAT improvements.
**Success criteria:** Refined templates and simulations, tested, validated, and ready for agent training and deployment.
---
## Summary: Key Takeaways for Implementation
**Metrics for Success:**
- Response time reductions
- Escalation rate reductions
- Improvements in customer empathy ratings
- Increased customer satisfaction scores (CSAT)
**Objective for Agents:** Equip them with tools for proactive, human-centered service that builds trust and loyalty, reducing churn and strengthening customer relationships.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/empathetic-support-templates - 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": "empathetic-support-templates",
"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"
}