Use case · Clinic front desk
Agent Inbound & Outbound answers appointment calls, workflows send WhatsApp reminders, and staff approve anything clinical before a patient hears it.
An illustrative clinic front desk use case for Agent Serve, the AI workspace where teams build, deploy, and manage AI agents: appointment calls with Agent Inbound & Outbound, WhatsApp reminders, a front-desk knowledge base and a complaints Relay.
At a glance
The problem it removes
The phone rings while the desk is checking a patient in. Calls go unanswered, reminders are sent by hand if at all, and the same questions about hours, parking and preparation take up the time staff need for patients in the room.
Step by step
Agent Inbound & Outbound answers, hears what the caller needs and passes the request to the front desk.
Questions about hours, parking and preparation are answered from the front-desk knowledge base.
Anything about symptoms, results or treatment goes to staff, who approve every reply.
How it fits together
A knowledge base holds the front-desk answers staff have written and approved.
An appointments table holds each booking, its reminder and the patient’s reply.
A workflow sends a WhatsApp reminder with Confirm and Reschedule buttons the day before.
A front-desk Relay sorts complaints and drafts replies a manager approves.
A front-desk dashboard shows calls, confirmations and no-shows by day.
How it runs
Agent Serve sends the reminders and answers routine questions, and clinic staff handle anything clinical.
Staff confirm the slot, and the booking is written to the appointments table.
A scheduled workflow sends an approved WhatsApp template with Confirm and Reschedule buttons.
The WhatsApp webhook trigger receives the reply, and the workflow updates the appointments table.
A message about symptoms or treatment is flagged for staff, who write or approve the reply.
What to measure
Example figures for a multi-chair clinic handling a few hundred appointments a week.
−30%
No-shows
Patients confirm or reschedule the day before.
−40%
Missed calls
Calls are answered while the desk is busy.
−50%
Routine questions to staff
Hours, parking and preparation answered from the knowledge base.
100%
Clinical replies by staff
Every clinical answer comes from a person.
Illustrative example. Figures show how the workflow is measured; they are not customer results.
In depth
Agent Serve gives the practice manager the Relay, its permissions, call quality checks and Chat in one workspace.
Start an Agent Serve Relay from a clinic front-desk specialization, give it the complaints inbox and the knowledge base it may use.
An Agent Serve Relay never sends email on its own. A manager approves the exact message before it reaches a patient.
The Agent Serve Call Compliance dashboard scores call transcripts against the clinic’s own checks, such as never giving clinical advice.
Front-desk staff ask Agent Serve Chat about clinic procedures, attach the knowledge base with @, and get an answer with its source.
Examples
Three clinics running front-desk work on Agent Serve, each with staff approving anything clinical.
An Agent Serve workflow sends a WhatsApp reminder the day before each visit and records whether the patient confirms.
Agent Inbound & Outbound answers calls when the desk is busy and passes each appointment request to staff.
An Agent Serve Relay sorts patient complaints by site and topic and drafts a reply for the practice manager.
Examples show what teams can build in Agent Serve. They describe patterns, not named customer deployments.
Before and after
| Work | Before | With Agent Serve |
|---|---|---|
| Appointment calls | BeforeMissed while the desk checks a patient in. | With Agent ServeAnswered by Agent Inbound & Outbound and passed to staff. |
| Reminders | BeforeSent by hand, when someone has time. | With Agent ServeSent on WhatsApp the day before, with the reply recorded. |
| Routine questions | BeforeAnswered by staff, the same way, many times a day. | With Agent ServeAnswered from the knowledge base staff approved. |
| Complaints | BeforeRead late from a shared inbox. | With Agent ServeSorted on arrival and replied to after a manager approves. |
Governance
Agent Serve handles front-desk work only, gives no medical advice, and keeps patient details out of places they do not belong.
Security and governanceMessages about symptoms, results or treatment are flagged for clinic staff, and every Agent Serve Relay email waits for approval.
The Agent Serve front-desk knowledge base holds only content clinic staff have written and approved.
Relays never send email or book meetings without an approval, under any autonomy setting. An approval covers the exact payload the reviewer saw and expires if nobody decides.
A Guardrails block detects personal data and blocks or masks it before text reaches the next step.
Proposals, approvals, declines and executed actions are written to the workspace audit log, which admins can export.
Admin, write and read roles per workspace, plus permission groups that limit which models, blocks and integrations a team can use.
Run Agent Serve in your own cloud or data centre, next to the systems it reads.
Further reading
Front desks lose hours to booking calls and reminder rounds, and no-shows still slip through. Here is how the parts fit: AI voice for bookings and confirmations, workflows for WhatsApp and SMS, and staff for anything clinical.
Outpatient clinics · 5 min readComplaints reach a clinic by phone, email, WhatsApp and public reviews, and each lives in a different place. These field notes cover one queue, a Relay that triages and drafts, and a practice manager who approves every reply.
Clinic operations · 6 min readA front desk takes hundreds of calls a week and nobody can listen to them all. This dashboard checks each one for identity verification, consent, clinical boundaries and complaints, and points the practice manager at the calls that need a person.
Clinics & diagnostics · 5 min readQuestions
No. In this use case Agent Serve answers front-desk questions only, from content staff approved. Anything about symptoms, results or treatment goes to clinic staff.
Agent Inbound & Outbound, a separate Valnora & Elric product available by invitation. Agent Serve Relays do not place or answer phone calls.
Agent Serve does not ship a patient record integration. If your system has an API, a workflow can reach it through the API block, with the key stored as a workspace secret.
Agent Serve does not claim a healthcare certification. Teams can redact personal data in logs, mask it with a Guardrails step, and self-host Agent Serve.
No. The figures are illustrative examples of what a clinic might measure with Agent Serve, not customer results.
Last updated
Enterprise access
Agent Serve is available to teams by invitation. Tell us what you want to build and we will set up your workspace with you.