Asking IT for help with the context they replay

What you clicked, what you saw, what you already tried, and the one thing you need. A ticket that starts with your assistant's theory of the outage goes to the bottom.

1 min read

IT does not need your journey. They need a failure they can replay.

The four lines

What you were doing. What you saw — the actual string, not "it broke." What you already tried. What "fixed" means for you — log in, or send mail, or join the call.

Then the ask: reset this account, or tell me the next check.

Your assistant will diagnose

It will be confident. Mark it or delete it. A help desk that chases a model's certificate theory loses the morning.

They already have a queue

If policy is the portal, use the portal. If you are writing to a vendor's engineer, email is enough unless they already have an account — then you need an accepted contact. Same facts. Same one ask.

Do not put your nickname for the vendor in the letter. Use the name on the contract.

Tags work operations briefings

Frequently asked questions

We have a ticket system. Why a briefing?
Use the ticket system if that is how work is assigned. A briefing is for a named person when the form ate the context, or when the other company has no ticket you can see.
Can I attach a screenshot?
No. Describe the error text exactly. If they need a picture, they will ask on the channel they use for pictures.
Should I include what my assistant thinks is wrong?
Only as a labeled guess. "VPN disconnects at 09:00" is a fact. "The cert is expired" is an inference until someone checked.

Related articles