Apptoto — Implementation Playbook (DSO)
Apptoto Implementation Playbook for DSOs
1. Executive Summary
What Apptoto Does
Apptoto is an AI-powered appointment reminder and scheduling automation platform that sends intelligent, multi-channel reminders (SMS, email, voice) to patients, enables two-way messaging, automates appointment confirmations, and reduces no-shows through predictive engagement. The platform integrates with major dental practice management systems to sync appointments in real-time and optimize patient communication workflows.
| Scale Advantage |
Strategic Impact |
| Standardization |
Enforce consistent patient communication protocols across all 15–50 locations, eliminating front desk variability |
| Data Aggregation |
Centralized analytics on no-show rates, confirmation patterns, and communication effectiveness across your entire portfolio |
| Labor Efficiency at Scale |
Reduce manual reminder calls by 80–90% across all locations, translating to significant FTE savings |
| Predictive Intelligence |
AI-driven timing optimization learns from aggregate patient behavior patterns impossible to detect at single-location level |
| Brand Consistency |
Unified patient experience across all locations strengthens DSO brand equity |
Expected Timeline: Decision to Full Deployment
| Phase |
Timeline |
Milestones |
| Pre-Implementation |
Weeks 1–2 |
Vendor contract, stakeholder alignment, baseline metrics |
| Wave 1 Pilot |
Weeks 3–5 |
2–3 pilot locations live, initial optimization |
| Wave 2 Expansion |
Weeks 6–9 |
Next 5–8 locations deployed |
| Wave 3+ Full Rollout |
Weeks 10–16 |
Remaining locations, based on DSO size |
| Optimization & Stabilization |
Weeks 17–20 |
Full deployment, ROI assessment complete |
For a 30-location DSO, expect 16–20 weeks from contract signature to full deployment with optimized workflows.
2. Pre-Implementation Checklist (Weeks 1–2)
Technical Requirements
Hardware
☐ Verify each location has workstations with current browser versions (Chrome 90+, Edge 90+, Firefox 88+)
☐ Confirm minimum internet speed of 10 Mbps download/upload per location
☐ Identify any locations with firewall restrictions that may block SaaS platforms
Software
☐ Document PMS version at each location (Dentrix, Eaglesoft, Open Dental, Denticon, Curve)
☐ Verify PMS is on a supported version for Apptoto integration
☐ Identify locations using cloud-based vs. server-based PMS installations ⚠️
Network Requirements
☐ Ensure outbound ports 443 (HTTPS) and 587 (SMTP) are open
☐ Whitelist Apptoto domains: *.apptoto.com, *.twilio.com
☐ Verify SMS deliverability is not blocked by carrier-level filters
Vendor Onboarding Steps
| Step |
Owner |
Timeline |
Vendor Involvement |
| Execute enterprise agreement and BAA |
Legal/Ops |
Day 1–3 |
🔵 |
| Assign dedicated Apptoto account manager |
VP Ops |
Day 2 |
🔵 |
| Schedule enterprise onboarding kickoff |
Project Lead |
Day 3–5 |
🔵 |
| Establish support escalation contacts |
IT Lead |
Day 5 |
🔵 |
| Access enterprise admin portal |
IT Lead |
Day 5–7 |
🔵 |
☐ Enterprise Account Manager (strategic relationship)
☐ Technical Implementation Specialist (integration support)
☐ Enterprise Support Line (escalation path)
☐ Customer Success Manager (post-launch optimization)
Data/Access Prerequisites
☐ Generate API credentials for each PMS instance requiring integration
☐ Document admin login credentials for each location's PMS
☐ Export patient contact data quality report (% with valid mobile, % with email)
☐ Compile location-specific phone numbers for SMS sending
☐ Determine toll-free vs. local number strategy per location
☐ Document existing appointment reminder workflows (manual calls, existing tools)
Internal Stakeholder Alignment
Stakeholder Alignment Map 🟣
| Stakeholder Level |
Who |
Role in Implementation |
Communication Cadence |
| Board/Investors |
Board Chair, PE Partners |
Approval of enterprise spend, ROI expectations |
Monthly summary, final ROI report |
| C-Suite |
CEO, CFO, COO, CDO |
Strategic direction, budget approval, success metrics |
Bi-weekly updates, escalation point |
| VP Operations |
VP Ops, VP Clinical |
Project sponsor, cross-functional coordination |
Weekly standups, decision authority |
| Regional Managers |
Regional Directors |
Cascade communication, location accountability |
Weekly progress reviews |
| Office Managers |
Practice Managers |
Local execution, staff coordination |
Daily during rollout, weekly post-launch |
| Providers |
Dentists, Specialists |
Clinical workflow awareness, patient communication input |
Training + monthly feedback |
| Front Desk Staff |
Receptionists, Schedulers |
Primary users, daily workflow execution |
Training + daily support access |
Approval Checkpoints 🟣
☐ Budget approval from CFO/Finance
☐ Data governance approval from Compliance/Legal
☐ IT security approval for new SaaS vendor
☐ Clinical workflow sign-off from CDO
☐ Regional manager commitment to rollout timeline
Baseline Metrics to Capture BEFORE Go-Live ⚠️
Critical: Standardize measurement methodology across all locations to enable cross-location comparison.
| Metric |
How to Measure |
Standardization Notes |
| No-Show Rate |
(Missed appointments / Total scheduled) × 100 |
Define "no-show" consistently: include/exclude same-day cancellations |
| Confirmation Rate |
(Confirmed appointments / Total scheduled) × 100 |
Measure at consistent interval (e.g., 48 hours before appointment) |
| Manual Reminder Calls |
FTE hours/week spent on reminder calls |
Use time-tracking for 2 weeks pre-launch |
| Front Desk Phone Volume |
Inbound calls per day per location |
Pull from phone system reports |
| Patient Response Time |
Average time from reminder sent to confirmation received |
Estimate if no current system tracks this |
| Cancellation Rate |
(Cancelled appointments / Total scheduled) × 100 |
Separate from no-shows |
| Schedule Fill Rate |
(Filled appointment slots / Total available slots) × 100 |
Measure weekly average |
| Production per Chair Hour |
Daily production / Chair hours available |
Track 4-week average |
Baseline Data Collection Protocol
- Designate a single analyst or team to compile metrics centrally
- Use standardized Excel template distributed to all locations ⚠️
- Collect 4 weeks of pre-launch data minimum
- Identify outlier locations that may skew aggregate data
- Document any known data quality issues by location
Enterprise-Level Requirements
Network Standards Across Locations
☐ Verify all locations meet minimum bandwidth requirements
☐ Confirm VPN configurations (if applicable) allow Apptoto traffic
☐ Document locations with non-standard IT infrastructure
Hosting Model Decision 🟣
| Option |
Pros |
Cons |
Recommendation |
| Centralized (Enterprise) |
Unified admin, consistent settings, single pane of glass |
Requires reliable WAN, less local autonomy |
✅ Recommended for DSOs |
| Location-Level |
Faster local customization, less WAN dependency |
Configuration drift, harder to manage at scale |
Not recommended |
SSO (Single Sign-On) Configuration
☐ Determine SSO provider (Okta, Azure AD, Google Workspace)
☐ Verify Apptoto supports your SSO protocol (SAML 2.0) 🔵
☐ Plan SSO integration timeline with vendor
☐ Define role-based access levels in SSO
Centralized Credentialing
☐ Create standardized user roles: Admin, Manager, Staff, Read-Only
☐ Define role permissions matrix
☐ Establish user provisioning/deprovisioning workflow
☐ Document access audit requirements
3. Location Readiness Assessment
Scoring Framework
Score each factor 1–5 per location (1 = Low readiness, 5 = High readiness)
Factor 1: IT Infrastructure Maturity
| Score |
Criteria |
| 1 |
Outdated PMS (3+ versions behind), unreliable internet (<10 Mbps), aging hardware |
| 2 |
PMS 1–2 versions behind, occasional connectivity issues, hardware 4–5 years old |
| 3 |
Current PMS version, stable internet (10–25 Mbps), standard hardware |
| 4 |
Current PMS, reliable high-speed internet (25–50 Mbps), newer hardware |
| 5 |
Latest PMS version, enterprise-grade internet (50+ Mbps), modern hardware, cloud-based PMS |
Factor 2: Staff Tenure and Adaptability
| Score |
Criteria |
| 1 |
>40% annual turnover, no recent tech training, vocal resistance to change |
| 2 |
30–40% turnover, minimal tech training, passive resistance |
| 3 |
20–30% turnover, some tech training, neutral attitude toward change |
| 4 |
10–20% turnover, regular tech training, positive attitude, some tech champions |
| 5 |
<10% turnover, continuous learning culture, enthusiastic early adopters |
Factor 3: Patient Volume
| Score |
Criteria |
Impact Assessment |
| 1 |
<80 patients/week |
Low impact, low risk |
| 2 |
80–120 patients/week |
Moderate impact, low risk |
| 3 |
120–180 patients/week |
Good impact, moderate risk |
| 4 |
180–250 patients/week |
High impact, moderate risk |
| 5 |
>250 patients/week |
Highest impact, higher go-live risk |
Factor 4: Existing Tech Stack Compatibility
| Score |
Criteria |
| 1 |
Unsupported PMS, incompatible imaging, multiple conflicting tools |
| 2 |
Supported PMS with known integration issues, some conflicting tools |
| 3 |
Supported PMS, standard configuration, no major conflicts |
| 4 |
Well-integrated PMS, clean tech stack, documented workflows |
| 5 |
Fully integrated, modern cloud stack, existing Apptoto-compatible tools |
Factor 5: Local Champion Availability
| Score |
Criteria |
| 1 |
No identifiable champion, leadership actively resistant |
| 2 |
Potential champion but uncommitted or inexperienced |
| 3 |
Willing champion with moderate influence and tech comfort |
| 4 |
Engaged champion with strong influence and proven tech adoption history |
| 5 |
Exceptional champion (manager or lead provider) with dedicated capacity and enterprise perspective |
Composite Readiness Score Calculation
| Component |
Weight |
Rationale |
| IT Infrastructure |
25% |
Foundation for successful integration |
| Staff Adaptability |
25% |
Critical for adoption and sustainability |
| Patient Volume |
15% |
Balances impact vs. risk |
| Tech Stack Compatibility |
20% |
Reduces technical implementation risk |
| Local Champion |
15% |
Key driver of local success |
Formula: Composite Score = (IT × 0.25) + (Staff × 0.25) + (Volume × 0.15) + (Tech × 0.20) + (Champion × 0.15)
Score Interpretation
| Composite Score |
Readiness Level |
Rollout Wave |
| 4.0–5.0 |
High Readiness |
Wave 1 (Pilot) |
| 3.0–3.9 |
Moderate Readiness |
Wave 2 |
| 2.0–2.9 |
Low Readiness |
Wave 3 |
| <2.0 |
Not Ready |
Defer and remediate |
Sample Location Readiness Matrix
| Location |
IT (×0.25) |
Staff (×0.25) |
Volume (×0.15) |
Tech (×0.20) |
Champion (×0.15) |
Composite |
Wave |
| Oakdale |
5 (1.25) |
4 (1.00) |
3 (0.45) |
5 (1.00) |
5 (0.75) |
4.45 |
1 |
| Riverside |
4 (1.00) |
5 (1.25) |
4 (0.60) |
4 (0.80) |
4 (0.60) |
4.25 |
1 |
| Maple Grove |
3 (0.75) |
3 (0.75) |
3 (0.45) |
3 (0.60) |
3 (0.45) |
3.00 |
2 |
| Downtown |
2 (0.50) |
2 (0.50) |
5 (0.75) |
2 (0.40) |
2 (0.30) |
2.45 |
3 |
4. Rollout Strategy
Wave Structure Recommendation
| Wave |
Locations |
Timeline |
Purpose |
| Wave 1 (Pilot) |
2–3 locations |
Weeks 3–5 |
Validate integration, refine workflows, train champions, capture learnings |
| Wave 2 (Early Expansion) |
5–8 locations |
Weeks 6–9 |
Scale proven processes, stress-test support model, build momentum |
| Wave 3+ (Full Rollout) |
Remaining locations |
Weeks 10–16+ |
Efficient deployment using established playbook |
Wave 1 Pilot Location Selection Criteria 🟣
Required Criteria (Must Have)
☐ Composite readiness score ≥ 4.0
☐ PMS on supported version with confirmed API access
☐ Identified and committed local champion
☐ Office manager engaged and supportive of initiative
☐ No major competing projects during pilot period
Preferred Criteria (Nice to Have)
☐ Representative of broader portfolio (geography, size, specialty mix)
☐ Moderate patient volume (not highest-risk, not lowest-impact)
☐ Proximity to central/regional leadership for in-person support
☐ Track record of successful technology adoption
☐ Clean patient data (high % valid mobile numbers)
Anti-Criteria (Avoid for Wave 1)
⚠️ Locations with recent staff turnover or leadership changes
⚠️ Highest-volume locations (too much at stake)
⚠️ Locations with unresolved PMS or IT issues
⚠️ Geographically isolated locations (harder to support)
Timeline Per Wave
Wave 1: Weeks 3–5 (Pilot)
| Week |
Activities |
| Week 3 |
Integration setup, configuration, champion training |
| Week 4 |
Soft launch with limited patient volume, daily monitoring |
| Week 5 |
Full go-live, workflow optimization, capture lessons learned |
Buffer: 1 week between Wave 1 and Wave 2 for process refinement
Wave 2: Weeks 6–9
| Week |
Activities |
| Week 6 |
Deploy to first 3–4 Wave 2 locations |
| Week 7 |
Deploy to remaining Wave 2 locations |
| Week 8–9 |
Stabilization, optimization, support capacity management |
Buffer: 1 week between Wave 2 and Wave 3
Wave 3+: Weeks 10–16+
| Week |
Activities |
| Weeks 10–12 |
Deploy to 8–10 locations per week |
| Weeks 13–14 |
Final locations go-live |
| Weeks 15–16 |
Portfolio-wide stabilization |
Go/No-Go Criteria 🟣
To Advance from Wave 1 to Wave 2
| Category |
Go Criteria |
No-Go Criteria |
| Technical |
Integration stable >95% uptime |
Persistent sync failures or data issues |
| Adoption |
>80% staff using system as designed |
>30% staff workarounds or manual overrides |
| Patient Impact |
No-show rate stable or improved |
No-show rate increased >10% |
| Support Load |
Manageable ticket volume, fast resolution |
Support overwhelmed, unresolved critical issues |
| Champion Confidence |
Champions recommend proceeding |
Champions advise delay |
To Advance from Wave 2 to Wave 3
| Category |
Go Criteria |
No-Go Criteria |
| Scalability |
Support model handles 5–8 locations |
Support capacity maxed out |
| Consistency |
Configuration reproducible across locations |
Significant per-location customization required |
| ROI Indicators |
Early positive metrics vs. baseline |
No measurable improvement in key metrics |
| Training Model |
Train-the-trainer working effectively |
Centralized training still required |
Rollback Plan ⚠️
Rollback Triggers
- Critical integration failure affecting >50% of appointments
- Data security incident or HIPAA concern
- Staff unable to perform core functions for >24 hours
- Patient complaints exceed defined threshold (>1% of communications)
Rollback Procedure
Immediate (Hour 0–2)
- Disable Apptoto reminders at affected location(s)
- Revert to manual confirmation workflow
- Notify regional manager and central project team
Short-Term (Hours 2–24)
- Document issue with vendor support 🔵
- Activate backup communication protocol (manual calls)
- Communicate timeline to staff
Recovery (Days 1–5)
- Root cause analysis with vendor
- Remediation plan with go/no-go for re-launch
- Adjust rollout timeline for remaining waves
Isolation Protocol
- Rollback at one location does NOT require pause at other locations unless issue is systemic
- Regional manager determines if issue is isolated or portfolio-wide
- Central IT escalates immediately if integration layer (API/PMS) is implicated
5. Configuration & Integration (Weeks 2–3)
Step-by-Step PMS Integration
Dentrix Integration 🔵
| Step |
Action |
Owner |
Time Estimate |
| 1 |
Verify Dentrix version (G6.2+ required for best results) |
Local IT |
15 min |
| 2 |
Install Dentrix Connector (if server-based) |
IT/Vendor |
1 hour |
| 3 |
Configure Dentrix API access credentials |
IT |
30 min |
| 4 |
Map appointment types in Apptoto to Dentrix categories |
Project Lead |
1 hour |
| 5 |
Test sync: Create test appointment in Dentrix |
Champion |
15 min |
| 6 |
Verify appointment appears in Apptoto within 15 min |
Champion |
30 min |
| 7 |
Test bidirectional sync: Confirm in Apptoto → status in Dentrix ⚠️ |
Champion |
30 min |
| 8 |
Validate provider calendars sync correctly |
Champion |
30 min |
Eaglesoft Integration 🔵
| Step |
Action |
Owner |
Time Estimate |
| 1 |
Verify Eaglesoft version (21.x+ recommended) |
Local IT |
15 min |
| 2 |
Enable Eaglesoft API and generate API key |
IT |
45 min |
| 3 |
Configure Apptoto with Eaglesoft API credentials |
IT/Vendor |
30 min |
| 4 |
Map appointment types and operatories |
Project Lead |
1 hour |
| 5 |
Test initial sync (allow 30 min for first sync) |
Champion |
45 min |
| 6 |
Validate patient contact data pulled correctly ⚠️ |
Champion |
30 min |
| 7 |
Test confirmation writeback to Eaglesoft |
Champion |
30 min |
Open Dental Integration 🔵
| Step |
Action |
Owner |
Time Estimate |
| 1 |
Verify Open Dental version (19.x+ required) |
Local IT |
15 min |
| 2 |
Enable Open Dental API in Program Links |
IT |
30 min |
| 3 |
Generate API key with appropriate permissions |
IT |
20 min |
| 4 |
Configure Apptoto connection |
IT/Vendor |
30 min |
| 5 |
Map appointment types, providers, operatories |
Project Lead |
45 min |
| 6 |
Test sync and validate data accuracy |
Champion |
30 min |
| 7 |
Configure confirmation status writeback |
Champion |
20 min |
Denticon (Cloud) Integration 🔵
| Step |
Action |
Owner |
Time Estimate |
| 1 |
Request API access from Planet DDS support |
IT |
1–3 days |
| 2 |
Receive API credentials and documentation |
IT |
— |
| 3 |
Configure Apptoto with Denticon API |
IT/Vendor |
1 hour |
| 4 |
Test sync across multiple locations (enterprise advantage) |
Champion |
1 hour |
| 5 |
Validate multi-location data segregation |
IT |
30 min |
Test Environment Setup and Validation Checklist
Pre-Production Testing Requirements
☐ Create dedicated test patient records (clearly marked as test data)
☐ Configure test phone numbers/emails to receive messages
☐ Set up test appointment types that won't impact production
☐ Document expected behavior for each test scenario
Integration Validation Checklist
| Test Scenario |
Expected Result |
Pass/Fail |
| New appointment created in PMS |
Syncs to Apptoto within 15 minutes |
☐ |
| Appointment rescheduled in PMS |
Apptoto updates with new time, cancels old reminder |
☐ |
| Appointment cancelled in PMS |
Apptoto removes from queue, no reminder sent |
☐ |
| Patient confirms via SMS |
Status updates in both Apptoto and PMS ⚠️ |
☐ |
| Patient requests reschedule via SMS |
Alert generated for front desk |
☐ |
| Patient opts out of SMS |
Opt-out recorded, no future SMS sent |
☐ |
| Voice reminder delivered |
Call completed, response captured |
☐ |
| Email reminder delivered |
Email sent, open/click tracked |
☐ |
Data Migration / Historical Data
⚠️ Note: Apptoto primarily syncs forward-looking appointments. Historical data migration is typically not required.
☐ Run report on % of patients with valid mobile numbers
☐ Identify patients with landlines only (voice reminder candidates)
☐ Flag patients with no contact info for staff follow-up
☐ Validate email addresses (check for obvious errors)
Data Cleansing Recommendations
- Target: >80% of active patients with valid mobile numbers
- If below target, consider patient data update campaign before go-live
- Estimate 2–4 weeks for meaningful contact data improvement
Security and HIPAA Compliance Verification Checklist
Enterprise-Level HIPAA Requirements
| Requirement |
Verification Step |
Status |
| Business Associate Agreement (BAA) 🔵 |
Execute BAA with Apptoto before any PHI transmission |
☐ |
| Data Encryption - Transit |
Verify TLS 1.2+ for all data transmission |
☐ |
| Data Encryption - Rest |
Confirm AES-256 encryption for stored data |
☐ |
| Access Controls |
Role-based access configured, minimum necessary principle applied |
☐ |
| Audit Logging |
Confirm Apptoto logs access and modifications |
☐ |
| Data Retention |
Document retention policy, confirm deletion capability |
☐ |
| Breach Notification |
Verify vendor's breach notification commitment |
☐ |
| Subcontractor BAAs |
Confirm Apptoto has BAAs with Twilio and other subcontractors |
☐ |
Access Control Matrix
| Role |
View Appointments |
Send Messages |
Modify Settings |
View Reports |
Admin Functions |
| Enterprise Admin |
✅ All locations |
✅ |
✅ |
✅ All locations |
✅ |
| Regional Manager |
✅ Region |
❌ |
❌ |
✅ Region |
❌ |
| Location Manager |
✅ Location |
✅ |
Limited |
✅ Location |
❌ |
| Front Desk Staff |
✅ Location |
✅ |
❌ |
Limited |
❌ |
| Read-Only |
✅ As assigned |
❌ |
❌ |
✅ As assigned |
❌ |
DSO-Specific Configuration
Standardized Configuration Template (Centralize These)
| Setting |
Standard Value |
Rationale |
| Reminder Sequence |
7-day email → 3-day SMS → 1-day SMS → 2-hour SMS |
Optimal confirmation window with escalation |
| SMS Sender Name |
DSO brand name or practice brand |
Brand consistency |
| Message Templates |
Centrally approved language |
Compliance, brand voice |
| Business Hours |
No messages before 8am or after 8pm local |
Patient experience |
| Confirmation Keywords |
"C" or "CONFIRM" = confirmed, "R" = reschedule request |
Simplicity |
| Two-Way Messaging |
Enabled |
Patient engagement |
| Opt-Out Handling |
Automatic compliance with STOP |
TCPA compliance |
| No-Show Flagging |
Automatic status update at appointment time +15 min |
Data accuracy |
Location-Specific Configuration (Allow Local Discretion)
| Setting |
Local Discretion |
Examples |
| Provider-Specific Messages |
Yes |
Specialist may have different instructions |
| Appointment Type Language |
Yes |
Pediatric practice uses kid-friendly language |
| Language Preferences |
Yes |
Bilingual locations may send Spanish messages |
| Voice vs. SMS Default |
Yes |
Demographics may favor one channel |
| Additional Reminders |
Yes |
High no-show location adds extra touchpoint |
Centralized Test Environment Approach ✅ Recommended
- Create enterprise-level test account with Apptoto 🔵
- Configure test account with standardized templates
- Connect test PMS instances (if available) or use sandbox
- Validate configuration centrally before location deployment
- Export proven configuration to production locations
6. Team Training Plan
Train-the-Trainer Model for DSOs
Overview
- Goal: Certify 1 local champion per location to train their own team
- Central Team: Trains Wave 1 champions directly; Wave 1 champions help train subsequent waves
- Scalability: Reduces central training burden from N locations to ~3 master sessions
Champion Selection Criteria
| Criteria |
Weight |
Ideal Profile |
| Tech Comfort |
High |
Uses smartphone/apps comfortably, learns new software quickly |
| Influence |
High |
Respected by peers, can motivate adoption |
| Communication |
Medium |
Can explain concepts clearly, patient with learners |
| Availability |
Medium |
Has capacity for training (not maxed out operationally) |
| Tenure |
Medium |
Has been at location 1+ years, knows workflows |
| Role |
Variable |
Office manager ideal, but lead receptionist or tech-forward provider acceptable |
Champion Responsibilities
| Phase |
Responsibility |
| Pre-Launch |
Complete certification training, customize materials for local context |
| Go-Live Week |
Lead local training sessions, be on-site for questions |
| Weeks 2–4 |
Daily check-ins with staff, report issues to regional/central |
| Ongoing |
Train new hires, deliver quarterly refreshers, submit enhancement suggestions |
Champion Certification Checklist
☐ Complete 2-hour central training session (live or video)
☐ Pass configuration quiz (80% minimum score)
☐ Demonstrate message sending and workflow in test environment
☐ Deliver practice training to central team observer
☐ Receive champion toolkit (materials, escalation guide)
Role-Specific Training Outlines
Front Desk / Office Manager (Primary Users)
Training Time: 90 minutes + 30-minute practicum
Format: Live demo (in-person or video), hands-on practice, shadow session Day 1
Learning Objectives
- Understand how Apptoto syncs with PMS and what triggers messages
- Monitor incoming confirmations and reschedule requests
- Respond to patient two-way messages
- Handle opt-outs and message failures
- Run basic reports (confirmation rate, no-show rate)
- Troubleshoot common issues before escalating
Agenda
| Time |
Topic |
| 0–15 min |
Why we're implementing (context, benefits, expectations) |
| 15–40 min |
Dashboard walkthrough: appointments, message queue, conversation threads |
| 40–60 min |
Workflow scenarios: confirmations, reschedule requests, cancellations, opt-outs |
| 60–75 min |
Reporting overview and daily/weekly review process |
| 75–90 min |
Troubleshooting guide and escalation path |
Common Resistance Points & Responses
| Resistance |
Response |
| "I already have a good system with reminder calls." |
"This doesn't replace your personal touch—it handles the routine calls so you can focus on patients who need real conversation." |
| "Patients don't want texts from their dentist." |
"93% of patients prefer text reminders. You'll actually see better responses than phone calls." |
| "What if something goes wrong and patients don't show up?" |
"We'll run parallel for the first week. Nothing changes for patients until we're confident." |
Day 1 Cheat Sheet: Front Desk
┌─────────────────────────────────────────────────────────────┐
│ APPTOTO QUICK REFERENCE - FRONT DESK │
├─────────────────────────────────────────────────────────────┤
│ CHECK FIRST THING EVERY MORNING: │
│ ☐ Dashboard → Today's appointments → All synced? │
│ ☐ Conversations tab → Any unread patient messages? │
│ ☐ Alerts → Any delivery failures? │
│ │
│ PATIENT CONFIRMS ("C" or "CONFIRM"): │
│ → Status auto-updates in PMS (green = confirmed) │
│ → No action needed unless you see otherwise │
│ │
│ PATIENT REQUESTS RESCHEDULE ("R"): │
│ → Alert appears in Conversations │
│ → Respond via Apptoto OR call patient │
│ → Update appointment in PMS (Apptoto syncs automatically) │
│ │
│ PATIENT