Resolution Agent

Using Ascendo in ServiceNow

A practical walkthrough for teams who have standardised on ServiceNow and need to know exactly what changes in the agent workflow before committing to a pilot: where suggestions appear, what an agent does with one, and what ends up written back to the incident.

  • What changes in the agent workflow, step by step
  • Accept, edit or discard — the agent decides
  • What gets written back to the incident
  • For teams whose ITSM process is already settled

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

Nobody can approve a change they cannot picture

Teams that have standardised on ServiceNow have spent years getting the process right, and the people who own it are appropriately conservative about changing it.

What a change board wants is not whether the AI is good but a walkthrough: what appears, where, what the agent does with it, and what ends up in the record. Without that, everybody agrees it looks useful and nobody can describe the change precisely enough to approve it.

Four questions from a change board, an ITSM owner, a support lead and reporting funnelling into a capability demonstration, which produces a verdict of useful but unapprovable.
A demo answers what the AI can do. None of the four people on the left of this diagram were asking that.

What actually changes for an agent

Read this as the before-and-after your change board is asking for.

  1. Step 1

    The incident opens as it always did

    Nothing about creation, assignment or the queue changes. The agent opens the same record in the same place.

  2. Step 2

    Suggestions appear against it

    The likely resolution, similar incidents and a drafted update appear alongside the record.

  3. Step 3

    The agent accepts, edits or discards

    Nothing is applied automatically. The agent judges the suggestion, adjusts it, or discards it where it does not fit.

  4. Step 4

    The result is written to the incident

    What the agent used ends up in the record, so your reporting sees what it always saw.

Four stages showing creation, assignment, queue and SLA unchanged, suggestions added against the record, the agent accepting, editing or discarding, and the result written back to the incident.
Only the middle two stages are new. The first and last are the workflow the team already runs.

Why this is a smaller change than it sounds

Three things a change board normally wants confirmed in writing.

The workflow is unchanged around it

Creation, assignment, escalation, approvals, SLAs and reporting all work exactly as today. What is added sits inside that process rather than alongside it.

The agent stays the decision maker

Every suggestion is a proposal. Nothing is applied or sent without a person choosing it, and that choice becomes the signal for the next one.

The record stays complete

What was used is written back, so the incident tells the whole story. That is what keeps ServiceNow authoritative and your reporting honest.

A nine-row table of the ITSM process showing what happens today and what happens with Ascendo, with seven rows marked unchanged and two carrying a suggestion and a draft.
Nine process steps, two of them different — the whole change written the way a change board asks for it.

Why evaluations stall

Each of these answers a question nobody was blocked on.

Evaluating on capability alone

Shows what the AI can do, not what changes for an agent.

Piloting in a separate tool first

Tests the model and not the integration, which is what actually decides adoption.

A proof of concept on synthetic data

Proves the pipeline runs, and says nothing about whether it helps on your incidents.

Rolling out to everyone at once

Removes the ability to compare, so afterwards nobody can say whether it worked.

Two columns setting how AI evaluations usually run against what a change board is actually able to approve.
A held-back group is the difference between knowing it worked and believing it did.

What things are called

The words that will appear in the change request.

Incident
The ServiceNow record an agent works.
Agent workspace
The ServiceNow interface your support agents use day to day.
Suggestion
A proposed resolution or draft, presented for the agent to accept, edit or discard.
Write-back
Returning what the agent used into the incident so the record stays complete.
Autonomy level
How much proceeds without a person, set per issue type. In this pattern the agent approves.

Frequently Asked Questions

They open the same incident in the same place, and suggestions appear alongside it. They accept, edit or discard, and what they used is written back. Creation, assignment, escalation and reporting are untouched.

Where this fits

AI Companion for ServiceNow

What appears in the incident, and what the suggestions are grounded in.

ServiceNow integration setup

The administrator’s half: scope, data flow, and what stays authoritative where.

Teradata case study

A published ServiceNow deployment, and what changed in their support operation.

More Resolution Agent tours

All tours

ServiceNow

Walk it through with your change board

Bring the people who have to approve it. We will go through exactly what changes in the agent workflow, and — just as importantly — what does not.

Talk to us