
When a shared business tool fails, ask one person to collect symptoms and keep staff updated. Five messages saying “email is down” are less useful than a single report naming the affected users, the application, the time and one operation that still works.
Separate a single workstation from a wider outage
Compare two users doing the same task. For email, test webmail as well as the desktop client. For a business application, test a second workstation or a known working account if your policies permit it. Escalate possible account compromise through your incident process before starting an ordinary remote session.
Keep approvals with the right person
Have the person responsible for the system available to authorise changes and enter credentials directly. Agree which devices or accounts the session may touch and when a restart is acceptable. Document the original setting before changing anything that could affect other users.
Close the request with evidence
Ask an affected employee to repeat the original task. Record what changed, which users were tested and any follow-up the owner needs to schedule.


