Top 20 90-Day Goals That Drive Performance

Maintain a CSAT score of 90% or higher across all support interactions for three consecutive months.

Consistency matters more than peaks — one great week means nothing if three bad ones follow.

• Before every customer interaction, take 30 seconds to read the customer's history so you arrive informed, not cold.
• After every interaction below a CSAT of 8, spend five minutes identifying one specific thing you would do differently next time.

Increase your first contact resolution rate to 80% or higher within the next quarter.

Every ticket that requires a follow-up costs twice the time and twice the frustration.

• Before closing any ticket, ask yourself: is there anything else that could bring this customer back for the same issue? Fix it now if so.
• Spend 15 minutes each day reviewing your previous day's resolved tickets and identifying any that might reopen — and why.

Lower the average time to resolve a support interaction by 20% within 90 days through better tooling and sharper diagnostic skills.

Reducing handle time through competence — not cutting corners — creates capacity for more customers without sacrificing care.

• Identify the single type of ticket that takes you longest to resolve each week and spend 20 minutes building or refining a reusable solution for it.
• Before each interaction, spend 60 seconds reviewing your most-used macros and templates — are they still the fastest path to resolution?

Resolve customer issues so completely that no customer needs to contact support again for the same issue within 30 days.

A repeat contact is a signal that the first resolution missed something.

• End every ticket resolution with one question: what else might go wrong for this customer as a result of what brought them here today? Review your reopened tickets each week and identify the single most common reason for reopening — then fix the root cause in your resolution process.

Create and maintain a personal library of 20 detailed, reusable solutions within 90 days.

Documented solutions compound. What takes 20 minutes today becomes a 2-minute reference next month.

• After resolving any ticket that required you to search for a solution, spend five minutes documenting the answer before closing it.
• Review and update two entries in your knowledge base each week — solutions become outdated, and accurate documentation is only useful if it is current.

Receive a score of 9 or 10 from at least 70% of customers who complete a post-interaction NPS survey.

A 9 or 10 means a customer would actively recommend — that is extraordinary in a support context.

• At the end of every interaction, ask yourself: did that customer leave better off than when they arrived? If not, what one thing could have changed it? Once a week, re-read three of your highest-rated interactions and identify the specific behaviours that earned the score — then replicate them deliberately.

Earn a recognised product certification or complete one structured training programme within 90 days.

Deep product knowledge is the single biggest lever on resolution quality.

• Spend 20 minutes each morning — before the queue opens — on your certification or training programme.
• Apply one new piece of product knowledge to a live ticket each day and note whether it improved your resolution speed or quality.

Surface three emerging issues to the product or engineering team within the next quarter.

Support is the earliest warning system in any tech company.

• Spend five minutes at the end of each day reviewing your ticket queue for patterns — three customers with the same issue is a signal worth escalating.
• Write one brief product observation each week — a recurring pain point, a confusing feature, a missing functionality — and share it with the product team.

Achieve perfect SLA compliance for two consecutive months.

SLA compliance is a promise to the customer. Keeping it perfectly, consistently, builds the trust that creates loyalty.

• Check your queue at the start of every hour and flag any ticket approaching its SLA window — do not let the deadline find you.
• Set a personal response time target 20% tighter than your SLA — if your SLA is 4 hours, aim for 3.2 hours as your daily standard.

Identify and invest additional care in one challenging customer each week, with a goal of achieving a positive resolution.

The hardest interactions are the most important ones. A customer who arrives angry and leaves satisfied becomes your most credible advocate.

• Identify your most frustrated customer each morning and make them your first priority — not your last.
• After resolving a difficult interaction, write down the one thing that turned it around — over time, you will build a personal playbook for de-escalation.

Build the processes and coaching rhythms that sustain a team-wide CSAT of 92% or higher for 90 days.

A sustained team CSAT above 90% is a cultural achievement — it means the whole team is delivering consistently.

• Review CSAT scores with the team every Monday — celebrate the highest, discuss the lowest, and identify one specific improvement for the week.
• Listen to or read one low-CSAT interaction each day and use it as a coaching moment — specific, immediate, and focus on one behavior to change.

Lower the team's average handle time by 25% within 90 days through weekly coaching and process improvements.

Handle time at the team level is a multiplied factor: a 25% reduction across a team of ten equals 2.5 additional people's worth of capacity.

• Review the team's longest-handle-time tickets each week and identify the single most common cause — then build a solution into the knowledge base.
• Run one 15-minute weekly skills session focused on a specific technique that reduces handle time.

Create a knowledge base comprehensive enough that agents can resolve 50% of tickets without seeking input from a senior colleague.

A strong knowledge base makes every team member more capable and reduces dependence on institutional knowledge held by a few.

• Add one new knowledge base article each day — assign one per team member on rotation so the burden is shared and the library grows steadily.
• Review the three most common escalation types each week and ask: could a better knowledge base article have prevented this escalation?

Lift the team's overall FCR rate to 75% or higher within 90 days.

First contact resolution at the team level reflects the quality of training, tooling, and process.

• Review FCR by agent weekly and identify who is furthest below the team average — schedule a targeted coaching session that week.
• Ask the team to flag any ticket where they had to follow up unnecessarily — collect these daily and use them to identify systemic fixes.

Reduce customer churn events attributable to support experience to zero within the next 90 days by auditing every at-risk account and implementing proactive interventions now.

Support-driven churn is entirely preventable. When customers leave because of how they were treated, it is a leadership failure.

• Review every at-risk account flagged by customer success each Monday and identify one proactive support action to take this week.
• Debrief every churn event with the team within 48 hours — not to assign blame, but to identify the single intervention that might have prevented it.

Identify two high-potential agents, agree on a documented development plan with each, and deliver their first structured stretch assignment within 90 days.

Support teams lose good people when they cannot see a path forward.

• Give each high-potential agent one stretch assignment each week — a complex ticket, a training delivery, a process improvement project.
• Have a dedicated monthly development conversation with each identified agent — 30 minutes, focused entirely on their growth.

Establish a team practice of sharing and celebrating one outstanding customer interaction per week for 90 consecutive days.

Support professionals rarely hear when they do something exceptional. Making great work visible reinforces the behaviors that produce it.

• Read through your team's highest-rated interactions each day and identify one worth sharing at the next team meeting.
• Send one personalized recognition message to a team member each day — specific to the interaction, specific to the behavior.

Eliminate the current backlog completely and maintain zero backlog for 30 consecutive days.

A persistent backlog demoralizes teams and frustrates customers. Eliminating it proves the fix was structural, not accidental.

• Review backlog age and volume each morning as a team — make it visible, make it a shared problem, and celebrate every reduction.
• Identify the single biggest source of backlog growth each week and address the root cause — not just the symptoms.

Design and publish a self-service knowledge base that deflects at least 20% of inbound support volume within 90 days.

Self-service done well gives customers faster answers and gives the team capacity for more complex work.

• Review the top 10 ticket types each week and ask: could a well-written self-service article have prevented this contact? Assign one team member each week to write or improve one self-service article — rotate the responsibility so everyone contributes.

Build a team culture where agents feel genuinely valued, challenged, and supported — measured by an engagement score of 8.5+.

Support is one of the most emotionally demanding roles in any organization. A high engagement score is a direct predictor of CSAT.

• Check in informally with each team member once a week — not about tickets, but about how they are finding the work and what they need.
• Publicly acknowledge one team win each day — in writing or in a standup — so the team sees their collective progress, not just individual scores.