Yapi — Implementation Playbook (DSO)

Yapi Implementation Playbook for DSOs

Patient Communication AI Deployment Guide

---

1. Executive Summary

What Yapi Does

Yapi is a comprehensive patient communication and engagement platform that automates appointment reminders, confirmations, recalls, online scheduling, digital forms, and two-way texting. The platform integrates with major practice management systems to eliminate manual patient outreach while improving show rates and patient satisfaction.

Why DSOs Benefit from Patient Communication AI at Scale

Patient communication is the highest-volume, most repetitive operational function in dental—and the most inconsistent across locations. DSOs that deploy a standardized communication platform gain:

• Operational Leverage: One configuration can eliminate thousands of manual calls daily across 50 locations
• Data Aggregation: Centralized dashboards reveal which locations have communication gaps, enabling targeted intervention
• Standardized Patient Experience: Patients receive the same professional, timely communication whether they visit your Phoenix location or your Chicago location
• Measurable ROI at Scale: When you move confirmation rates from 75% to 92% across 40 locations, the production recovery is substantial and attributable

Expected Timeline

• Decision to First Pilot Location Live: 3–4 weeks
• Full DSO Deployment (15–50 locations): 12–18 weeks depending on location count and IT infrastructure variance

---

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

Technical Requirements

Hardware

☐ Verify workstations meet minimum specs: Windows 10+ or macOS 10.14+, 8GB RAM, modern browser (Chrome, Edge, Firefox) ☐ Confirm front desk stations have reliable internet (minimum 25 Mbps download recommended) ☐ ⚠️ Identify any locations still using legacy hardware (5+ year-old workstations) that may need upgrades ☐ Verify webcams if using video communication features

Software

☐ Document current PMS version at each location (Dentrix, Eaglesoft, Open Dental, Denticon, etc.) ☐ Confirm PMS versions are within vendor-supported range for Yapi integration ☐ Identify any locations using PMS versions more than 2 years behind current release

Network

☐ Test outbound SMS/email deliverability from each location's network (some corporate networks block these) ☐ Verify firewall rules allow Yapi's required ports and domains ☐ ⚠️ Document any locations with unreliable internet (frequent outages = failed patient communications)

Integrations

☐ Inventory existing patient communication tools to be replaced (Lighthouse, RevenueWell, Weave, etc.) ☐ Document any active integrations those tools have that must be preserved or replicated ☐ Identify phone system type at each location (VoIP, landline, cloud-based)

Vendor Onboarding Steps

Week	Action	Owner
1	🔵 Schedule enterprise kickoff call with Yapi account executive and implementation lead	VP of Operations
1	🔵 Obtain enterprise-level BAA from Yapi legal team	Compliance/Legal
1	🔵 Request dedicated DSO implementation manager (single point of contact for all locations)	VP of Operations
1	🔵 Obtain complete API documentation if planning custom integrations	IT Director
2	🔵 Confirm training resource availability (live vs. recorded, train-the-trainer support)	L&D Manager

Key Contacts to Establish

☐ Yapi Enterprise Account Executive (commercial/contract) ☐ Yapi Implementation Manager (technical deployment) ☐ Yapi Tier 2 Support Contact (escalation path) ☐ Yapi Customer Success Manager (post-deployment optimization)

Data/Access Prerequisites

☐ Create master list of all PMS login credentials for each location (admin-level access required for integration) ☐ 🔵 Obtain Yapi API keys and enterprise portal credentials ☐ Document current patient communication workflows at 3 representative locations (high-performing, average, struggling) ☐ Export current patient contact data quality report from PMS (% with valid mobile, % with email, % with both) ☐ ⚠️ Identify any locations with significant patient data quality issues (<70% mobile capture rate)

Enterprise-Level Requirements

Network Standards

Requirement	Standard	Verification Method
Minimum bandwidth	25 Mbps download/10 Mbps upload	Speed test at each location
Firewall configuration	Whitelist Yapi domains and ports	IT verification ticket
DNS	Consistent resolution across locations	Automated DNS check

Hosting Decision

🟣 Executive Decision Required: Centralized vs. Location-Level Hosting

Approach	Pros	Cons	Recommendation
Centralized cloud (Yapi-hosted)	Easier management, automatic updates, single dashboard	Requires internet at all times	✅ Recommended for most DSOs
Hybrid (local cache + cloud sync)	Some offline resilience	More complex, potential sync issues	Consider only for locations with unreliable internet

