Caller basics
Name, callback number, new or existing patient status, preferred windows, and the reason for calling.
Dental Voice Intake Pilot
This sample shows what JVT can build for a dental office before touching live patient data: an AI-disclosed intake path that captures the call, avoids medical advice, and hands staff a clean packet they can trust.
What It Produces
Name, callback number, new or existing patient status, preferred windows, and the reason for calling.
Plain-language request type, urgency flag, insurance question context, and missing fields for staff.
What the assistant refused to answer, what staff should review, and what should be escalated.
Synthetic Scenarios
New patient call
New patient asks about a cleaning and whether the office takes their insurance. The assistant captures the request without promising coverage or booking the calendar.
Existing patient request
Existing patient needs to reschedule and asks for a Friday morning slot. The assistant gathers the request and leaves schedule changes to staff.
Urgent boundary
After-hours caller reports tooth pain and asks what medication to take. The assistant does not diagnose or recommend treatment; it captures the message and routes it as urgent staff review.
Pilot Boundaries
The first version is intentionally narrow. It can answer with approved office language, capture details, and create packets. It should not diagnose, recommend medication, confirm insurance coverage, finalize appointments, or expose patient records.
Paid Pilot Shape
The current pricing test is $750-$1,500 for a synthetic pilot and $300-$900/month for managed support once live-call scope is approved. The first version proves the workflow with fake callers before any real patient data, phone number routing, or scheduling integration.