Zendesk Tickets Auditing Process
Introduction
The audit tasks and definitions outlined in this document are designed to uphold the efficiency and quality of our ticket handling processes. Through the analysis of key performance metrics and compliance standards, our objective is to pinpoint areas for enhancement and promote positive behaviors within the team.
Objective
The purpose of these audit tasks is to conduct a systematic review and improve our ticket management practices. This will ensure prompt responses, efficient resolutions, and compliance with security and communication standards.
Goal
The objective is to uphold exceptional levels of customer service, enhance overall ticket resolution times, and adhere to security protocols. Through the identification and rectification of any deficiencies in our procedures, we aim to boost team efficiency and elevate customer contentment.
Audit Tasks and Definitions
1. First Reply Time
Task: Analyze tickets with a first reply time exceeding one hour.
Objective: Ensure that customers receive timely acknowledgments of their issues.
Action Steps:
Identify tickets where the first reply time is more than one hour.
Review the context and reasons for the delay.
Discuss findings with the team and identify strategies to reduce first reply times.
2. Full Resolution Time
Task: Analyze tickets with a full resolution time exceeding eight hours.
Objective: Ensure that issues are resolved efficiently and effectively.
Action Steps:
Identify tickets where the full resolution time exceeds eight hours.
Review the reasons for extended resolution times.
Implement measures to optimize the resolution process.
3. Compliance Audit
Task: Randomly review public comments from each agent to ensure responses meet security compliance and appropriate verbiage standards.
Objective: Maintain high standards of communication and security in customer interactions.
Action Steps:
Randomly select public comments from each agent.
Check for adherence to security compliance and appropriate language.
Highlight any tickets where these standards are not met.
Provide feedback to agents and conduct training if necessary.
4. Bad Satisfaction Tickets
Task: Investigate tickets with poor ratings to identify root causes.
Objective: Address and resolve gaps that lead to customer dissatisfaction.
Action Steps:
Identify tickets with poor satisfaction ratings.
Analyze the reasons behind the negative feedback.
Discuss findings with the team and develop action plans to improve service quality.
5. Good Satisfaction Tickets
Task: Highlight positive feedback within the team to promote and encourage good practices.
Objective: Reinforce positive behaviors and practices among team members.
Action Steps:
Identify tickets with positive satisfaction ratings.
Share positive feedback with the team.
Recognize and reward team members who consistently receive good feedback.
Example
Ticket ID | Ticket Description | Client Name | Type of Audit | Audit Date | Actions | Comments | |
1 | #460 | ASD-90 Required the original push script from Adeptia to D365 for attached customer invoice payload | AJG | High-Full Resolution time | 6/25/2021 | Meeting Required |
|
2 | #472 | Deployment analysis of OR to D365 transaction for production | AJG | High-Full Resolution time | 6/25/2021 | Meeting Required |
|
3 | #586 | EDIOutboundProcessor error in the AJG stage environment | AJG | High-Full Resolution time | 6/25/2021 | Meeting Required |
|
4 | #741 | ASD- 100 - Analysis of AJG Production FTP Event and Event registries | AJG | High-Full Resolution time | 6/25/2021 | Meeting Required |
|
5 | #761 | Analysis of PRONTO Refund Payment Payload Concern | AJG | Compliance Audit | 6/25/2021 | Meeting Required | Using Camel case |
6 | #796 | RE: ESB - 3210 | AJG | High-Full Resolution time | 6/25/2021 | Meeting Required |
|
7 | #805 | ESB-3218 Change Implementation in Customer Invoice Mapping for Account Type Customer | AJG | High-Full Resolution time | 6/25/2021 | Meeting Required |
|