DentAI — Implementation Playbook (DSO)

DentAI Implementation Playbook

AI Receptionist Deployment Guide for Dental Service Organizations

---

1. Executive Summary

What DentAI Does

DentAI is an AI-powered virtual receptionist platform that automates inbound and outbound patient communications—including appointment scheduling, confirmations, recalls, insurance verification, and general inquiries—across voice, SMS, and web chat channels. The system integrates with your practice management software to access real-time scheduling availability and patient records, enabling 24/7 patient engagement without additional staffing.

Why DSOs Benefit from AI Receptionists at Scale

Scale Advantage	Impact
Standardization	Consistent patient experience across all locations; every caller receives the same quality interaction regardless of location or time
Labor Arbitrage	Reduce front desk staffing ratios while handling higher call volumes; critical given persistent dental staffing shortages
Data Aggregation	Centralized analytics reveal system-wide patterns in call volumes, scheduling efficiency, no-show rates, and patient sentiment
Capacity Optimization	AI identifies scheduling gaps across locations and can cross-book patients to nearby underutilized practices
Cost Structure	Per-location AI licensing typically costs 60-80% less than a full-time receptionist; savings multiply across 15-50 locations

Expected Timeline: Decision to Full Deployment

DSO Size	Pilot Phase	Full Rollout	Total Timeline
15-25 locations	4-6 weeks	8-12 weeks	12-18 weeks
26-50 locations	6-8 weeks	12-20 weeks	18-28 weeks

Timeline assumes 3-4 location waves with 2-week buffers between waves.

---

2. Pre-Implementation Checklist (Weeks 1-2)

Technical Requirements

Network & Infrastructure

☐ Minimum 50 Mbps download / 10 Mbps upload per location (verify actual speeds, not advertised) ☐ Dedicated static IP address or VPN tunnel capability for secure API connections ☐ Quality of Service (QoS) configuration for voice traffic prioritization ☐ Backup internet connection or failover protocol documented ☐ Firewall rules to whitelist DentAI IP ranges (obtain from vendor)

Hardware

☐ Server/workstation requirements: Modern browser (Chrome, Edge, Firefox) on any workstation ☐ Optional: Dedicated reception desk monitor for AI dashboard display ☐ VoIP phone system compatibility verification (SIP trunk access required) ☐ USB headsets for staff monitoring/intervention (one per reception desk)

Software & Integrations

☐ Practice Management System version verification:

• Dentrix G7.3+
• Eaglesoft 21.0+
• Open Dental 22.1+ ☐ Active PMS API access or integration module license ☐ Phone system administrator access (RingCentral, 8x8, Vonage, or on-premise PBX) ☐ SMS/text messaging platform credentials (if separate from phone system)

🔵 Vendor Onboarding Steps

Step	Timeline	DentAI Contact
Execute Master Service Agreement	Day 1-3	Account Executive
Complete Business Associate Agreement (BAA)	Day 1-3	Legal/Compliance
🔵 Schedule technical discovery call	Day 3-5	Implementation Manager
🔵 Receive sandbox environment credentials	Day 5-7	Technical Account Manager
🔵 Assign dedicated Customer Success Manager	Day 7	CSM Team Lead
🔵 Establish support escalation contacts	Day 7-10	Support Operations

Key Vendor Contacts to Document: ☐ Primary Implementation Manager (name, direct line, email) ☐ Technical Account Manager for integrations ☐ 24/7 Support hotline and escalation path ☐ Executive sponsor at DentAI for strategic issues

Data & Access Prerequisites

☐ PMS administrator credentials for integration setup ☐ API keys or OAuth tokens for PMS (obtain from PMS vendor if needed) ☐ Phone system admin portal access ☐ Historical call volume data export (minimum 90 days) ☐ Current appointment scheduling rules document ☐ Insurance verification credentials (payer portals, clearinghouse logins) ☐ Patient communication templates currently in use ☐ Business hours and holiday schedule for all locations ☐ Provider schedules and booking rules

Internal Stakeholder Alignment

🟣 Decision Makers (Approval Required)

Stakeholder	Decision Authority	Timeline to Engage
CEO/President	Budget approval, strategic alignment	Week 1, Day 1
CFO	ROI validation, contract terms	Week 1, Day 1-2
Chief Dental Officer	Clinical workflow impact sign-off	Week 1, Day 2-3
VP of Operations	Implementation ownership, rollout authority	Week 1, Day 1
General Counsel	BAA, data privacy, liability review	Week 1, Day 1-3