Single Sign-On (SSO)

☐ Determine if SSO integration is required (recommended for 25+ locations) ☐ 🔵 Request SSO configuration documentation from Yapi (SAML 2.0, Azure AD, Okta compatible) ☐ Coordinate with IT to configure SSO if applicable ☐ Define user provisioning/deprovisioning process for terminated employees

Centralized Credentialing

☐ Create role-based access template (Front Desk, Office Manager, Regional Manager, HQ Admin) ☐ Define permission sets for each role across all locations ☐ Establish process for onboarding new locations and users ☐ Document user audit procedures (quarterly access review)

Internal Stakeholder Alignment

Stakeholder Alignment Map

Stakeholder	Role in Implementation	Communication Need	Cadence
Board/Investors	Approve budget, receive ROI updates	High-level progress, financial impact	Monthly summary
CEO/COO	Executive sponsor, remove obstacles	Rollout status, escalations	Weekly during rollout
VP of Operations	Project owner, owns timeline	Detailed status, decisions needed	2x weekly
Chief Dental Officer	Clinical workflow validation	Provider adoption, clinical impact	Weekly
IT Director	Technical integration owner	Integration status, issues	Daily during setup
Regional Managers	Cascade to locations, local accountability	Location-specific readiness, training	Weekly
Office Managers	Local execution, staff coordination	Training, go-live prep, daily issues	Per location schedule
Providers	Adopt new communication workflows	What's changing, why it helps them	Pre-training, go-live
Front Desk Staff	Primary daily users	How to use, troubleshoot basics	Training + ongoing support

Approval Requirements

🟣 Board/Investor Approval (if applicable): ☐ Budget approval for enterprise licensing ☐ Approval for patient communication AI adoption (some boards require AI-specific authorization)

🟣 C-Suite Approval: ☐ Project charter and timeline ☐ Rollout wave structure ☐ Go/no-go criteria between waves ☐ Fallback/rollback authority

🟣 Internal Alignment Meeting

Schedule 60-minute kickoff with:

• VP of Operations (project sponsor)
• IT Director (technical owner)
• Chief Dental Officer (clinical workflow validation)
• Regional Managers (field execution)
• Compliance Officer (HIPAA validation)

Agenda:

1. Tool capabilities overview (15 min)
2. Rollout strategy and timeline (15 min)
3. Role assignments (10 min)
4. Success metrics alignment (10 min)
5. Q&A and concerns (10 min)

Baseline Metrics to Capture

⚠️ Critical: Capture these BEFORE go-live to enable accurate ROI measurement. Standardize measurement methodology across all locations.

Required Baseline Metrics

Metric	Definition	How to Measure	Target Source
Appointment Confirmation Rate	% of scheduled appointments confirmed by patient	PMS report + manual sample	PMS confirmation status
No-Show Rate	% of confirmed appointments where patient did not show	PMS report	Schedule vs. arrived
Recall Effectiveness Rate	% of patients due for recall who schedule within 30 days of outreach	PMS recall report	Recall module
Same-Day/Short-Notice Fill Rate	% of open slots filled with <24 hour notice	Manual tracking	Front desk log
Front Desk Outbound Call Volume	Calls made per day for confirmations/recalls	Call log or estimate	Staff time study
Average Time to Confirm	Days between scheduling and patient confirmation	Sample 100 appointments	Manual calculation
Online Scheduling Utilization	% of appointments booked online vs. phone	PMS source tracking	PMS scheduling source
Patient Reactivation Rate	% of inactive patients (12+ months) who return after outreach	PMS patient status	90-day lookback
Text/Email Opt-In Rate	% of patients with mobile + permission to text	PMS patient data	Patient records
Staff Time on Manual Communication	Hours per week spent on confirmation/recall calls	Time study	Staff survey

Standardization Protocol for DSOs

To enable cross-location comparison:

1. Uniform Measurement Period: Capture all baselines for the same 30-day period across all locations
2. Consistent Definitions: Distribute written definitions for each metric to all Office Managers
3. Central Data Collection: Use standardized spreadsheet template for all locations to submit baselines
4. Validation: Regional Managers spot-check 10% of reported metrics against PMS data
5. Documentation: Store baselines in central repository with location ID, date range, and submitter

---

