escalation-rules

Classify support cases into triage categories and assemble required evidence bundles.

Updated Apr 6, 2026
One-click install
npx skills add https://github.com/cellarwood/figurio --skill escalation-rules
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: escalation-rules
Source: https://github.com/cellarwood/figurio/tree/main/skills/escalation-rules
Command: npx skills add https://github.com/cellarwood/figurio --skill escalation-rules

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Frontline support often lacks a consistent way to decide when a case requires escalation, which owner should receive it, and what information they need to act without re-triage; this Skill provides clear criteria and a required evidence bundle to prevent delays and preserve customer trust.

Core Features & Use Cases

  • Clear escalation criteria for immediate, same-day, and standard handoffs covering safety, shipping failures, damage, refund judgment, fraud risk, and approval conflicts.
  • Triage taxonomy that classifies cases into fulfillment, quality, approval, refunds, or trust so the correct team can own the next action.
  • Required escalation bundle and language guidance to ensure every handoff includes order ID, timeline, evidence, summary, and a concise request, and to protect customer-facing tone.
  • Use Case: When a customer reports a damaged figurine with photos and asks for a refund, use these rules to classify the case as quality/refunds, assemble the required evidence, and route to the financial or production owner with a clear request.

Quick Start

Prepare an escalation: classify the case (fulfillment/quality/approval/refunds/trust), attach order ID, customer contact, timeline, evidence and a one-sentence request for the receiving owner (investigate, approve refund, re-ship, or confirm).

Frequently Asked Questions about escalation-rules

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I decide whether to escalate a customer support case?▼

Evaluate the case against clear escalation criteria covering safety, shipping failures, damaged items, refund judgment, fraud risk, and approval conflicts to determine whether an immediate, same-day, or standard handoff is required.

What information do I need to include when escalating a support ticket?▼

An escalation bundle requires the order ID, customer contact, timeline, evidence, a case summary, and a concise one-sentence request so the receiving owner can act immediately without further re-triage.

How do I triage support cases involving refunds and damaged items?▼

Classify the case using a triage taxonomy into fulfillment, quality, approval, refunds, or trust categories, then route it to the correct team with the required evidence bundle and handoff instructions.

When should I escalate a fraud risk or trust-sensitive customer communication?▼

Escalate fraud risk and trust-sensitive communications immediately to the trust team, as these cases require urgent handoff to prevent security issues and protect overall customer trust.

What is the best way to route a damaged item refund request to the correct owner?▼

Classify the case as quality or refunds, assemble the required evidence bundle including photos and order ID, then route it to the financial or production owner with a clear request to approve the refund or re-ship.

Can I use these escalation rules for custom order approval conflicts?▼

Yes, the escalation criteria cover custom approval conflicts by classifying them under the approval triage category and routing them with the required evidence bundle to the appropriate owner for resolution.