Informed Stakeholders

Stakeholder	Communication Need	Timeline
Board/Investors	Strategic initiative awareness	Before contract execution
Regional Managers	Rollout planning participation	Week 1, Day 3-5
IT Director/MSP	Technical requirements, security review	Week 1, Day 1-3
HR Director	Staffing model changes, role evolution	Week 1, Day 3-5
Marketing Director	Patient communication, brand voice	Week 1, Day 5-7

Location-Level Notification

☐ Office Managers: Initial awareness communication ☐ Lead Receptionists: Role evolution discussion ☐ Providers: Workflow change preview Detailed communication cascade handled in Change Management section

⚠️ Baseline Metrics to Capture BEFORE Go-Live

Critical: Standardize measurement methodology across all locations before capturing baselines. Inconsistent measurement makes ROI comparison impossible.

Metric Standardization Protocol

Metric	Definition	Data Source	Capture Method
Call Volume	Total inbound calls to main practice number, excluding internal extensions	Phone system CDR	90-day daily average
Answer Rate	% of inbound calls answered by human within 30 seconds	Phone system CDR	90-day average
Abandonment Rate	% of calls disconnected before answer or after >2 min hold	Phone system CDR	90-day average
Appointment Booking Rate	% of inbound calls that result in scheduled appointment	Manual tracking + PMS	30-day sample period
Cost per Call	Front desk labor cost ÷ total calls handled	Payroll + phone data	Monthly calculation
No-Show Rate	% of scheduled appointments with no patient arrival	PMS report	90-day average
Recall Compliance	% of patients scheduling recall within 30 days of due date	PMS report	Rolling 6-month
After-Hours Call Volume	Calls received outside business hours	Phone system CDR	90-day average
Average Speed to Schedule	Days between new patient call and first appointment	PMS report	90-day average
Front Desk FTE Ratio	Front desk FTEs ÷ active patient count	HR + PMS data	Current snapshot

⚠️ Common Baseline Capture Failures

• Using advertised call volumes instead of actual CDR data
• Inconsistent definitions of "answered" across phone systems
• Missing after-hours call data due to voicemail-only setups
• Comparing locations without normalizing for patient volume

DSO-Specific Data Aggregation

☐ Create centralized baseline dashboard with all locations visible ☐ Calculate portfolio-wide averages AND standard deviations ☐ Identify outlier locations (both high and low performers) ☐ Document any locations with incomplete or unreliable baseline data

Enterprise-Level Requirements

Network Standards Across Locations

☐ Confirm all locations meet minimum bandwidth requirements ☐ Document network topology variations (locations with unique ISPs, firewalls, etc.) ☐ 🟣 Decision: Standardize network configuration or accommodate variations? ☐ Create remediation plan for locations below requirements

Hosting Model Decision

Option	Pros	Cons	Recommended For
Centralized Cloud Hosting	Single management point, easier updates, disaster recovery	Single point of failure, latency for voice	DSOs with reliable connectivity across all locations
Distributed with Central Management	Local voice processing reduces latency, resilience	More complex management	DSOs with variable connectivity or high call volumes

🟣 Executive Decision Required: Hosting architecture selection

Single Sign-On (SSO) Integration

☐ Identify existing identity provider (Okta, Azure AD, Google Workspace) ☐ 🔵 Confirm DentAI SSO compatibility with your IdP ☐ Define role-based access control (RBAC) structure ☐ Map corporate directory groups to DentAI permissions

Centralized Credentialing

☐ Create master admin account for VP Operations/IT Director ☐ Define regional manager permission scope ☐ Define office manager permission scope ☐ Define view-only access for executive reporting ☐ Document credential provisioning workflow for new hires ☐ Document de-provisioning workflow for terminations

---

3. Location Readiness Assessment

Readiness Scoring Framework

Score each location on the following factors using a 1-5 scale. Multiply each score by the weight, then sum for a composite score (maximum 100 points).

Scoring Rubric

Factor 1: IT Infrastructure Maturity (Weight: 25%)

