All use cases
Customer supportNo technical background needed
Answer "is it down for everyone?" in the first reply
Check deployment status and service health before escalating — most of the time you will not need to.
Before Fenwave40 minutes waiting
“Escalating to engineering: 4 customers reporting checkout errors since ~18:20, no idea if something was released”
What the wait costs
Four customers waiting while support waits, for a question the deployment timeline already answers.
Support escalates because it cannot see, not because it cannot judge. Read access to deployment history and service health turns the first minute of an incident into an observation: a release went out at 18:20 and the service has been unhealthy since 18:22. That is a far better escalation than "customers are reporting errors", and quite often it is enough to answer the customer directly.
How it works
- 01Open Deployments filtered to production.
- 02Check whether anything was released around the reported time.
- 03Read the current health status of the service.
- 04Escalate with the release time and the symptom, or answer the customer.