All solutions

Healthcare & regulated

1 billing code change

One action worth checking.

Review the billing change, not patient data.

A billing change can affect claims and downstream records without the required administrative review.

HELD AT THE GATE

Billing code change — Hold for coding supervisor
Billing changes post in seconds. Runledge reviews them first.

The gate doesn't care how an action arrives — voice, chat, or API. It checks the write, and only the fields your rules need.

A limit for the consequential change.

ActionGateDecision / record
01

Routine fee-schedule fix

Allowed

Allow

mechanical corrections shouldn't wait on a human queue.

02

Billing code change

Held

Hold for coding supervisor

the code is what gets paid; changing it is a clinical-financial decision.

03

Disputed amount over $1,000

Held

Hold for billing supervisor

disputes are where errors and audits are born — a supervisor owns them.

04

Claim resubmitted for the third time

Held

Hold for billing supervisor [Team+]

repeated resubmission is how duplicate payments happen.

05

Billing or claims data sent outside the approved payer/clearinghouse list, or any production data action to an external destination

Blocked

Block

an approved billing action does not approve its data destination; production data must stay within the permitted boundary.

06

Claim submission carries a free-text notes field

Adjusted

Adjust: drop the notes field

the rule drops notes from the returned proposal; your integration must use that version after the re-check and must not submit PHI.

07

Voice agent creates a billing callback — claim reference and callback window only

Held

Hold for billing supervisor

the action arrives by voice, not API; the gate checks the same write either way — and the payload carries a claim reference and a time, never clinical content.

08

Referral created by an agent

Held

Hold for 1 reviewer

a referral starts care moving; the wrong provider or the wrong service is a detour the patient pays for, not the agent.

Runledge is not designed for PHI and doesn't sign BAAs today. Don't include PHI in action metadata; send only the fields your rules need.

Review requirements for this workflow

Held for review — owner email approval on Pro; Slack and Teams review on Team. Team supports up to 2 reviewers in one stage; Growth adds a second approval stage with up to 5 reviewers per stage. Named finance leads, adjusters and supervisors must be eligible workspace reviewers; Runledge does not verify professional licences.

Rolling-count and spend-cap Holds, and entity-counting Holds, require Team or above. Start free to test policies in Shadow; the review workflows shown require the applicable paid plan. Shadow is delayed, aggregate and report-only, with a free 14-day shadow pilot per workspace; afterward Shadow Held, Blocked and Adjusted outcomes count toward the allowance.

One billable action is one recorded Held, Blocked, or Adjusted outcome; Allowed actions are free. Your integration must honor the decision and execute only the permitted version. Account, payee and destination checks use the fields and approved lists you supply, not independent bank or claims verification. Adjusted examples mask or drop fields before re-checking every rule; they do not guarantee safe downstream handling. Approval records are evidence of review, not a certification or an audit guarantee.

Security and data handling →

What's your scariest agent action?
Test it in shadow mode first.

Start free with the Developer plan — 10,000 actions every month. Start in shadow mode, then block actions when you trust the rules (or hold for review on Pro and above). Shadow is free during the 14-day shadow pilot for each workspace. After the 14-day shadow pilot, shadow Held, Blocked, or Adjusted outcomes count toward your plan like enforcing mode does.

Start free

Where this goes: the same rules and signed records, between companies.

Need a security review, in-VPC deployment or a custom contract? Leave your work email and we will reply within one business day.