Score	Criteria
5	Fiber internet, modern networking equipment (<3 years old), VoIP phone system, PMS on current version
4	Cable internet >100 Mbps, networking equipment <5 years old, VoIP or hybrid phone, PMS within 1 version of current
3	Cable internet 50-100 Mbps, some legacy equipment, VoIP phone, PMS within 2 versions of current
2	DSL or variable connectivity, aging equipment, legacy phone system requiring upgrade, outdated PMS
1	Unreliable internet, antiquated equipment, analog phone system, PMS incompatible with integration

Factor 2: Staff Tenure & Adaptability (Weight: 20%)

Score	Criteria
5	Front desk turnover <10%, demonstrated tech adoption history, staff actively requests new tools
4	Front desk turnover 10-20%, positive response to past tech changes, adequate training participation
3	Front desk turnover 20-30%, neutral tech adoption history, some resistance but manageable
2	Front desk turnover 30-50%, past tech rollouts encountered significant resistance
1	Front desk turnover >50%, active hostility to change, history of failed technology implementations

Factor 3: Patient Volume (Weight: 20%)

Score	Criteria
5	200+ calls/day, high impact potential, mature processes can absorb change
4	100-200 calls/day, significant impact potential
3	50-100 calls/day, moderate impact and moderate risk
2	25-50 calls/day, lower impact but good for controlled testing
1	<25 calls/day, minimal impact, not representative of portfolio

Note: For pilot selection, a score of 3 may actually be optimal—high enough volume to test meaningfully but not so high that failures cause major disruption.

Factor 4: Tech Stack Compatibility (Weight: 20%)

Score	Criteria
5	Dentrix/Eaglesoft/Open Dental current version, existing API integrations active, documented workflows
4	Supported PMS version, some API experience, reasonable documentation
3	Supported PMS version, no existing API integrations, basic documentation
2	PMS version requires update before integration, limited documentation
1	Unsupported PMS, requires migration before AI implementation

Factor 5: Local Champion Availability (Weight: 15%)

Score	Criteria
5	Tech-forward Office Manager + engaged lead provider, both committed to championing
4	Strong Office Manager OR engaged provider as champion
3	Willing Office Manager, neutral provider support
2	Reluctant Office Manager, no provider interest
1	No viable champion identified, leadership vacuum

Scoring Worksheet

Location	IT (×25)	Staff (×20)	Volume (×20)	Tech (×20)	Champion (×15)	Total
Example: Main St	4 (100)	3 (60)	4 (80)	5 (100)	4 (60)	80
Location A	___	___	___	___	___	___
Location B	___	___	___	___	___	___
Continue for all locations

Readiness Tiers

Tier	Score Range	Rollout Recommendation
Green - Ready	75-100	Wave 1 or 2 candidate
Yellow - Conditional	50-74	Wave 2 or 3 with remediation plan
Red - Not Ready	<50	Defer until remediation complete

Recommended Rollout Sequence Logic

Wave 1 Selection Criteria (2-3 Locations):

• Score 70+ (avoid picking only your highest scores—you want representative locations)
• Mix of market types if applicable (urban/suburban, different regions)
• At least one location with a strong champion who can provide feedback
• ⚠️ Avoid: Flagship locations where failure visibility is high, newest acquisitions still in integration mode

Wave 2 Selection Criteria (5-8 Locations):

• Score 60+ OR score 50-60 with completed remediation
• Include at least one "stretch" location to test your support model
• Geographic clustering for efficient regional manager support

Wave 3 and Beyond:

• Remaining locations based on descending readiness scores
• Red-tier locations addressed individually with specific remediation plans

---

4. Rollout Strategy

Wave Structure Recommendation

Standard DSO Wave Model (15-50 Locations)

Wave	Locations	Duration	Cumulative %
Pilot (Wave 1)	2-3	4 weeks	5-10%
Early Majority (Wave 2)	5-8	3 weeks	25-35%
Majority (Wave 3)	8-15	3 weeks	55-70%
Remainder (Wave 4+)	Balance	2-3 weeks each	100%

Buffer Between Waves: Minimum 2 weeks for learning capture, training refinement, and configuration adjustments.

Wave 1 Pilot Location Selection

Selection Matrix

Criterion	Why It Matters	Ideal Profile
Readiness Score	Ensures smooth execution	70-85 (not necessarily the highest)
Representative Portfolio	Learnings transfer to other locations	Mix of patient volumes, specialties
Champion Quality	Active feedback, quick issue identification	Engaged OM + supportive provider
Risk Tolerance	Failure won't derail entire initiative	Not flagship, not recently acquired
Geographic Proximity	Enables on-site support if needed	Within reasonable drive of HQ or RM

