Every large IT organization runs dozens of service desk ticket workflows on RPA. A user submits a request, a bot logs into a portal, fills out a form, clicks a button, and closes the ticket. On paper this looks efficient. In practice the bots break every time the HR or asset management application updates its layout, when a new vendor portal launches, or when a legacy Citrix session changes its window name. The maintenance backlog grows, developers spend more time fixing selectors than building new automations, and managers watch a tool they invested in slowly become a liability.
Why RPA breaks on IT service desk work
Traditional RPA binds to brittle technical identifiers like selectors, xpaths, or object IDs. When a UI refreshes or a vendor changes a field label, the bot can no longer find its targets and stops working. Industry benchmarks show that 30 to 40 percent of RPA maintenance effort is spent on these selector updates and rewrites. For a service desk with dozens of bots spanning HR, finance, and vendor portals, that translates to hundreds of bot rebuilds per year. Every rebuild carries a cost: developer hours, testing cycles, and the risk of introducing new bugs. The process becomes a treadmill where the more you automate, the more you have to fix.
What changes with computer use agents
Computer use agents do not rely on selectors. They see the screen, read the text, and act like a human would: move the mouse, click buttons, type in fields, and read the resulting UI. This gives them several key advantages for IT service desk processes.
- Survives UI and app updates without rebuilding the bot
- Does not depend on brittle selectors or object IDs
- Recovers from exceptions and unexpected states instead of halting
- Follows the SOP as written, in plain language
- Works across any application, including legacy systems and Citrix sessions
Selectors are brittle. Seeing the screen is durable.
A realistic pilot for your service desk
You do not have to rip out all your existing RPA to start. Pick a single high‑pain workflow where bots break often and reworking them is costly. Common candidates include onboarding employee accounts, provisioning software licenses, or closing vendor invoices. Work with the process owner to document the SOP in plain language, not as a flowchart. Then run a pilot using a computer use agent. Compare the time to implement, the frequency of failures, and the total cost of ownership against the same process running on your current RPA bots. Use those metrics to decide where to expand and where RPA still makes sense for high‑volume, stable backend tasks.
Where RPA still fits
RPA is still very effective for high‑volume, deterministic processes where the UI is stable and the inputs are predictable, such as batch data entry or repeated API calls. The real opportunity in IT service desk automation is the long tail: workflows that touch multiple systems, change frequently, and rely on human‑written SOPs. Computer use agents are built to handle that complexity and the exception handling that comes with it.
If your IT service desk is spending more time fixing bots than delivering on automations, it is time to look beyond selectors to agents that can see the screen. Book a demo with the Coasty team to see how computer use agents can follow your SOPs, survive UI changes, and reduce the maintenance burden on your automation program. Visit https://cal.com/coasty/15min to schedule a conversation.
Want to see this in action?
View Case Studies