Touches per Ticket
Also known as: Interactions per Ticket, Replies per Ticket, Ticket Touches
Touches per Ticket measures the average number of interactions or exchanges required to resolve a support ticket. Fewer touches generally indicate more efficient resolution, while many touches may signal complex issues or ineffective communication.
Why Touches per Ticket Matters
This metric helps you:
- Assess efficiency — Are issues being resolved quickly?
- Identify complexity — Which categories require more back-and-forth?
- Improve FCR — High touches indicate missed first-contact resolution opportunities
- Reduce effort — Both customer and agent effort increase with each touch
How to Calculate Touches per Ticket
Average Touches = Total Interactions / Number of Tickets Resolved
An “interaction” or “touch” typically includes:
- Agent replies
- Customer responses
- Internal notes (sometimes)
- Phone calls or chats
Interpreting Touches
| Touches | Interpretation |
|---|---|
| 1-2 | Excellent efficiency or simple issues |
| 3-4 | Typical for moderate complexity |
| 5-7 | Complex issues or communication gaps |
| 8+ | Investigate for systemic issues |
Factors Increasing Touches
Issue-related: - Complex technical problems - Multi-step processes - Dependencies on external teams
Process-related: - Poor initial information gathering - Unclear communication - Missing knowledge or documentation - Ticket routing issues
Reducing Touches per Ticket
Strategies for more efficient resolution:
- Complete information — Gather all details upfront
- Thorough responses — Answer potential follow-up questions proactively
- Clear communication — Avoid jargon and confusion
- Templates — Use proven response formats
- Empowerment — Let agents resolve issues without handoffs
Touch Analysis in TicketBoard
TicketBoard helps you understand ticket efficiency through:
- Reply count tracking
- Reopen analysis (reopens add touches)
- Resolution time correlation