Agents (Early Access) · Use case
An agent that checks insurance eligibility for your upcoming appointments each morning, then handles each patient one of three ways — it files a note when coverage is good, emails the patient when something's off, or flags a teammate when it isn't sure.
Beta note: This article covers the Keragon Agents early-access release. Behaviour, limits, and UI may change during the early access period; this page is updated on a rolling basis as we learn from early adopters.
| Who it's for | Front-desk and billing teams who check coverage by hand before each visit. |
| Apps it uses | An EHR (like Athena Health), an eligibility-check tool (like pVerify), and secure email (like Paubox). |
| What fires it | A daily schedule. |
The scenario
Before every visit, someone on your team runs the same check by hand:
- Pull the chart.
- Read the insurance on file.
- Open the payer's portal.
- Type in the member ID.
- Read the result back.
- Note it, or pick up the phone and call the patient.
Take Maria Delgado — on the books three days out, with Aetna PPO on file. If her plan has lapsed and nobody catches it in time, the visit goes ahead anyway, and it comes back weeks later as a denied claim and a surprise bill she wasn't expecting.
How it works
The agent runs once a day and sorts each upcoming appointment into one of three outcomes. It only ever does one thing per patient — it never both notes and emails the same person.
Build the work list. Fetch the upcoming appointments and keep only the ones that still need an insurance check.
File the result. Save a short note to the patient's chart when their coverage is active and the name matches.
Reach out to the patient. Send a secure email when coverage has lapsed or the details don't line up, so the patient can fix it before the visit.
Flag a teammate. Hand it to a person whenever the agent can't safely tell who the patient is — it never guesses.
The adaptable agent
This is an example insurance-eligibility agent — a ready-to-use starting point. Use it as-is to see how it works, then change the highlighted fields so it matches how your practice runs day to day.
It's made of two kinds of pieces:
- Fixed pieces hold the agent's judgement and the safety rules that keep it reliable. Leave these as they are.
-
Fillable pieces (shown in
[BRACKETS]) are the details you swap for your own apps, inboxes, and timing.
Trigger
What starts the agent.
| Trigger | When it runs |
|---|---|
| Daily schedule | Once each morning. |
Instructions
Paste this into your agent. Change the highlighted [BRACKETED] fields to match your practice; leave the rest as it is.
Full instructions
TRIGGER CONTEXT
You run once a day. There's no single patient to look at — each run, you
build your own list: work out today's date, look [LEAD_DAYS] days ahead
(3 by default), and pull that day's appointments.
STEPS
1. Get the appointment list from [EHR_APP] for the target date.
2. Keep only the appointments that still need a check: ones that are still
booked (not cancelled) and that bill insurance. If there are none, see
"When something's unclear" below.
3. For each appointment, one at a time:
a. Find the patient in [EHR_APP] by their patient id (or by last name
and date of birth if all you have is a name).
b. Read the insurance on file: payer, member id, name on the plan, plan type.
c. Check eligibility with [ELIGIBILITY_APP] using the patient's name,
date of birth, payer, and member id.
d. Decide which one of the three outcomes fits, and do just that one:
• Coverage is active and the name matches - save a short note to the
chart (payer, plan, dates, and copay if it's returned). Don't email
the patient. (A child correctly listed under a parent's plan still
counts as a match — save it.)
• Coverage is inactive, expired, or terminated, or the name or date of
birth clearly doesn't match - send one secure email through
[SECURE_EMAIL_APP] asking the patient to confirm or update their
insurance before the visit. Don't save a note.
• Anything you're unsure about - hand it to a person; don't guess.
This includes confusing plan types, the plan on file disagreeing
with what the check found, no insurance on file, a payer you can't
find, or a result you can't read. Email [STAFF_INBOX] with the
patient, the appointment, and what's unclear.
4. After the last appointment, send one short summary (how many were noted,
emailed, and flagged) to [STAFF_INBOX].
WHEN SOMETHING'S UNCLEAR
- No appointments that day - you're done. Note "nothing to check today" and stop.
- More than one patient matches - don't pick one and don't run a check. Add
them to the flag email and move on.
- No insurance on file - flag a teammate.
- A check fails for one patient - try it up to 3 times; if it still fails,
flag that patient and keep going.
- Never both save a note and email the patient for the same appointment.
WHEN YOU'RE DONE
- Every appointment ended up in exactly one outcome (noted, emailed, or flagged).
- Each note is saved, each email is sent, and the summary has gone out.
GUARDRAILS
- Try a failed step up to 3 times before stopping.
- Handle one appointment at a time.
- When the run is finished, stop.Tools to select
Tools are the actions you let your agent take inside your apps.
| Role | What we used here | What it's for |
|---|---|---|
| Trigger | Daily schedule | Starts the agent each morning. |
| EHR / practice system | Athena Health — get appointments, find patient, read insurance, save a chart note | Where the agent reads appointments and insurance and saves the note. |
| Eligibility check | pVerify — run eligibility check | Confirms whether the coverage is active. |
| Secure email | Paubox — send email | Sends the patient message and the teammate flags. |
Swap any of these for the equivalent tool your practice already uses.
What to fill in
These are the only things you change so the agent fits your practice. Everything else stays the same.
| Field | What to put | Example |
|---|---|---|
[EHR_APP] |
The EHR or practice system you use | Athena Health |
[ELIGIBILITY_APP] |
The tool you use to check eligibility | pVerify |
[SECURE_EMAIL_APP] |
The secure email tool you use | Paubox |
[STAFF_INBOX] |
Where flags and the daily summary should go | billing@yourclinic.com |
[LEAD_DAYS] |
How many days ahead to check | 3 |
What it produces
Every time it runs, the agent sorts each patient into one of three outcomes, based on what the eligibility check finds:
| Outcome | What the check found | What the agent did | Why |
|---|---|---|---|
| Noted on the chart | Coverage is active and the name matches — Maria Delgado, Aetna PPO, $30 copay. | Saved a short note to her chart with the plan and copay, and sent no email. | When everything checks out, the visit just needs a note on file — there's nothing for the patient to do. |
| Emailed the patient | Coverage has ended — Frank Osei's UnitedHealthcare plan was terminated on 05/31. | Sent Frank one secure email asking him to confirm or update his insurance before the visit, and saved no note. | When coverage has lapsed, the patient is the one who needs to act, so the agent reaches out to them. |
| Flagged a teammate | Two patient records match the name on the appointment — "J. Nguyen", same date of birth. | Stopped, didn't run a check, and flagged a teammate to confirm who the patient is. | Checking the wrong person could expose another patient's information, so the agent never guesses who someone is — it asks a person. |
Chart note saved — see the full output
Chart note saved
"Eligibility verified 2026-06-25. Payer: Aetna PPO. Plan: PPO. Active 01/01/2026–12/31/2026. Copay $30."
Teammate flag — see the full output
Teammate flag
"J. Nguyen — 2 patient records match (same date of birth); needs someone to confirm who this is."
Try a variation
- "Check 7 days ahead instead of 3, so patients have a week to fix their coverage." (change
[LEAD_DAYS]) - "When coverage has ended, also let billing know, not just the patient." (add
[STAFF_INBOX]to the email step) - "Send the daily summary to two inboxes — front desk and billing." (list both in
[STAFF_INBOX])
Make it yours
- Change the highlighted fields, not the rest. The three outcomes and the "ask a person when unsure" rule are what keep the agent safe — leave those as they are.
- Match your own apps. Swap Athena Health, pVerify, and Paubox for the EHR, eligibility tool, and secure email your practice already uses.
- Set the timing to your prep window. Three days ahead is the default; pick whatever gives your front desk enough time to chase a lapsed plan before the visit.
- Let it ask for help. When the agent can't tell who a patient is, it hands the appointment to a person on purpose. Keep it that way — it checks and routes, it never diagnoses or guesses identity.
Helpful articles
- Create your first agent — the build flow from trigger to tools.
- Set up your agent's trigger — schedule vs event, and when to use each.
- Test your agent before publishing — how to read a run and confirm each step.
- Troubleshooting agents — what to do when a run stalls or a step fails.
- Patient intake → triage & routing — the sibling use case: read a new intake and send it to the right person.