SUPPORT OPERATIONS KNOWLEDGE HUB
Practical guides & playbooks for support teams.
Everything here comes from real rollouts. Select any guide on the left to read the full playbook on the right.
Smart Ticket Triage
In ProgressParsed intent: 'Database Latency'. Assigned High Priority.
SLA Response Timer
Active CountdownResponse due in 14m 30s. Escalation rule active.
Todo Checklist Attached
VerifiedIncident Response Template: 3 of 3 tasks completed.
Resolution Audit Log
ClosedResolution note recorded. CSAT 5.0 ⭐ score received.
Designing your ticket request types
How to structure request types and sub-types so automated routing stays obvious as volume grows.
From shared inbox to tracked queue
A two-week step-by-step migration plan covering intake, ownership rules, and customer communication.
Todo templates that actually get used
Practical checklist patterns for agent onboarding, outage incident response, and returns handling.
Reading your support analytics
Which trends matter most: backlog age, priority mix, first response time, and staff load balance.
Roles and permissions matrix reference
Detailed breakdown of what administrators, managers, and support agents can each see and modify.
Email deliverability for support teams
SMTP configuration best practices, template previews, and reading email logs when pings bounce.
Designing your ticket request types
A clean taxonomy of request categories is the foundation of fast ticket triage. When categories are too granular, customers pick randomly. When too broad, agents waste time reassigning.
1. The 3-Tier Categorization Model
Group incoming requests into broad Parent Categories (e.g. Account & Access, Billing & Invoices, Product Bug, Feature Request) paired with specific Sub-Types.
- Keep top-level categories under 6 items to prevent decision paralysis
- Use mandatory sub-types only when auto-routing rules depend on them
- Avoid ambiguous catch-all labels like 'General Inquiry' or 'Other'
2. Setting Priority Levels Based on Impact
Priority should reflect business impact, not customer emotion. Establish strict thresholds:
- P1 (Urgent): Core application offline or payment gateway down for all users
- P2 (High): Key workflow broken for a business tier client with no workaround
- P3 (Medium): Feature malfunction with viable manual workaround
- P4 (Low): Cosmetic bug or general how-to inquiry
Review your category metrics monthly. Any sub-type receiving less than 2% of total volume should be consolidated.
Built-in Knowledge Base
Your own help center ships out of the box.
Publish categorized articles so customers get instant answers to common questions before opening a ticket.
General
How to raise a support ticket from the portal
General
Understanding ticket statuses and priorities
Accounts
Resetting your customer portal password
Accounts
Adding staff members and assigning roles
Billing
Where to find invoices and receipts
Get started