Dental appointment calls can be administrative without becoming clinical conversations. Evaluate Zanus AI around booking requests, cancellations and desk callbacks, with a clear boundary when the caller asks a question that needs the practice team.
Define the appointments available to book
Use the practice’s approved appointment categories, calendars and booking conditions. A request for “a check” may need clarification before choosing a slot. Confirm which arrangements the phone agent may complete and which require reception to review the request.
For an illustrative trial, request an appointment category that is deliberately unavailable in the test calendar. The useful result is an accurate explanation and a desk handoff. It should not be a different appointment silently booked to fill the gap.
Match the person and the intended visit
Shared household numbers make identity and booking references important. Follow the practice’s approved verification procedure before disclosing appointment details or making changes. Ask the supplier how those checks are implemented in the proposed setup.
Do not collect additional health information just to make a test conversation sound complete. Establish the information the practice needs for administrative routing and the separate process for clinical questions.
Distinguish a request from a confirmed change
| Caller response | Administrative result to inspect |
|---|---|
| Confirms an existing visit | The correct booking records confirmation |
| Cannot attend | The cancellation follows practice policy |
| Wants another date | A real alternative or owned desk request exists |
| Asks a clinical question | The designated practice handoff is used |
Test reminders and inbound calls together
A patient may receive a reminder and then call reception to change the arrangement. Review both conversations against the authoritative calendar. Ensure staff can tell whether the visit is confirmed, cancelled or awaiting a new date.
Test an unanswered outbound call separately from a spoken confirmation. A voicemail is evidence of an attempted contact, not evidence that the person has agreed to attend. Verify how the outcome appears to reception.
Check escalation and privacy before launch
Use the practice’s approved wording and destination when a caller needs a clinical response. The administrative agent should not improvise medical advice or assess symptoms. Review access, recording, retention and contractual requirements with the supplier and the practice’s responsible team before handling real patient information.
Compare the resulting workflow with Sysevo only against documented deployment requirements. This guide does not establish clinical suitability, a healthcare certification or a supplier’s contractual commitments.
Review the desk’s next action
After the trial, reception should be able to recover the right visit, see the caller’s request and identify who must respond. Measure booking corrections and unresolved desk requests alongside calls answered. Those observations show whether the administrative process works for the practice.
Official documentation and related reading
- Zanus AI official product guide
- Zanus AI official supporting documentation
- GoHighLevel for Trades: Compare Voice AI and Webchat Costs
- Zanus AI for home services: the broader evaluation
Explore the relevant Sysevo product, Voice Agents and CRM. Compare Sysevo plans and pricing or book a demo using the same requirements.
Reviewed 3 November 2026. Independent Sysevo editorial guide using the linked official documentation. Scenarios are proposed evaluation steps, not reported customer results or a hands-on vendor benchmark. Sysevo sells its own business software; availability and deployment requirements need confirmation.
Mapping the Full Booking Journey Before a Call Is Answered
Before evaluating any telephone automation tool for a dental practice, it helps to trace every administrative step that a single appointment request touches. A booking enquiry is rarely a single exchange. It begins before the call, when a patient decides to reach out, and it ends only when a confirmed, accurate record sits in the practice calendar and the relevant staff member knows what to do next. Working through that sequence on paper, before configuring any system, reveals gaps in process that automation cannot fill if the underlying procedure is undefined.
Consider a fictional scenario to make this concrete. A caller named Jordan phones the practice on a weekday afternoon to book a check-up for a family member, Sam, who is listed under the same household telephone number. The administrative steps immediately branch. The phone agent must first establish which patient the request concerns, because the household number could relate to several records. That is not a technical question alone; it is a practice policy question. The practice should document in advance which verification fields are required before the agent proceeds, and that document should be consistent with the practice's existing reception procedure for exactly the same situation.
If Jordan provides Sam's name and date of birth and those match the record, the journey can continue. If the details do not match, the practice needs a written rule for what the agent does next: offer a desk callback, ask for an alternative identifier, or stop and transfer. Each of those options has a different privacy implication and a different operational consequence, and the choice belongs to the practice, not to the supplier.
Once identity is confirmed, the agent moves to appointment availability. The practice should have pre-agreed which appointment categories appear in the bookable calendar and which require a clinical decision before scheduling. A request for a routine check-up may proceed automatically. A request for an assessment following a specific symptom should not. The distinction matters because allowing an administrative system to select an appointment type on the basis of a caller's description of symptoms is not an administrative act; it crosses into clinical triage. The practice's standard operating procedure should name the appointment types that are off-limits for autonomous booking and specify the transfer or callback that takes over instead.
Cancellation Procedure as a Distinct Workflow
A cancellation call looks simpler than a booking call, but it contains its own evaluation criteria. When a caller says they cannot attend, the administrative outcome should be unambiguous: the appointment is marked cancelled, the slot is released according to practice policy, and a record of the cancellation exists with a timestamp and the reason if the practice collects that information.
What should not happen is ambiguity about whether the appointment was cancelled or merely flagged for review. Reception staff arriving the following morning should not be reconstructing whether a caller from the previous evening intended to cancel or reschedule. If the system logs an intent to reschedule without confirming a new date, that state needs a visible label in the calendar and a clear task assigned to reception to follow up. An unresolved reschedule request sitting silently in a log that only the system can read is operationally equivalent to a lost call.
For evaluation purposes, a practice could run a structured scenario in which a test caller cancels an appointment during a period when no alternative slots are immediately available. The observable outcomes worth examining are: whether the cancellation is recorded accurately, whether the caller is offered a desk callback or waitlist option rather than silence, whether reception can see the open cancellation in their view of the calendar, and whether any outbound reminder that was already scheduled for that appointment is suppressed. That last point is easy to overlook. Sending a reminder for an appointment the patient has just cancelled damages confidence in the practice's administrative processes and generates unnecessary inbound calls from confused patients asking why they received a reminder after cancelling.
Handling the In-Between States
Most evaluation frameworks focus on clean outcomes: a booking succeeds, or a cancellation is confirmed. The more revealing tests involve the states in between, where the caller is uncertain or the available options do not match the request.
In a fictional scenario, a caller asks for a slot on a specific day and time that does not exist in the bookable calendar. A well-functioning administrative process produces one of several defined outcomes: the caller is offered the nearest available alternative with a clear description of what it involves, the caller is offered a desk callback so reception can check for options not available through automated booking, or the caller is told honestly that nothing is available and invited to call back. What the process should not produce is a silence, an error, or a booking into a slot the caller did not request without explicit confirmation.
Another in-between state worth examining is the caller who begins a booking request and then raises a clinical question mid-conversation. This is not unusual in a dental context. A patient calling to book a check-up may mention that they have been experiencing discomfort. At that moment, the administrative boundary is reached. The practice should have a pre-written response path that acknowledges the caller's concern, transfers or escalates to a member of the clinical or reception team, and does not attempt to assess, minimise or characterise the symptom. The phone agent's role at that point is to hand off accurately, not to conclude the booking.
The evaluation question for this scenario is not whether the handoff language sounds reassuring. It is whether the clinical team receives enough context to follow up appropriately. Does the desk callback record show what the caller mentioned? Does reception know that the call ended without completing a booking? Is there a task in the system, or does the handoff disappear into an unrecorded transfer?
Staff Readiness and Handover Arrangements
A telephone system that performs well in isolation can still cause administrative difficulty if the practice team is not prepared to work with its outputs. Before any live deployment, the reception team should be able to answer several practical questions from their normal working view of the calendar.
They should be able to identify at a glance which bookings were made through the automated phone agent and which were made through other channels. This matters for follow-up: if a booking made by phone needs confirmation of specific patient information, reception needs to know the channel so they understand the verification steps already completed. They should also be able to identify calls that ended in a desk callback request, sorted by urgency if the practice distinguishes routine callbacks from those flagged during a potential clinical concern.
A useful acceptance exercise for the practice team is to give reception a set of fictional call logs and ask them to reconstruct the calendar state without assistance from the system administrator. If a receptionist cannot determine from the record whether an appointment is confirmed, pending, cancelled, or awaiting a reschedule, the log format is insufficient for the practice's operational needs, regardless of what the underlying system recorded. The record must be readable by the people responsible for acting on it.
Handover arrangements between automated and human responses also need a defined protocol for periods when reception is unavailable. If a caller reaches the phone agent outside practice hours, the practice should have agreed in advance what can be completed autonomously and what must be deferred to the next staffed period. An out-of-hours cancellation may be recorded reliably without human involvement. An out-of-hours request involving a clinical concern requires a different response path, potentially a recorded message directing the caller to an appropriate urgent care service rather than an administrative callback queue.
Comparing Administrative Process Options Before Committing
When a practice is deciding how to structure its telephone booking and cancellation process, whether assisted by automation or otherwise, several criteria help distinguish options that suit the practice's specific patient profile from those that suit a generic telephone workflow.
Patient recall patterns matter. A practice with a high proportion of patients who attend on regular recall cycles has different telephone volume characteristics than one with a larger proportion of first-time or irregular visitors. Regular recall patients may already have a strong expectation of how confirmation and reminder calls feel, and a significant departure from that expectation deserves attention before launch rather than after.
Staff workflow integration matters separately from system capability. A feature that the system can perform but that requires reception to check a separate log, log into a different interface, or request a manual export is a feature that will be used inconsistently. The evaluation question is not whether a capability exists but whether it appears in the workflow that staff already use for managing their day.
Exception handling volume is worth estimating before going live. If the practice expects a proportion of calls to involve patients who are elderly, who have communication needs, or who routinely call on behalf of dependent family members, the process for those calls should be as clearly documented as the standard booking flow. Those calls may require longer verbal exchanges, more verification steps, or more frequent transfers to reception. If the practice does not know how many such calls to expect, a pilot period with detailed logging of exception types will provide better evidence than any pre-launch estimate.
Reviewing Records After a Pilot Period
A structured review after a defined pilot period gives the practice team concrete observations rather than impressions. The review should focus on administrative accuracy, not on the subjective quality of the telephone interaction. Appointment records made through the phone agent should be compared against the authoritative calendar to identify any discrepancies in patient name, appointment type, time, or confirmation status. Cancellation records should be checked to confirm that corresponding reminder communications were suppressed. Desk callback requests should be reviewed against reception's record of follow-up actions to confirm that none were lost.
The review should also examine the calls that did not produce an outcome. A call that ended without a booking, a cancellation, or a callback request warrants attention. The practice should understand whether those calls ended because the caller chose not to proceed, because the system reached an unhandled state, or because the caller encountered difficulty and hung up. Each of those causes suggests a different operational response.
Where the review surfaces a pattern of unresolved desk requests, the practice team should examine whether the resolution responsibility is clearly assigned. An unresolved request is not simply a system problem; it is a process problem that requires a named owner and a defined time window for follow-up. Agreeing those ownership rules before the pilot begins means the review can measure compliance with a defined standard rather than discovering that no standard was ever set.
Practical administrative improvement in dental appointment management comes from clarity about boundaries: which decisions are administrative, which are clinical, which are the system's responsibility, and which are the team's. Defining those boundaries on paper, testing them with structured fictional scenarios, and reviewing real outcomes against a documented standard gives the practice a reliable basis for deciding whether the process serves patients, staff, and the practice's operational requirements.
Evaluating Records When a Caller Acts on Behalf of Someone Else
A dental practice regularly receives calls in which the person speaking is not the patient whose appointment is being managed. A parent booking for a child, an adult child arranging care for an older parent, or a carer acting on behalf of a patient with reduced communication capacity are all administratively distinct from a patient calling on their own behalf. Each situation involves a different relationship between the caller's identity, the patient's record, and the authority to make or change a booking. An evaluation of any telephone administrative system should test these cases explicitly, because a process designed around a caller who is also the patient will behave differently when those two roles are separated.
For an illustrative scenario, consider a caller named Alex who phones to cancel an appointment belonging to a patient named Evie. Alex states the relationship and provides Evie's name and date of birth. The administrative question is not whether Alex sounds credible; it is whether the practice has a documented procedure for accepting a third-party cancellation and what verification it requires. The phone agent cannot invent that procedure. It must follow one the practice has already written down.
Before any deployment involving real patient records, the practice should produce a written matrix covering at least three caller-to-patient relationships: the patient calling for themselves, an adult calling for a dependent registered at the same address, and an adult calling for a patient not registered under their own contact details. For each combination, the matrix should name the required verification fields, the permitted administrative actions, and the action the system takes when verification cannot be completed. That matrix becomes a test script, not merely a policy document. Each row should be tested with a structured fictional call during the evaluation period, and the record produced by each call should be checked against what the matrix specifies.
The record is the critical output. After a third-party cancellation in the fictional scenario, the calendar entry should reflect not only that the appointment was cancelled but, if practice policy requires it, that the cancellation was made by a representative rather than the patient. That distinction may be relevant if the practice later wants to understand its cancellation patterns or if a patient disputes whether they personally cancelled. The granularity of what the system records about caller identity versus patient identity is an evaluation criterion worth examining specifically, because a system that conflates the two may produce records that are accurate about the outcome but silent about the administrative process that produced it.
Testing the Boundary Between Administrative Confirmation and Clinical Content
Telephone conversations in a dental context sometimes drift toward clinical territory through no particular design. A patient calling to confirm a routine appointment may mention that they are nervous about a procedure, that they have recently started a medication, or that they are experiencing sensitivity. Each of those statements is different in kind and calls for a different administrative response.
Nervousness about a procedure is an emotional communication that reception staff routinely acknowledge. An administrative system should be able to pass that note to the practice team so that the clinician is aware before the appointment begins. The evaluation question is whether the note appears in the record in a form the clinical team will actually see, not whether the system generated a sympathetic-sounding response during the call.
A mention of a new medication is a clinical data point. An administrative system should not attempt to assess its relevance, record it in an unstructured way that could be missed, or reassure the caller that it is unlikely to matter. The appropriate administrative response is to flag the call for a clinical team member to follow up and to ensure the booking is not silently confirmed without that review. The evaluation test for this scenario is to ask reception, after the fictional call, whether they were aware of the mention and what action the record prompted them to take. If they were not aware, or if the record produced no visible prompt, the administrative boundary is not functioning as intended.
A mention of sensitivity or discomfort is the clearest clinical boundary case. The practice should have agreed language for exactly this situation, and the evaluation should confirm that the phone agent uses that language and hands off appropriately rather than proceeding with the booking as if the clinical information was not raised. The test outcome worth recording is not subjective; it is binary. Did the handoff occur? Did reception receive context about what was mentioned? Is there a task or flag in the system requiring clinical follow-up before the appointment proceeds?
A Worked Acceptance Exercise: From Inbound Call to Resolved Record
An acceptance exercise gives the practice team a structured method for deciding whether the administrative process is ready for live use. What follows is a fictional worked example designed to be adapted to a practice's own circumstances, not a description of how any particular system behaves.
The exercise begins with a fictional patient, Morgan, who calls to reschedule an appointment. Morgan's preferred new date is not available in the bookable calendar. Morgan asks whether a later slot might become available and also mentions briefly that the reason for rescheduling is that they have recently had some dental work done elsewhere and want to make sure everything is reviewed. That final detail introduces a clinical nuance into an otherwise administrative call.
The reception team should evaluate the record produced by this call against five observable criteria. First, is Morgan's existing appointment correctly marked as pending reschedule rather than either confirmed or silently cancelled? Second, is there a desk task assigned to a named role, requiring follow-up contact with Morgan about alternative dates? Third, is the detail about recent external dental work noted in the record in a place the clinical team will see before any new appointment is confirmed? Fourth, was Morgan offered a callback rather than an unexplained end to the call? Fifth, does the outbound reminder scheduled for the original appointment show as suppressed or flagged for review?
If the practice team can answer all five questions from the record alone, without consulting system logs or a system administrator, the administrative process is functioning at a level suitable for operational use. If any question cannot be answered, that gap identifies a specific improvement to make before the process handles real patient enquiries. Framing the acceptance exercise this way gives the practice a decision rule rather than a general impression.
The exercise should be run by someone who uses the calendar and task system in their normal working role, not by the person who configured the system. The goal is to confirm that the outputs are legible and actionable for the staff who will rely on them daily, under normal working conditions, without specialist knowledge of the underlying configuration.



