AI Payment Agent
Move patient balances forward with a clear next step
A planned agent for approved balance reminders, payment follow-up, and staff handoff when a patient has a question or dispute.
Coming soon
The intended workflow
Product direction, not a generally available capability — the shape of the workflow the practice would approve:
- 01
Start with an approved balance list
The practice would choose which accounts enter the workflow and confirm the amount and contact details come from the appropriate system.
- 02
Send a clear reminder
An approved message with the next action — and a route to the practice when something looks wrong.
- 03
Record the response
Payment intent, a question, a dispute, a callback request, and no response are each a distinct status.
- 04
Staff get the right exceptions
Sensitive or complex situations would go to the team with the available context.
What the planned agent is intended to handle
Persistence for the routine follow-up; people for the judgment calls.
-
Approved balance reminders
Sent on the practice's schedule, within attempt limits.
-
An approved payment path
Patients directed to the payment destination the practice chooses.
-
Responses recorded
Replies and promised next steps captured as statuses.
-
Outreach that stops
Payment, policy, or an opt-out would end the workflow.
-
Questions routed to staff
Billing questions, disputes, and hardship requests go to people.
-
Status per balance
The state of each follow-up, visible to the team.
Judgment stays with authorized staff
The planned agent would not negotiate, make financial judgments, or continue outreach outside the approved policy. Disputes, payment plans, and hardship situations belong with people.
Context travels with the handoff: a changed appointment or an insurance exception may explain why a balance needs staff review.
-
Disputes and payment plans
Practice policy and human judgment — routed to authorized staff, never decided by the agent.
-
Hardship situations
Handled by the team, with the available context carried into the handoff.
-
Policy-bounded outreach
Message, timing, attempt limits, and stop conditions would all be practice-approved.
-
No unannounced payment rails
The final payment path and supported connections have not been announced — any named capability will be labelled before launch.
What a practice should be able to measure
The intended records, once the agent ships:
-
Balances in the workflow
Accounts added to an approved follow-up queue.
-
Reminders delivered
Reminders sent and their delivery status.
-
Responses and promises
Patient responses and promised actions.
-
Questions and disputes
What went to staff, and why.
-
Outreach stopped
Stopped for payment, policy, or opt-out.
-
Accounts needing a decision
Balances still waiting on the practice.
Intended reporting for a planned capability — workflow outcomes, not collection results or revenue promises.
Frequently Asked Questions
It is planned. Contact us if patient balance follow-up is a major source of administrative work for your practice.