Free template · Sales / CS
Performance review template for a customer support representative
A ready-to-use, section-by-section template with the competencies that matter for a customer support representative, 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 customer support representative this period, and your overall verdict. Lead with the headline.
Example phrasing
“Handled 1,840 tickets across the year with median first response under 12 minutes, 71% first-contact resolution against a team target of 65%, and a CSAT of 4.7/5. Authored eight macros that the team adopted across L1.”
Strengths
The behaviours and outcomes that made the work happen. Anchor in evidence: median first-response time, first-contact resolution (FCR) rate, tickets handled per shift / period.
- Evidence for: first-response time and SLA adherence.
- Evidence for: first-contact resolution rate.
- Evidence for: ticket quality (documentation, root-cause clarity).
- Evidence for: CSAT contribution and customer-experience trend.
Areas for Growth
Forward-looking development edges. Frame as opportunities, not deficiencies. Specific behaviours to develop, not generic customer support representative 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 customer support representative review structures around, in priority order. Use these as the spine of the Strengths and Areas for Growth sections.
- first-response time and SLA adherence
- first-contact resolution rate
- ticket quality (documentation, root-cause clarity)
- CSAT contribution and customer-experience trend
- knowledge-base / macro contributions
- escalation calibration to engineering / specialist teams
- queue discipline and workload management
Before you write
Strong support reps are not the ones who close the most tickets. They're the ones who solve the actual problem cleanly the first time, document the resolution so the next rep doesn't have to re-solve, and escalate at the right moment. The ratio of speed-to-resolution-quality is the craft. A review that anchors only on ticket volume misses the rep who's leaning on the team and over-credits ticket-closure speed at the cost of resolution depth.
Evidence to gather
Strong reviews for a customer support representative 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.
- median first-response time
- first-contact resolution (FCR) rate
- tickets handled per shift / period
- CSAT score (with response rate context)
- SLA adherence rate by tier
- escalation rate (and quality of escalations)
- knowledge-base articles / macros authored or updated
Where to find the evidence
Work products a customer support representative produces. Reference these by name in the review when they’re relevant — it signals you know the work.
- ticket-handling notes with root-cause analysis
- knowledge-base articles and macros
- escalation handoff documentation to L2 / engineering
- customer-satisfaction survey follow-ups
- weekly queue review and personal metrics review
- shadow / coaching notes on calls or chats
Phrasing that lands vs phrasing that doesn’t
Strong — specific, evidenced, role-appropriate
“Handled 1,840 tickets across the year with median first response under 12 minutes, 71% first-contact resolution against a team target of 65%, and a CSAT of 4.7/5. Authored eight macros that the team adopted across L1.”
Weak — vague, unevidenced, generic
“Great with customers and resolves tickets quickly.”
Phrases to never use
Stock filler that AI-written customer support representative reviews slip into. Managers spot it instantly. Rewrite to name a specific behaviour instead.
- “great with customers”
- “always goes the extra mile”
- “consistently delivers exceptional customer service”
- “passionate about helping customers”
- “customer-obsessed”
- “lives and breathes support”
- “wears the customer hat”
Don’t invent these specifics
The details an AI tends to fabricate for customer support representativereviews. 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 ticket volumes the manager didn't provide
- FCR or CSAT values not in input
- named customer accounts the rep helped
- specific SLA tiers / response times not mentioned
- named escalation cases not in input
- particular knowledge-base articles not referenced by the manager
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 customer support representative. Two reviews free, no card.
Try Crestento free