LegioSoft designs and builds front-desk and booking assistants for dental businesses. The assistant answers routine administrative questions, checks availability, arranges or moves appointments under rules your clinic approves, and passes anything unusual to your team. Below is a working demonstration of that workflow.
Interactive demonstration using fictional clinics and patients. No real appointment is made.
Guided demonstration with scripted replies. No AI service is called.
Prefilled sample patient details are used throughout. You never need to enter real contact information.
Demo Dental, shared record for both locations
Demo Dental, its Riverside and Parkside clinics, all availability and all patients shown on this page are fictional and were created for this demonstration. The page describes a proposed service. The demonstration runs entirely in your browser; no data is transmitted or stored.
Patients ask in their own words at the hour that suits them. The assistant answers administrative questions from answers your practice has approved, and guides the enquiry towards the few details a booking actually needs: location, appointment type and a workable time.
Only genuinely available slots are offered, and only after the patient confirms is the booking written. The slot then leaves availability so it cannot be taken twice. A reschedule keeps the original appointment until the replacement is confirmed.
Clinical questions, unusual requests and anything outside the approved rules stop the automation and become a task with the clinic, the request and the conversation attached, so a person picks it up with the context already there.
Each site's hours, closures and holiday patterns, so the assistant never offers a time the practice is shut.
Your own appointment types, durations, buffers, clinician or surgery constraints, and the limits on what may be booked without a person checking.
Directions, parking, what to bring, cancellation terms and similar questions answered only from wording your practice has signed off.
Who receives which handoff, what counts as urgent, and where the assistant must stop and let a person take over.
Where the appointment is actually written, and which records the assistant may read or create.
No. Demo Dental, its two clinics, the availability and every patient in the demonstration are fictional. The booking, the reschedule and the staff task all happen in your browser's memory and disappear when you reload or press Reset demo. Nothing is sent anywhere, nothing is stored, and no message, email or calendar entry is created.
The assistant operates inside rules your practice approves, and everything it does is visible in a staff view like the one above: the current enquiry and its status, the appointments it has written, a summary of the conversation and a history of what happened. Anything the rules do not cover, such as clinical questions, unusual requests or a patient who asks for a person, stops the automation and becomes a task with the clinic, the request and the conversation attached. In the demonstration a task stays open until you use Mark handled yourself; no one else is notified, because there is no one on the other end.
Yes, that is the usual reason groups ask for it. Each location keeps its own opening hours, appointment book and availability, while the booking rules, approved answers and escalation paths are managed once and applied consistently across sites. The demo shows a small version of this: two clinics with different hours, a shared staff record, and a location filter. A patient who has no preference is offered the earliest suitable slot at either clinic.
During scoping we look at your practice-management or scheduling software, what it exposes for reading availability and writing appointments, and what access your practice is able to authorise. The assistant is then built against that, so appointments land in the book your team already works from. Where a direct integration is not available, we propose the practical alternative, for example writing a structured request for a staff member to approve, and we say plainly which parts are automatic and which stay manual. We do not claim universal compatibility.
No. The scope is administrative: enquiries, availability, booking, rescheduling, opening hours, locations and similar routine questions. Symptoms, pain, treatment decisions and triage are explicitly out of scope; in the demonstration those inputs are refused and turned into a staff handoff instead. Where a question should reach a clinician, it reaches a person.
Bring your locations, appointment types, scheduling rules and the systems you already run on. We will tell you what a front-desk and booking assistant could realistically take off your reception team, what needs to stay with a person, and what the integration depends on.
Discuss your projectTell us what you want to improve and which software your practice uses. Please don't include patient details.
We'll review your message and get back to you as soon as possible.
Something went wrong on our side. Please try again in a moment.
We’ll review your message and contact you to discuss the requirements.
Once the scope is clear, we’ll propose an approach and prepare an estimate.
