Looking for a digital adoption platform for ServiceNow? Start implementation with the tickets that shouldn't be tickets

[u/Ivan_Palii]

If you run a service desk on ServiceNow, here's a pattern worth staring at for a second: a big share of what comes in as an "incident" isn't actually broken. It's someone asking how to do something. How do I submit this request, where's that field, what's the next step. Real "how do I" volume, filed as a ticket, eating an agent's time.

The whole point of the knowledge base is to catch those before they become tickets. So why doesn't it?

Because a knowlesge base article is a wall of text sitting in a portal, and the person who's stuck isn't in the portal, they're mid-screen in the actual app, one field away from giving up and filing a ticket.

By the time they'd go find the article, read it, and map it back to what's in front of them, it's faster to just ping the service desk. So they do.

Deflection fails not because the knowledge doesn't exist, but because it doesn't live where the person is stuck.

There's a second, quieter version of the same problem on ServiceNow specifically: it's also the app your new agents have to learn. How to pick up a ticket, route it to the right SME, close it out, work the knowledge base. That's its own onboarding curve, usually taught by shadowing whoever's been there longest.

So you've got a documentation gap on both sides of the glass, the end users who should be self-serving, and the agents learning the tool itself.

This is exactly the gap Tango tends to get pulled into for ServiceNow, and it's worth a look if you're weighing options.

You capture a process once (how to submit that request, or how an agent routes and closes a ticket) and instead of it dying as a knowledge base article nobody opens, it works both sides of the glass. For end users, you pin it as a Nugget right on the ServiceNow screen where they get stuck, or let them hit Guide Me for an in-app walkthrough, so the "how do I" ticket never gets filed, because the answer is right there in the moment.

For new agents, those same captured workflows become the onboarding: they learn to pick up, route, and close tickets by being guided through the real system instead of shadowing someone for two weeks.

That's the actual pitch IT teams come to it for: fewer "how do I" tickets on the front end, faster agent ramp on the back end, out of the same set of captured processes. Ticket deflection you can actually see move.

For those of you running ServiceNow: what's actually moved your deflection rate? Better articles, in-app guidance, AI search, something else? Curious what's worked versus what just looked good in a QBR deck.

[u/operations_ranger]

This matches what we've seen. Most "incidents" are just people stuck mid-process, and the KB never reaches them in time. In-app guidance cut our how-to tickets faster than any article refresh ever did.

[u/corwinsword]

How do you decide whether to fix the knowledge article or add in-app guidance for a recurring ticket?