How Eva compares
How Eva compares to a typical AI dental scribe
This is a category comparison, not a call-out. We compare Eva to the shape of a typical AI dental scribe, and every Eva capability is tagged with where it stands (shipped, in testing, or on the roadmap) so you can check each one.
The whole loop
A scribe is built around the note. Eva starts where it ends.
The note is what you can test today. Here is where the rest of the loop stands.
The clinical note
Record or upload a consult, get a source-grounded note you review and copy to your PMS, plus a Team Brief and Patient Assessment. This is the demoable-today core.
Case, plan & pipeline
Treatment plans and fees, the case pipeline and attention queues, and in-treatment-to-completed tracking are built and running. They are being validated, not yet a day-one promise.
Follow-ups & outbound
Letters & Documents, generated follow-ups, and automated outbound (messaging and email) are on the roadmap. They'll appear here, tagged shipped, when they land.
Where Eva is different
Where Eva is different, and what she's still building
Each row states the general pattern for a typical scribe, then Eva's real answer, tagged with the maturity of the Eva capability it describes.
Dimension
A typical AI dental scribe
Eva
Scope
A typical AI dental scribe
A scribe is built to produce the note. A transcript goes in, a structured note comes out, and the product is organised around that.
Eva
In testingEva starts at the note and is built to carry the case to completion. One recording already gives you the source-grounded note, a Team Brief for the front desk, a patient-readiness read and Consult Intelligence on how the consult went. Case building, treatment plans and the pipeline are built and in testing; follow-ups, outbound and reporting are on the roadmap.
Who writes to the chart
A typical AI dental scribe
Publishing the note into the practice-management system is a selling point: some products insert it into the record for you, in one click or on their own.
Eva
ShippedEva hands the note to a person. She never diagnoses, never decides treatment, and never writes a note into your system on her own. That is a boundary we chose, not a connection we have not built: the only outbound write Eva will ever make is an appointment, and it will never carry a note. Nothing reaches your chart that a person did not decide belonged there.
Someone to ask
A typical AI dental scribe
An assistant, where a scribe has one, is aimed at the document or at the clinical reference: drafting the wording, checking a drug interaction, looking up a guideline.
Eva
ShippedEva answers about the patient in front of you. She is on every screen once you are signed in and knows the screen you are on, so you can ask why this patient was graded the way they were, what their barrier means, or how this note got drafted. The answer comes from your own clinic's record rather than a reference library.
Whose voice it is
A typical AI dental scribe
Several products learn your phrasing from the notes you have already produced, so the voice arrives once there is enough of your output to infer it from.
Eva
ShippedYour clinic sets Eva's tone and identity in a Clinic Persona form, and note wording in a bounded Clinical Voice setting, filled in before the first recording and changed whenever you want rather than inferred from a body of past notes. What you tune is the voice, never the clinical rules: those are the same for every clinic, deliberately.
Where a row describes work that isn't finished, it carries an In testing or On the roadmap tag.
Compare Eva on a real consult, not a spec sheet
Book a walkthrough and we'll run the capture → draft → review flow end to end, and answer, on the record, exactly where each part of the loop is.