HR Shared Services Automation Without Brittle Bots
HR shared services teams spend half their time on repetitive workflows. Onboarding, benefits enrollment, leave approvals, and document triage. Most organizations are already running bots on these processes, but the bots are breaking more often each month. The development team is constantly rebuilding flows. The backlog of fixes is climbing. The process owners say the bots can only run on stable, desktop-only screens. The result is a maintenance treadmill that burns engineering hours and leaves the business frustrated. This is the classic RPA problem in HR: brittle bots that break on every UI change and SOPs that only humans can follow.
Why RPA breaks here
Traditional RPA tools like UiPath, Automation Anywhere, and Blue Prism rely on selectors, XPath statements, and object IDs. These are the technical instructions that tell the bot exactly where to click and what text to look for. HR systems change. The UI is refreshed. A new version of the benefits portal is deployed. When the selector no longer points to the correct element, the bot fails. The error is logged and sent to the development team. The engineer has to open the process, update the selector, test, and redeploy. This cycle can repeat multiple times in a single month. Gartner estimates that unstructured, exception-heavy processes account for 40 to 60 percent of total automation effort, with a significant portion of that effort spent on maintenance and rework. In HR, where screens and workflows shift frequently, that maintenance burden can easily consume more than half of an automation team’s capacity. The bot becomes a moving target rather than a stable asset.
What changes with computer use agents
- ●Survives UI changes: The agent sees the screen and reacts to what it actually looks like, not to a fixed selector.
- ●No brittle selectors: There are no XPath or object references that break when the app is updated.
- ●Recovers from exceptions: If the bot lands in an unexpected state, it can reason about the situation and try an alternative path instead of halting.
- ●Follows the SOP as written: A standard operating procedure in plain English maps directly to the agent’s behavior, with no flowchart bot to build and babysit.
- ●Works on legacy and Citrix: Because the agent interacts with the visual desktop, it can operate on virtualized environments and legacy applications where RPA struggle to maintain reliable selectors.
Think of an RPA bot as a set of instructions for a fixed screen. Think of a computer use agent as a worker who can see the screen, read the SOP, and keep going when the layout changes.
How to move without the risk
Moving from brittle RPA to computer use agents does not require a full replacement of your automation stack. Start with one high-pain process that is slow to change. Identify the steps that are documented in a written SOP. A bot can handle parts of the process, but the team is spending too much time fixing it when HR updates the portal. Run a pilot with a computer use agent on that same process. The agent can follow the SOP, interact with the same screens, and recover when the UI changes. Measure the time saved on maintenance versus the time spent on the pilot. If the agent reduces the number of fixes and enables the process to run on multiple HR screens, expand the use case to related workflows. Over time, you can gradually shift more of the HR portfolio to agents, while keeping RPA for the high-volume, stable, backend tasks where it still fits well. The goal is to reduce the maintenance burden and increase the number of processes that can handle change without a developer intervention.
HR automation should be about freeing people from repetitive work, not about rebuilding bots every time the portal updates. Computer use agents let you follow SOPs directly, adapt when the UI changes, and recover from exceptions instead of halting. If your HR team is stuck on a maintenance treadmill, it is time to explore a more durable automation approach. Book a demo with the Coasty team to see how agents can work with your HR processes.