3. Location Readiness Assessment

Scoring Framework

Rate each location 1–5 on the following factors, then calculate composite score.

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

Score	Criteria
1	Internet outages weekly, PMS version >3 years old, hardware >7 years old
2	Occasional connectivity issues, PMS 2-3 versions behind, hardware 5-7 years old
3	Stable internet, PMS 1-2 versions behind, hardware 3-5 years old
4	Reliable internet, current PMS version, hardware 2-3 years old
5	Excellent connectivity, latest PMS version, modern hardware, prior successful tech deployments

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

Score	Criteria
1	>50% annual turnover, no prior tech training, known resistance to change
2	30-50% turnover, minimal tech training history, some resistance expected
3	20-30% turnover, moderate tech comfort, neutral toward change
4	10-20% turnover, good tech adoption history, generally positive toward improvement
5	<10% turnover, strong tech skills, enthusiastic early adopters of past tools

Factor 3: Patient Volume (Weight: 15%)

Score	Criteria	Strategic Note
1	<400 patients/month	Lower impact potential
2	400-600 patients/month	Modest impact
3	600-900 patients/month	Solid impact, manageable risk
4	900-1200 patients/month	High impact, moderate risk
5	>1200 patients/month	Highest impact, highest risk—not ideal for Wave 1

Note: Score 3-4 is ideal for Wave 1 pilots—enough volume to demonstrate impact without overwhelming risk

Factor 4: Existing Tech Stack Compatibility (Weight: 25%)

Score	Criteria
1	PMS not supported by Yapi, multiple conflicting tools, custom integrations
2	PMS supported but heavily customized, 2+ competing communication tools
3	Standard PMS, 1 existing communication tool to sunset, minor customizations
4	Clean PMS install, minimal existing communication tech, proven integration history
5	Ideal PMS version, no competing tools, previous successful Yapi integration (if applicable)

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

Score	Criteria
1	No suitable champion candidate, disengaged office manager, no tech-forward staff
2	Marginal candidate (willing but inexperienced), limited bandwidth
3	Adequate candidate (office manager with moderate tech comfort, some training experience)
4	Strong candidate (engaged office manager or lead provider, tech-savvy, respected by team)
5	Exceptional candidate (proven tech leader, previous implementation experience, strong communicator)

Composite Score Calculation

Factor	Weight	Location Score (1-5)	Weighted Score
IT Infrastructure	20%	___	___
Staff Tenure/Adaptability	20%	___	___
Patient Volume	15%	___	___
Tech Stack Compatibility	25%	___	___
Local Champion	20%	___	___
TOTAL	100%	—	___

Readiness Classification

Composite Score	Readiness Tier	Rollout Wave
4.0–5.0	High Readiness	Wave 1 Candidate
3.0–3.9	Moderate Readiness	Wave 2
2.0–2.9	Low Readiness	Wave 3 (with remediation)
<2.0	Not Ready	Defer until remediation complete

Wave Assignment Matrix (Example for 25-Location DSO)

Wave	Timeline	Location Count	Selection Criteria
Wave 1 (Pilot)	Weeks 3-5	2-3 locations	Score 4.0+, diverse geography, representative mix (urban/suburban, high/moderate volume)
Wave 2	Weeks 6-9	6-8 locations	Score 3.5+, leverage Wave 1 learnings
Wave 3	Weeks 10-14	8-10 locations	Score 3.0+, address identified issues
Wave 4	Weeks 15-18	Remaining	All remaining locations, full playbook refined

---

4. Rollout Strategy

Wave Structure Recommendation

For a 15–50 location DSO, we recommend a 4-wave structure with intentional buffer periods for organizational learning.

Wave Design

Week 1-2:   Pre-Implementation (All locations baseline, Wave 1 prep)
Week 3-5:   Wave 1 — Pilot (2-3 locations)
Week 6:     Buffer — Learning capture, playbook refinement
Week 7-9:   Wave 2 — Early Adopters (5-8 locations)
Week 10:    Buffer — Process optimization
Week 11-14: Wave 3 — Majority (8-15 locations)
Week 15:    Buffer — Final refinements
Week 16-18: Wave 4 — Remaining (all remaining locations)
Week 19-20: Stabilization and optimization across all locations

Wave 1 Pilot Selection Criteria

🟣 Executive Decision Required: Select 2–3 locations that meet ALL of the following:

