When this skill is activated, always start your first response with the 🧢 emoji.

Customer Support Operations

Customer support operations covers the full support lifecycle - from triage and routing through SLA tracking, escalation, and resolution - plus the operational layer of macros, queue management, VIP handling, and on-call rotations. This skill provides actionable frameworks for each layer: priority matrices, SLA structures by tier and priority, macro libraries, escalation paths, and queue optimization. Built for support leaders moving from reactive firefighting to a measurable, repeatable support machine.

When to use this skill

Trigger this skill when the user:

• Needs to design or improve a ticket triage system or priority matrix
• Wants to define or audit SLAs by customer tier or ticket priority
• Is building or standardizing a macro and response template library
• Needs to design or document escalation workflows and trigger conditions
• Wants to optimize queue management or reduce queue aging
• Is setting up VIP or enterprise support lanes
• Needs to design a support on-call or follow-the-sun rotation
• Is measuring or improving first response time or resolution time

Do NOT trigger this skill for:

• Production incident management or war room coordination (use incident-management skill)
• Writing individual customer replies without a process context (use a writing assistant skill)

Key principles

1. First response time is king - The metric customers feel most is how quickly someone acknowledges their problem. A fast FRT buys goodwill and time. Every SLA must prioritize FRT above all others. Measure it first; everything else is secondary.

2. Triage before solving - An untriaged queue is a random queue. Agents working in random order guarantee high-priority problems wait behind low-priority ones. Triage assigns priority, tier, and routing - it does not solve the problem.

3. Macros save hours, not minutes - One macro used 50 times a day saves 50x the time invested in writing it. Expand the library whenever agents write the same reply more than once a week. Review quarterly. A bad macro is worse than no macro.

4. Escalation paths must be clear - Ambiguous escalation is the leading cause of tickets stalling. Every agent must know, without asking, exactly when and where to escalate. If an agent has to think about whether to escalate, the path is not clear.

5. Measure everything - Support intuition degrades under volume. Track FRT, resolution time, CSAT, first contact resolution rate, escalation rate, and queue age. Review weekly. Data surfaces problems before customers do.

Core concepts

Support tiers

Tier assignment rule: Tier is set at account creation from the billing plan and must trigger automatic re-routing in the ticketing system. Never rely on agents to manually route by tier - automate it.

SLA components

SLA clock rules:

• FRT clock starts immediately on ticket creation, including nights and weekends, unless the tier contract specifies business hours only.
• Clock pauses when a ticket enters "Pending Customer" status (waiting on customer).
• Clock never pauses for internal notes or transfers between agents.

Ticket lifecycle

Submitted -> Triaged -> Assigned -> In Progress -> Pending Customer
                                        |                  |
                                    Escalated          Reopened
                                        |
                                    Resolved -> Closed (auto after 7 days)

Each transition must have a defined owner and time constraint. Tickets sitting in "Triaged" for more than 30 minutes indicate a routing or staffing problem. Tickets in "In Progress" beyond the resolution SLA need a manager flag.

Queue management

Queue states to monitor:

Common tasks

Design a triage system

Priority matrix (impact x urgency):

Priority definitions:

P1 - Critical:  Service down, data loss, security issue, or revenue blocked.
                FRT target: 1 hour. Assign immediately. Page on-call if needed.

P2 - High:      Core feature broken, workaround difficult, or VIP affected.
                FRT target: 4 hours. Pull from queue before P3/P4.

P3 - Normal:    Feature degraded, workaround exists, standard customer.
                FRT target: per tier SLA (8h or 24h).

P4 - Low:       Cosmetic issue, how-to question, feature request.
                FRT target: 48 hours. May be batch-processed.

Triage checklist (run on every new ticket):

1. Assign priority using the matrix above.
2. Confirm customer tier from CRM. Upgrade priority if enterprise.
3. Check for duplicate tickets from the same account - merge if found.
4. Apply tags: product area, issue type, channel source.
5. Route to the correct queue or agent group.
6. Set SLA clock based on tier and priority.

Set up SLAs

SLA matrix by tier and priority:

SLA escalation rules:

• At 75% of FRT window: auto-flag the ticket as "at-risk" in the queue view.
• At 100% of FRT window: alert the team lead via Slack and mark as breached.
• At 150% of FRT window: escalate to support manager, log as SLA violation.

Weekly SLA health report: FRT compliance % per tier (target > 95%), resolution compliance % per tier (target > 90%), breach count by priority, top 5 breach reasons.

Create a macro and template library

Macro taxonomy:

Acknowledgment:
  - First response: issue received
  - First response: investigating
  - First response: needs more info

Status Updates:
  - Update: investigating root cause
  - Update: fix in progress, ETA known
  - Update: fix in progress, ETA unknown
  - Update: escalated to engineering

Resolution:
  - Resolution: issue fixed, steps to verify
  - Resolution: workaround provided
  - Resolution: known issue, linked to status page

Closures:
  - Closing: no response from customer (7 days)
  - Closing: duplicate ticket
  - Closing: feature request logged

VIP and Escalations:
  - VIP: acknowledgment with named CSM
  - Escalation received: enterprise path

Macro quality rules:

• Every macro must have a human-review checkpoint. Never send blind.
• Macros must include placeholder fields for: customer name, product area, ticket number, and agent name.
• Review and update the full library every quarter.
• Retire macros with a < 2% usage ra