Installed snapshot · immutable source audit

A sophisticated dental front desk with unfinished installation wiring.

A node-level review of Votel’s v33 Dental AI Receptionist: multilingual intake, booking, cancellation, confirmation, staff transfer and four appointment-notification fanouts.

Votel library v33Reviewed Sep 21, 2026Agency-level installNo live channels used
VOTEL SNAPSHOT AUDIT02 / DENTAL

Dental AI
Receptionist

Installed agent1
Agent workflows2
Real nodes84
Connected edges113
Audit statusRemediation required
2Installed workflows
84Real nodes
113Connected edges
19Placeholder terminals
0Recorded runs
01 · Executive verdict

The architecture is reusable. The installed configuration is not.

Two workflows contain 84 real nodes and 113 connected edges. The core pattern is strong, but four booking nodes have no calendar, four appointment triggers have no source, copied account references remain, installer placeholders are visible, and no run history proves an end-to-end route.

Reusable

Patient lifecycle

Multilingual intake, booking, confirmation, cancellation, messaging and staff handoff are represented.

Unbound

Scheduling

Four booking nodes and four appointment triggers require installer-owned sources.

Unproven

Execution

The agent is inactive, has zero active channels and has no recorded runs.

Do not activate this source snapshot as installed. Freeze this version as the audit baseline, then repair copied references, bind scheduling, complete the content layer and validate every route with synthetic patients.
02 · Installed inventory

One agent, two workflows and a six-stage dental Lead pipeline.

AssetStatusVerified detail
Dental AI ReceptionistInactive

GPT-5.4 Mini, Nova voice, en-US, 207-word prompt and zero active channels.

Incoming Call44 nodes

61 edges plus three placeholder terminals; multilingual intake and five English intent branches.

Appointment Notification40 nodes

52 edges plus sixteen placeholder terminals; four repeated appointment-to-email fanouts.

Lead pipeline6 stages

Appointment Scheduled, Confirmation Request, Cancellation Request, Call Forwarded, Left a Message and Not interested.

Booking infrastructure8 unbound

Four booking nodes show “No calendar”; four appointment triggers show “Source: Not configured.”

Email layer36 nodes

Four Incoming Call emails plus 32 patient/internal notification emails; one patient confirmation is disabled.

Knowledge, tools and widgetsNone

No selected knowledge base, no custom tools, 0/17 enabled built-in tools and no widgets.

Execution evidence0 runs

No simulator or live run appears in the agent’s execution history.

Dental snapshot inventory: one inactive agent, two workflows with 84 real nodes and 113 edges, one six-stage Lead pipeline, 36 email nodes, five triggers, four unbound booking nodes, three Ask and Save nodes, three extracted variables, no selected knowledge base, no tools, no widgets and no runs
Installed inventory, source v33. Counts come from the installed agency-level snapshot; account configuration is kept separate.
Text version of this diagram

The snapshot installs one inactive agent, two workflows with 84 real nodes and 113 edges, a six-stage Lead pipeline and 36 email nodes. The workflows contain five triggers, four unbound booking nodes, three Ask and Save nodes and three extracted variables. No knowledge base, tool, widget or run is configured.

Dental snapshot architecture: the agent runs Incoming Call and Appointment Notification, writes contact fields and Lead pipeline stages, and sends email; installer-owned calendars, appointment sources, staff handoff, knowledge, company values and email delivery sit outside the installed core
Architecture, reconstructed from the installed build. Dashed red nodes are unresolved dependencies or copied account references.
Text version of this diagram

The Dental AI Receptionist runs Incoming Call and Appointment Notification. Incoming Call writes contact data and Lead pipeline stages and depends on calendar, staff and email configuration. Appointment Notification depends on appointment sources and email. The prompt reads company and support values and expects dental knowledge that is not selected.

03 · Incoming Call

The front-desk workflow covers the right jobs but carries copied dependencies.

The conversation-started trigger accepts chat, voice or SMS, branches by language, then sends English callers into booking, cancellation, message, staff or confirmation routes. The Spanish route transfers to a named AI agent from the source account.

Node familyCountVerified role
Conversation22

Language, intent, appointment-type, reschedule, success and fallback copy.

Ask & Save3

Five questions each for confirmation, message and cancellation; maps first name, last name and phone.

Calendar booking4

Eight questions each; all are set to America/New_York and show “No calendar.”

Pipeline5

Four Lead stage updates plus one TOIP / Cancellation Request mismatch.

Transfer and forwarding2

One account-specific AI-agent transfer and one call-forwarding rule set.

Extraction2

Produces appointment date/time and appointment location.

Incoming Call top-level routing: conversation started goes to language selection; English goes to booking, cancellation, message, staff and confirmation; Spanish goes to a copied account-specific agent transfer whose outputs terminate at placeholders; Chinese continues to a conversation route
Incoming Call, part 1: language and intent. The copied Spanish transfer is a source-account dependency, not normal installer setup.
Text version of this diagram

Conversation Started routes by English, Spanish or Chinese. English exposes five intents. Spanish transfers to an account-specific AI agent, and both transfer outcomes end at placeholders. Chinese continues through conversation handling.

Incoming Call operational branches: booking routes through four unbound calendar nodes, Lead Appointment Scheduled, variable extraction and email; cancellation routes through Ask and Save, a mismatched TOIP pipeline reference, email and reschedule choice; message routes through Ask and Save, Lead Left a Message and email; staff routes through Lead Call Forwarded and forwarding outcomes
Incoming Call, part 2: operational branches. Normal owner configuration is shown separately from the two source defects: the TOIP pipeline mismatch and copied transfer.
Text version of this diagram

