Zocdoc — Implementation Playbook (DSO)
Zocdoc Implementation Playbook for DSOs
A Strategic Guide for Enterprise-Scale Scheduling & Operations Deployment
1. Executive Summary
What Zocdoc Does
Zocdoc is a patient scheduling and practice visibility platform that connects patients seeking dental care with available appointment slots across your locations in real-time. The platform handles online booking, automated appointment reminders, patient reviews, insurance verification, and waitlist management—serving as a digital front door that operates 24/7 without requiring front desk intervention.
Why DSOs Specifically Benefit from AI-Powered Scheduling Technology
Scale Advantages: With 15–50 locations, you're managing thousands of appointment slots daily. AI-driven scheduling eliminates the inefficiency of decentralized booking processes, reduces no-show rates through predictive reminder optimization, and surfaces systemwide availability that individual locations would never expose to patients searching online.
Standardization: Zocdoc enforces consistent patient acquisition and scheduling workflows across all locations—regardless of whether your Phoenix office has a veteran office manager and your Tampa location has new hires. The technology becomes the equalizer.
Data Aggregation: For the first time, you gain enterprise visibility into scheduling patterns, demand by specialty, conversion rates by location, and patient acquisition costs—data that lives in a centralized dashboard rather than scattered across PMS instances.
Expected Timeline: Decision to Full Deployment
| Phase |
Duration |
Milestone |
| Pre-Implementation |
Weeks 1–2 |
Technical readiness confirmed, baseline metrics captured |
| Pilot Wave (2–3 locations) |
Weeks 3–6 |
Live booking, initial optimization |
| Wave 2 Expansion (5–8 locations) |
Weeks 7–12 |
Scaled deployment, playbook refinement |
| Wave 3 Full Rollout (remaining locations) |
Weeks 13–20 |
Enterprise-wide deployment |
| Total Timeline |
16–20 weeks |
Full deployment with stabilization |
2. Pre-Implementation Checklist (Weeks 1–2)
Technical Requirements
Hardware
- ☐ Workstations at each location with Chrome/Edge (updated within last 6 months)
- ☐ Minimum 10 Mbps upload/download per location (25+ Mbps recommended for high-volume sites)
- ☐ Patient-facing tablets for check-in kiosks (if deploying Zocdoc Check-In)
Software
- ☐ Practice Management System (PMS) version compatibility confirmed:
- Dentrix G6.2+
- Eaglesoft 21+
- Open Dental 21.1+
- Curve Dental (cloud-native)
- ☐ Current browser versions on all workstations
- ☐ VPN/firewall configurations documented if using on-premise PMS
Network
- ☐ Static IP addresses documented for locations with on-premise servers
- ☐ Firewall whitelist entries prepared for Zocdoc API endpoints
- ☐ Network stability assessment (uptime >99.5% over past 90 days)
Integrations
- ☐ Identify existing patient communication tools (Weave, RevenueWell, Lighthouse) that may overlap
- ☐ Document current insurance verification workflow and tools
- ☐ Map patient review platforms currently in use (Google, Yelp, proprietary)
Vendor Onboarding Steps 🔵
| Step |
Action |
Owner |
Timeline |
| 1 |
Execute Master Service Agreement (MSA) and Business Associate Agreement (BAA) |
Legal/Compliance + Zocdoc |
Day 1–3 |
| 2 |
Assign dedicated Account Executive and Implementation Manager |
Zocdoc |
Day 1 |
| 3 |
Complete enterprise onboarding questionnaire |
VP Operations + Zocdoc |
Day 3–5 |
| 4 |
Schedule kickoff call with technical implementation team |
Central IT + Zocdoc |
Day 5 |
| 5 |
Receive sandbox/test environment credentials |
Zocdoc → Central IT |
Day 7 |
| 6 |
Establish escalation contacts and SLA expectations |
VP Operations + Zocdoc |
Day 7 |
Key Contacts to Establish:
- ☐ Zocdoc Enterprise Account Executive (strategic relationship owner)
- ☐ Zocdoc Implementation Manager (day-to-day project lead)
- ☐ Zocdoc Technical Support escalation contact (for integration issues)
- ☐ Zocdoc Customer Success Manager (post-implementation optimization)
Data/Access Prerequisites
Credentials Required
- ☐ PMS admin credentials for each location (or centralized if applicable)
- ☐ API keys or integration credentials from PMS vendor
- ☐ SSO provider credentials (Okta, Azure AD, etc.) if implementing enterprise SSO
- ☐ Insurance eligibility verification service credentials (if using Zocdoc's verification)
Data Exports Needed
- ☐ Provider roster with NPIs, specialties, and license numbers
- ☐ Location addresses, phone numbers, and hours of operation
- ☐ Insurance plans accepted per location
- ☐ Appointment type catalog with duration standards
- ☐ Historical appointment data (past 12 months) for baseline analysis
⚠️ Common Failure Point: PMS vendors often take 2–3 weeks to provision API access. Initiate this request on Day 1.
Internal Stakeholder Alignment 🟣
Stakeholder Alignment Map
| Stakeholder Level |
Key Individuals |
Role in Implementation |
Communication Needs |
| Board/Investors |
Board Chair, PE Partners |
Approval of enterprise expenditure, strategic alignment confirmation |
Monthly summary updates, ROI projections |
| C-Suite |
CEO, CFO, COO, CDO |
Executive sponsorship, budget authorization, strategic direction |
Weekly status updates, escalation decisions |
| VP Operations |
VP Ops, VP Clinical |
Day-to-day project ownership, resource allocation |
Daily involvement during rollout phases |
| Regional Managers |
Regional Directors (4–8) |
Wave coordination, local escalation, champion management |
Weekly briefings, wave-specific playbooks |
| Office Managers |
Location OMs (15–50) |
Local execution, staff coordination, go-live ownership |
Training + daily check-ins during go-live |
| Providers |
Lead Dentists, Associates |
Clinical workflow adoption, schedule preference configuration |
Role-specific training, feedback loops |
| Front Desk Staff |
Patient coordinators |
Primary daily users |
Comprehensive training + cheat sheets |
Approval Gates Required 🟣
- ☐ Budget Approval: CFO/CEO sign-off on enterprise subscription and implementation costs
- ☐ Legal/Compliance Approval: BAA execution, data governance review
- ☐ IT Security Approval: Integration architecture, data flow review
- ☐ Clinical Leadership Approval: Chief Dental Officer endorsement of workflow changes
- ☐ HR/Training Approval: Training time allocation across locations
Baseline Metrics to Capture
⚠️ Critical: Without standardized baseline metrics, you cannot demonstrate ROI or compare location performance post-implementation.
Required Metrics (Standardized Across All Locations)
| Metric Category |
Specific Metric |
Measurement Method |
Capture Period |
| Patient Acquisition |
New patient appointments per month |
PMS report |
Trailing 3 months |
| Patient Acquisition |
Patient acquisition cost |
Marketing spend ÷ new patients |
Trailing 3 months |
| Patient Acquisition |
Source of new patients (referral breakdown) |
PMS or intake forms |
Trailing 3 months |
| Scheduling Efficiency |
Chair utilization rate |
Scheduled hours ÷ available hours |
Trailing 3 months |
| Scheduling Efficiency |
Time-to-appointment (days from request to visit) |
Manual tracking or PMS |
Sample 50 patients |
| Scheduling Efficiency |
No-show rate |
No-shows ÷ scheduled appointments |
Trailing 3 months |
| Scheduling Efficiency |
Same-day/next-day fill rate |
Last-minute bookings ÷ open slots |
Trailing 3 months |
| Revenue |
Production per new patient (first 90 days) |
PMS report |
Trailing 6 months |
| Patient Experience |
Online review volume and rating |
Google/Yelp/Zocdoc |
Current snapshot |
| Staff Efficiency |
Phone calls received per day |
Phone system report |
Trailing 1 month |
| Staff Efficiency |
Time spent on manual scheduling tasks |
Staff survey estimate |
Snapshot |
Standardization Protocol
- ☐ Create a centralized data collection template (Google Sheets or similar)
- ☐ Assign Regional Managers responsibility for location data accuracy
- ☐ Set data submission deadline: 5 business days before pilot launch
- ☐ Validate data completeness—flag locations with incomplete baselines
Enterprise-Level Requirements
Network Standards
- ☐ Minimum bandwidth standard adopted across all locations
- ☐ Consistent firewall/security policy applied
- ☐ Network monitoring in place to identify connectivity issues pre-emptively
Hosting Architecture Decision 🟣
| Option |
Best For |
Considerations |
| Centralized Configuration |
DSOs with standardized workflows |
Easier governance, limited local flexibility |
| Location-Level Configuration |
DSOs with diverse specialties/brands |
More setup time, requires local admin training |
| Hybrid |
Most DSOs |
Central standards + limited local customization |
Recommendation: Hybrid approach—centralize branding, appointment types, and insurance configurations; localize provider schedules and hours.
Single Sign-On (SSO)
- ☐ Confirm Zocdoc supports your identity provider (Okta, Azure AD, Google Workspace)
- ☐ Coordinate with IT to configure SAML/OIDC integration
- ☐ Test SSO in sandbox before production rollout
🔵 Vendor Involvement: Zocdoc enterprise team provides SSO configuration documentation and technical support.
Centralized Credentialing
- ☐ Compile master provider roster with credentialing status
- ☐ Ensure all listed providers have current state licenses
- ☐ Verify NPI numbers are active and correctly associated
- ☐ Plan for credentialing updates workflow (new hires, departures)
3. Location Readiness Assessment
Scoring Framework
Each location should be scored on the following five factors using a 1–5 scale. Composite scores determine rollout wave placement.
Factor 1: IT Infrastructure Maturity
| Score |
Criteria |
| 1 |
Outdated PMS version, unreliable internet, aging workstations |
| 2 |
PMS within 1 version of supported, occasional connectivity issues |
| 3 |
PMS supported version, stable internet (15+ Mbps), functional hardware |
| 4 |
Current PMS, reliable high-speed internet (25+ Mbps), recent hardware |
| 5 |
Latest PMS, enterprise-grade network, modern workstations, IT support on-site |
Factor 2: Staff Tenure and Adaptability
| Score |
Criteria |
| 1 |
High turnover (>40% annually), minimal tech training history, known resistance |
| 2 |
Moderate turnover (25–40%), limited tech comfort, some resistance expected |
| 3 |
Average turnover (15–25%), adequate tech skills, neutral toward change |
| 4 |
Low turnover (<15%), demonstrated tech adoption success, positive toward change |
| 5 |
Stable team, tech-forward culture, history of successful implementations |
Factor 3: Patient Volume
| Score |
Criteria |
Strategic Note |
| 1 |
<200 patients/month |
Low impact potential |
| 2 |
200–400 patients/month |
Moderate impact |
| 3 |
400–600 patients/month |
Good balance of impact and manageable risk |
| 4 |
600–800 patients/month |
High impact, requires strong execution |
| 5 |
>800 patients/month |
Highest impact, highest risk—consider for Wave 2+ |
Factor 4: Existing Tech Stack Compatibility
| Score |
Criteria |
| 1 |
PMS not supported by Zocdoc, multiple conflicting tools |
| 2 |
PMS supported but older version, overlapping reminder systems |
| 3 |
PMS fully supported, some tool overlap to manage |
| 4 |
PMS current version, minimal overlap, clear integration path |
| 5 |
PMS current with existing Zocdoc-like tools, easy transition |
Factor 5: Local Champion Availability
| Score |
Criteria |
| 1 |
No identifiable champion, leadership vacuum |
| 2 |
Potential champion identified but unconfirmed availability |
| 3 |
Champion identified with moderate capacity and interest |
| 4 |
Strong champion (OM or provider) committed to ownership |
| 5 |
Multiple champions, including provider and OM alignment |
Composite Score Calculation
Formula: Sum of all five factors (max = 25)
| Composite Score |
Readiness Tier |
Wave Recommendation |
| 21–25 |
High Readiness |
Wave 1 (Pilot) |
| 16–20 |
Moderate-High Readiness |
Wave 2 |
| 11–15 |
Moderate Readiness |
Wave 3 |
| 6–10 |
Low Readiness |
Defer or Remediate First |
| 1–5 |
Not Ready |
Requires infrastructure investment before rollout |
Location Assessment Template
| Location |
IT (1-5) |
Staff (1-5) |
Volume (1-5) |
Tech Stack (1-5) |
Champion (1-5) |
Total |
Wave |
| Site A |
|
|
|
|
|
/25 |
|
| Site B |
|
|
|
|
|
/25 |
|
| Site C |
|
|
|
|
|
/25 |
|
Rollout Sequence Recommendations
Wave 1 Selection Criteria (Pilot: 2–3 Locations)
- ☐ Composite score ≥21
- ☐ Geographic diversity (different regions represented)
- ☐ Mix of practice profiles (general dentistry + at least one specialty if applicable)
- ☐ Strong local champion willing to participate in feedback loops
- ☐ Not highest-volume locations (manage risk during learning phase)
Wave 2 Selection Criteria (5–8 Locations)
- ☐ Composite score 16–20
- ☐ Include at least one high-volume location to test at scale
- ☐ Address any remediation items surfaced during Wave 1
Wave 3 Selection Criteria (Remaining Locations)
- ☐ Composite score 11–15 (with any remediations complete)
- ☐ Apply all lessons learned and refined playbook from Waves 1–2
4. Rollout Strategy
Wave Structure Overview
| Wave |
Locations |
Duration |
Buffer Before Next Wave |
| Wave 1 (Pilot) |
2–3 |
4 weeks |
2 weeks |
| Wave 2 (Expansion) |
5–8 |
4 weeks |
1 week |
| Wave 3 (Full Rollout) |
Remaining |
4–6 weeks |
N/A |
Wave 1: Pilot Phase Details
Selection Criteria Checklist
- ☐ High readiness score (21+)
- ☐ Champion identified and confirmed
- ☐ Representative of broader portfolio (not an outlier)
- ☐ Regional Manager available for active oversight
- ☐ Manageable patient volume (400–600/month ideal)
Timeline: Week 3–6
| Week |
Activities |
| Week 3 |
Configuration, integration testing, staff training |
| Week 4 |
Go-live, daily monitoring, issue resolution |
| Week 5 |
Optimization, workflow refinement |
| Week 6 |
Assessment, lessons learned documentation |
Daily/Weekly Cadence During Pilot
- Daily (Week 4): 15-minute check-in with location champion
- Every Other Day (Week 5): Issue log review, workflow adjustment
- Weekly (Weeks 4–6): Regional Manager + VP Ops status call
- End of Wave: Formal debrief with all stakeholders
Go/No-Go Criteria 🟣
Criteria to Advance from Wave 1 to Wave 2
| Category |
Go Criteria |
No-Go Trigger |
| Technical |
<5 integration errors per day after Week 4 |
>20 errors/day or data sync failure |
| Adoption |
>80% of appointments booked via Zocdoc flow |
<50% adoption after training |
| Staff Sentiment |
Champion reports "manageable" or better |
Champion escalates inability to continue |
| Patient Experience |
No patient complaints about booking process |
>5 patient complaints about booking issues |
| Revenue Impact |
No measurable decrease in new patient appointments |
>20% decrease in new patients |
Decision Authority 🟣
- Go Decision: VP Operations + Regional Manager
- No-Go Decision: Escalate to COO/CEO for path forward
Rollback Plan
Triggers for Rollback
- Critical integration failure not resolvable within 48 hours
- Patient-facing issues causing appointment loss
- Staff refusal to use system after remediation attempts
- Data security or HIPAA concern identified
Rollback Procedure
| Step |
Action |
Owner |
Timeline |
| 1 |
Disable Zocdoc booking on affected location's profile |
Zocdoc + Central IT |
2 hours |
| 2 |
Revert to previous booking workflow (phone/web form) |
Office Manager |
Immediate |
| 3 |
Communicate to patients with pending Zocdoc appointments |
Front desk |
Same day |
| 4 |
Document root cause and resolution plan |
VP Operations |
48 hours |
| 5 |
Re-assess readiness before re-attempting |
Regional Manager |
1–2 weeks |
Isolation Protocol
- Rollback at one location does NOT impact other locations in same wave
- Wave progression decisions consider rollback locations separately
- Failed location moves to remediation track, not abandoned
Wave 2 and Wave 3 Refinements
Wave 2 Adjustments (Based on Pilot Learnings)
- ☐ Update training materials with pilot FAQs
- ☐ Refine configuration templates based on what worked
- ☐ Add any new integration troubleshooting steps to runbook
- ☐ Adjust champion responsibilities based on pilot champion feedback
Wave 3 Acceleration Opportunities
- ☐ Parallel deployments within regions (multiple locations same week)
- ☐ Shortened training for locations with experienced OMs
- ☐ Reduced daily check-in cadence if prior waves stable
5. Configuration & Integration (Weeks 2–3)
Practice Management System Integration
Dentrix Integration 🔵
| Step |
Action |
Owner |
Est. Time |
| 1 |
Confirm Dentrix version compatibility (G6.2+) |
Central IT |
30 min |
| 2 |
Enable Dentrix Connector service on practice server |
Central IT |
1 hour |
| 3 |
🔵 Request Zocdoc integration credentials from Zocdoc |
Zocdoc |
1 day |
| 4 |
Configure API connection in Dentrix connector settings |
Central IT |
1 hour |
| 5 |
Map appointment types from Dentrix to Zocdoc |
Office Manager + Zocdoc |
2 hours |
| 6 |
Test bi-directional sync (book test appointment via Zocdoc, verify in Dentrix) |
Central IT |
1 hour |
| 7 |
Validate patient demographic data flow |
Central IT |
1 hour |
⚠️ Common Failure Point: Dentrix connector requires specific Windows service configurations. Verify service is running and set to auto-start.
Eaglesoft Integration 🔵
| Step |
Action |
Owner |
Est. Time |
| 1 |
Confirm Eaglesoft version (21+) and cloud vs. on-premise |
Central IT |
30 min |
| 2 |
🔵 Coordinate with Patterson technical support for API enablement |
Central IT + Patterson |
3–5 days |
| 3 |
🔵 Receive Zocdoc Eaglesoft integration package |
Zocdoc |
1 day |
| 4 |
Install integration module per Zocdoc specifications |
Central IT |
2 hours |
| 5 |
Configure appointment type mapping |
Office Manager + Zocdoc |
2 hours |
| 6 |
Test appointment creation and cancellation sync |
Central IT |
1 hour |
| 7 |
Validate insurance information transfer |
Central IT |
1 hour |
⚠️ Common Failure Point: Patterson API access may require separate subscription. Clarify licensing before assuming availability.
Open Dental Integration 🔵
| Step |
Action |
Owner |
Est. Time |
| 1 |
Confirm Open Dental version (21.1+) |
Central IT |
15 min |
| 2 |
Enable Open Dental API in program settings |
Central IT |
30 min |
| 3 |
Generate API key with appropriate permissions |
Central IT |
30 min |
| 4 |
🔵 Provide API key to Zocdoc implementation team |
Central IT → Zocdoc |
1 day |
| 5 |
🔵 Zocdoc configures connection and tests endpoints |
Zocdoc |
1–2 days |
| 6 |
Map operatories and appointment types |
Office Manager + Zocdoc |
2 hours |
| 7 |
Test full booking flow including patient creation |
Central IT |
1 hour |
Curve Dental Integration 🔵
| Step |
Action |
Owner |
Est. Time |
| 1 |
Confirm Curve Dental subscription includes API access |
Central IT |
15 min |
| 2 |
🔵 Zocdoc initiates Curve partnership integration (pre-built) |
Zocdoc |
1–2 days |
| 3 |
Authorize Zocdoc connection in Curve admin settings |
Central IT |
30 min |
| 4 |
Map appointment types and providers |
Office Manager + Zocdoc |
1 hour |
| 5 |
Test booking and sync |
Central IT |
1 hour |
Test Environment Setup and Validation
Centralized Test Environment (Recommended for DSOs)
- ☐ 🔵 Request Zocdoc sandbox environment for enterprise testing
- ☐ Clone configuration from one pilot location into sandbox
- ☐ Create test patient records (do not use real PHI in sandbox)
- ☐ Document test cases covering all appointment types
Validation Checklist
| Test Case |
Expected Outcome |
Pass/Fail |
| New patient books appointment via Zocdoc |
Appointment appears in PMS within 5 minutes |
☐ |
| Existing patient books appointment |
Patient matched correctly, no duplicate created |
☐ |
| Patient cancels via Zocdoc |
Appointment marked canceled in PMS |
☐ |
| Practice cancels in PMS |
Zocdoc reflects cancellation, patient notified |
☐ |
| Provider schedule change in PMS |
Zocdoc availability updates within sync cycle |
☐ |
| Insurance information captured |
Insurance fields populate in PMS patient record |
☐ |
| Appointment reminder sent |
Patient receives SMS/email per configuration |
☐ |
| Patient arrives and checks in |
Check-in status visible in practice workflow |
☐ |
Data Migration / Historical Ingestion
What Zocdoc Typically Requires
- Provider roster (bulk upload via CSV)
- Location information
- Insurance plan acceptance list
- Appointment type catalog
What Zocdoc Does NOT Require
- Historical patient records (HIPAA consideration)
- Past appointment history
- Clinical notes or treatment plans
Migration Steps
| Step |
Action |
Owner |
Est. Time |
| 1 |
Export provider roster from HR system or PMS |
Central IT |
2 hours |
| 2 |
Format per Zocdoc bulk upload template |
VP Ops team |
2 hours |
| 3 |
🔵 Submit for Zocdoc bulk processing |
Zocdoc |
1–2 days |
| 4 |
Validate all providers appear correctly on platform |
Office Managers |
1 hour per location |
| 5 |
Export and format insurance plan lists |
Billing/Insurance team |
4 hours |
| 6 |
🔵 Upload insurance acceptance to Zocdoc |
Zocdoc |
1 day |
Security and HIPAA Compliance Verification
Enterprise-Level HIPAA Checklist
| Requirement |
Action |
Owner |
Status |
| BAA Executed |
🔵 Sign Zocdoc Business Associate Agreement |
Legal + Zocdoc |
☐ |
| Data Encryption in Transit |
Verify TLS 1.2+ for all API communications |
Central IT |
☐ |
| Data Encryption at Rest |
🔵 Confirm Zocdoc's encryption standards (should be AES-256) |
Zocdoc → Compliance |
☐ |
| Access Controls |
Configure role-based access in Zocdoc admin |
Central IT |
☐ |
| Audit Logging |
🔵 Confirm Zocdoc provides access logs for compliance |
Zocdoc → Compliance |
☐ |
| Data Retention Policy |
Align Zocdoc retention with DSO data governance policy |
Compliance |
☐ |
| Breach Notification |
Review Zocdoc's breach notification procedures |
Compliance + Zocdoc |
☐ |
| Subcontractor Due Diligence |
🔵 Request Zocdoc's list of subcontractors handling PHI |
Zocdoc → Compliance |
☐ |
| Employee Training |
Zocdoc confirms staff HIPAA training |
🔵 Zocdoc |
☐ |
Standardized vs. Location-Specific Configuration
Configuration Template: Standardize Centrally
| Setting |
Standard Value |
Notes |
| Branding (logo, colors) |
DSO master brand |
Unless multi-brand portfolio |
| Appointment type names |
Standardized catalog |
"New Patient Exam," "Cleaning," etc. |
| Appointment durations |
Per clinical protocol |
60 min new patient, 45 min hygiene, etc. |
| Reminder timing |
48 hours + 2 hours pre-appointment |
Enterprise standard |
| Reminder channels |
SMS + Email |
Both enabled |
| Booking lead time (minimum) |
2 hours |
Prevents last-minute unmanageable bookings |
| Booking lead time (maximum) |
90 days |
Standard visibility window |
| Insurance acceptance display |
Central master list |
Updated quarterly |
| Review response templates |
Approved response library |
Compliance-reviewed |
Configuration: Allow Local Discretion
| Setting |
Local Discretion Allowed |
Governance |
| Provider schedules/availability |
Yes |
Must match PMS |
| Provider photos and bios |
Yes |
Must meet brand guidelines |
| Specialty services offered |
Yes |
Based on local provider capabilities |
| Languages spoken |
Yes |
Accurate to staff |
| Office hours |
Yes |
Must be accurate |
| Specific operatory assignments |
Yes |
Local workflow preference |
| Holiday closures |
Yes |
Communicated to central team |
6. Team Training Plan
Train-the-Trainer Model
Overview
Rather than deploying central trainers to 15–50 locations, certify one "Champion" per location who delivers training locally. Central team provides standardized materials; Champions customize for their team.
Champion Selection Criteria
| Criteria |
Weight |
Ideal Profile |
| Role |
High |
Office Manager or senior Front Desk |
| Tech Comfort |
High |
Comfortable with new software, troubleshoots before escalating |
| Influence |
Medium |
Respected by providers and staff |
| Availability |
High |
Can dedicate 8–10 hours to certification and training delivery |
| Communication |
Medium |
Can present information clearly to mixed audiences |
Champion Responsibilities
- ☐ Complete central certification training (3–4 hours)
- ☐ Customize training for local team context
- ☐ Deliver role-specific training sessions before go-live
- ☐ Track training completion for all staff
- ☐ Serve as first point of contact for Zocdoc questions post-launch
- ☐ Escalate unresolved issues to Regional Manager
Champion Certification Process 🔵
| Step |
Activity |
Duration |
Format |
| 1 |
🔵 Complete Zocdoc Champion onboarding module |
90 min |
Online self-paced |
| 2 |
🔵 Attend live Champion training webinar |
60 min |
Virtual with Zocdoc |
| 3 |
Pass Champion certification quiz (80%+ required) |
30 min |
Online assessment |
| 4 |
Shadow a live go-live from Wave 1 (for Wave 2+ Champions) |
2 hours |
Virtual observation |
| 5 |
Receive Champion toolkit and presentation materials |
N/A |
Digital delivery |
Standardized Training Materials (Created Centrally)
Materials to Develop
- ☐ Role-specific training slide decks (4 versions)
- ☐ "Day 1 Cheat Sheets" for each role (1-page PDFs)
- ☐ Short video walkthroughs (3–5 min each) for common tasks
- ☐ FAQ document based on pilot feedback
- ☐ Troubleshooting flowchart for common issues
Materials Champions Customize
- ☐ Local provider names and photos in examples
- ☐ Specific hours and scheduling preferences
- ☐ Local workflow quirks (e.g., "We always book Dr. Smith's cleanings in Op 3")
Role-Specific Training Outlines
Front Desk / Office Manager
Training Duration: 2 hours (primary users)
Topics Covered:
- Zocdoc dashboard overview (15 min)
- Understanding incoming appointment notifications (20 min)
- Confirming and managing Zocdoc appointments in PMS (30 min)
- Handling appointment changes and cancellations (15 min)
- Patient communication: what Zocdoc sends vs. what you send (15 min)
- Waitlist management and same-day fill (15 min)
- Responding to patient reviews (10 min)
- Troubleshooting sync issues (10 min)
- Q&A (10 min)
Common Resistance Points:
- "This is more work, not less" → Emphasize reduced phone time and after-hours booking
- "Patients won't use it" → Share data on patient preference for online booking
- "I'll lose control of the schedule" → Show how to set booking rules and block times
Day 1 Cheat Sheet Content:
- How to access Zocdoc dashboard
- Where new appointments appear in PMS
- How to manually confirm an appointment
- How to reach Zocdoc support
- What to tell a patient who calls about a Zocdoc booking
Dentists/Providers
Training Duration: 45 minutes
Topics Covered:
- What Zocdoc is and why we're using it (5 min)