Criterion	Rationale	Verification
Composite readiness score 4.0+	High probability of success	Readiness assessment
Exceptional local champion	Provides detailed feedback, troubleshoots locally	Champion interview
Patient volume 600-1000/month	Meaningful data without overwhelming risk	PMS report
Tech stack compatibility score 4+	Clean integration reduces variables	IT assessment
Geographic diversity	Tests in different regions/time zones	Location map
Represents portfolio mix	At least one general, one specialty if applicable	Location type
Regional manager engaged	Can dedicate oversight time	RM confirmation

⚠️ Wave 1 Anti-Patterns (Avoid):

• Highest-volume flagship locations (too much risk)
• Newly acquired locations (still integrating)
• Locations with ongoing PMS migrations
• Locations with significant staffing turnover in past 90 days
• Locations with known Office Manager departure planned

Timeline Per Wave

Wave 1: Pilot (Weeks 3-5)

Day	Activity	Owner
1-2	🔵 Yapi account setup and configuration	Yapi + IT Director
3-4	🔵 PMS integration and testing	Yapi + IT Director
5-6	Champion training (intensive, 4 hours)	Yapi + L&D Manager
7	Champion trains local staff (2 hours)	Local Champion
8	⚠️ Parallel run begins (old system + Yapi simultaneously)	Office Manager
8-12	Daily check-ins (15 min)	Champion + Regional Manager
13-14	Full transition to Yapi (sunset old system)	Office Manager
15-17	Intensive monitoring and optimization	Regional Manager
18-21	Document learnings, update playbook	VP of Operations

Wave 2-4: Standard Timeline (3 weeks per wave)

Week	Activity
Week 1	Configuration, integration, champion training
Week 2	Staff training, parallel run, daily monitoring
Week 3	Full go-live, optimization, feedback capture

Go/No-Go Criteria Between Waves

🟣 Executive Decision Required: Advance to next wave only when ALL criteria met.

Go Criteria (All must be true)

Category	Criterion	Threshold
Technical	Integration stable, no critical errors	<2 integration errors/day
Adoption	Staff using Yapi for >90% of confirmations	Usage audit
Outcomes	Confirmation rate maintained or improved	≥ baseline
Champion	Champion confidence in supporting expansion	Champion attestation
Staff	No unresolved staff resistance escalations	Regional Manager confirmation
Patient	No patient complaints about communication	Zero complaints

No-Go Triggers (Any one pauses advancement)

Trigger	Required Action
Integration failures affecting patient communication	Resolve with vendor before proceeding
>25% staff actively resisting adoption	Change management intervention
Confirmation rate dropped >5% from baseline	Root cause analysis and correction
Champion requests additional time	Extend wave by 1 week
Patient complaints about duplicate/missing messages	Communication workflow audit

Rollback Plan

If a wave experiences critical failure:

Immediate Response (Hour 0-4)

1. Champion activates previous communication method (manual calls or legacy system)
2. Champion notifies Regional Manager immediately
3. Regional Manager notifies VP of Operations
4. 🔵 Yapi support engaged for emergency troubleshooting

Short-Term Containment (Day 1-3)

1. Affected location returns to previous workflow entirely
2. Other Wave locations continue if unaffected
3. Root cause analysis initiated
4. Daily status calls until resolution

Decision Framework

Scenario	Action
Issue isolated to one location	Continue wave, remediate location separately
Issue affects multiple Wave locations	Pause wave, remediate before continuing
Issue is systemic (affects all locations)	Full pause, escalate to vendor executive sponsor

Rollback Authority

• Location-level rollback: Office Manager + Regional Manager can authorize 24-hour rollback
• Wave-level pause: Regional Manager + VP Operations required
• 🟣 Full program pause: VP Operations + C-suite required

---

5. Configuration & Integration (Weeks 2–3)

Practice Management System Integration

Dentrix Integration

Step	Action	Time	Owner
1	Verify Dentrix version compatibility (G6+ recommended)	15 min	IT
2	🔵 Install Yapi connector module (provided by Yapi)	30 min	Yapi + IT
3	Configure Dentrix API access (obtain API key from Dentrix)	20 min	IT
4	Map Dentrix appointment types to Yapi message categories	45 min	Office Manager + Yapi
5	Configure provider schedules (block times, off days)	30 min	Office Manager
6	Set operatory assignments if using room-specific messaging	20 min	Office Manager
7	⚠️ Test bidirectional sync (appointment changes reflect in both systems)	60 min	IT + Office Manager
8	Validate patient demographic sync (name, DOB, phone, email)	30 min	IT
9	Document any custom Dentrix fields that need mapping	30 min	Office Manager

