Free template · Sales / CS
Performance review template for a support / service manager
A ready-to-use, section-by-section template with the competencies that matter for a support / service manager, role-specific example phrases, and a guard against the stock filler that makes most reviews read as generic. Copy the structure, fill in your evidence, or skip the writing entirely with Crestento.
The template
Four sections, in this order. Length should match the evidence you have — a thin section is honest; an invented paragraph is not.
Summary
One or two paragraphs setting the context: what was expected of support / service manager this period, and your overall verdict. Lead with the headline.
Example phrasing
“Team SLA adherence held at 96% through a 35% volume increase, ramped two new reps off cycle without missing tier-1 metrics, and stood up the weekly product-feedback digest now used by Engineering.”
Strengths
The behaviours and outcomes that made the work happen. Anchor in evidence: team SLA adherence rate, first-contact resolution at team level, average ticket handle time (with quality context).
- Evidence for: team SLA performance and queue health.
- Evidence for: rep coaching and tier-progression development.
- Evidence for: hiring, ramping, and rep retention.
- Evidence for: process and workflow improvement.
Areas for Growth
Forward-looking development edges. Frame as opportunities, not deficiencies. Specific behaviours to develop, not generic support / service manager criticism.
- One pattern observed across the period.
- One specific behaviour to develop.
- One concrete next step.
Goals for the Next Period
Two or three concrete goals. Each should name a specific behaviour change, a measurable target, and a deadline. Avoid vague aspirations.
Competencies to evaluate
The 7 competencies a strong support / service manager review structures around, in priority order. Use these as the spine of the Strengths and Areas for Growth sections.
- team SLA performance and queue health
- rep coaching and tier-progression development
- hiring, ramping, and rep retention
- process and workflow improvement
- cross-functional partnership (engineering, product)
- voice-of-customer reporting and product feedback
- tooling and knowledge-base ownership
Before you write
Support managers are evaluated on three things at once: the team's SLA and quality numbers, the rate at which reps develop into tier-2 and tier-3, and the upstream feedback loop into Engineering and Product. The dashboard tells you SLAs. The harder work — coaching individual reps, improving workflows that compound over time, surfacing the right product signal to Engineering — is mostly invisible to the dashboard but is what makes a strong support manager.
Evidence to gather
Strong reviews for a support / service manager cite evidence of these shapes. Only use a specific value (a percentage, a count, a dollar amount) if you actually have it — don’t invent a number to sound concrete.
- team SLA adherence rate
- first-contact resolution at team level
- average ticket handle time (with quality context)
- rep retention rate and tier-progression count
- CSAT trend at team level
- escalation rate to engineering / specialist
- backlog and queue-health trend
Where to find the evidence
Work products a support / service manager produces. Reference these by name in the review when they’re relevant — it signals you know the work.
- weekly queue review and SLA report
- rep development plans
- process improvement docs and rollout plans
- voice-of-customer / product-feedback digest
- team training materials and knowledge-base curation
- escalation playbooks
Phrasing that lands vs phrasing that doesn’t
Strong — specific, evidenced, role-appropriate
“Team SLA adherence held at 96% through a 35% volume increase, ramped two new reps off cycle without missing tier-1 metrics, and stood up the weekly product-feedback digest now used by Engineering.”
Weak — vague, unevidenced, generic
“Strong support leader.”
Phrases to never use
Stock filler that AI-written support / service manager reviews slip into. Managers spot it instantly. Rewrite to name a specific behaviour instead.
- “strong support leader”
- “builds great team culture”
- “drives customer satisfaction”
- “passionate about customer experience”
- “consistently leads by example”
- “trusted by the team”
Don’t invent these specifics
The details an AI tends to fabricate for support / service managerreviews. If you don’t have the specific number, name, or date in your notes, leave it out — generic-but-honest beats specific-but- invented every time.
- specific SLA percentages not in input
- team CSAT or retention values not provided
- specific volume increase numbers not mentioned
- named reps developed when only counts were given
- particular product-feedback initiatives not in input
- specific tooling implementations not referenced
Skip the template, generate the review
Drop your bullet points into Crestento and it produces the polished draft using this exact template structure, tuned for a support / service manager. Two reviews free, no card.
Try Crestento free