Guru Dental — Implementation Playbook (DSO)

Executive Summary

Guru Dental provides AI-powered patient communication solutions that automate appointment reminders, post-treatment follow-ups, and clinical protocol compliance across multi-location dental practices. For DSOs managing 10+ locations, Guru Dental eliminates manual outreach workflows while improving patient adherence and clinical outcomes at scale.

DSOs benefit uniquely from Guru Dental because centralized deployment creates operational leverage—one implementation team manages standardized communication across dozens of locations simultaneously, reducing per-location setup costs by 60-70% compared to implementing point solutions at individual practices. With proper sequencing, DSOs see ROI within 90 days through reduced no-shows, improved case acceptance, and recaptured production time previously spent on manual follow-ups.

Expected Timeline: 16 weeks from kickoff to full deployment across a 15-location DSO, with the first pilot location live in week 4.

Pre-Implementation Checklist (Weeks 1-2)

Technical Requirements

Infrastructure Assessment

• Audit all practice management software (PMS) versions across locations. Guru Dental requires PMS integration via API or SFTP. Document all instances of legacy systems (Dentrix G7 or earlier, older Open Dental versions) that may require manual data mapping.
• Verify HIPAA-compliant data environment. Confirm all locations have firewall logging, encrypted data storage, and intrusion detection active.
• Test bandwidth at 2-3 representative locations. Guru Dental's real-time messaging requires minimum 5 Mbps upload speed. Identify any branch offices with connectivity constraints.
• Create a centralized IT contact list with on-call support windows.

Patient Data Validation

• Run a sample export of 500 patient records from your largest location. Check for formatting inconsistencies in phone numbers, dates of birth, and email addresses. These must be standardized before integration (e.g., all phone numbers as +1-XXX-XXX-XXXX).
• Document current opt-in/opt-out protocols. Many DSOs discover compliance gaps here; you'll need a clear audit trail of patient consent across all locations.

Stakeholder Alignment

Executive Steering Committee (CEO, COO, Chief Clinical Officer)

• Secure commitment to allocate 1 full-time implementation lead for 12 weeks.
• Agree on centralized vs. location-autonomy model for communication templates. (Recommendation: central approval with local customization on clinical protocols only.)
• Define success metrics and get sign-off on ROI targets.

Location Champions (2-3 doctors, 2-3 office managers from pilot sites)

• Schedule kickoff with pilot site teams to understand current workflows. How are appointment reminders currently sent? Who manages patient follow-ups post-treatment?
• Address resistance upfront. Common concern: "This feels impersonal." Reframe as: clinical protocols ensure patient safety; automation frees staff to handle complex conversations.
• Establish a Slack or Teams channel for implementation questions.

IT & Operations Leadership

• Confirm data governance policies. Who owns patient communication data? (Typically IT, but clarify escalation paths.)
• Agree on change management cadence—weekly syncs are standard during pilot.

Baseline Metrics to Capture

Before any implementation, establish your starting point:

Document these in a shared spreadsheet. You'll need them for 30/60/90 benchmarking.

Pilot Wave (Weeks 3-6)

Location Selection Criteria

Choose one pilot location with these traits:

• Patient population size: 3,500–6,000 active patients. Large enough for meaningful ROI, small enough to troubleshoot quickly.
• Technology maturity: Staff comfortable with PMS; at least one person has integrated external software before.
• Clinical stability: No major staffing changes scheduled. A revolving door of hygienists will derail training.
• Leadership buy-in: The doctor and office manager must actively champion the rollout. If they're skeptical, pick a different location.
• Realistic urgency: Not the busiest month (avoid holiday season or major marketing campaign launch).

Avoid: Your largest or most complex location as the pilot. Resist the temptation to solve your biggest problem first.

Configuration and Setup

Week 3: Data Preparation & Integration

1. Export full patient list from PMS at pilot location. Guru Dental will map fields.
2. Identify communication gaps:
   • Which patients are missing phone numbers? Email addresses? (Aim for 90%+ phone coverage.)
   • Are appointment statuses standardized? (Confirmed, no-show, cancelled, completed must align across system.)
3. Guru Dental technical team configures API connection or SFTP data feed. Test with 100 sample records first.
4. Set up SMS/email sender credentials. Register clinic phone number with carrier for A2P messaging (compliance requirement).

Week 4: Workflow Design & Template Creation

• Map current patient journey: Initial consultation → Treatment proposal → Pre-appointment → Post-op → Recall
• For each touchpoint, draft Guru Dental message templates:
  • 24-hour pre-appointment reminder (SMS + email, personalized by patient name and appointment type)
  • Post-operative protocol (e.g., "Day 1 post-filling: avoid hard foods for 2 hours. Any pain? Reply YES for callback.")
  • Recall engagement (soft outreach at 6-month interval, escalating to harder asks at 9 months)
  • Treatment acceptance nudge (automated at 3 days if patient hasn't accepted proposal)
• Get clinical sign-off from the pilot location's doctor on all messaging.

Week 5: Staff Training & UAT

• Conduct 90-minute training with front desk (appointment owners), clinical staff (treatment notes), and office manager (oversight).
• Live walkthrough: Show how to view patient engagement history in Guru Dental dashboard. Demonstrate how to override automated messages if patient calls with questions.
• User acceptance testing: Staff manually trigger messages for test patients and verify delivery timing, tone, and accuracy.
• Create 1-page laminated quick-start guide for new hires.

Training Approach

Train the trainers: Designate one office manager as the "Guru champion." They'll handle day-to-day troubleshooting and onboard staff during pilot. (They'll train champions at other locations in scaled rollout.)

Blended delivery:

• Live Zoom session (knowledge transfer)
• Recorded session available for asynchronous learning (accommodate different shifts)
• Hands-on lab (each staff member sends 2 test messages)
• Office-specific playbook (PDF guide tailored to their workflows)

Scaled Rollout (Weeks 7-16)

Wave Planning

After pilot concludes (week 6 debrief):

Between waves (1-week gap): Conduct "health check" review. Are adoption rates strong at Wave 1 locations? If not, pause Wave 2 and diagnose.

Change Management

• Weekly DSO implementation standup (30 min): Executive sponsor, implementation lead, 1 IT representative. Review: # messages sent, adoption rate by location, blockers, upcoming wave readiness.
• Bi-weekly location check-ins: Implementation lead calls each active location's office manager. "How