Eaglesoft Integration

Step	Action	Time	Owner
1	Verify Eaglesoft version (18+)	15 min	IT
2	Enable Eaglesoft remote access if using cloud Yapi	20 min	IT
3	🔵 Install Yapi Eaglesoft bridge application	30 min	Yapi + IT
4	Configure database connection string	20 min	IT
5	Map procedure codes to appointment types	45 min	Office Manager
6	⚠️ Test sync: create test appointment, verify appears in Yapi within 5 min	30 min	IT
7	Configure recall types and intervals	30 min	Office Manager
8	Validate patient contact information import	30 min	IT

Open Dental Integration

Step	Action	Time	Owner
1	Verify Open Dental version (current or current-1 recommended)	10 min	IT
2	🔵 Enable Open Dental API in Program Properties	15 min	IT
3	🔵 Generate API key for Yapi	10 min	IT
4	🔵 Configure Yapi with Open Dental API endpoint	20 min	Yapi
5	⚠️ Test real-time sync (Open Dental known for excellent API)	30 min	IT
6	Map appointment categories and operatories	30 min	Office Manager
7	Configure automated appointment status updates	20 min	Office Manager

Denticon (Cloud) Integration

Step	Action	Time	Owner
1	🔵 Request Denticon-Yapi integration activation from Planet DDS	Vendor dependent	IT
2	🔵 Obtain Denticon API credentials	30 min	IT + Planet DDS
3	🔵 Configure Yapi with Denticon sandbox first	60 min	Yapi
4	Test in sandbox environment (create appointments, verify sync)	60 min	IT
5	🔵 Migrate configuration to production Denticon instance	30 min	Yapi
6	⚠️ Validate multi-location data segregation (critical for DSOs)	60 min	IT

Test Environment Setup

Validation Checklist

☐ Create test patient record (use obvious fake name: "Test Patient-DoNotContact") ☐ Create test appointment for test patient 48 hours in the future ☐ Verify automated confirmation message sends at correct time ☐ Test confirmation response (reply "C" to confirm) ☐ Verify confirmation status updates in PMS ☐ Test appointment change scenario (reschedule, verify new reminder) ☐ Test cancellation scenario (cancel appointment, verify message stops) ☐ Test recall sequence (mark test patient due for recall, verify outreach) ☐ ⚠️ Verify messages do NOT send to real patients during testing (sandbox mode) ☐ Test online scheduling link (book appointment, verify creates in PMS) ☐ Test two-way texting (send message, receive reply) ☐ Test after-hours auto-response ☐ Verify opt-out handling (patient texts STOP, confirm removed from messaging)

Test Environment Approach (DSO)

Approach	Description	When to Use
Centralized sandbox	One test environment for all locations to validate configuration	Initial configuration development
Location-specific test	Each location has test patient records to validate their specific setup	Pre-go-live validation per location
Production test	Limited test in production with real system (test patient only)	Final go-live verification

Recommendation: Start with centralized sandbox for template development, then location-specific test for 48 hours before each go-live.

Standardized Configuration Template (DSO)

Settings to Standardize Centrally

Setting	Standard Configuration	Rationale
Message timing	48 hours before, 24 hours before, 2 hours before	Consistent patient experience
Message branding	DSO brand name + location name	Brand consistency
Confirmation keyword	"C" or "YES" to confirm	Simplicity across all locations
Cancellation keyword	"CANCEL"	Standardized workflow
After-hours response	Standardized message with central scheduling number	Consistent service
Recall intervals	By procedure type (6mo hygiene, 12mo exam, etc.)	Clinical consistency
HIPAA-compliant message content	Approved templates that don't include PHI	Compliance
Opt-out compliance	Immediate removal, logged	Legal requirement
Character limits	160 characters for SMS	Deliverability

Settings Allowing Location Discretion

