Agent OS · Channels & Integrations
Reaches every patient. Connects to every system.
Channels connect your agents to people. Tools connect them to your systems. Both run on one contract, so an agent works the same way on a phone call as on a payer portal.
People · Channels
- Voicepatients
- Messagingpatients
- Podiumpatients
- Emailpatients
- Slackstaff
- Microsoft Teamsstaff
One case · both directions
Omar K. · Knee MRI tomorrow, 10:30
- EHR · APITomorrow’s schedule pulled. Omar’s MRI is on it.
- Clearinghouse · EDI 270/271Eligibility re-checked overnight: active, $40 copay.
- Payer portal · Browser AgentLogged in with two-factor. Auth approved, attached to the visit.
- Messaging · to Omar“Your MRI is tomorrow at 10:30. Your $40 copay: secure link.”
- Payments · APICopay posted, then read back.
- Teams · to the front deskOmar K. is ready for 10:30: auth on file, copay paid.
Systems · Tools
- EHR / PMAPI
- ClearinghouseEDI
- Payer portalBrowser Agent
- SharePointMicrosoft 365
- PaymentsAPI
- Reporting DBSQL
Channels
Any channel, same agent.
Connect a channel once and every agent can use it. Identity is verified before anything sensitive is shared, and each request is answered on the channel that’s safe for it, not just the one it arrived on.
Patients
- Voice
- Messaging
- Podium
Your staff
- Slack
- Microsoft Teams
Already text patients through Podium? Agents answer in the same threads your front desk uses.
Channel routing
Where each request gets answered
| The request | Answered on |
|---|---|
| “Can I pay my balance?” | Text A secure pay link. A card number is never read out on a call. |
| “Should I stop my medication?” | A person Clinical questions go to your team, on every channel. |
| Statements and receipts | Email Itemized, with the pay link. |
| A same-day schedule change | Call Voice, then a text to confirm. |
| A case that needs a decision | Slack · Teams The handoff, with everything already tried. |
Integrations
Works inside the systems you already run.
Full read and write, not the read-only slice most EHR APIs expose. No rip-and-replace.
EHR & practice management
- athenahealth
- NextGen
- AdvancedMD
- eClinicalWorks
- Greenway
- ModMed
- SIS
Lab & imaging
- Phoenix LIS
- RadSource
Payers & prior auth
- eviCore
- Payer portals
- Medicare
- Medicaid
Clearinghouses & eligibility
- EDI 270/271 eligibility
- EDI 837 claims
- EDI 835 remittance
Documents & fax
- Microsoft 365
- Google Workspace
- SharePoint
- OneDrive
- Inbound fax
Patient messaging
- Podium
- Twilio
Don’t see yours?
If your practice runs it, we can very likely build it. Request an integration →
How it connects
Whatever the system allows, one contract on top.
APIs
Wherever a real API exists: EHR/PM, documents, payments.
EDI
Eligibility, claims and remits in the standard format.
Databases
Parameterised queries against your reporting database.
Documents & fax
Classify, split and extract, with anything unsure flagged for review.
Browser Agents
For every screen no API reaches.
Payer portals and EHR screens that only a person could use, until now. Browser Agents log in, including two-factor codes, find what they need, and return it as data the agent can act on.
Sessions can be recorded, so you can watch exactly what an agent did on a screen.
What starts the work
Agents don’t wait to be asked.
Events
A new fax, a form, a payment, a Podium message.
Schedules
Every night at 2am, every Monday, month-end.
Webhooks
Any system that can call a URL can start an agent.
Work queues
New items run, finished ones are skipped, failures retry.
Reads run free. Writes are gated by confidence and your autonomy tier.Every write is read back to confirm it posted, whatever the connection.
See it connect to your own systems.
Tell us what your practice runs. We’ll show an agent working in it.