What problem does it solve?
Support teams struggle to consistently decide which customer tickets must be escalated to a human before any automated reply is sent, and first replies often use generic apology templates that frustrate customers. This Skill provides clear escalation criteria and tone guidelines for drafting the first customer reply.
Core Features & Use Cases
- Escalation Rules: Sets needs_human_review to true and blocks automated replies for security incidents, data exposure, billing disputes, and legal-risk tickets.
- Urgency Distinction: Clarifies that urgency alone (such as a production outage with a known workaround) does not require human review.
- Reply Tone Guidance: Instructs replies to open with the customer's own framing, state concrete next steps and owners, avoid uncommitted timelines, and match the customer's register.
- Use Case: When drafting a reply to a customer reporting an unauthorized charge, the Skill flags the ticket for human review instead of sending an automated response.
Quick Start
Use the escalation-and-reply-tone skill to review this customer ticket and draft an appropriate first reply or flag it for human review.
