Approved information only
Your clinic chooses the information source the agent answers from, per workflow.
Responsible Voice AI agents
Boundaries first
Every workflow has a boundary.
Make the agent useful for repeatable operations while keeping sensitive decisions with the people responsible for care.
Explicit allowed actions
Each workflow defines what the agent may do - nothing is implied or automatic.
Clinical advice out of scope
Diagnosis, prescription, and clinical judgement stay outside the default operational scope.
Sensitive moments route to a person
High-risk, sensitive, or uncertain requests move to your team, not deeper into the bot.
Handoffs carry context
Your team receives the reason, the details, and the next action - not just a recording.
Roles and permissions
Who can configure or review workflows is controlled by your clinic’s roles.
The workflow contract
Rules your clinic sets, states you can see.
Each workflow is a contract: what is enabled, what is routed to people, and what is always required. This is the shape of that contract.
| Rule | Example state |
|---|---|
| Approved answersAnswers from clinic-reviewed information | Enabled |
| Booking workflowBook within configured rules | Enabled |
| Reminder workflowOutbound confirmation and reminder calls | Enabled |
| Clinical adviceDiagnosis and prescription topics | Disabled · human route |
| Uncertainty thresholdRequest is unclear after clarification | Escalate |
| Summary and ownershipEvery conversation closes with an owner | Required |
Questions clinics ask
Safety, in plain terms.
Does the agent diagnose patients?
No. Clinical advice is outside the default operational scope. Clinical topics route to a person on your care team with the conversation context attached.
What happens if it does not understand?
It asks a clarifying question first. If the request stays uncertain, it escalates to a person instead of guessing, and the team receives what was understood so far.
Can the clinic disable a workflow?
Yes. Every workflow is enabled per clinic and can be paused or turned off. Disabled workflows are no longer answered or acted on by the agent.
Who reviews escalated calls?
Whoever your roles and permissions define - reception, care teams, or specific reviewers. Ownership is part of every handoff.
What data does the agent need to perform booking?
Only the approved information the connected scheduling workflow requires to check and confirm a slot. There is no broad access by default.
How are permissions and access controlled?
Configuration and review are role-gated. Your clinic decides who can change what the agent says, what it can do, and who reviews its work.
Compliance and certification claims are added to this page only after they are verified for the product.