Dental City — Implementation Playbook (DSO)

Executive Summary

Dental City is a cloud-based scheduling and operations platform designed to centralize appointment management, provider coordination, and patient communication across multiple dental locations. Built for Dental Service Organizations (DSOs), it consolidates fragmented scheduling systems, eliminates overbooking, and creates unified visibility across your entire portfolio. DSOs specifically benefit because they operate multiple locations with shared resources, staff rotation, and complex compliance requirements—Dental City's multi-location architecture and role-based permissions eliminate the chaos of managing 5, 50, or 500 practices independently.

Expected Timeline: 16 weeks from kickoff to full production deployment across all locations, with rapid value capture beginning in Week 6.

Pre-Implementation Checklist (Weeks 1–2)

Technical Requirements

• Network & Infrastructure: Verify all locations have stable internet (minimum 5 Mbps upload/download). Document existing PMS systems, EHR platforms, and third-party integrations (insurance verification, lab ordering, patient portals).
• User Capacity Planning: Count total users (scheduling coordinators, providers, hygienists, front desk, admin staff). Dental City requires one administrator account per location and supports unlimited seat licenses.
• Data Audit: Export current appointment calendars, provider availability, room/operatory configs, and patient lists. Identify data quality gaps (missing appointment types, undefined chair assignments, inconsistent provider credentials).
• API & Integration Mapping: Confirm which systems must connect to Dental City (Practice Management Software, EHR, patient communication platforms). Request API documentation from vendors.
• Browser & Device Compatibility: Dental City supports Chrome, Firefox, Safari, and Edge (latest two versions). Test on the devices and browsers your staff actually uses.

Stakeholder Alignment

• Executive Sponsorship: Secure C-level or Dental Director buy-in. DSO rollouts fail when leadership views this as "IT's project" rather than a business transformation.
• Local Champion at Each Location: Identify one scheduling lead or office manager per practice who will be the go-to resource and cultural advocate.
• Resistance Mapping: Conduct informal interviews with 5–8 schedulers across different locations. Understand pain points (double-booking, manual room assignment, staff communication delays) and concerns (job security, learning curve, system downtime).
• Governance Structure: Establish a steering committee (DSO Operations Director, Regional Managers, IT Lead, Dental City Account Manager). Schedule bi-weekly 30-minute check-ins.

Baseline Metrics to Capture

Before system go-live, measure and document:

• Scheduling Efficiency: Average time to book an appointment, # of rebooking/cancellations per week, chair/room utilization %.
• Provider Productivity: Total patient visits/provider/week, average daily schedule fill rate %, no-show rate %.
• Operational Costs: Staff hours spent on scheduling, manual communication (phone, email, SMS), appointment confirmation labor.
• Patient Experience: Net Promoter Score (NPS) from scheduling, average time from call to appointment, patient cancellation reasons.
• System Performance: Current PMS downtime incidents/month, data sync errors, manual workarounds per week.

Store these in a shared spreadsheet; you'll measure against them at 30/60/90 days.

Pilot Wave (Weeks 3–6)

Location Selection Criteria

Choose 2–3 locations, not 1. Single-site pilots often don't surface multi-location coordination issues.

• Size: Prioritize a medium-sized location (8–15 operatories, 4–6 providers). Avoid your smallest practice (insufficient data) and largest (too many variables).
• Readiness: Select locations with stable staff and current office managers. Avoid sites mid-transition or with known leadership gaps.
• Diversity: If you have different practice models (high-volume hygiene-focused, specialist practices, pediatric), include one of each in the pilot.
• Geographic Proximity: If possible, include one location near your corporate office for easier in-person support.

Configuration and Setup

Week 3–4: Tenant Setup & Data Migration

1. Dental City provisions a staging environment specific to your DSO. Import provider credentials, operatory/room configs, and available appointment types from your PMS export.
2. Map your PMS specialty codes and appointment types (e.g., "Cleaning 60min," "Emergency Exam 30min," "Implant Placement 120min") to Dental City's taxonomy.
3. Set provider availability rules: days off, recurring blocks (e.g., "Dr. Smith doesn't see patients after 3 PM on Fridays"), and lunch hours.
4. Configure notification rules: Which staff get SMS/email reminders? At what intervals (24h, 1h before)?
5. Test integrations: Send test data between your PMS and Dental City. Confirm appointment creates/updates flow bidirectionally without duplication.

Week 4–5: User Access & Role Configuration

• Create user accounts for all staff at pilot locations. Assign roles:
  • Scheduling Coordinators: Can create, modify, cancel, and reschedule appointments; view all providers.
  • Providers: Can view their own schedule, mark as unavailable, request coverage.
  • Front Desk: Can check in/out patients, confirm appointments, note no-shows.
  • Location Admin: Can manage staff, reports, and settings for their site.
• Set up multi-location visibility rules: Can Dr. Johnson at Location A book into Location B's rooms if she works both sites? Define this now.
• Create a sandbox environment so staff can practice without affecting live data.

Training Approach

Week 5–6: Hands-On Rollout

• Classroom (2 hours): Group training on the "why" (DSO-wide visibility, efficiency gains) and core workflows (searching availability, blocking time, managing double-bookings, communicating changes). Use screen recordings and role-play scenarios.
• 1:1 Shadowing (30 min/person): Pair each staff member with the Dental City Customer Success team or your local champion. Work through their real appointment scenarios.
• Cutover Plan: On Day 1 of Week 6, go live at pilot locations with a 3-day "parallel run"—staff book in both old and new systems to catch gaps. Dedicate someone to reconciliation daily.
• Office Hours: Host 15-minute daily drop-in calls during Week 6. Staff can ask quick questions without feeling "dumb."

Scaled Rollout (Weeks 7–16)

Wave Planning

Wave 2 (Weeks 7–9): 5–8 locations
Wave 3 (Weeks 10–12): 8–12 locations
Wave 4+ (Weeks 13–16): Remaining locations in groups of 8–12

Space waves 2–3 weeks apart so your support team isn't overwhelmed. Each wave repeats the configuration → testing → training → cutover cycle.

Change Management

• Weekly Steering Committee: Review go-live readiness, escalations, and usage metrics for live locations.
• Resistance Mitigation: Schedulers often fear Dental City will "eliminate" their role. Communicate proactively: "Dental City removes manual busywork; you'll focus on complex scheduling, patient retention, and provider support."
• Quick Wins Narrative: In Week 8–9, share stories: "Location B reduced average booking time from 8 minutes to 3 minutes." Celebrate adoption milestones (e.g., "5,000 appointments booked in Dental City").
• Feedback Loops: Send a brief 3-question survey to staff at live locations monthly: What's working? What's confusing? What would help you do your job better?

Support Infrastructure

• Primary Support Tier: Dental City's 24/5 support (phone/email/chat) handles technical issues and feature questions. Response SLA: 1 hour for critical issues (system down), 4 hours for standard questions.
• Secondary Tier: Your IT/Ops team manages PMS integration issues, data quality problems, and location-specific customizations. Assign one person as the Dental City liaison.
• Escalation Path: If a location goes dark (scheduling unavailable), your IT lead pages the Dental City on-call engineer. Document this in your incident response plan.
• Knowledge Base: Compile a "Frequently Asked Questions" document within your DSO by