All articles

Blog

Zendesk and ServiceNow Escalations to Engineering: Where the Time Goes

When a ticket escalates from Zendesk or ServiceNow to engineering, most of the elapsed time is not spent fixing anything. It goes to three things: crossing from the support system into the engineering tracker, waiting in the engineering queue, and reconstructing what happened inside that one customer's environment. The fix itself is usually the shortest stage. Unthread's 2026 survey of 1,000 SaaS companies puts the reconstruction alone at 2 to 4 hours of engineering time per escalation, per Unthread's resolution statistics. For enterprise software sold with per-customer configuration, that number is a floor, not a ceiling.

The Escalation Path at a Glance

The same path shows up at almost every B2B software company, whether the front end is Zendesk, ServiceNow or Salesforce Service Cloud and the back end is Jira or Azure DevOps. The list below maps each stage to where the time goes and who owns it.

  1. Intake and triage. L1 confirms the issue is real and not a how-to question. Time goes to: back-and-forth with the customer for details. Owner: support.
  2. L1 to L2. A support engineer tries known fixes and the knowledge base. Time goes to: re-gathering details L1 didn't capture. Owner: support.
  3. Support to engineering. The ticket becomes a linked Jira issue. Time goes to: rewriting the case for a different audience in a different tool. Owner: support and engineering.
  4. The engineering queue. The issue waits for an engineer with the right context. Time goes to: competing with sprint work. Owner: engineering.
  5. Reconstruction. An engineer works out what actually happened. Time goes to: logs, database, config, code and past tickets, one tool at a time. Owner: engineering.
  6. Customer follow-up. Questions go back to the customer through support. Time goes to: each question is a full round trip. Owner: support and engineering.
  7. Fix and handback. The change ships and support closes the ticket. Time goes to: usually the shortest stage. Owner: engineering.

Stages 3, 4 and 5 are where escalated tickets lose days. None of them show up as a line item on a support dashboard.

Stage 1 and 2: Intake and the First Handoff

The first handoff loses information before engineering is even involved. Practitioners describe L1 escalating with "minimal information — often just a sentence like 'user can't access email' — forcing L2 engineers to spend 10-15 minutes gathering information before troubleshooting can begin," per an r/msp discussion of escalation context loss.

Ten to fifteen minutes sounds small. The cost is in what it signals. If L2 has to re-ask, the customer answers the same questions twice, and the record of what was already tried is split across two people's notes.

AI deflection has changed this stage too. Liveops' 2026 Resolution Gap Report surveyed 1,000 U.S. consumers and found 59% had to re-explain their issue after an automated channel failed, per Liveops. That is a consumer sample, not a B2B one. The pattern still applies. The bot had the whole conversation and passed none of it on.

Stage 3: Crossing From the Support System Into Jira

This is the boundary most teams underestimate. Zendesk and ServiceNow are built for customer conversations. Jira is built for engineering work. When a ticket crosses from one to the other, someone has to translate it.

Both platforms connect to Jira. Zendesk has a native Jira integration that links a ticket to an issue, and ServiceNow offers a Jira spoke through IntegrationHub. The link carries the ticket ID and status. It does not carry the reasoning. The engineer opening the Jira issue sees a summary written by someone in support, not the customer's environment, version or history.

Unito reports that L2 to L3 escalations take 60% longer when the teams work in different systems, per Unito's escalation metrics guide. Unito sells sync tooling, so read that figure with its source in mind. The direction matches what most support leaders see.

Stage 4: Waiting in the Engineering Queue

Once the Jira issue exists, it competes with roadmap work. Engineering teams plan in sprints. An escalated ticket from one customer is an interruption to that plan, and it gets treated like one.

The ticket usually waits for a specific person. At most enterprise software companies, two or three senior engineers understand how a given module behaves inside a given customer's setup. The queue is not really a queue. It is a line for those people.

This stage is where SLAs break quietly. The customer sees "escalated to engineering." Support sees a Jira status that hasn't moved. Nobody is doing anything wrong, and nothing is moving.

Stage 5: Reconstructing What Happened

When the engineer finally opens the issue, the real work starts. The question is no longer "what is the bug." It is "what happened inside this customer's environment, on this version, with this configuration."

Answering that means opening the logs, querying the database, checking the customer's configuration, reading the relevant code and searching past tickets for anything similar. Each lives in a different tool. Developers surveyed by Cambridge University and Undo named bug reproduction as the single biggest barrier to resolving failures faster, cited by 41%.

