No-show recovery
Text delivered • No reply yet
Workflow Use Case
Automate patient communication across reminders, recall, surveys, no-show recovery, and follow-up workflows.
Operational picture
Use triggers, response logic, and task routing to turn messaging into finished work instead of one-way notifications.
Signals
Text delivered • No reply yet
Low score submitted
Patient ready to schedule
What Calvient handles
These are the operational motions the system has to coordinate well if the workflow is going to move cleanly.
Workflows
Launch outreach from appointment events, recall lists, survey timing, or no-show triggers instead of one-off manual campaigns.
Conversations
Interpret patient replies and send them down the right path, whether that means scheduling, escalation, or closure.
Tasks
Turn non-response, low survey scores, or reschedule requests into tracked operational tasks instead of loose follow-up promises.
Reporting
See which sequences get responses, where patients drop off, and which cohorts need a different approach.
How it works
The workflow should move because the system keeps state, ownership, and next action visible at every step.
01
Use visit events, recall logic, care-gap timing, no-show events, or survey timing as the starting point.
Outreach begins with a clear reason and target population.
02
Send the right message cadence across text, phone, or other supported channels based on workflow type.
Patients receive timely outreach instead of generic reminders days too late.
03
Handle confirmations, questions, reschedule requests, low survey scores, or silence with the next appropriate action.
Responses turn into action, not manual inbox cleanup.
04
Generate follow-up work when staff involvement is required or close the workflow when the patient has completed the needed step.
Communication workflows finish with a state change, not just a sent message.
What operators see
These are the working surfaces that keep the queue understandable, actionable, and measurable.
Workflow queue
Operators can see which communication workflows are active, which patients replied, and which need a human next step.
Recall campaign
12 patients ready for scheduling
No-show recovery
6 cases need live outreach
Survey follow-up
2 low-score responses flagged
Conversations
Staff can see what the patient said, what automation already did, and what needs human attention now.
“I need to reschedule”
Route to access team
“Can I complete forms later?”
Send follow-up instructions
No response after 3 touches
Escalate to call task
Reporting
See which sequences convert, which patients re-engage, and which follow-up motions are still underperforming.
Recall outreach
Best completion rate
Survey escalation
Needs faster staff follow-up
Reminder sequences
High response but low reschedule completion
Workflow Views In Product
Workflow queue showing campaign, reminder, and escalation states.
Patient reply thread with the downstream follow-up task visible.
Special Agents
These agents are useful because they handle the repetitive middle of the workflow while leaving sensitive or ambiguous decisions with staff.
Starts the recovery sequence as soon as a visit is missed and keeps the case moving until it is rescheduled or closed.
Trigger
Missed appointment or no-show event
Actions
Handoff
Escalates only when the patient needs direct staff intervention.
Converts feedback into operational follow-up instead of letting low-scoring survey responses sit unseen.
Trigger
Negative survey response or risk keyword
Actions
Handoff
Routes sensitive or urgent responses to the appropriate team queue.
Runs scheduled or triggered recall outreach and branches patients into scheduling, reminders, or close-out paths.
Trigger
Recall list, care-gap logic, or time-based follow-up window
Actions
Handoff
Leaves a clear outcome for each patient instead of an open-ended outreach list.
Operational channels
Patient communication is only useful if it connects directly back to operational work. Calvient ties the message thread to the task queue and outcome state.
Fax
Occasional supporting documents or outside responses tied back into the follow-up case
Text
Reminders, recall messages, surveys, and two-way response handling
Phone
Escalated call attempts, AI-call workflows, and live follow-up when text is not enough
Browser
Appointment or portal actions triggered by patient response workflows
Forms
Survey flows, patient intake updates, and structured response capture
EHR / integrations
Appointment and chart context that determines when outreach should start or stop
Teams that use this
Outreach work usually spans access, front office, and coordination teams. The system needs to know when a message becomes a task.
KPIs / outcomes
The right operating system should make these measures easier to see, easier to improve, and easier to explain to leadership.
KPI
How often patients engage with the communication workflow.
KPI
How often workflows finish with the intended next step completed.
KPI
How many patients actually finish the survey experience you launched.
KPI
How often missed visits are converted into a recovered appointment or closed outcome.
Related use cases
Prepare patients before visits with reminders, paperwork, insurance updates, and appointment coordination.
Centralize inbound and outbound referral work, track status, request missing information, and move patients forward.
Show queue health, backlog, turnaround time, productivity, and automation/reporting metrics.
Bring one process. Leave with a launch plan.