Make the current impact clear
An emergency request should say what is unavailable, who is affected, when it began and whether there is an active security or data concern. That information helps separate a total outage from a limited failure and identify the safest first action.
Examples of urgent impact
- The public website or admin is unavailable.
- Checkout, payment or a critical customer path fails.
- The website redirects, displays malware or has suspicious access.
- A domain, DNS or SSL change has taken the site offline.
- A deployment or update caused a severe regression.
Triage before broad change
The first objective may be containment, rollback or restoring a stable service—not completing every long-term improvement during the incident. Once the immediate impact is controlled, the root cause and durable repair can be addressed.
Availability is confirmed, not assumed
Mark the form as urgent and provide a reachable email address. The website does not publish an unsupported response-time guarantee. Availability, access, scope and any urgent-work terms are confirmed before work starts.