K-12 Tech Help Ticket Best Practices Guide

Why Proper Ticket Submission Matters

The EdTech Department's Tech Help ticketing system is the primary way we ensure equitable service delivery to all end users across our district. By following these best practices, you help us provide faster, more effective support while ensuring every staff member receives the same high-quality assistance they deserve.

Essential Information to Include

1. Be Specific and Detailed

Instead of: "My computer is slow" or "Won't work" Write: "The web browser is extremely slow to load pages, and it takes several minutes to open a new tab"

Instead of: "The screen isn't working" Write: "The Newline board in Room 204 will not display what is on my computer"

2. Identify Affected Systems

Always specify:

• Device details: Computer name, model, or specific equipment
• Applications involved: Chrome, Schooltool, Google Classroom, etc.
• Network or system: WiFi, district network, specific website(s)
• Location: Building, room number, or area

Example: "The Newline Board in Room 112 at Cumberland Head Elementary School won't connect to my district-issued Chromebook (Asset Tag #B623006092)"

3. Provide Step-by-Step Reproduction

Document exactly what you were doing when the issue occurred:

1. "I opened Google Chrome"
2. "Navigated to Schooltool"
3. "Clicked on 'Gradebook' tab"
4. "Selected Period 3 Math class"
5. "Error message appeared when trying to enter grades"

4. Record Error Messages Exactly

Copy error messages word-for-word, including:

• Error codes or numbers
• Exact wording of pop-up messages
• System notifications

Example: "Error 404: Page Not Found - The requested URL /gradebook/period3 was not found on this server"

5. Include Timestamps

For time-sensitive issues, note:

• Date and time the issue first occurred
• Duration of the problem
• Whether it's ongoing or intermittent

Example: "Issue started at 8:15 AM on October 15th during first period. Problem persists as of 10:30 AM."

6. Attach Visual Evidence

Screenshots and recordings provide invaluable context:

• Screenshots: Capture error messages, frozen screens, or unusual displays
• Screen recordings: Show intermittent issues or complex problems
• Photos: Document physical equipment issues

Tips for good screenshots:

• Include the entire screen when possible
• Ensure text is readable
• Highlight relevant areas if needed

Sample Well-Written Ticket

Subject: Chrome browser extremely slow on classroom computer - Room 205

Description: The desktop computer in Room 205 (Asset Tag: ##B623007134) is experiencing severe browser performance issues. Chrome takes 3-5 minutes to load any webpage, including Google Classroom and district email.

Steps taken:

1. Opened Chrome at 9:15 AM on October 16th
2. Attempted to navigate to classroom.google.com
3. Page began loading but stalled at approximately 25%
4. Waited 4 minutes before page fully loaded
5. Tried opening a second tab - same delay occurred

Impact: Unable to access lesson materials during 2nd period science class. Affects 28 students.

Additional details:

• Other applications (Docs and Slides) run normally
• Microsoft Edge shows similar slow performance
• Issue has persisted for 3 days
• Restarted computer twice with no improvement

Attached: Screenshot of loading screen and network speed test results

One Issue Per Ticket - Keep It Simple

Submit separate tickets for each distinct problem. Even if multiple issues occur simultaneously, create individual tickets for each one. This approach ensures:

• Clear communication and tracking for each problem
• Appropriate assignment to specialized staff members
• Faster resolution times
• Better documentation and follow-up

Instead of: "My computer is slow, the Newline board won't connect, and I can't access email" Submit three separate tickets:

1. Computer performance issues
2. Newline board connectivity problems
3. Email access troubles

Remember: Quality Tickets = Faster Resolution

Taking a few extra minutes to provide comprehensive information helps our department:

• Diagnose issues more quickly
• Avoid back-and-forth questions
• Provide targeted solutions
• Ensure equitable service for all users

When in doubt, include more detail rather than less. Your thoroughness helps us serve the entire district more effectively.