User unblocked
The employee can complete the expected task and knows which action changed the result.
“What happens after we ask?”
One path from problem to next step.
The desk does not need an invented countdown or a vague “closed” status. It needs a safe intake, visible ownership, and an outcome the employee or business owner can understand.
- 01
Prepare
Capture the person, app, device, exact wording, impact, recent change, and whether anyone else is affected.
- 02
Sort
Identify whether the need is user guidance, a routine administrative change, an approval, a wider project, security, or another IT layer.
- 03
Work
Guide the employee or complete the appropriate authorized everyday change without collecting authentication secrets.
- 04
Handoff
Record what changed, what the user should try, which approval is missing, or why another owner must take the work.
Sample support handoff
What a useful handoff record looks like.
This is an illustrative record structure-not a customer ticket, result, or promise that a live queue exists.
- Observed
- Outlook desktop stopped updating for one employee after a password change. Browser mail still opens.
- Checked
- Device, connection, account address, time observed, exact status, and recent change are recorded. No credential is included.
- Next action
- Confirm the supported profile/session path with the user, or name the tenant/device owner if the symptom sits elsewhere.
- Close or handoff
- Record whether the employee is unblocked, an approved change was made, information is missing, or wider ownership is needed.
How a request ends
"Resolved" is only useful when it says what happened.
Routine change completed
An approved account, access, mailbox, group, or licence adjustment is recorded.
Waiting on an owner
The missing user detail, manager approval, device, vendor response, or business decision is explicit.
Scoped handoff
The known facts, impact, boundary, and next accountable owner travel together.
Useful context
Bring details that can be safely repeated.
- Affected person and device
- App or Microsoft 365 service
- Exact wording or a safe screenshot
- What changed or was already tried
- Whether anyone else is affected