How it works.How we check it.
For the IT or compliance person who wants the mechanism. Where a call goes, what checks it, how we test it, and what comes next.
Every step, and the check on it.
Each box is a role. The suppliers behind each role are on the subprocessors page.
- Practice phone lineYour office line forwards calls to us. We answer only after your BAA is signed.
- Call handlingTakes the call in the cloud host and passes the audio on. Recording is off by default, and Leady staff do not play call audio.
- Voice modelHears the caller and speaks. It can only propose an action. It has no direct access to your schedule.
- Leady checksEach proposal arrives as a typed request. The server checks it against your practice’s settings before anything happens.
- DatabaseHolds calls, transcripts and holds. Connections are encrypted and verified, and storage is encrypted. It refuses overlapping bookings.
- Practice-management systemOpen Dental today. Leady reads the schedule and writes the appointment through your own connector.
- Sign-in service and portalStaff open the portal through a separate sign-in service that sees names, work emails and roles. Every transcript view is logged.
The dashed box is the BAA boundary. Patient data lives inside it, in a United States region. Your own practice system holds what it already held.
The model proposes. The database decides.
A booking passes four steps. Only the third one cannot be talked around.
The model proposes
It can only use the booking tools your practice allows. There is no tool to cancel, delete or read clinical notes.
The server checks
Each request is checked against your practice’s configuration before it goes further.
The database decides
It refuses a second claim on the same chair at the same time, even if the model and the application both err.
The front desk approves
A booking is a hold for your front desk unless you choose to book directly. Nothing is deleted.
We check the checks, outside the model.
A model’s word is not evidence. We score what happened in the database, not what the model said happened.
Staged calls
We play scripted calls against the agent and score every outcome from what reached the database.
A test copy of Open Dental
Tests write to a test copy of Open Dental. No practice’s patient data is used.
Fixed sentences
Answers that must not vary, such as the call disclosure, come from a versioned catalogue of fixed sentences.
Every call knows its rules
Each call records which version of your practice’s rules it ran under, so any call can be traced back to the rules at the time.
What we will measure and add.
Each item below is planned. It moves up the page once it runs.
Measured error rates
PlannedWe will score staged calls at telephone quality and report each kind of failure as a rate per 1,000 calls, with a confidence range, for a practice to read before it forwards its phone.
Caller identity on noisy audio
PlannedWe will test spell-back and read-back checks on phone-quality audio, and measure wrong-patient matches.
Desk edits at the same moment
PlannedWe will test a hold per chair that reconciles with your practice system when your staff book at the same time as a caller.
Fixed sentences held by the model
PlannedWe will measure how closely a speech model keeps to fixed sentences and tool results, including against spoken attempts to change its instructions.
One record of your rules
PlannedYour Digital Twin will become one versioned record that drives both what the agent says and what Leady allows.
An independent audit
PlannedWe plan the SOC 2 audit after our beta practices go live. Leady is not SOC 2 certified today.
Go deeper
- Named suppliers and what each sees
- The nine guardrail layers
- What we collect, and what we leave unread
- Who sees what, by role
Security questions: security@meetleady.com · Privacy questions: privacy@meetleady.com
