Escalation

Use to define incident tiers, response protocols, and stakeholder communications.

Published by @gtmagents·from gtmagents/gtm-agents·0 agent reads / 30d·0 saves·

Community Escalation Framework Skill

When to Use

  • Preparing moderators for sensitive situations (security issues, harassment, outages, leaks).
  • Coordinating cross-functional response when community incidents impact customers or brand.
  • Reviewing past incidents to tighten governance and tooling.

Framework

  1. Tiering – classify incidents (info request, policy violation, critical escalation) with examples.
  2. Ownership – map responders per tier (moderators, comms, legal, security, exec sponsor).
  3. Response Playbooks – outline steps, messaging, approvals, and timelines per tier.
  4. Tooling & Evidence – define logging requirements, screenshots, data retention, and ticketing.
  5. Post-incident Review – document root cause, remediation, and preventive actions.

Templates

  • Escalation matrix (tier → trigger → primary owner → backup → SLA).
  • Incident log form with fields for context, actions, and status.
  • Postmortem template (summary, timeline, impact, actions, follow-ups).

Tips

  • Tie escalation flows into community-ops automation for faster routing.
  • Keep response macros ready for common issues to ensure consistent tone.
  • Conduct quarterly tabletop exercises to keep responders aligned.

More on the bench

SKILL0

Ticket Triage

Triage and prioritize a support ticket or customer issue. Use when a new ticket comes in and needs categorization, assigning P1-P4 priority, deciding which team should handle it, or checking whether it's a duplicate or known issue before routing.

customer-success+2
32
SKILL0

Onboarding Playbook

Design customer onboarding playbooks with milestone tracking, training plans, health checks, and success criteria

customer-success+1
31
SKILL0

Launch Readiness

Assesses pre-launch readiness across every function and produces an explicit Go / Conditional Go / No-Go recommendation. Use when preparing for any product or feature launch, running a pre-launch review, or determining whether a release is safe to ship. Produces a function-by-function readiness status, a ranked blockers list with owners and deadlines, a risk register, and a clearly reasoned launch recommendation.

product-management+2
31