Setting	Customization Options	Who Approves
Provider-specific message wording	Personalized sign-off ("Dr. Smith's team")	Office Manager
Specialty-specific reminders	Ortho vs. general vs. pedo messaging	Office Manager
Local phone number display	Location-specific caller ID	Office Manager
Holiday schedule adjustments	Location-specific closure dates	Office Manager
Spanish language option	Enable if >20% Spanish-speaking patients	Office Manager
Appointment type-specific timing	Surgery reminders may need different cadence	Provider + OM

Security and HIPAA Compliance Verification

Enterprise HIPAA Checklist

☐ 🔵 Business Associate Agreement (BAA) signed with Yapi at enterprise level ☐ Verify BAA covers all locations and all data types (appointment, contact, health info) ☐ Document data storage location (US-based, SOC 2 compliant) ☐ Verify encryption standards (in transit: TLS 1.2+, at rest: AES-256) ☐ Confirm audit logging capability (all message access logged) ☐ Establish data retention policy (messages stored X months, then purged) ☐ Verify patient consent documentation (opt-in/opt-out tracked) ☐ Document breach notification procedures (Yapi → DSO → patients if applicable) ☐ Review access control model (role-based, minimum necessary) ☐ Confirm termination procedures (employee leaves, access revoked within X hours)

Access Control Setup

Role	Access Level	Example Permissions
HQ Admin	Enterprise-wide	All locations, all settings, user management
Regional Manager	Multi-location	View all locations in region, limited settings
Office Manager	Single location	Full access to own location, no other locations
Front Desk	Single location, limited	View appointments, send messages, no settings
Provider	Single location, view only	View schedule confirmation status only

Data Governance

🟣 Executive Decision Required: Data ownership and access policy

Policy Element	Options	Recommendation
Data ownership	DSO owns all data	Ensure contract specifies
Data portability	Can export all data on termination	Verify with vendor
Cross-location data access	HQ can see all, locations see only own	Role-based, enforce
Retention period	7 years (aligned with records retention)	Set in configuration
Audit frequency	Quarterly access review	Assign to compliance team

---

6. Team Training Plan

Train-the-Trainer Model

Champion Selection Criteria

Each location must identify ONE designated Champion who will:

• Receive intensive training from Yapi and central team
• Train their local team members
• Serve as first-line support for staff questions
• Provide feedback to central team on issues and improvements
• Participate in weekly champion calls during rollout

Criterion	Weight	Evaluation Method
Tech comfort	High	Self-assessment + manager observation
Communication skills	High	Can explain concepts clearly
Peer influence	High	Respected by team, not seen as "boss's pet"
Availability	Medium	Has bandwidth during rollout period
Role	Medium	Office Manager or senior front desk preferred
Longevity	Medium	Will be at location for 12+ months

Champion Responsibilities

Phase	Responsibility	Time Commitment
Training Phase	Attend 4-hour intensive training	4 hours
Pre-Go-Live	Train local team (2-3 sessions)	4-6 hours
Go-Live Week	Available for questions, on-call	2 hours/day additional
Week 2-4	Daily check with staff, escalate issues	30 min/day
Ongoing	New hire training, refreshers	2 hours/month

Standardized Training Materials

Create centrally, customize locally as appropriate:

Material	Creator	Customization Allowed
Role-specific training decks	Central L&D	Location name/branding only
Day 1 cheat sheets (per role)	Central L&D	None—standardized
Video walkthroughs (5 min each)	Central L&D or Yapi	None
FAQ document	Central L&D	Add local questions as they arise
Quick reference cards	Central L&D	None
Troubleshooting guide	Central IT + Yapi	Add local-specific issues
Patient communication scripts	Central Marketing	Office Manager can personalize tone

Role-Specific Training Outlines

Training Plan: Front Desk Staff

Primary Users — Estimated Training Time: 90 minutes

Training Format: Champion-led live demo (60 min) + hands-on practice (30 min)

Topics to Cover:

1. What Yapi does and why we're using it (5 min)
2. How Yapi integrates with our PMS—what syncs automatically (10 min)
3. Dashboard overview—what you'll see when you log in (15 min)
4. Reviewing confirmation status before patient arrival (10 min)
5. Two-way texting: responding to patient questions (15 min)
6. Manual message sending: when and how (10 min)
7. Common scenarios: patient says they didn't get reminder, etc. (15 min)
8. Hands-on: practice with test patient (30 min)

Common Resistance Points:

Concern	Response
"I'm faster doing it manually"	Show time study data; this tool is for consistency, not just speed