Booking chooses a dental need, enters one of four unbound calendars, updates Lead / Appointment Scheduled, extracts date/time and location and sends email. Cancellation collects identity, points to TOIP / Cancellation Request, sends email and offers rescheduling. Message collects identity, updates Lead / Left a Message and emails staff. Staff updates Lead / Call Forwarded and uses answered, no-answer and outside-hours outcomes.

04 · Appointment Notification

Four repeated notification trees generate 32 emails.

Each appointment-booked trigger feeds a four-path decision: Consult, Followup, Cleaning and Treatment. Each path sends a patient confirmation and then an internal/support notification. All four triggers lack a source and all sixteen final internal emails terminate at placeholders.

4

Appointment triggers

Every trigger reports “Source: Not configured.”

4 × 4

Decision paths

Consult, Followup, Cleaning and Treatment repeated for four sources.

16

Terminal placeholders

Each internal notification ends without a connected next action.

Four appointment triggers with no configured source each feed a four-path decision for Consult, Followup, Cleaning and Treatment, then four patient confirmation emails and four internal support emails, ending at sixteen placeholder terminals
Appointment Notification: repeated fanout pattern. The chart compresses four structurally identical trees while preserving their exact node and edge counts.
Text version of this diagram

Four unconfigured appointment triggers each lead to a decision with four appointment-type paths. Every decision leads to four patient emails, then four internal support emails. The sixteen internal emails end at placeholder terminals.

05 · Data & dependencies

The contact contract is clear; the account contract is incomplete.

ValueSourceDestination
first_name · last_name · phoneAsk & Save

Contact fields, pipeline context and message copy.

appointment_date_and_timeExtraction

Appointment summary and notification content.

appointment_location2 extractors

Booking and confirmation messaging.

company_name_Global value

Prompt and email subjects; installer must supply.

system.support_emailSystem value

Internal appointment, cancellation, message and booking notifications.

contact.emailContact

Patient-facing confirmations.

Dental data flow from Ask and Save and extracted appointment values into the contact record, Lead pipeline, patient email and internal support email, with company name and calendar sources supplied by the account owner
Data flow. Contact and appointment values are installed workflow outputs; company, support-email and scheduling values are account-owned inputs.
Text version of this diagram

Ask and Save writes identity and phone information to the contact record and pipeline. Extraction produces appointment date, time and location for patient and internal email. The account must supply company name, support email and calendar or appointment sources.

Dental dependency map separating the installed agent, workflows and Lead pipeline from owner-supplied copy, scheduling, email delivery, human handoff, healthcare review and synthetic tests, plus repair items for the copied transfer, TOIP pipeline mismatch and unresolved email terminals
Dependency map. Gray items are normal owner setup. Red items are defects that belong in remediation, not onboarding.
Text version of this diagram

The installed core includes the agent, two workflows and Lead pipeline. The owner supplies company copy, four scheduling sources, email delivery, human handoff and healthcare rules, then runs synthetic validation. Remediation must separately repair the copied transfer, TOIP pipeline mismatch and unresolved email terminals.

06 · Defect register

Nine actionable findings, separated from normal owner setup.

ID · findingSeverityRequired disposition
DENT-001 · Four booking nodes have no calendarHigh

Map four installer-owned dental bookables and verify success and error paths.

DENT-002 · Four appointment triggers have no sourceHigh

Bind every trigger to the intended booking source and appointment type.

DENT-003 · Spanish transfer is account-specificHigh

Replace the copied AI-agent destination and connect both Forwarded and Failed outcomes.

DENT-004 · Cancellation pipeline mismatchHigh

Replace TOIP / Cancellation Request with the installed Lead stage.

DENT-005 · Installer placeholders remain in caller copyHigh

Replace company, tagline, doctor and phone placeholders before activation.

DENT-006 · FAQ / knowledge layer is unfinishedMedium

Correct the FQA placeholder and attach approved dental knowledge.

DENT-007 · Sixteen email chains end at placeholdersMedium

Confirm intentional terminal behavior or connect explicit completion steps.

DENT-008 · One patient confirmation is disabledMedium

Remove the duplicate or intentionally enable and connect it.

DENT-009 · No route has execution evidenceHigh

Run the complete synthetic test matrix and preserve successful runs.

Normal configuration is not a defect: an inactive agent, disconnected live channels, owner-selected calendars, verified senders and installer-specific business values are expected setup. Copied references, mismatched assets and dangling outcomes are remediation work.
07 · Launch standard

The next document is remediation, not activation.

  • 1
    Freeze the source baseline

    Preserve this exact v33 inventory, node/edge counts, mappings and finding IDs.

    Complete
  • 2
    Build a private repair account

    Use a clean `[Votel Snapshot] Dental AI Receptionist` sub-account and never modify this source record.

    Next
  • 3
    Repair snapshot defects

    Fix the copied transfer, pipeline mismatch, placeholders, disabled email and terminal outcomes.

    Required
  • 4
    Add the improvement layer

    Standardize calendar naming, setup copy, dental knowledge, safety escalation and review collection.

    Plan
  • 5
    Validate every route

    Use synthetic patient data only; test all languages, intents, appointment types, handoff outcomes and failures.

    Required

Dental source audit complete.

The installed snapshot now has an exact inventory, workflow maps, data contract, dependency map and defect register. The private repair account is now tracked separately.

Open the Dental remediation report →
Audit method: read-only agency-account review on September 21, 2026. The agent remained inactive. No patient, contact, message, appointment, channel, tool, pipeline or integration was created, edited or triggered.