120 customer service performance review phrases
Three phrases for each competency and rating, from Outstanding (5) to Unsatisfactory (1). Replace [Name] with the agent's name. Phrases for ratings 1 and 2 include a concrete goal: adjust the numbers and dates to your own targets.
Customer empathy & tone review phrases
5. Outstanding
- [Name] consistently makes customers feel heard, acknowledging their frustration before moving to the fix and adapting tone to each person.
- [Name] handles upset customers with calm and genuine warmth, and often turns a complaint into a thank-you by the end of the conversation.
- [Name] sets the standard for tone on the team: their replies are regularly shared as examples of empathy done well.
4. Exceeds expectations
- [Name] shows real empathy in difficult conversations and keeps a friendly, professional tone even under pressure.
- [Name] regularly acknowledges how the customer feels before explaining the solution, which keeps conversations constructive.
- [Name] adapts tone well to most customers; with a little more personalisation in routine replies, this would be a role-model strength.
3. Meets expectations
- [Name] is polite and professional with customers and acknowledges their concerns in most interactions.
- [Name] keeps a steady, respectful tone; in tense conversations there is room to slow down and acknowledge the customer's feelings more explicitly.
- [Name] meets the tone standard; adding a short personal touch instead of relying on standard wording would lift the customer experience further.
2. Needs improvement
- [Name] is courteous, but replies can come across as rushed or scripted. Goal: open every complaint with a sentence that acknowledges the customer's situation, checked in the next four QA reviews.
- [Name] sometimes moves to the solution before the customer feels heard. Goal: use one acknowledgement phrase per interaction and review two recorded calls with the team lead each month.
- [Name]'s tone becomes short when conversations get tense. Goal: complete the de-escalation training this quarter and apply its steps in every escalated case.
1. Unsatisfactory
- [Name]'s tone has led to customer complaints this period, which is below the expected standard. Goal: no tone-related complaints next period, supported by weekly call reviews with the team lead.
- [Name] rarely acknowledges the customer's frustration and replies often read as dismissive. Goal: pass the empathy line on the QA scorecard in at least 8 of 10 reviewed interactions within 60 days.
- [Name] needs to show more patience and respect in difficult conversations. Goal: shadow a senior agent for two sessions, then apply an agreed tone checklist to every reply for the next 30 days.
Problem solving & accuracy review phrases
5. Outstanding
- [Name] gets to the root cause quickly and resolves complex issues on the first contact, rarely needing to escalate.
- [Name] gives accurate, complete answers and anticipates the customer's next question before it is asked.
- [Name] is the person colleagues turn to for tricky cases, and their fixes are thorough enough that customers seldom need to come back.
4. Exceeds expectations
- [Name] solves most issues on the first contact and checks facts before replying, so answers are rarely wrong.
- [Name] asks the right questions to understand the full problem and follows through until it is resolved.
- [Name] handles non-standard cases with good judgement and escalates only when it is truly needed.
3. Meets expectations
- [Name] resolves routine issues accurately and follows the agreed process.
- [Name] gives correct answers in most cases; on less common issues, checking the knowledge base before escalating would raise first contact resolution.
- [Name] reaches a solution reliably; asking one more clarifying question at the start would help avoid repeat contacts.
2. Needs improvement
- [Name] sometimes gives incomplete answers that lead to repeat contacts. Goal: confirm the full issue back to the customer before replying, and reduce repeat contacts on their cases over the next quarter.
- [Name] escalates issues that could be solved at the first level. Goal: check the knowledge base and a peer before escalating, and cut avoidable escalations in half within 90 days.
- [Name]'s answers occasionally contain errors that need a follow-up. Goal: use an accuracy checklist on every case for 30 days and pass the accuracy line in every QA review.
1. Unsatisfactory
- [Name] frequently gives wrong or incomplete answers, which creates rework for the team. Goal: zero accuracy auto-fails in QA over the next 60 days, with a weekly case review with the team lead.
- [Name] often misses the real cause of the issue and closes cases that are not resolved. Goal: follow the troubleshooting guide step by step and have no more than one reopened case per week next period.
- [Name] needs significant support to solve standard issues. Goal: complete the core troubleshooting training within 30 days and handle the top five contact reasons without escalation by the end of the quarter.
Product knowledge review phrases
5. Outstanding
- [Name] has deep, up-to-date knowledge of the product and explains even complex features in simple terms.
- [Name] learns new releases quickly and regularly spots gaps or errors in the knowledge base, then helps fix them.
- [Name] is a trusted product expert on the team and confidently handles questions that usually need a specialist.
4. Exceeds expectations
- [Name] knows the product well and answers most questions without needing to look things up.
- [Name] keeps up with product changes and applies new information quickly in customer conversations.
- [Name] has strong product knowledge; going deeper into the most complex product areas would make them a go-to expert.
3. Meets expectations
- [Name] has solid knowledge of the core product and uses the knowledge base well for less common questions.
- [Name] keeps up with the main product updates and gives correct information on standard topics.
- [Name] knows what is needed for daily work; building knowledge of advanced features would reduce the need for escalations.
2. Needs improvement
- [Name] often needs to check or ask before answering standard product questions. Goal: complete the product training modules for the top three contact reasons within 45 days.
- [Name] is not yet up to date on recent product changes. Goal: read every release note within one week of release and summarise one change at the team meeting each month.
- [Name]'s product knowledge gaps slow down resolution. Goal: pass the internal product quiz with at least 80% by the end of next quarter.
1. Unsatisfactory
- [Name] lacks the product knowledge the role needs, which leads to wrong answers and escalations. Goal: repeat the full product onboarding within 30 days, with a knowledge check at the end.
- [Name] relies on colleagues for most product questions. Goal: answer the top ten contact reasons independently, verified in a session with the team lead within 60 days.
- [Name] does not yet use the knowledge base consistently. Goal: link the relevant article in every case note for the next 30 days and review gaps weekly with a mentor.
Productivity (volume, handle time) review phrases
5. Outstanding
- [Name] handles a high volume of contacts while keeping quality high, and consistently exceeds the productivity target.
- [Name] manages time very well, keeps handle time efficient without rushing customers, and helps clear the backlog at peak times.
- [Name] finds smarter ways to work, such as saved replies and better tagging, and shares them so the whole team moves faster.
4. Exceeds expectations
- [Name] regularly exceeds the volume target and keeps handle time within the expected range.
- [Name] works efficiently and prioritises the queue well during busy periods.
- [Name] is productive and dependable; their output stays strong even on high-volume days.
3. Meets expectations
- [Name] meets the productivity target and keeps handle time within the team range.
- [Name] handles the expected volume of contacts and keeps the queue moving.
- [Name] meets volume expectations; using saved replies and shortcuts more would free up time for complex cases.
2. Needs improvement
- [Name] is below the volume target for most of the period. Goal: reach the team target within 60 days, with a weekly check-in on handle time and after-contact work.
- [Name]'s handle time is above the team range, often because of long after-contact work. Goal: bring average handle time within the team range by the end of next quarter.
- [Name] sometimes leaves cases idle while working on others. Goal: follow the queue priority rules and keep no case idle beyond the agreed response time for the next 30 days.
1. Unsatisfactory
- [Name]'s output is well below the expected level, which adds pressure on the rest of the team. Goal: reach at least 80% of the volume target within 30 days and 100% within 90 days.
- [Name] spends much longer than expected on routine contacts. Goal: work through a handle-time plan with the team lead and review progress every week for the next two months.
- [Name] does not yet manage time in a way that meets the role's needs. Goal: agree a daily plan for queue work and breaks, and meet the volume target on at least four days a week next period.
Quality (QA score) review phrases
5. Outstanding
- [Name] delivers excellent quality on every channel, with QA reviews that rarely find anything to correct.
- [Name] follows process and documentation standards to the letter, which makes their cases easy for anyone to pick up.
- [Name]'s work is used as a calibration example for the team's QA reviews.
4. Exceeds expectations
- [Name] scores well in QA reviews and acts quickly on the feedback they receive.
- [Name] produces accurate, well-documented work with only minor points to improve.
- [Name] keeps quality high and consistent across contact types.
3. Meets expectations
- [Name] meets the quality standard and follows the main process steps.
- [Name]'s QA results are steady; more consistent case notes would lift the score further.
- [Name] meets expectations on quality; the main area to watch is the lowest-scoring line on the QA scorecard.
2. Needs improvement
- [Name]'s QA results are below the standard, mostly on documentation and process steps. Goal: reach the team QA target within 60 days, with two coaching sessions on the lowest scorecard lines.
- [Name] repeats the same QA findings from review to review. Goal: keep a personal checklist for the top two findings and remove them from reviews by the end of next quarter.
- [Name] sometimes skips required steps such as tagging or identity checks. Goal: pass every compliance line in QA for the next eight reviews.
1. Unsatisfactory
- [Name]'s quality is well below the standard, with auto-fail findings this period. Goal: no auto-fails and a QA average at or above target within 90 days, with weekly reviews.
- [Name] does not yet follow the core process steps consistently. Goal: complete process refresher training within 30 days and pass the next four QA reviews.
- [Name]'s work often needs correcting by colleagues. Goal: reduce corrected or reopened cases to no more than one per week by the end of next period.
Communication (written & verbal) review phrases
5. Outstanding
- [Name] writes and speaks with exceptional clarity, so customers understand the answer the first time.
- [Name] adjusts style to each customer and channel, from short chat replies to detailed emails.
- [Name]'s written replies are clear, well-structured and free of errors, and are often reused as templates by the team.
4. Exceeds expectations
- [Name] communicates clearly and confidently, and explains technical topics in plain words.
- [Name]'s replies are well-structured and easy to follow, with very few errors.
- [Name] keeps customers informed about next steps and timing, which reduces follow-up questions.
3. Meets expectations
- [Name] communicates clearly in most interactions and uses correct spelling and grammar.
- [Name]'s explanations are accurate; shorter sentences and clearer next steps would make them even easier to follow.
- [Name] meets the communication standard; using less internal jargon with customers would help further.
2. Needs improvement
- [Name]'s replies are sometimes long or unclear, which leads to follow-up questions. Goal: keep one topic per paragraph and end with a clear next step, reviewed in four emails per month.
- [Name]'s written replies contain frequent spelling and grammar errors. Goal: use a spell-checker on every reply and have no language findings in QA for the next 60 days.
- [Name] does not always set clear expectations about next steps. Goal: end every interaction with what happens next and when, checked in the next QA reviews.
1. Unsatisfactory
- [Name]'s communication is often unclear or wrong for the channel, which causes confusion and complaints. Goal: complete written communication training within 30 days and pass the communication line in 8 of 10 reviews.
- [Name] frequently uses internal jargon or incomplete explanations. Goal: rewrite five past replies with the team lead and apply a plain-language checklist to every reply for the next month.
- [Name] rarely confirms that the customer has understood the answer. Goal: confirm understanding before closing in every interaction, checked weekly for the next 60 days.
Teamwork & knowledge sharing review phrases
5. Outstanding
- [Name] is a generous team player who shares knowledge freely and helps colleagues without being asked.
- [Name] helps onboard new team members and turns their own know-how into knowledge base articles.
- [Name] lifts the whole team: they share solutions in the team channel, volunteer at peak times and give helpful, kind feedback.
4. Exceeds expectations
- [Name] works well with others, shares useful tips and steps in to help during busy periods.
- [Name] contributes actively in team meetings and is happy to help colleagues with difficult cases.
- [Name] collaborates well with other departments and passes on what they learn to the team.
3. Meets expectations
- [Name] works well with colleagues and supports the team when asked.
- [Name] is a reliable, respectful team member; sharing solutions more often would help others learn from their experience.
- [Name] meets expectations on teamwork; writing up one useful fix per month for the knowledge base would be a good next step.
2. Needs improvement
- [Name] tends to work in isolation and rarely shares what they learn. Goal: share one solution or tip in the team channel each week for the next quarter.
- [Name] sometimes hands off cases without enough context for the next person. Goal: use the handover template on every transferred case for the next 60 days.
- [Name] seldom takes part in team discussions. Goal: bring one case or idea to each team meeting next quarter.
1. Unsatisfactory
- [Name]'s behaviour has caused friction with colleagues this period. Goal: agree working norms with the team lead within two weeks and review them in each 1:1 for the next quarter.
- [Name] does not yet support colleagues or share knowledge, which puts extra load on others. Goal: take part in the team's peer-help rota at least once a week for the next 60 days.
- [Name] often leaves shared tasks to others. Goal: take ownership of one agreed team task per month and report progress in team meetings.
Reliability (schedule adherence, attendance) review phrases
5. Outstanding
- [Name] is fully dependable: always on time, follows the schedule closely and is ready to help when cover is needed.
- [Name] plans time off well in advance and keeps schedule adherence at an excellent level.
- [Name] can be counted on in any situation, including peak days and last-minute changes.
4. Exceeds expectations
- [Name] is punctual and reliable, with very few schedule deviations.
- [Name] follows the schedule well and communicates early when something changes.
- [Name] keeps commitments and can be relied on to complete what they start.
3. Meets expectations
- [Name] meets attendance and schedule expectations.
- [Name] is generally on time and takes breaks and lunch as planned.
- [Name] meets the adherence standard; logging in a few minutes before shift start would avoid occasional late starts.
2. Needs improvement
- [Name] has had several late starts and long breaks this period. Goal: reach the team schedule adherence target within 60 days, tracked weekly.
- [Name] does not always tell the team lead about changes in time. Goal: report any absence or delay before shift start, every time, for the next quarter.
- [Name]'s adherence drops at certain times of day. Goal: agree a plan for breaks and offline work, and reach the adherence target each week for the next two months.
1. Unsatisfactory
- [Name]'s attendance and punctuality are well below the standard and affect team coverage. Goal: no unplanned absences without notice and adherence at target within 60 days, reviewed weekly.
- [Name] often misses scheduled shifts or arrives late. Goal: follow the attendance policy in full for the next 90 days, with a check-in every two weeks.
- [Name] cannot yet be relied on to keep commitments. Goal: complete every agreed task by its deadline for the next 60 days, with a weekly progress check.
How to write a fair customer service review
- Start from evidence, not memory: QA reviews, CSAT, first contact resolution, schedule adherence and a few real tickets or calls from the whole period, not just the last month.
- Use the same scale and the same definitions for every agent, so two people with the same results get the same rating.
- Back every comment with one example: what the agent did, when, and what it changed for the customer or the team.
- Read metrics in context. A hard queue, a product outage or a small sample can move a number without any change in the agent's work.
- Keep areas to develop to one or two, each with a measurable goal, the support you will give and a check-in date.
- Share the draft in a 1:1, listen to the agent's view, and adjust the text where they bring facts you did not have.
Example: a finished review
Example only: Maya is a fictional agent and the ratings below are made up to show the format the generator produces. No metrics were entered, so none are quoted.
Performance review: Maya Review period: Q3 2026 Overall rating: 3.6 / 5 (Exceeds expectations) Summary Maya is rated "Exceeds expectations" overall for Q3 2026, with an average of 3.6 out of 5 across eight competencies. The clearest strengths are teamwork and knowledge sharing, customer empathy and tone and problem solving and accuracy. The main focus for the next period is reliability. Strengths - Teamwork & knowledge sharing (5/5, Outstanding) - Customer empathy & tone (4/5, Exceeds expectations) - Problem solving & accuracy (4/5, Exceeds expectations) - Quality (QA score) (4/5, Exceeds expectations) - Communication (written & verbal) (4/5, Exceeds expectations) Areas to develop - Reliability (schedule adherence, attendance) (2/5, Needs improvement) Comments by competency Customer empathy & tone (4/5, Exceeds expectations): Maya shows real empathy in difficult conversations and keeps a friendly, professional tone even under pressure. Problem solving & accuracy (4/5, Exceeds expectations): Maya solves most issues on the first contact and checks facts before replying, so answers are rarely wrong. Product knowledge (3/5, Meets expectations): Maya has solid knowledge of the core product and uses the knowledge base well for less common questions. Productivity (volume, handle time) (3/5, Meets expectations): Maya meets the productivity target and keeps handle time within the team range. Quality (QA score) (4/5, Exceeds expectations): Maya scores well in QA reviews and acts quickly on the feedback they receive. Communication (written & verbal) (4/5, Exceeds expectations): Maya communicates clearly and confidently, and explains technical topics in plain words. Teamwork & knowledge sharing (5/5, Outstanding): Maya is a generous team player who shares knowledge freely and helps colleagues without being asked. Reliability (schedule adherence, attendance) (2/5, Needs improvement): Maya has had several late starts and long breaks this period. Goal: reach the team schedule adherence target within 60 days, tracked weekly. Goals for the next period 1. Reliability (schedule adherence, attendance): Reach the team schedule adherence target every week for the next 8 weeks, tracked in the weekly 1:1. 2. Product knowledge: Complete the product training for the top three contact reasons and pass the knowledge check with at least 80% within 60 days. 3. Productivity (volume, handle time): Reach the team volume target and keep average handle time within the team range for four weeks in a row during the next quarter.
How to use the generator
- Type the agent's first name and the review period. Without a name, the text says "the agent".
- Rate the eight competencies from 1 to 5. The overall rating is their average, shown with one decimal and the nearest label.
- Add CSAT, QA score, first contact resolution or schedule adherence if you have reliable figures: the matching comments and goals will quote them.
- Click "Another phrase" on any competency, or Shuffle for all, until the wording fits. Then edit the full text in the box.
- Copy the review into your HR system, or download it as CSV, a printable page with signature lines, or Excel with the phrase bank.
Limits of review phrases
These phrases are a starting point, not a verdict. A review must describe behaviour you actually observed, so change any sentence that does not match what the agent did, and add your own examples. Follow your company's HR policy on rating scales, weighting, calibration and how reviews are shared and stored. For the numbers behind the review, use the QA score calculator and the schedule adherence calculator, and judge an agent on the whole period, never on one interaction.
Frequently asked questions
- What are good performance review phrases for customer service?
- Good phrases name one specific behaviour and its effect on customers or the team, for example 'acknowledges the customer's frustration before explaining the fix, which keeps conversations constructive'. Avoid vague words like 'great attitude'. For lower ratings, add a concrete goal with a number and a date so the agent knows exactly what to change.
- How do you write a performance review for a customer service representative?
- Gather evidence first: QA reviews, CSAT, first contact resolution, schedule adherence and two or three real interactions. Rate each competency on the same scale, write one comment per competency backed by that evidence, summarise strengths and areas to develop, and close with two or three SMART goals for the next period.
- What should I write in the areas for improvement section?
- Describe the behaviour, not the person: what happened, how often, and what it caused (repeat contacts, complaints, extra work for the team). Then give one measurable goal, the support you will provide (coaching, training, call reviews) and when you will check progress. One or two clear areas work better than a long list.
- Should I include metrics like CSAT and QA score in a review?
- Yes, when they are reliable and the agent knows how they are measured. Metrics make a review fairer and easier to discuss, but read them in context: a small sample, a hard queue or a product issue can move CSAT without any change in the agent's work. Pair each figure with an observed example.
- How do you calculate an overall rating on a 1 to 5 scale?
- The simplest method is the average of the competency ratings, shown with one decimal and rounded to the nearest label (for example 3.6 rounds to 4, Exceeds expectations). Some companies weight competencies such as quality or reliability more heavily; if yours does, follow that policy instead of a plain average.
Related
About the author
Abdessamad Ghanem
Customer Experience & Customer Success Consultant · Founder of Clarivoxx
Abdessamad Ghanem works across Customer Support, Sales, Customer Success, Account Management and Partner Management. He writes Clarivoxx Insights for B2B SaaS professionals who own retention, adoption and customer outcomes.