Blog · All

AI agent, RPA, or a macro? Picking the right tool for repetitive screen work.

A practice manager asks for help with a task that eats the front desk's morning. Three answers come back from three directions. Record a macro. Buy RPA. Build an AI agent. All three are sold for the same repetitive screen work, and the words get used as if they were interchangeable. The useful distinction is how much variation in the input each one handles, and how much of the workflow has to be written down for it to work.

A macro: a recording of your steps

In Excel, you turn on the macro recorder, do the task once, and the recorder saves what you did as code that can be replayed. Microsoft's own description is that the recorder captures almost every move you make, including clicks you did not mean to make, and that fixing a mistake means recording again or editing the code by hand.

A simple recorded macro works best when the task follows a predictable sequence: the same cells, the same commands, the same layout every time. Reformatting a report that always arrives in the same shape is a common fit. More variation usually means adding code and maintaining it. Programmed macros can inspect values, branch and work across Office applications, but at that point someone is writing and keeping software, not pressing record.

RPA: a specified workflow across applications

Robotic process automation is software that follows a workflow someone has specified, step by step, across several applications: sign in here, read these fields, type them there, run on a schedule. It is a real category with real money behind it. In August 2022, Gartner forecast worldwide spending on RPA software at $2.9 billion for that year, 19.5 percent above 2021, and $3.4 billion for 2023, and gave the plain reason that organisations still have a lot of repetitive manual work.

Worldwide spending on RPA software: Gartner forecast, August 2022
  • $2.9 billionForecast spending on RPA software in 2022
  • 19.5%Forecast growth over 2021
  • $3.4 billionForecast spending in 2023

Source 1

RPA fits a defined workflow with information in a predictable format. Moving records between two internal systems on a nightly schedule is a typical job. Modern platforms can find screen elements by their labels rather than fixed positions, handle errors in configured ways, and read text from images, so a changed screen or a scanned page is not out of reach. What those cases cost is specification and maintenance: each new document layout, each changed portal, each exception path is something a person has to describe to the tool and keep up to date. The same Gartner release notes that growth was slowing and that vendors were building beyond RPA alone, which is a fair description of where the category sits.

An agent: interprets, then follows your rules

An agent, as we build them, is software that signs in to the systems your team already uses, with its own login, and does one repetitive job inside them by following rules your team wrote down with us.

What the agent adds is interpretation at the front of the task. A faxed prescription, an emailed invoice, a referral in another clinic's layout: the agent reads the document and finds the fields by their meaning and context, rather than relying only on a fixed position or a single layout. The same applies to the screens it works in. That is the part of the work where a macro or a scripted robot needs a new specification for each variation.

Everything after that is workflow, and we build it in deliberately: the agent enters the fields, reads each one back and compares it with the source before it saves, and when a value does not match or the rules do not cover what it is looking at, it stops on that item and hands it to a person with the reason. Every run is recorded. None of that is unique to agents. Source checks, clear rules and human handoffs can be built into a script or an RPA workflow too, and good ones have them. The difference is that the agent handles the varied inputs those checks are applied to without a person first describing every variation.

How to tell which one you need

Ask four questions about the task.

  1. How much does the input vary? Same layout every time points to a macro. Predictable fields across applications points to RPA. Documents and screens in formats you do not control point to an agent.
  2. Is the workflow defined, or does it depend on what arrives? A fixed sequence can be specified once. If the sequence changes with the document, the tool has to interpret before it acts.
  3. Does each entry need to be checked against a source before it is saved? Ask this of every solution. A wrong entry has a cost, and the check has to be designed in whichever tool you pick.
  4. What happens when something does not match? Ask this of every solution too. The answer should be that the item goes to a person with the reason, not that the run fails silently or guesses.
Which tool fits

A recorded macro or RPA often fits

  • A short, predictable sequence inside one program (a recorded macro)
  • A defined workflow across applications with information in a predictable format (RPA)
  • Screens and inputs that change rarely, with someone to maintain the script when they do

An agent is useful when

  • Interpreting varied documents or screens is a central part of the work
  • Prescriptions, referrals, invoices or forms arrive in formats you do not control
  • The workflow has to be described in rules your team owns, and reviewed when the rules do not cover a case

The tools can also be combined. An agent can read the document and an existing script can do the entry, and a macro can still tidy the report at the end.

What stays with your team

Your team keeps the decisions that require its authority. The pharmacist's verification, the office manager's call on an inactive plan, the bookkeeper's approval of a bill: those stay where they are whichever tool does the typing. The tools differ in how much reading, entry and checking they carry before that point, and in how much has to be written down for them to carry it.

If a task on your team's desk is being offered a macro, a robot and an agent at once, tell us about it. We will look at one workflow with you and say plainly which of the three it is, and whether we are the right people to build it.

Tell us the task

Sources

  1. Gartner, press release, "Gartner Says Worldwide RPA Software Spending to Reach $2.9 Billion in 2022", 1 August 2022. Forecast spending of $2,854 million in 2022, 19.5 percent growth over 2021, and $3,352 million in 2023. https://www.gartner.com/en/newsroom/press-releases/2022-08-1-rpa-forecast-2022-2q22-press-release
  2. Microsoft Support, "Automate tasks with the Macro Recorder" (Excel). The recorder records steps as Visual Basic for Applications code, captures almost every move including unintended clicks, and VBA can automate within and between Office applications. https://support.microsoft.com/en-us/office/automate-tasks-with-the-macro-recorder-974ef220-f716-4e01-b015-3ea70e64937b

This article is general information about automation tools. It is not legal, financial or technical advice for any particular business.

Book a demo