Agents in regulated work: drafts, not decisions

“Chase the three clients still missing documents.” For an agent, writing those three emails is the easy part. Whether anyone keeps using it depends on everything around the writing: whose name the emails go out under, what the agent was allowed to read to write them, and who notices when one of them is wrong.

In finance and healthcare, those aren’t details. They decide whether an agent becomes part of the week or gets switched off after its first mistake.

Where agents stall

It works for “the team”. An agent with no owner produces work nobody is responsible for reviewing. Drafts pile up in a shared queue, and the team goes back to doing the work by hand.

It can send on its own, so nobody lets it. An agent that writes to clients or patients by itself turns every message into a risk. The quickest way to remove the risk is to stop using the agent.

It was given access “just in case”. Read access to the whole shared drive, the accounting system, the patient record. A security review stops it, and it should.

It lives in a new window. A chat tool nobody opens on a busy day. The agent’s work waits there, next to everything else nobody opened.

Nobody can say what it did. A controller or a practice manager asks which documents it read and what it sent, and there’s no answer. That’s the first question anyone asks after a mistake, and it needs an answer.

What changes when control stays with your team

Every agent works for a named person. The intake coordinator, the AP lead, the relationship manager. They ask for the work, and they decide what happens to it.

It drafts; the person sends. Anything that leaves your team goes out as a draft for that person to approve, unless a rule you agreed in writing says otherwise. An appointment reminder built from an approved template can go out on its own. A new message to a patient or a client can’t.

Access is scoped to the task. The referral inbox and the intake queue, not every system the practice runs. It’s granted one task at a time, and you can revoke it.

It works where the person works. Outlook, Teams, the intake queue. The draft arrives where the decision gets made.

Everything is on the record. What it read, what it drafted, who approved it, and when. That record is what lets a controller or a compliance lead trust the agent, and it’s what you need when someone asks why.

What this looks like

These are examples of the shape of the work, not client results.

A referral missing insurance details. The agent checks the referral against the fields your intake team requires, drafts the request to the referring practice, and puts it in the coordinator’s queue. The coordinator sends it. Scheduling stays with your team, and clinical triage stays with clinicians.

A prior authorization packet. The agent gathers the documents the payer’s checklist asks for, puts them in order, and flags what’s missing, like a signed order or a form the payer added this year. Your staff review the packet and submit it.

Missing client documents. “Chase the three clients still missing documents” becomes three short, specific drafts, each naming the document that’s missing and when it’s needed, for the relationship manager to send or edit.

None of these needs an agent that acts on its own. Each needs one that gathers and checks well, and hands a person something they can decide on in a minute.

What we run, and what stays with you

We run the agent. We monitor it, handle the exceptions it raises, and update its rules when your process changes. Your team keeps the decisions: what gets sent, recorded, paid or submitted, and anything clinical.

That makes for a less impressive demo than an agent that does everything itself. It’s also the version a controller or a practice manager will let near their work. How we handle financial and patient data covers access, logging and the agreements we work under. Approval points that don’t become the new bottleneck covers how to keep those approvals fast.