IT service desks run on two things: rigid scripts and human-only procedures. Scripts die when applications update. Procedures sit in PDFs that sit in shared drives nobody reads. The result is a backlog of tickets, high repeat rates, and a team that constantly puts out fires instead of preventing them.
Why RPA breaks here
Traditional RPA tools like UiPath, Automation Anywhere, and Power Automate bind to selectors, xpaths, or object IDs. When the ITSM UI changes, or when a vendor updates a portal, the bot stops working. Analysts estimate that about 30 percent of RPA maintenance time goes into rebuilding bots after minor UI changes. In a high-volume service desk that means developers spend more time chasing down broken flows than building new ones. On top of that, RPA bots halt on exceptions. A missing field, a slightly different error message, or a system that goes down forces a human to intervene. The process is brittle, expensive, and hard to scale across multiple applications or environments.
What changes with computer use agents
- They survive UI changes because they see the screen, not selectors.
- No brittle selectors or object IDs to maintain.
- They recover from exceptions and unexpected states instead of halting.
- They can follow an SOP written in plain English without a designer building a flowchart bot.
- They work across any app including legacy systems, Citrix, and virtualized desktops where RPA struggles.
Computer use agents treat the screen like a human does: they know where things are, they read what appears, and they act when the result matches expectations. That is the durable way to automate IT service desk work.
How to move without the risk
You do not have to rip out all your existing RPA at once. A practical path is to pick one high-pain, SOP-heavy process that is currently riddled with exceptions and UI fragility. Examples include password resets, account provisioning, or ticket triage. Pilot a computer use agent on that process, measure time saved and repeat rates, then expand. Keep your bots that handle high-volume, stable, back-end tasks. They still make sense there. Use computer use agents for the changing UIs, exception-heavy workflows, and procedures that are best expressed as steps a human would follow.
Your IT service desk can move from fragile scripts and unwieldy procedures to a more durable way of working. Book a demo with the Coasty team to see a computer use agent in action on a real desktop at https://cal.com/coasty/15min .
Want to see this in action?
View Case Studies