# What is Engineering Escalation?

> A ticket support hands to engineering because it needs code-level investigation.

Canonical: https://www.decimal.app/glossary/engineering-escalation · Last reviewed: 2026-09-23

An engineering escalation moves a customer issue from the support team to product engineers, usually because it involves a suspected bug, data problem, or behavior that only someone with code and system access can explain.

## Why it matters

Escalations are the most expensive tickets a company handles. They pull engineers off roadmap work, they're slow for the customer, and many turn out to be config questions or known issues that didn't need an engineer.

## Best practices

1. Define clear criteria. Write down what qualifies, and require evidence before a ticket crosses over.
2. Use a template. Standardize the bug report so engineers don't have to ask follow-ups.
3. Close the loop. Feed the root cause back to support so the next similar ticket stays in support.

## How Decimal helps

Reducing engineering escalations is what Decimal is built for. Customers report results like 62% lower MTTR (Resilinc) and zero added support hires while growing (Guide).

## Related terms

- [Escalation Rate](https://www.decimal.app/glossary/escalation-rate): The percentage of tickets support can't resolve without another team.
- [Escalation Path](https://www.decimal.app/glossary/escalation-path): The defined route a ticket follows when the current owner can't resolve it.
- [Tiered Support (L1, L2, L3)](https://www.decimal.app/glossary/tiered-support): A support structure where harder issues move up through levels of expertise.
- [Bug Report](https://www.decimal.app/glossary/bug-report): A write-up of unexpected behavior with enough detail for an engineer to reproduce it.

---

Decimal · Book a demo: https://cal.com/decimal-demo/30m · Markdown index: https://www.decimal.app/llms.txt