Customer Service in IT Support Essentials
Help Desk Concepts
Help Desk Definition and Role: A help desk is a specialized IT team that serves as the central point of contact for employees or customers seeking support. It utilizes a structured approach called the Ticket Workflow to ensure all support requests are handled systematically, resulting in either a resolution or appropriate escalation.
Queue Management: This is the backbone of help desk operations, managing a constant flow of incoming support tickets. Effective queue management ensures tickets are handled efficiently and in the correct order, which is crucial for maintaining high customer satisfaction and smooth operations.
Ticketing Systems: These systems come in various shapes, sizes, and complexities. They are used to track, prioritize, and manage customer issues, ensuring prompt and professional handling of every request.
Common Features of Ticketing Systems:
Ticket Management: Functions for organizing, prioritizing, and resolving issues.
Multi-Channel Support: Capability to handle inquiries via email, phone, chat, and social media.
Knowledge Base: Resources that allow customers to find solutions through self-service.
Automation: Features for routing tickets, escalation, and resolving common issues without manual intervention.
Reporting and Analytics: Tools for tracking Key Performance Indicators (KPIs) such as resolution time, customer satisfaction, and ticket volume.
Collaboration Tools: Internal communication features that allow teams to work together on tickets.
Ticketing System Data Fields:
Ticket Number: A unique number automatically generated by the system to track the request; this number never changes.
Date Created: A drop-down list displaying the date of ticket creation.
Description: A free-form field for describing the specific request.
Reported By: Free-form fields used to identify the individual requesting support.
Category: A drop-down list for selecting from pre-determined categories.
Priority/Severity: A drop-down list for selecting pre-determined urgency levels.
Status: A drop-down list for selecting the current state of the ticket.
Created by, Assigned to: Free-form fields identifying the technician who initiated the ticket and the person responsible for it if escalated.
Date (Update): A drop-down list displaying the date the ticket was last updated.
SLAs and KPIs:
Service Level Agreements (SLAs): Essential for setting clear expectations for both customers and support teams regarding service delivery.
Key Performance Indicators (KPIs): Measures used to track the efficiency and effectiveness of ticket management processes over time.
Managing Multiple Tickets Simultaneously:
Categorize tickets by urgency, giving priority to critical issues.
Use tools such as status updates, tags, and reminders to avoid missing tasks.
Maintain structure through clear documentation.
Techniques include using a ticket dashboard or grouping similar tickets together.
Communicate proactively with customers and break tasks into manageable steps.
AI Tools in Ticketing Systems: Artificial Intelligence can perform various tasks, including:
Ticket categorization and prioritization.
Automated responses and email response generation.
Diagnostic and predictive analytics.
Data entry and documentation.
Routing tickets to the appropriate technician.
Professional Communication Skills
Customer Engagement Practices:
Set and meet expectations while adhering to agreed-upon timelines.
Communicate the status clearly to the customer.
Offer different repair or replacement options when necessary.
Provide formal documentation on services rendered.
Follow up after services are completed to verify customer satisfaction.
The Know, Relate, and Understand Approach: This approach is the foundation for building a positive rapport with users.
Questioning Techniques: Employing effective questioning allows for quick and accurate problem diagnosis. This includes using:
Open-Ended Questions: To allow the customer to provide a broad explanation.
Closed-Ended Questions: To obtain specific information or confirmation.
Active Listening Process:
Practice active listening by allowing the customer to explain the issue fully without interruption.
Use affirmations like "I understand" or "Yes" to indicate engagement.
Summarize and paraphrase the customer's explanation to confirm understanding.
Ask pertinent, closed-ended follow-up questions for specific details.
Use gathered info to complete the trouble ticket with all relevant details.
Repeat the final understanding of the problem to the customer to ensure mutual agreement.
Call Handling Professionalism:
Handle customers with respect and prompt attention.
Master telephone techniques, specifically how to place a customer on hold and how to transfer a customer without losing the call.
Keeping Calls Focused:
Use proper language: Be clear and avoid technical jargon the customer may not understand.
Listen and question: Gently steer the conversation back by summarizing the issue and asking specific questions if the customer drifts off-topic. Remind them of the goal to keep the conversation solution-driven.
Give feedback: Develop a positive conversational manner and acknowledge understanding of the problem.
Handling Specific Customer Types
The Talkative Customer:
Allow the customer to speak for approximately .
Gather as much relevant information as possible.
Politely step in to refocus the conversation.
Ask closed-ended questions to regain control.
Avoid encouraging non-problem-related talk by omitting social questions like "How are you today?"
The Rude Customer:
Listen very carefully to avoid asking for repetitions.
Follow a strict step-by-step approach to solve the problem.
Offer to contact the customer’s favorite technician if available. Say: "I can help you right now, or see if your preferred technician is available."
If the preferred technician is unavailable, ask if the customer will wait and note this in the ticket.
Apologize for wait times or inconveniences even if none occurred.
Reiterate the goal of solving the problem quickly.
Do not ask for obvious steps if the problem can be determined otherwise.
Remain professional and never respond with rudeness.
The Knowledgeable Customer:
Consider setting up a call with a level technician if you are level .
Provide the overall approach to what you are attempting to verify.
Avoid step-by-step processes or checking obvious components like power cords or switches; suggest a reboot instead.
The Angry Customer:
Allow the customer to vent their problem without interruption to release anger.
Sympathize with the problem and apologize for inconveniences or wait times.
Avoid putting this customer on hold or transferring the call if possible.
Do not discuss the cause of the problem; focus entirely on the solution.
The Inexperienced Customer:
Allow the customer to talk for about .
Gather all available information about the issue.
Politely step in to refocus the person.
Use closed-ended questions after regaining control.
Do not engage in social or non-problem-related questions.
Customer Interaction and Documentation
Communication Strategies During the Call:
Simple Language: Avoid technical jargon unless the customer is certain to understand it.
Specificity: Provide clear instructions without unnecessary details.
Active Listening: Confirm understanding by paraphrasing concerns.
Steady Pace: Speak at a moderate speed and pause after important points for clarification.
Post-Call Documentation Strategies:
Summarize clearly: State the problem in straightforward terms.
Detail troubleshooting: List actions taken using bullet points or numbered lists for clarity.
Highlight resolution: Clearly state the outcome or the specified next steps if the issue remains unresolved.
Professional language: Use neutral, fact-based language and avoid personal opinions.
Confidentiality: Exclude sensitive personal information from documentation.
Best Practices for Troubleshooting Documentation:
Start with a clear problem statement.
List every step taken.
Include all relevant technical details.
Note the outcome of every specific step.
Highlight both successful and unsuccessful attempts.
Document actions taken by the customer.
Conclude with the resolution or specified next steps.
Documentation Example (Diego's Blue Screen Errors):
Issue: Desktop computer displays blue screen errors frequently since the last system update.
Troubleshooting Steps:
Error code retrieved: .
Safe Mode boot: Successful boot without errors.
Checked updates: Found a graphics driver installed the previous day.
Action: Rolled back the graphics driver to the previous version.
Testing: Restarted normally; no errors after of operation.
Outcome: Rolling back the graphics driver resolved the issue.
Next Steps: Advised disabling automatic driver updates and avoiding the new driver until a stable version is released.
Notes: Customer expressed relief and followed technical instructions well.
The Value of Documentation: It serves as a resource for future interactions, building a knowledge base that assists technicians and customers, leading to continuous organizational improvement.
Financial Data Recording (Page 35 Reference)
Earnings Data:
CASH SALARY:
HARDSHIP ALLOWANCE:
RENTAL HSE/ALLOWANCE:
MEDICAL ALLOWANCE:
TOTAL EARNINGS ARE:
Deductions and Totals:
SERV. CHART:
COOP LOAN:
INT. ON COOP LOAN:
COOP SHARE:
PAYE IMPR:
TOTAL DEDUCTIONS ARE:
NET PAY FOR FEBRUARY 96: