Tell us what broke.
“Everything” is rarely the answer.
Tell us what happened, what you expected to happen, which device or service is involved, and what the screen actually says. Technical vocabulary is optional. Useful details are not.
Open a support ticket.
This is demonstration content. The form does not send information to a real support team.
Then what?
A support process should be slightly more sophisticated than yelling across the office until somebody wearing headphones looks concerned.
The request enters the queue with the details, business impact, user information, and whatever meaningful description was supplied.
Determine scope, urgency, affected systems, security implications, available workarounds, and whether “urgent” means urgent.
Troubleshoot the problem, communicate with the user, coordinate vendors when necessary, and restore normal operations.
Record what happened, what fixed it, and anything that should change so the same issue becomes easier or less likely next time.
Other ways to find us.
Screenshots are beautiful.
Especially when they include the actual error message, the full window, and enough context to identify what application we are looking at.