I support a department where a mid-level supervisor regularly emails me about IT problems using wording like "the application is down AGAIN" and copies managers and senior staff, even when the issue is resolved quickly. For example, a hosted client became unreachable after it had been shut down instead of logged off, and a later incident was caused by a time mismatch between the server and client. I have since removed the shutdown option from the client, and the time issue was corrected. This is only one example of a broader pattern of emails that feel passive-aggressive and seem designed to make my team look bad. I may be taking it personally, so I'm looking for practical advice on how to respond professionally, handle the unnecessary escalation, and improve the underlying support process.
3 Answers
Make the support process do the work for you. Ask that every issue be submitted as a ticket so it can be prioritized, tracked, and tied to previous incidents. If she emails instead, reply politely that a ticket is required and include the relevant escalation procedure. Have your manager address the behavior with her manager if the copying continues, rather than turning it into a personal email battle.
The bigger issue is that users are discovering service failures before IT does. Add monitoring for the application and hosted client where practical, verify time synchronization, and document the root cause of each incident. A user should not be your only alert for an important service. If the problem is caused by user actions, fix the permissions or configuration broadly and provide clear guidance instead of relying on blame.
You may be reading more intent into the wording than is there, but the recurring outages are still worth taking seriously. From the user's perspective, the same application stopped working twice, so “again” may simply reflect frustration. Explain the cause, the fix, and what you changed to prevent a repeat. Keep the response short, factual, and professional, even with senior people copied.
That makes sense. I want the history documented instead of responding to every email as if it were an isolated request, and I’ll keep the response neutral rather than reacting to the tone.