Story
Crown Holdings Standardizes On-call Response on Elastic
Crown Holdings, a materials organization in the United States, uses Elastic Observability from Elastic to support incident management for on-call rotations.
Value results
| Category | Value result |
|---|---|
| Productivity | Fewer stalled items because on-call response has a clear owner |
| Productivity | Handoffs in incident management sit in a shared queue instead of a mailbox trail |
| Risk and compliance | Elastic Observability is the governed place on-call rotations use for incident management |
Story
Crown Holdings is based in the United States and runs materials operations at a scale where on-call response cannot live in side channels. On-call rotations were reconciling competing copies of the same work, which slowed incident management and hid who owned the next step.
The company runs incident management on Elastic, with Elastic Observability as the product on-call rotations actually open. Elastic builds search, observability, and security software on Elasticsearch, used to find information and investigate operational data. For Crown Holdings, that means on-call rotations can open one workflow, see on-call response, and let neighboring teams join without inventing a parallel stack.
Public materials confirm the companies and products. They do not always publish a single verified KPI for this pairing, so the outcome here is operational: clearer ownership, fewer stalled handoffs, and a shared record for on-call response.