Scheduling that follows the way your team works
Handle appointment requests using approved rules for providers, exam rooms, visit types, hours, and escalation, with the connection path confirmed before implementation.
What happens during a patient call
A schedule combines providers, exam rooms, visit types, lengths, hours, and the exceptions your schedulers handle from experience. We map what the agent may complete, what it may offer, and what must go to staff: a clear outcome, not automation for its own sake.
-
The request is identified
A new visit, a different time, a cancellation, or help from the office. The intent is captured before any action.
-
Approved rules are checked
The schedule source and connection approved for the deployment: provider, exam room, visit type, and timing considered together.
-
Completed or handed off
Requests that fit the workflow are completed and recorded; anything outside the rules reaches staff with the reason and context.
-
The team reviews the outcome
Scheduled, rescheduled, cancelled, or sent for review. Every request ends in a visible outcome.
The rules your team can define
The agent needs your team's rules before it should act on a patient's request. All of these stay yours to approve.
-
Providers and clinical staff
Who the agent may book, and for which visit types.
-
Rooms and resources
Rooms and equipment shape what can be offered.
-
Visit types and duration
Each visit type carries its approved length and conditions.
-
New and existing patients
Separate workflows for each, where your team wants them.
-
Hours and after-hours behaviour
What the agent may do while the office is closed.
-
Reschedules and cancellations
The timing conditions under which changes are allowed.
-
Staff handoff triggers
The requests that must always reach a person.
-
Confirmation and follow-up
How outcomes are confirmed and what happens next.
Integration claims stay tied to product reality
Nephrology groups run different EHRs and configurations. We do not treat a planned connector as a live one. During evaluation the required connection is labelled, and the label is what governs.
Any named integration on this site carries one of these labels after the product owner confirms its status.
-
Available
Ready for the approved production workflow.
-
Pilot
In a limited, reviewed deployment.
-
Planned
On the product roadmap, not ready for production use.
-
Custom
Requires a scoped implementation and technical review.
One schedule, one version of the truth
Automation must not create a second source of truth. Before launch, your team and ours agree on:
-
The controlling system
Which system owns availability.
-
Where actions are written
Where completed appointment actions land.
-
How conflicts surface
How failed or conflicting updates appear to staff.
-
What needs validation
The actions that require a staff check before they stand.
-
How changes reach the team
How cancellations and changes are communicated.
A workflow is not ready because one ideal request worked. We validate routine cases, after-hours behaviour, unavailable options, changes, cancellations, and staff handoffs before production use.
Frequently Asked Questions
See all questionsCan EigenH AI connect to our EHR?
Yes. Every appointment, update, and call outcome is written back to your EHR. Tell us what you use and the connection is set up during onboarding.
Can staff control which appointments the agent handles?
Yes. Your team defines the visit types, timing, resources, and exceptions the agent may handle.
What happens if a schedule update fails?
The workflow should surface the failure and send the request to staff. The agent should not tell a patient an appointment is complete when the approved schedule source did not accept the action.
Ready to answer more patient calls?
See how our AI agents can help your team answer more calls and schedule more patients.