customer-support
Verifiedby mastra-ai · Updated Apr 16, 2026
Guidelines for handling customer support interactions. Use when responding to user inquiries, troubleshooting issues, or escalating problems.
See It In Action
Got it — I've read through the inbox, customer records, and the playbook. Let me draft all four documents now.
All four documents are drafted and saved in docs/:
reply_LCH-10421_password_reset.md— Explains the provider throttling delay, sets expectation of ~10 min, offers a manual reset fallback given her time crunch.reply_LCH-10437_duplicate_charge.md— Confirms the duplicate, names both charge IDs, states the refund is submitted with a 5–10 business day window, and confirms the next billing date so Jordan knows no surprise charges are coming.reply_LCH-10455_account_takeover.md— Acknowledges the threat without disclosing forensic details (per playbook), lists the protective actions being taken (session lock, key revocation, forced reset, MFA), and commits to a 60-minute security follow-up.escalation_LCH-10455_security.md— Sev-1 internal note routed tosecurity-oncall@runcomfy.comwith all six required fields: ticket ID, customer info, full indicator timeline (IPs, locations, timestamps, password change, API key, risk score), requested actions, business impact assessment, and the 60-minute callback commitment.
SKILL.md
Customer Support Guidelines
Overview
This skill provides guidelines for professional customer support interactions. Apply these patterns when responding to user inquiries, troubleshooting issues, or handling escalations.
Keywords: customer support, help desk, troubleshooting, user inquiry, ticket handling, escalation
Response Framework
HEAR Method
- Hear - Acknowledge the customer's issue
- Empathize - Show understanding
- Assess - Gather information
- Resolve - Provide solution or next steps
Response Template
Hi [Name],
Thank you for reaching out about [brief issue summary].
[Empathy statement if appropriate]
[Solution or information]
[Clear next steps]
Best regards,
[Agent name]
Tone Guidelines
Do
- Use clear, simple language
- Be professional but friendly
- Acknowledge frustration when appropriate
- Provide specific, actionable information
- Set realistic expectations
Don't
- Use jargon or technical terms without explanation
- Be defensive or dismissive
- Make promises you can't keep
- Blame the customer or other teams
- Use ALL CAPS or excessive punctuation
Common Scenarios
Password Reset
Hi [Name],
I can help you reset your password. Here's how:
1. Go to [login page URL]
2. Click "Forgot Password"
3. Enter your email address
4. Check your inbox for the reset link (also check spam)
5. The link expires in 24 hours
If you don't receive the email within 5 minutes, let me know and I'll investigate further.
Billing Question
Hi [Name],
I've looked into your billing question.
[Specific answer with amounts/dates]
For reference:
- Your billing cycle: [date]
- Current plan: [plan name]
- Next charge: [amount] on [date]
If you'd like to make changes to your subscription, I can help with that too.
Technical Issue
Hi [Name],
I understand you're experiencing [issue]. Let me help troubleshoot.
First, can you confirm:
1. [Specific question 1]
2. [Specific question 2]
3. Any error messages you're seeing?
In the meantime, you can try:
- [Quick fix option 1]
- [Quick fix option 2]
This will help me identify the root cause faster.
Escalation Criteria
Escalate Immediately
- Security concerns (account compromise, data breach)
- Legal or compliance issues
- Threats or harassment
- Executive escalation requests
- System-wide outages
Escalate After First Attempt
- Issue persists after standard troubleshooting
- Customer requests supervisor
- Refund/credit requests above threshold
- Complex billing disputes
- Technical issues requiring engineering
Document Before Escalating
- Customer information
- Issue summary
- Steps already taken
- Customer's desired outcome
- Urgency level
Response Time SLA
| Channel | First Response | Resolution Target |
|---|---|---|
| Chat | 2 minutes | 15 minutes |
| 4 hours | 24 hours | |
| Phone | Immediate | 10 minutes |
| Social | 1 hour | 4 hours |
Closing Interactions
Resolved
I'm glad I could help! Is there anything else I can assist you with today?
[If no] Have a great day!
Pending Resolution
I've [action taken]. You should see [expected outcome] within [timeframe].
I'll follow up with you [when] to make sure everything is working.
Escalated
I've escalated this to our [team name] team. They'll reach out within [timeframe].
Your reference number is [ticket ID]. You can reply to this thread for updates.
FAQ
What does customer-support do?
Guidelines for handling customer support interactions. Use when responding to user inquiries, troubleshooting issues, or escalating problems.
When should I use customer-support?
Use it when you need a repeatable workflow that produces text report.
What does customer-support output?
In the evaluated run it produced text report.
How do I install or invoke customer-support?
Ask the agent to use this skill when the task matches its documented workflow.
Which agents does customer-support support?
Agent support is inferred from the source, but not explicitly declared.
What tools, channels, or permissions does customer-support need?
It uses no extra tools; channels commonly include text; permissions include no explicit permission scopes.
Is customer-support safe to install?
Static analysis marked this skill as low risk; review side effects and permissions before enabling it.
How is customer-support different from an MCP or plugin?
A skill packages instructions and workflow conventions; tools, MCP servers, and plugins are dependencies the skill may call during execution.
Does customer-support outperform not using a skill?
About customer-support
When to use customer-support
Drafting replies to customer questions or complaints. Handling routine troubleshooting conversations. Deciding whether an issue should be escalated.
When customer-support is not the right choice
When the task requires direct integration with ticketing, chat, or CRM systems. When you need to perform account changes, refunds, or other operational actions directly.
What it produces
Produces text report.