Here's a number most support managers have never calculated: how many hours per week their team spends typing the exact same sentence.
Not similar sentences. The exact same ones. The "thanks for reaching out" opener. The "I've escalated this to our team" mid-ticket message. The "let me know if there's anything else" closer. Every agent writes them. Every day. From scratch.
The math
According to Zendesk's Customer Experience Trends Report, the average support agent handles 35–50 tickets per day depending on the channel. Each ticket involves 2–4 messages. Research from McKinsey estimates that knowledge workers spend 28% of their workday writing and answering emails — a figure that's even higher in customer-facing roles.
Run a simple estimate for a 5-person support team:
- 40 tickets per agent per day × 3 messages per ticket = 120 messages daily
- Average 90 seconds to write each message = 180 minutes of writing per agent
- Industry benchmarks suggest 50–60% of support messages are near-identical across tickets
- That's roughly 90 minutes of avoidable repetitive writing, per agent, every day
Rough estimate
At an average blended hourly cost of $25/hr per agent, 90 minutes of daily repetitive writing across a 5-person team equals roughly $47,000/year in recoverable time — before factoring in slower response times and inconsistent quality.
The three categories of repetitive support messages
1. Acknowledgement messages
These are the openers: confirming receipt, setting response time expectations, thanking the customer for patience. Every agent writes a version of these for every ticket. They should be templates.
2. FAQ responses
Billing questions, password resets, plan comparisons, cancellation policies — a large share of ticket volume is the same 10–15 questions cycling. Superoffice research found that 40% of support teams don't have a knowledge base or templating system at all.
3. Resolution and escalation messages
"We've looked into this and here's what we found" — the structure of these messages is identical across hundreds of tickets. Only the specific detail changes. This is exactly what variables in a snippet library are designed for.
Why teams don't fix it
- Templates live in a Notion doc or Google Sheet — a separate tab from where agents are typing
- Finding the right template takes longer than just typing the message
- Templates go stale and no one maintains them
- No shared ownership means no consistency across agents
The fix has to be inline. The snippet must appear in the same text field where the agent is already working — not in a separate tab.
What a well-structured snippet library looks like
- /ack → acknowledgement with {ticket_id} and {first_name}
- /billing-q → standard billing FAQ response
- /bug-eta → 'we're working on it' with {eta} variable
- /escalate → escalation message with {team} and {timeline}
- /resolve → ticket resolution confirmation
- /csat → post-resolution survey request