escalation-workflow
Automated escalation path determination and workflow execution
What this skill does
# Escalation Workflow Skill
## Overview
The Escalation Workflow skill provides automated escalation path determination, notification generation, and workflow execution for support and customer success operations. This skill ensures that complex or high-priority issues are routed to appropriate escalation tiers with proper documentation, tracking, and SLA monitoring.
## Capabilities
### Escalation Level Determination
- Evaluate issue severity and impact
- Apply escalation rules and criteria
- Determine appropriate escalation tier
- Consider customer segment and priority
- Factor in historical escalation patterns
- Calculate escalation urgency scores
### Notification Generation
- Generate escalation alerts to relevant parties
- Create escalation handoff documentation
- Produce management notification summaries
- Send customer escalation confirmations
- Trigger on-call and pager integrations
- Compose executive briefing communications
### Progress and Aging Tracking
- Track escalation progress through stages
- Monitor escalation age and elapsed time
- Generate aging alerts and reminders
- Track owner assignments and transitions
- Maintain escalation audit trails
- Report on stuck or stalled escalations
### Escalation Metrics Calculation
- Calculate escalation rates by category
- Measure mean time to escalation resolution
- Track escalation volume trends
- Analyze escalation causes and patterns
- Generate escalation performance dashboards
- Benchmark against escalation targets
### Handoff Documentation
- Generate structured handoff briefs
- Document troubleshooting steps completed
- Capture customer communication history
- Compile relevant technical details
- Include reproduction steps and evidence
- Create executive summary for stakeholders
### SLA Monitoring
- Track escalation-specific SLAs
- Generate SLA breach warnings
- Monitor response time compliance
- Calculate time remaining to breach
- Trigger escalation for SLA risks
- Report SLA performance by tier
### De-escalation Support
- Generate de-escalation recommendations
- Track resolution criteria completion
- Document de-escalation decisions
- Notify stakeholders of de-escalation
- Archive escalation records
- Update customer on resolution
## Usage
### Determine Escalation Level
```yaml
skill: escalation-workflow
action: determine-escalation
parameters:
issue:
id: "TICKET-12345"
severity: high
impact: multiple_customers
duration_hours: 4
current_tier: 1
customer:
segment: enterprise
health_score: 45
contract_value: 500000
context:
previous_escalations: 2
customer_sentiment: frustrated
```
### Generate Escalation Notification
```yaml
skill: escalation-workflow
action: generate-notification
parameters:
escalation_id: "ESC-2025-001"
notification_type: tier2_handoff
recipients:
- role: tier2_lead
- role: account_csm
- role: support_manager
include:
- issue_summary
- customer_context
- troubleshooting_history
- recommended_actions
urgency: high
```
### Track Escalation Progress
```yaml
skill: escalation-workflow
action: track-progress
parameters:
escalation_id: "ESC-2025-001"
update:
status: in_progress
owner: "[email protected]"
actions_taken:
- "Reviewed logs and identified memory leak"
- "Applied temporary workaround"
next_steps: "Deploy patch in next maintenance window"
estimated_resolution: "2025-01-25T10:00:00Z"
```
### Calculate Escalation Metrics
```yaml
skill: escalation-workflow
action: calculate-metrics
parameters:
date_range:
start: "2025-01-01"
end: "2025-01-31"
dimensions:
- escalation_tier
- issue_category
- customer_segment
metrics:
- escalation_count
- mttr_escalations
- escalation_rate
- sla_compliance
```
### Generate De-escalation Recommendation
```yaml
skill: escalation-workflow
action: recommend-deescalation
parameters:
escalation_id: "ESC-2025-001"
resolution:
root_cause: "Memory leak in v2.3.4"
fix_applied: "Patch deployed v2.3.5"
customer_confirmation: true
monitoring_period_complete: true
recommendation:
action: de-escalate
rationale: "Issue resolved, customer confirmed, stable for 48 hours"
```
## Process Integration
This skill integrates with the following customer experience processes:
| Process | Integration Points |
|---------|-------------------|
| escalation-management.js | Core escalation workflow, tier routing, stakeholder notification |
| itil-incident-management.js | Major incident escalation, P1 workflows, bridge management |
| ticket-triage-routing.js | Initial escalation triggers, priority-based escalation |
| sla-management.js | SLA breach escalation, response time alerts, compliance tracking |
## Escalation Tier Model
The skill supports configurable escalation tier models:
| Tier | Criteria | Response Target | Stakeholders |
|------|----------|-----------------|--------------|
| Tier 1 | Standard issues | 4 hours | Support Agent |
| Tier 2 | Complex technical | 2 hours | Senior Engineer |
| Tier 3 | Critical/Multi-customer | 1 hour | Engineering Lead, CSM |
| Tier 4 | Business critical | 30 minutes | Director, VP, Executive |
## Dependencies
- Escalation rules engine configuration
- Notification system integration (email, Slack, PagerDuty)
- Ticketing system integration for status sync
- On-call schedule access
- Customer segment and priority data
- SLA configuration definitions
## Best Practices
1. **Clear Criteria**: Define explicit escalation criteria to avoid subjective decisions
2. **Documentation**: Ensure thorough handoff documentation at each tier transition
3. **Customer Communication**: Keep customers informed throughout escalation
4. **Root Cause Tracking**: Document root causes to improve future triage
5. **Metrics Review**: Regularly review escalation metrics for process improvement
6. **Runbook Integration**: Link to relevant runbooks and troubleshooting guides
## Shared Potential
This skill has applicability to related domains:
- IT Service Management
- DevOps/SRE Incident Response
- Security Incident Response
- Operations Management
Related in General
modeling-omnistudio-epc-catalog
IncludedSalesforce Industries CME EPC product-modeling skill for Product2-based catalog creation. Use when creating EPC products, configuring product attributes, building offer bundles with Product Child Items, or reviewing EPC DataPack JSON metadata for product catalog changes. TRIGGER when: user creates or updates Product2 EPC records, AttributeAssignment payloads, AttributeMetadata/AttributeDefaultValues, Offer bundles, or ProductChildItem relationships. DO NOT TRIGGER when: designing OmniScripts/FlexCards/Integration Procedures (use building-omnistudio-omniscript, building-omnistudio-flexcard, or building-omnistudio-integration-procedure), implementing Apex business logic (use generating-apex), or troubleshooting deployment pipelines (use deploying-metadata).
relationship-science-coach
IncludedUse this skill for direct, practical adult relationship coaching: couples conflict, repair, trust, marriage, dating, flirting, attachment patterns, emotional connection, sex, desire differences, eroticism, kink negotiation, affection, love languages, breakups, and long-term passion. Draw on Gottman, EFT and Hold Me Tight, attachment science, modern sex research, Perel, Nagoski, Kerner, Schnarch, Love and Stosny, and flexible love-language tools. Be concrete and low-hedge. Redirect only for imminent danger, abuse, coercive control, minors, non-consent, self-harm, stalking, or medical/legal/psychiatric decisions.
building-sf-integrations
IncludedSalesforce integration architecture and runtime plumbing with 120-point scoring. Use this skill to set up Named Credentials, External Credentials, External Services, REST/SOAP callout patterns, Platform Events, and Change Data Capture. TRIGGER when: user sets up Named Credentials, External Services, REST/SOAP callouts, Platform Events, CDC, or touches .namedCredential-meta.xml files. DO NOT TRIGGER when: Connected App/OAuth config (use configuring-connected-apps), Apex-only logic (use generating-apex), or data import/export (use handling-sf-data).
venue-templates
IncludedAccess comprehensive LaTeX templates, formatting requirements, and submission guidelines for major scientific publication venues (Nature, Science, PLOS, IEEE, ACM), academic conferences (NeurIPS, ICML, CVPR, CHI), research posters, and grant proposals (NSF, NIH, DOE, DARPA). This skill should be used when preparing manuscripts for journal submission, conference papers, research posters, or grant proposals and need venue-specific formatting requirements and templates.
let-fate-decide
IncludedDraws the 12 Houses of the Zodiac Tarot spread to inject entropy into planning when prompts are vague, ambiguous, or casually delegated. Interprets the spread to guide next steps. Use when the user says 'let fate decide', 'YOLO', 'whatever', 'idk', or other nonchalant phrases, makes Yu-Gi-Oh references, or when you are about to arbitrarily pick between multiple reasonable approaches. Prefer over ask-questions-if-underspecified when the user's tone is casual or playful rather than precision-seeking.
net-ops
IncludedCross-platform network troubleshooting (Windows, macOS, Linux) via local or remote shell. Use for: DNS broken, can't resolve hostnames, nslookup/dig works but apps fail, NRPT, WFP, scutil, /etc/resolver, systemd-resolved, /etc/resolv.conf, NetworkManager, VPN DNS leak residue (ProtonVPN/Mullvad/WireGuard/AnyConnect), AV/firewall blocking DNS or DoH, Tailscale DNS interaction, intermittent connectivity, remote diagnostics over SSH.