In BuildWright's conversations with enterprise engineering leaders, investigation accounted for about 70% of the time to resolve an escalated ticket. The fix took the other 30%.

Configured software makes this worse. One enterprise software company BuildWright works with runs its product as about 70 separate codebases, one per customer, each with its own database. The same symptom can have a different cause at every customer. That is why the reconstruction stage cannot be fixed with a better runbook.

Stage 6: Going Back to the Customer

Most reconstructions surface a question only the customer can answer. Which user? What time? Did anything change on their side last week? Each question goes from engineering to support to the customer and back, and each round trip can cost a day.

a16z's analysis of B2B support data found hard tickets routed straight to humans took 5.3 messages to resolve, against a 3.9 baseline, per a16z. When AI prepared the context before a human took over, the human needed fewer messages than the baseline. The context, not the person, made the difference.

Stage 7: The Fix

The fix is often small. A configuration value, a data correction, a one-line code change. Engineers describe it the same way across companies: the investigation took days, the fix took minutes. By this stage the hard part is already done.

How Do You Shorten Each Stage?

The right fix depends on which stage is losing the most time. Work through them in order:

  1. Intake. Make the escalation form ask for the customer, environment, version and steps already tried. A required field costs L1 thirty seconds and saves L2 fifteen minutes.
  2. The system boundary. Link Zendesk or ServiceNow to Jira, and mirror comments both ways, not just status. Engineers should not have to log into the support tool to see the customer's last reply.
  3. The queue. Track time-in-queue for escalated issues separately from sprint work. If it isn't measured, it will always lose to the roadmap.
  4. Reconstruction. This is the largest stage and the hardest one to fix with process. Runbooks help with known issues. They do not help when the cause is specific to one customer's configuration.
  5. Customer follow-up. Ask every question the investigation might need in one message, not one per day.

What About Automating the Investigation Itself?

Process fixes shorten stages 1, 2, 3 and 6. Stage 5 is different. Reconstruction is not a handoff problem. It is a search across code, logs, data and past tickets that someone has to do before the fix can start.

BuildWright does that search automatically. When a ticket escalates, it investigates across the customer's code, logs, database and past resolutions in read-only mode, then posts a diagnosis on the ticket before an engineer opens it: the likely root cause, the evidence behind it, what was ruled out and the recommended next step. The engineer still makes the call. BuildWright does not change code. It works alongside Zendesk, ServiceNow and Jira, not instead of them.

Last updated November 2026.

FAQs

What is a support-to-engineering escalation?

A support-to-engineering escalation is when a customer ticket can't be resolved by the support team and is handed to the engineers who own the code. It usually happens at L3, after L1 has triaged the ticket and L2 has tried known fixes. In most companies the ticket stays open in Zendesk or ServiceNow while a linked issue is created in Jira for engineering.

How do you connect Zendesk or ServiceNow to Jira?

Zendesk offers a native Jira integration that lets an agent create or link a Jira issue from a ticket and see its status. ServiceNow connects to Jira through the Jira spoke in IntegrationHub. Both sync the link and status. Neither carries the investigation context, so teams usually add a structured escalation template on top.

What should an escalation to engineering include?

A good escalation includes the customer and account, the product version and environment, any customer-specific configuration, exact steps to reproduce, relevant timestamps and log excerpts, what support already tried, and the business impact or SLA at risk. Missing any one of these usually means a round trip back to the customer.

Does AI deflection reduce escalations to engineering?

AI deflection reduces simple tickets, not hard ones. Susana de Sousa put it this way in Plain's 2026 support engineering piece: "AI absorbs the volume, humans inherit what's left, and what's left gets harder every quarter." As the easy tickets disappear, the share of the queue that needs engineering grows.

How much does an escalated ticket cost?

Unthread estimates $200 to $500 per escalated ticket across the SaaS companies it surveyed. For enterprise software with per-customer configuration, the cost is usually higher, because reconstruction takes longer and the engineers doing it are the most senior on the team.

Conclusion

An escalated ticket loses most of its time in three stages: crossing into the engineering tracker, waiting for the right engineer, and reconstructing what happened inside one customer's environment. Better forms, linked systems and queue tracking shorten the first two. Reconstruction is the largest stage, and process alone does not shrink it.

Start by measuring time per stage on your last 20 escalations. The stage that dominates tells you what to fix first.

More from the BuildWright team

Get started

Grade BuildWright on your own escalations

Read-only access, personal data masked, running in your own cloud. Start on the sample app today, or bring a ticket your team already solved and judge what it finds.

Not ready for a call? Send us a note