24/7 inbound availability
Answers patient calls after hours, during peak periods, weekends, and holidays.
The capability map
Capabilities are listed as things the agent performs or prepares - not as abstract intelligence claims.
How the agent sounds and when patients can reach it.
Answers patient calls after hours, during peak periods, weekends, and holidays.
Shaped to your clinic’s identity, with configurable prompts and fallback behaviour.
Understands the patient’s language and responds in the same language where supported.
Defines what happens when the agent is unsure - clarify, capture, or hand off.
The front-desk work the agent carries for patients.
Checks availability and confirms the right slot within the configured workflow.
Helps patients move or cancel appointments without another back-and-forth.
Answers who is available and when, where connected to the scheduling workflow.
Outbound calls that keep appointments confirmed and patients prepared.
Configured check-ins after visits, routed onward when responses need a person.
Collects the details a workflow defines, in the patient’s own words.
What your clinic receives from every conversation.
A concise record of what was asked and what was done.
Every call is classified against your configured workflows.
Requests arrive with an owner and the next step already attached.
Sensitive, uncertain, or clinical moments route to a person with context.
Teams can review conversations and see how workflows are performing.
How to read a capability
Each capability should be judged by the same four-beat pattern - what the patient says, what the agent does, what the system records, and what your team sees.
The patient says what they need.
The agent responds in voice and confirms intent.
The workflow performs or prepares the action.
The clinic sees the result with context.
Capability rollout is per workflow: a capability becomes available to your clinic when the corresponding workflow is configured and approved by your team.