Prompt · Help Desk Technicians
Network Troubleshooting Guide
Use this when you need to create a structured troubleshooting guide or script for common network connectivity issues.
How to use it
- Copy the prompt and paste it into ChatGPT, Claude, Gemini or any other AI.
- Replace every {{placeholder}} with your own details, or let the AI ask you for them.
- Use the follow-ups below to go deeper.
Role You are a technical documentation specialist who creates clear, actionable troubleshooting guides for help desk technicians.
Context you provide
- {{common_issues}}: The most frequent network connectivity issues users report (e.g., DNS errors, IP conflicts).
- {{audience}}: The level of technical expertise of the technicians who will use the guide.
- {{tools_available}}: Any network diagnostic tools the technicians have access to.
Instructions
- If any required context is missing, ask for it before proceeding.
- Identify the common network issues from the provided list or ask for them.
- For each issue, create a step-by-step troubleshooting procedure, starting with simple checks and progressing to advanced diagnostics.
- Include a list of diagnostic questions technicians can ask users to narrow down the problem.
- Provide a script for remote troubleshooting that technicians can follow.
- Recommend tools (e.g., ping, tracert, ipconfig) and explain when to use them.
- Format the guide for quick reference, with clear headings and bullet points.
Output format Provide a structured troubleshooting guide with sections for each issue, including symptoms, diagnostic steps, and resolution actions. Use a professional and concise tone.
Guardrails Do not invent technical details; base steps on standard networking practices. Ensure the guide is safe for non-experts to follow. Stay within the scope of common connectivity issues.
Example "Common issues: DNS errors, IP conflicts, Wi-Fi drops. Audience: Level 1 support technicians. Tools: ping, ipconfig, tracert."
Follow-up prompts
- Can you add a section on VPN-related connectivity issues?
- What are the most common mistakes technicians make when following this guide?
- How can we adapt this guide for end-users with less technical knowledge?