Urgent incident
If a covered system is down, compromised, or creating immediate business risk, use the incident path defined in your agreement. If you cannot reach that path, use Emergency Help to identify the safest next action.
Support
Start with the route that matches the problem
Support coverage is agreement-specific. This page helps you reach the correct owner without inventing a universal hotline, response promise, or severity target that may not apply to your engagement.
Open emergency guidance
Engineering request
For architecture, environment, deployment, change, or implementation requests, contact the engineering queue and include the affected system and desired outcome.
Billing and administration
For invoice questions, billing traces, account administration, or commercial records, use the finance path so the request reaches the correct owner.
Coverage contract
The signed engagement controls support commitments.
Package names and public pages do not create a response-time, resolution-time, after-hours, or availability guarantee. The agreement defines what is covered, when coverage applies, how severity is determined, and how escalation works.
- Coverage window
- Defined by your agreement
- Severity and response targets
- Defined by your agreement
- Escalation path
- Named in the engagement record
- Incident communications
- Scoped to the affected service and evidence available
Escalation
Use the path your engagement names first.
If resolution quality, ownership, or communication falls outside the agreed process, escalate through the engagement owner. Public contact routes remain available when you do not know the assigned path.
Include with the escalation
The affected system, observed impact, incident or request identifier when available, and the outcome you need.