Resolution Agent

A junior agent, unfamiliar problem

Follow a newer agent taking a problem they have never seen from first contact through to a closed ticket. Ascendo suggests the next diagnostic step, pulls the matching history from similar cases, and keeps them moving — instead of the escalation that would otherwise happen in the first four minutes.

  • The next diagnostic step, not a wall of articles
  • Matching history from cases already resolved
  • Fewer escalations leaving Tier 1
  • Ramp measured in weeks rather than quarters

Watch the full tour

Verify your work email once and every research paper, case study and product tour on ascendo.ai opens, right here, without leaving the page.

  • Takes about 30 seconds
  • Work email only, no spam

The escalation happens before the diagnosis starts

A new agent facing an unfamiliar fault has two options and both are bad. Guess, and risk making it worse in front of a customer. Or escalate, which is safe, slow, and consumes a senior engineer for something they will close in four minutes.

Most escalate, and they are right to. That is how the majority of Tier 1 volume ends up on the desk of the five people who can least afford it — and training does not close the gap, because the gap is judgement built from cases.

Three cards covering what a new agent can do with an unfamiliar fault — guess, escalate, or be trained more — each marked with what it costs and what the agent is left knowing afterwards.
Escalating is the correct choice each time, which is exactly how most Tier 1 volume ends up on five people’s desks.

Keeping a newer agent moving

The fourth step matters as much as the first three.

  1. Step 1

    Suggest the next step

    Not a list of possibilities. The step worth trying next on this symptom, so an agent without the instinct still starts in the right place.

  2. Step 2

    Show what resembles it

    Cases with the same symptom on the same product, including what was tried and what worked.

  3. Step 3

    Explain where it came from

    Each suggestion carries the case or document behind it, which turns following one into learning something.

  4. Step 4

    Escalate when it should

    Some cases genuinely need a senior engineer. What changes is that the escalation happens after the elimination rather than instead of it.

Four stages: a single next step to try, cases with the same symptom on the same product, the source behind each suggestion, and an escalation that fires after the elimination rather than instead of it.
The fourth stage is not a fallback. Some faults genuinely need a senior engineer, and pretending otherwise is how customers get hurt.

Why this moves ramp time rather than handle time

The operational effect lands on your senior engineers, not on the individual ticket.

A next step beats more information

A junior agent with a hard fault does not need more to read. The useful output is the single next thing to check, which is the form knowledge takes in an experienced head.

They inherit the organisation’s cases

The difference between a new agent and a good one is largely how many faults they have seen. Retrieval across resolved cases hands over a version of that on day one.

The senior queue gets shorter

Every case closed without escalating is capacity returned to your actual constraint — usually a larger effect than minutes off any individual ticket.

A case view giving a new agent one next step to try, two resolved cases with the same symptom on the same product, the manual section behind the suggestion, and the elimination completed so far.
One instruction at the top, and the two closed cases underneath it that are the reason it is that instruction.

Why the usual approaches fall short

Three of these give a new agent more to read. The fourth removes the need to learn.

Classroom training and shadowing

Necessary, and it teaches products rather than judgement.

A knowledge base search

Returns documents to somebody who cannot yet tell which one applies.

Escalating early by policy

Safe, and it turns your senior engineers into the Tier 1 queue.

Scripts and decision trees

Work for the faults somebody anticipated and collapse on anything phrased differently.

Two columns comparing classroom training, knowledge base search, escalating early by policy and scripted decision trees with a single suggested next step drawn from resolved cases.
All four are reasonable responses to an agent being stuck, and none of them leaves that agent better at the job afterwards.

What things are called

Elimination is the word that describes what a diagnosis mostly is.

Next best step
The single diagnostic action worth taking now, rather than a list of possibilities to weigh.
Similar case
A resolved ticket matched on symptom and product rather than on shared wording.
Elimination
Ruling out candidate causes in order, which is what a diagnosis mostly consists of.
Escalation
Passing a case to a more senior engineer. Still correct sometimes, and much cheaper after elimination.
Ramp
The time it takes a new agent to reach normal productivity.

Frequently Asked Questions

No, and it should not try to. Some cases genuinely need a senior engineer. What changes is that the escalation arrives with the elimination already done, so it costs that person four minutes instead of forty.

Resolution Agent

Look at what your Tier 1 escalates

Take the cases your junior team escalated last month. We will show you which of them would not have needed to leave Tier 1 at all.

Talk to us