Playbook: Troubleshooting a Support Ticket
This workflow covers how to efficiently investigate and resolve a support ticket.
Step 1: Read and Classify
- Read the ticket description carefully — understand what the customer is reporting
- Set the priority based on impact (Critical → Low)
- Assign to yourself or the most appropriate team member
- Set status to In Progress
Step 2: Reproduce the Issue
- Navigate to Gyms → [Affected Gym]
- Click Enter Gym to see exactly what the customer sees
- Navigate to the page/feature mentioned in the ticket
- Try to reproduce the reported issue
- Add an internal note documenting what you found
Step 3: Diagnose
Common issues and where to look:
| Symptom | Check |
|---|---|
| "Feature not available" | Plan tier → Feature flags → Gym overrides → User role |
| "Payments not working" | Stripe connection → Payment method → Stripe dashboard |
| "Emails not sending" | Automation status → Email template exists → Sender domain → Error log |
| "Members missing" | Import status → Filter settings → Membership status |
| "Schedule issues" | Recurring class config → Coach assignment → Date range |
| "Can't log in" | Account status → Email verification → Password reset |
Step 4: Resolve and Communicate
- Fix the issue (if it's a configuration problem you can fix) or escalate (if it's a bug)
- Reply to the customer explaining what happened and what was done
- Link to relevant KB articles for self-service in the future
- Set status to Resolved — this triggers the "Support Ticket Resolved" automation email
Step 5: Document
- If the issue reveals a product gap, create an Ideas entry
- If the issue is common, consider writing or updating a KB article
- If the issue was caused by a bug, ensure it's tracked in the development workflow