Help Desk
# Cisco Support Network
Easy
1.3 Help Desk
1.3.1 Security Policy
Organizations operate according to clearly defined corporate, employee, and security policies.
A security policy document informs users, IT staff, and managers about the requirements for protecting technology and information assets. Policies may define how to:
- Identify and authenticate users
- Set password length, complexity, and renewal intervals
- Define acceptable behavior on the corporate network
- Establish remote-access requirements
- Maintain the network
- Handle security incidents
A security policy is a living document. It must evolve as the threat landscape, vulnerabilities, business requirements, and employee needs change.
Standard Operating Procedures (SOPs)
SOPs provide step-by-step instructions for completing tasks in compliance with organizational policies. Examples include:
- Replacing network devices
- Installing or uninstalling applications
- Onboarding new employees
- Processing employee departures
Guidelines
Guidelines provide recommended practices for situations that do not have a formal SOP.
Help Desk
The help desk is the central point of contact for network issues and support requests. It follows established SOPs and guidelines, uses a ticketing system to manage requests, and tracks the complete troubleshooting lifecycle.
When a user reports a problem, a ticket is created. The help desk uses the available SOPs and guidelines to investigate and resolve the issue, while the ticketing system records progress from the initial report through resolution and closure.
1.3.2 Help Desks
A help desk is a specialized team within an IT department that acts as the central point of contact for employees or customers.
Users may request support through:
- An online reporting tool
- Live chat
- Telephone
A help desk technician can:
- Resolve straightforward user issues quickly
- Create a problem ticket in the organization's ticketing system
- Gather diagnostic information
- Escalate unresolved issues to a more experienced technician
1.3.3 Ticketing Systems
Help desk ticketing systems help organizations manage user issues and service requests. They ensure that requests are recorded, assigned, tracked, and addressed.
Typical ticket fields include:
- Ticket number
- Description
- Reported by
- Creation date
- Contact information
- Category
- Priority or severity
- Status
- Created by
- Assigned to
1.3.4 Asking End Users Questions
When communicating with a user:
- Be considerate and empathetic
- Use a technical level the user can understand
- Listen carefully
- Avoid assumptions
- Confirm important details before taking action
Effective troubleshooting uses both open-ended and closed-ended questions.
1.3.5 Open-Ended and Closed-Ended Questions
An open-ended question encourages the user to explain what happened in their own words.
“What happened immediately before the problem started?”
Open-ended questions usually produce longer answers and help reveal context that may not appear in the original ticket.
A closed-ended question asks for a specific fact and usually has a short answer.
“Are you using Windows 11?”
Closed-ended questions are useful for confirming details, narrowing possible causes, and testing a hypothesis.
1.3.6 Active Listening
Active-listening practices include:
- Letting the customer tell the complete story
- Using brief acknowledgements such as “I understand,” “Yes,” or “OK”
- Avoiding interruptions
- Summarizing what the customer said
- Asking relevant follow-up questions
1.3.7 Active Listening and Summarizing
Use these practices when speaking with a customer:
- Allow the customer to describe the problem without being rushed
- Give occasional verbal confirmation so the customer knows you are listening
- Summarize the issue after the customer finishes
- Ask clarifying questions where details are missing
- Confirm that both parties understand the same problem before troubleshooting begins
1.3.8 Gathering Information for Host-Related Tickets
Useful host information includes:
- Manufacturer, model, and serial number
- Operating-system version
- Network environment
- Network-connectivity test results
Additional diagnostic information may include:
- Beep codes
- Event Viewer logs
- Device Manager settings
- Task Manager data
- Diagnostic-tool results
1.3.9 Gathering Information for Cisco Device Tickets
Use Cisco IOS commands, packet captures, and device logs to collect information.
| Command | Description |
|---|---|
ping {host | ip-address} | Sends an ICMP echo request to a destination and waits for a reply. The destination may be a hostname or IP address. |
traceroute destination | Identifies the path packets take through the network to the destination. |
telnet {host | ip-address} | Connects to a device through Telnet. Use SSH instead whenever possible because Telnet is not secure. |
ssh -l user-id ip-address | Connects securely to a device through SSH. |
show ip interface brief<br />show ipv6 interface brief | Displays a concise status summary for all interfaces and helps identify interface addressing quickly. |
show ip route<br />show ipv6 route | Displays the current IPv4 or IPv6 routing table and the known routes to network destinations. |
show protocols | Displays configured Layer 3 protocols and their global and interface-specific status. |
1.3.10 Analyzing the Information
Information sources may include:
- Ticketing-system knowledge bases
- Vendor documentation and support resources
- Internal network documentation
- Device logs and command output
- Reliable online research
Compare the collected evidence with known-good behavior, identify the most likely cause, and test one change at a time. If the issue cannot be resolved within the technician's responsibility or skill level, document the work already completed and escalate the ticket to a more experienced member of the IT team.
1.3.11 Check Your Understanding — Help Desks
Review the following topics before continuing:
- The purpose of security policies, SOPs, and guidelines
- The role of a help desk and ticketing system
- Open-ended and closed-ended questions
- Active listening and issue summarization
- Information required for host and Cisco-device tickets
- When and how to escalate a ticket