⚠️ Common Wave 1 Selection Mistakes

• Choosing only top performers (doesn't test real-world challenges)
• Picking flagship locations (excessive visibility of any issues)
• Selecting based on executive relationships rather than readiness
• Ignoring geographic factors (makes on-site support difficult)

Timeline Per Wave

Week 1: Preparation

• Days 1-2: Location champion training (train-the-trainer)
• Days 3-4: Staff training delivered by champion
• Day 5: Technical integration verification
• Days 6-7: Parallel testing and soft launch prep

Week 2: Go-Live + Stabilization

• Day 1: Official go-live (see Go-Live Day Runbook)
• Days 2-5: Daily monitoring and rapid response
• Days 6-7: First-week retrospective

Weeks 3-4: Monitoring + Optimization

• Daily check-ins reduce to every-other-day
• Workflow adjustments based on feedback
• Documentation of location-specific learnings
• Preparation of "What we learned" brief for next wave

🟣 Go/No-Go Criteria to Advance Waves

Automatic "Go" (Green Light) — All Must Be True: ☐ AI successfully handling >80% of routine calls without human intervention ☐ No unresolved critical technical issues ☐ Staff satisfaction survey average >3.5/5.0 ☐ No increase in patient complaints related to scheduling ☐ Appointment booking rate equal to or better than baseline ☐ Champion recommends proceeding

Conditional "Go" (Yellow Light) — Evaluate Individually: ☐ AI handling 60-80% of routine calls (acceptable for Wave 2 if improving) ☐ Minor technical issues with documented workarounds ☐ Staff satisfaction 3.0-3.5/5.0 (identify specific concerns) ☐ Slight dip in metrics (within 10% of baseline)

"No-Go" (Red Light) — Any One Triggers Pause: ☐ AI handling <60% of routine calls after optimization ☐ Unresolved critical technical issues affecting operations ☐ Staff satisfaction <3.0/5.0 with specific tool-related complaints ☐ Patient complaints increasing meaningfully ☐ Appointment booking rate down >15% from baseline ☐ Champion raises fundamental concerns

⚠️ Rollback Plan

Pre-Define Rollback Triggers:

• System outage >4 hours during business hours
• Data integrity issue affecting patient records
• Patient safety concern (incorrect appointment type booking for emergency)
• Regulatory compliance concern (HIPAA, state dental board)

Rollback Procedure by Severity:

Level	Scenario	Action	Recovery Time
1 - Pause	Significant issues, recoverable	Revert to human-only for affected call types	2-4 hours
2 - Partial Rollback	Major issues, single location	Fully disable AI at location, maintain elsewhere	24-48 hours
3 - Full Rollback	System-wide critical issue	Disable AI across all locations, vendor escalation	Immediate

Rollback Communication Chain:

1. Location champion → Regional Manager (immediate)
2. Regional Manager → VP Operations + IT Director (within 1 hour)
3. VP Operations → DentAI executive contact (within 2 hours for Level 2-3)
4. VP Operations → C-suite (within 4 hours for Level 3)

Rollback Checklist: ☐ Document exact issue and trigger ☐ Notify all affected parties per chain above ☐ Revert phone routing to pre-AI configuration ☐ Ensure front desk staff aware and ready to absorb volume ☐ 🔵 Open critical ticket with DentAI support ☐ Schedule root cause analysis within 24 hours ☐ Draft patient communication if any appointments affected ☐ Document lessons learned before re-attempting

---

5. Configuration & Integration (Weeks 2-3)

Practice Management System Integration

🔵 Dentrix Integration (G7.3+)

Prerequisites: ☐ Dentrix Server administrator credentials ☐ eCentral account with API access enabled ☐ Current Dentrix eCentral subscription ☐ Dentrix developer tools license (if applicable)

Step-by-Step Integration:

Step	Task	Duration	Owner
1	🔵 Request API credentials from DentAI implementation team	Day 1	DentAI
2	Log into eCentral → Settings → Third Party Access	Day 1	DSO IT
3	Create new integration partner, input DentAI credentials	Day 1	DSO IT
4	Configure data access permissions (schedule read/write, patient demographics read, insurance read)	Day 1	DSO IT
5	🔵 DentAI runs connection test from their environment	Day 1-2	DentAI
6	Verify bi-directional sync: pull schedule, push test appointment	Day 2	DSO IT + DentAI
7	⚠️ Test appointment type mapping (ensure AI categories match Dentrix categories)	Day 2-3	DSO IT + OM
8	Configure provider availability rules	Day 3	OM
9	Set up operatory assignment logic	Day 3	OM
10	Full integration validation with 10 test scenarios	Day 3-4	DSO IT + DentAI

⚠️ Common Dentrix Integration Failures:

• API timeout due to server performance (ensure Dentrix server meets specs)
• Appointment type mismatch causing incorrect durations
• Provider ID inconsistencies between Dentrix and DentAI
• Operatory blocking logic not properly configured

---

🔵 Eaglesoft Integration (21.0+)

Prerequisites: ☐ Eaglesoft Server administrator credentials ☐ Patterson eClaims account (for API access pathway) ☐ Current Eaglesoft support subscription ☐ ⚠️ Eaglesoft often requires Patterson involvement—budget 3-5 extra days

Step-by-Step Integration:

Step	Task	Duration	Owner
1	Contact Patterson support to enable third-party API access	Day 1-3	DSO IT
2	🔵 DentAI provides integration specifications to Patterson	Day 1	DentAI
3	Patterson provisions API endpoint and credentials	Day 3-5	Patterson
4	🔵 DentAI configures connection using Patterson-provided credentials	Day 5-6	DentAI
5	Configure data access: schedule, patient, insurance modules	Day 6	DSO IT
6	Map Eaglesoft procedure codes to DentAI appointment types	Day 6-7	DSO IT + OM
7	Test appointment creation workflow end-to-end	Day 7-8	DSO IT + DentAI
8	Configure provider-specific rules and chair assignments	Day 8	OM
9	Full integration validation with 10 test scenarios	Day 8-9	DSO IT + DentAI

⚠️ Common Eaglesoft Integration Failures:

• Patterson API provisioning delays (start this early)
• Database timeout for large practices (>5,000 active patients)
• Sync conflicts with Patterson backup schedules

---

🔵 Open Dental Integration (22.1+)

Prerequisites: ☐ Open Dental administrator credentials ☐ Open Dental API license (additional purchase if not already owned) ☐ MySQL database access credentials (read-only sufficient for most functions) ☐ Open Dental eServices subscription for enhanced features

Step-by-Step Integration:

Step	Task	Duration	Owner
1	Open Dental → Setup → Security → API Access → Enable	Day 1	DSO IT
2	Create dedicated API user with appropriate permissions	Day 1	DSO IT
3	🔵 Provide API endpoint URL and credentials to DentAI	Day 1	DSO IT
4	🔵 DentAI configures Open Dental connection	Day 1-2	DentAI
5	Verify read access: pull patient list, pull schedule	Day 2	DSO IT + DentAI
6	Verify write access: create test appointment, update status	Day 2	DSO IT + DentAI
7	Configure appointment type mapping (Open Dental definitions)	Day 2-3	DSO IT + OM
8	Set up provider schedule sync and availability rules	Day 3	OM
9	Configure recall list access for outbound campaigns	Day 3	OM
10	Full integration validation with 10 test scenarios	Day 3-4	DSO IT + DentAI

⚠️ Common Open Dental Integration Failures:

• API rate limiting on large queries (implement pagination)
• Time zone mismatches between Open Dental server and DentAI
• Permission scope too narrow (missing schedule write access)

---

Phone System Integration

SIP Trunk Configuration (RingCentral, 8x8, Vonage, Others)

Prerequisites: ☐ Phone system administrator credentials ☐ Current SIP trunk configuration documentation ☐ DID (Direct Inward Dial) numbers for each location ☐ Understanding of current call routing rules

Step-by-Step Integration:

Step	Task	Duration	Owner
1	Document current call flow for each location	Day 1	DSO IT + OM
2	🔵 DentAI provides SIP endpoint configuration	Day 1	DentAI
3	Create call routing rule: inbound → DentAI → office (failover)	Day 2	DSO IT
4	Configure DentAI as primary handler for main line	Day 2	DSO IT
5	Set up transfer pathways: AI → front desk, AI → provider	Day 2-3	DSO IT
6	Configure after-hours handling rules	Day 3	DSO IT + OM
7	Test inbound call routing (10 test calls minimum)	Day 3	DSO IT + DentAI
8	Test transfer scenarios (emergency, complex request, etc.)	Day 3-4	DSO IT + OM
9	Configure outbound caller ID for AI-initiated calls	Day 4	DSO IT
10	Test outbound calls (confirmation, recall)	Day 4	DSO IT + DentAI

⚠️ Common Phone Integration Failures:

• SIP authentication issues (check firewall settings)
• Audio quality issues (QoS not configured for voice traffic)
• Transfer failures (incorrect extension mapping)
• After-hours routing not matching actual business hours

---

Test Environment Setup and Validation Checklist

Pre-Production Testing Protocol

☐ Environment Isolation: Confirm test environment is fully isolated from production ☐ Test Data: Load synthetic patient data (no real PHI in test) ☐ Test Phone Number: Provision dedicated test line routing to sandbox ☐ Test Scenarios Document: Create minimum 20 test scenarios covering:

• New patient scheduling (various appointment types)
• Existing patient scheduling
• Schedule changes/cancellations
• Insurance verification questions
• After-hours inquiries
• Transfer to human (emergency, complex request)
• Outbound confirmation calls
• Outbound recall attempts
• Non-English language handling (if applicable)
• Error scenarios (unavailable provider, no openings)

Validation Checklist

Category	Test	Pass Criteria	Result
Connectivity	API connection to PMS	Response <500ms, no errors	☐
Connectivity	Phone system integration	Calls route correctly 100%	☐
Scheduling	New patient booking	Appointment appears in PMS within 30 seconds	☐
Scheduling	Existing patient booking	Patient matched correctly, appointment created	☐
Scheduling	Cancellation/reschedule	Changes reflected in PMS, confirmation sent	☐
Data	Patient lookup	Correct patient identified 95%+ of attempts	☐
Data	Insurance information	Accurate retrieval and communication	☐
Voice	Call quality	Clear audio, no latency >150ms	☐
Voice	Transfer function	Successful transfer in <3 seconds	☐
Fallback	AI escalation to human	Smooth handoff with context	☐
Outbound	Confirmation call	Accurate details, proper timing	☐
Outbound	Recall campaign	Correct patient targeting, scheduling	☐

---

Data Migration / Historical Data Ingestion

If importing historical data (call logs, patient preferences):

☐ Export historical call logs from previous phone system (CSV format) ☐ Export patient communication preferences from PMS ☐ 🔵 Provide data exports to DentAI for ingestion ☐ 🔵 DentAI maps historical data to new schema ☐ Verify imported data accuracy via spot-check audit (minimum 5%) ☐ ⚠️ Flag any data quality issues before go-live

---

Security and HIPAA Compliance Verification

Enterprise-Level HIPAA Checklist

Item	Description	Status
Business Associate Agreement	🟣 Executed BAA covering all locations in scope	☐
Data Encryption - Transit	All API calls use TLS 1.2 or higher	☐
Data Encryption - Rest	PHI stored with AES-256 encryption	☐
Access Controls	Role-based access control implemented	☐
Audit Logging	All PHI access logged with user, timestamp, action	☐
Minimum Necessary	AI only accesses data required for function	☐
Data Retention	🔵 Confirm DentAI retention policy aligns with your requirements	☐
Breach Notification	Vendor breach notification procedure documented	☐
Subcontractor Agreements	🔵 Confirm BAAs with DentAI subcontractors	☐
Physical Security	🔵 Confirm data center security certifications (SOC 2 Type II)	☐

Access Control Matrix

Role	Patient Demographics	Schedule	Insurance	Call Recordings	Analytics
VP Operations	View	View/Edit	View	View	Full
Regional Manager	View	View/Edit	View	View	Regional
Office Manager	View	View/Edit	View	Location	Location
Front Desk	View	View/Edit	View	None	None
Provider	View	View	View	None	Own

---

DSO-Specific Configuration

Standardized Configuration Template (Enforce Centrally)

The following settings should be IDENTICAL across all locations:

Setting Category	Specific Settings	Rationale
Branding/Voice	AI voice selection, greeting script structure, hold music	Consistent patient experience
Compliance	HIPAA-required disclosures, recording consent language	Legal consistency
Security	Password requirements, session timeout, MFA requirements	Security baseline
Appointment Types