Short intake
Start with what is getting in the way.
Describe the interruption in the language your team uses. You do not need to diagnose it first.
Keep authentication secrets out of the message.
Do not include passwords, recovery codes, private keys, or approval prompts. Describe what appeared instead.
What happens next
First, the request is checked for fit.
- 01
The issue and affected users are understood.
- 02
The desk confirms whether it is everyday support or needs separate scope.
- 03
The next useful action or clarification is returned—without a published response-time promise.
Tell the desk what is getting in the way
Share the affected app, how many people are involved, and the outcome your team needs. The desk will first confirm fit and the next useful step.