Scheduling & Integrations
Scheduling that follows the way your practice works
Handle appointment requests using approved rules for providers, operatories, visit types, hours, and escalation, with the connection path confirmed before implementation.
What happens during a patient call
A schedule combines providers, operatories, visit types, lengths, hours, and the exceptions your front desk handles from experience. EigenH AI maps what the agent may complete, what it may offer, and what must go to staff — a clear outcome, not automation for its own sake.
- 01
The request is identified
A new visit, a different time, a cancellation, or help from the office — the intent is captured before any action.
- 02
Approved rules are checked
The schedule source and connection approved for the deployment: provider, operatory, visit type, and timing considered together.
- 03
Completed or handed off
Requests that fit the workflow are completed and recorded; anything outside the rules reaches staff with the reason and context.
- 04
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
EigenH AI needs your office's rules before it should act on a patient's request. All of these stay yours to approve.
-
Providers and hygienists
Who the agent may book, and for which visit types.
-
Operatories and resources
Constrained chairs 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 the office 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
Healthcare practices run different practice-management systems 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, the practice and EigenH AI 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
It depends on the system, required actions, and deployment stage. Tell us what you use and what the agent needs to do. We will confirm the current availability label before proposing the workflow.