IT Support Automation: What Production Deployments Show

Yes — and the documented resolution rates are specific enough to plan against. trivago's internal IT chatbot auto-resolves 35% of requests inside a company where AI adoption passed 90% of employees and the measured saving reached 16 workdays per person per year. Agoda's GenAI stack handles 45% of internal tech support tickets, with its AskGoda assistant taking half of everything incoming. At the vendor end, Aisera reports an 81% auto-resolution rate for one customer, and Moveworks customers report over 30% of employee issues auto-resolved at 96% employee adoption. Smartsheet cut helpdesk volume 30% within weeks of a company-wide rollout that had 49% of employees actively using the platform in two and a half weeks.

Read the spread honestly: a third resolved is the credible floor for a grounded agent on real ticket mix; the high-end figures come from mature deployments with connectors doing real work — resets, access, provisioning — not just answering. And notice which number recurs next to every resolution rate: adoption. An internal agent nobody opens resolves nothing, which is why the deployments that work live where employees already are and earn usage before they earn autonomy.

Grounding — and the record's best-documented failure is also its best-documented recovery. Grab's first attempt was the obvious one: feed the platform documentation to a chatbot. It failed for the era's plainest technical reason — the context window couldn't hold the docs, heavy summarisation left it covering a handful of FAQs, and embedding search didn't rescue it. The instructive part is what Grab did next: instead of patching a narrow support bot, they built GrabGPT, a general internal assistant — 300 users on day one, three thousand within three months. Sometimes the fix for a failed helpdesk bot is admitting the helpdesk bot was the wrong scope.

The second failure is action scoping, and it cuts both ways. An agent wired too broadly into identity and provisioning systems is a security incident waiting for a prompt; wired too narrowly, it can diagnose your problem and then apologise for being unable to touch it — which is precisely the half-capable state that adds a step before the human. The deployments that resolve at the high end all solved this with scoped, audited connectors for the boring high-volume actions first: password resets, access requests, standard provisioning. Safe actions, then more actions — never the reverse.

Slack tops the recurrence list by a wide margin, and that's the finding in miniature: the successful agents live in the chat surface employees already have open, not in a portal they must remember. Behind the front door, the record splits into three stacks. Dedicated employee-support platforms — Aisera and Moveworks most visibly — sell resolution rate and ship with the connector libraries that make action possible. The ticketing systems of record, ServiceNow above all, are what everything must read from and write to. And the build stack — Claude, Amazon Bedrock, LangChain — appears because a meaningful slice of this record is companies that built their own internal assistants rather than buying one.

Enterprise search deserves its own mention: tools like Glean recur because half of IT support is finding the answer that already exists, and an agent is only as good as its retrieval. As always on this site, recurrence reflects who deployed and who published rather than a ranking — and the fit test for this category is concrete: does it live in your chat, connect to your identity and ticketing stack, and show you what it did.

This record genuinely documents both paths at company scale, which most categories don't. The buy case is straightforward: employee-support platforms arrive with the grounding machinery, ticketing integrations and — critically — the scoped action connectors that take years to harden, and their documented resolution rates are the category's highest. If IT support is a cost centre you want smaller, that path is proven and fast.

The build case here is unusually strong too, but notice what the builders actually built: not helpdesk bots, but internal AI platforms where support became one surface among many. Grab's GrabGPT, Agoda's 204 deployed GenAI applications, trivago's company-wide assistant programme — in each, the support win rode on a broader internal-AI investment with its own momentum and its own team. The distinction matters for planning: building a standalone support agent gets you Grab's failed first attempt; building an internal platform gets you their second.

So the decision inputs: if you have (or want) an internal AI platform strategy, support is an excellent first surface for it and the record shows the way. If you don't, buy the platform — and judge vendors on the three things this record's winners share: chat-native presence, real action connectors, and adoption numbers from reference customers, not just deflection claims.