Insurance claims processing is full of moving parts. Adjusters, third-party vendors, and multiple document systems. Most teams rely on RPA to move files between systems, copy data into spreadsheets, and flag missing documents. But every time the insurer updates its portal or the vendor rolls out a new release, the bot breaks. The team stops new work, opens a ticket, waits for a developer to rebuild the bot, and starts over. The backlog grows. The cost of maintenance keeps climbing. Meanwhile, the SOPs sit untouched, written in plain English, but only humans can follow them.
Why RPA breaks here
RPA bots in claims work by binding to exact UI elements: a specific button ID, an xpath for the policy number field, a CSS selector for the upload area. When the insurer rebrands, changes a column, or rearranges a form, those bindings become stale. The bot clicks the wrong field or skips steps. It halts. The team does not know until a human reviews a case or a user reports an issue. A common pattern in large insurers is that a single process that should take minutes ends up consuming hours of developer time each quarter, just to keep the bot alive. That is the maintenance treadmill. It is predictable, expensive, and completely avoidable.
What changes with computer use agents
- Agents see the screen instead of relying on brittle selectors. When a field moves or a label changes, they still find it.
- No selectors or xpaths to maintain. The agent reads the UI and reacts, just as an adjuster would.
- They recover from exceptions instead of halting. If a pop-up appears or a field is blank, the agent pauses and tries another path.
- Agents follow the SOP as written. A standard operating procedure in plain English is already a prompt. The agent can execute it directly.
- They work on legacy systems, Citrix, and virtual desktops where traditional RPA struggles to see the contents.
Selectors are brittle. Seeing is durable.
How to move without the risk
You do not have to rip out all RPA at once. Pick one high-pain process where UI changes frequently and exceptions are common. For example, move a recurring cross-system data entry task or a document collection workflow from a brittle bot to a computer use agent pilot. Run the agent alongside the existing bot for a week. Compare cost, uptime, and manual intervention. Then decide whether to expand to more processes. This phased approach lets you prove the value of computer use agents without disrupting the entire automation portfolio. For tasks that are high volume, stable, and fully backend, RPA may still be the right choice. The win comes from handling the long tail of processes that RPA cannot touch.
The future of insurance automation is not about more bots. It is about agents that see the screen, follow SOPs, and survive the messy reality of real systems. Book a demo with the Coasty team to see how computer use agents can replace brittle RPA with durable automation. https://cal.com/coasty/15min
Want to see this in action?
View Case Studies