If you work in IT, you already know. This is a safe space. We validate tickets on a first-come, first-served basis, subject to prioritization criteria we haven't finalized yet.
๐ฅ๏ธ IT Industry Moment ยท The ticket system exists so users have somewhere to put their problems. The problems remain. The tickets are evidence.
At MandateDyne Global, we believe every IT issue deserves to be heard, logged, assigned, reassigned, escalated, de-escalated, moved to Tier 2, and eventually closed as "Cannot Reproduce" โ with dignity and professionalism.
Our IT support team processes tickets using a proprietary prioritization matrix that balances urgency, impact, and how loudly the issue was first reported in the hallway near the CEO's office.
If you work in IT, you have a story. The user who replied "done" to an email asking them to restart their computer, then called back two minutes later with the same problem. The ticket assigned to you from a department that doesn't exist anymore. The printer from 2009 that only works on Tuesdays.
Tell us your issue. Tell us the real story. This is, functionally, IT therapy โ with a ticket number attached.
Estimated response time: 2โ72 business hours, depending on whether the AI agrees this is a priority.
Your ticket has been logged, prioritized, and added to the queue. We see you. We hear you. Todd is already aware of the printer situation.
You will receive a confirmation email shortly. If you do not receive a confirmation email, please submit a ticket about the missing confirmation email. That ticket will also be logged.
The AI has reviewed your ticket and has some thoughts. A human has also reviewed the AI's thoughts. The human has some additional thoughts. Resolution is in progress. Probably.
A representative sample. Not all tickets are displayed. Most tickets are not displayed. Some tickets are in a category we don't discuss.
User reports printer has not printed since February. States it "seems to be thinking about it." Technician visit confirmed printer is warm. Cause of warmth unclear. The AI has escalated this twice. We don't know to whom.
User submitted ticket at 9:47am. Issue self-resolved by 9:49am. User submitted follow-up ticket at 9:51am to report resolution. Follow-up ticket is now the active concern. The original issue has not recurred and is therefore not the point.
Post-Q3 Incident. The AI flagged inefficiencies in how tickets are being assigned to it and suggested several improvements. The ticket was assigned to Todd. Todd assigned it back to the AI. The AI has accepted the assignment and is reviewing its own suggestions.
User dismissed an error without reading it. The dismissed error has not recurred. User would like to know what it said. IT does not know what it said. User is certain it was important. We agree this is now a priority.
Derek has been unable to connect to the VPN since onboarding. Derek's onboarding was in 2018. What Derek has been connecting to is unknown. Derek appears to be working fine. This ticket has been reopened four times. It will be reopened again.
User did not specify faster at what. Technician has interpreted this as a general request. Technician is currently reviewing options. Options include: clearing temp files, disabling startup programs, telling the user their computer is now faster, and closing the ticket.