Net32 — Implementation Playbook (DSO)

Executive Summary

Net32 is a cloud-based scheduling and operations platform designed to streamline appointment management, reduce no-shows, and optimize staff utilization across multi-location dental practices. For Dental Service Organizations (DSOs), Net32 delivers centralized control, standardized workflows, and real-time visibility into operational metrics across dozens of locations simultaneously—eliminating the fragmentation that typically plagues group practices.

DSOs benefit uniquely because Net32's multi-location architecture replaces disconnected legacy systems with a single source of truth. This enables DSO leadership to enforce consistent scheduling standards, identify underperforming locations, reallocate resources dynamically, and scale new locations faster. Expected timeline to full deployment: 16 weeks (pilot + rollout).

Pre-Implementation Checklist (Weeks 1-2)

Technical Requirements

• Infrastructure: Ensure all locations have stable broadband (minimum 25 Mbps). Identify any offices with legacy equipment or slow networks requiring upgrades before Go-Live.
• Integration Points: Map existing systems (practice management software, EHR, patient communication platform). Net32 integrates natively with major platforms (Dentrix, Eaglesoft, Curve). Identify any custom integrations requiring API development (typically 2-4 week lead time).
• Device Rollout: Order tablets/check-in kiosks for high-traffic locations. Budget ~$400-600 per location for hardware (iPad, stand, payment terminal if adding chair-side capture).
• Network Segregation: Confirm IT security protocols allow HIPAA-compliant cloud access. Test VPN/firewall rules for seamless login across locations.

Stakeholder Alignment

• Executive Sponsorship: Secure commitment from DSO leadership (COO, VP of Operations) to attend kickoff and 30/60/90 reviews. Lack of visible sponsorship is the #1 reason pilots stall.
• Location Buy-In: Schedule calls with office managers and lead clinicians at pilot sites. Address concerns upfront: "Will this add steps to my day?" "Can patients still walk in?" "What if the system goes down?"
• IT/Security Review: Have your Chief Information Officer or IT director review Net32's SOC 2 Type II certification and data residency practices. Document sign-off.
• Finance Alignment: Clarify whether Net32 is centralized cost (DSO absorbs) or location-based (practices pay per active provider). This affects adoption messaging.

Baseline Metrics to Capture (Pre-Implementation)

Measure these at all pilot locations before going live to establish a true baseline:

Use patient surveys and staff time logs for two weeks to establish baseline. This prevents cherry-picking numbers later.

Pilot Wave (Weeks 3-6)

Location Selection Criteria

Choose 2-3 pilot locations that represent diversity but not chaos:

• Maturity: Select locations with stable staff, organized workflows, and an open-minded office manager. Avoid your most dysfunctional location (it will blame Net32 for pre-existing problems).
• Volume: Pick locations doing 150-300 patient visits/week—large enough to surface real issues, small enough to manage closely.
• Diversity: If your DSO spans urban/rural or single-provider/multi-provider models, include both. Pain points differ significantly.
• Geographic Distribution: Choose locations in different regions if your DSO is geographically dispersed. You'll catch regional broadband/telecom issues early.

Avoid: Corporate headquarters (too many executives watching) and your flagship location (too much risk).

Configuration and Setup

• Data Migration: Work with Net32's onboarding team to migrate historical appointment data and patient records. This typically takes 1-2 weeks. Verify data integrity post-migration (spot-check 50-100 records).
• Workflow Customization: Configure appointment types, provider schedules, and buffer times to match each pilot location's current state. Do not force them to change workflows before go-live—that's Phase 2 optimization.
• Automation Rules: Set up basic automations:
  • SMS reminder at 48 hours and 24 hours (reduces no-shows 15-25%)
  • Auto-rebooking for cancellations (prevents chair downtime)
  • Escalation alerts for unscheduled gaps (clinician overbooked? Reassign)
• Reporting Dashboards: Pre-build DSO-level and location-level dashboards. Show office managers their own data in real-time. Transparency drives adoption.

Training Approach

• Blended Model: Combine live training, recorded videos, and one-on-one support.
  • Day 1: 90-minute live session for all staff (receptionists, clinicians, office manager). Cover: login, daily schedule view, rescheduling a patient, handling no-shows.
  • Days 2-5: Video library (5-minute modules) on desk. Link to Slack/email for easy access.
  • Weeks 2-3: On-site "super user" support person (could be Net32 trainer or your own empowered office manager) embedded 3 days/week to answer questions and catch errors in real-time.
  • Ongoing: Weekly 15-minute "office hours" call with pilot locations for Q&A. Track common questions and create FAQs.

Scaled Rollout (Weeks 7-16)

Wave Planning

Divide remaining locations into 3 waves (each wave ~3-4 weeks apart):

• Wave 2 (Weeks 7-10): 8-10 locations. Include some high-revenue locations to signal confidence internally.
• Wave 3 (Weeks 11-14): 12-15 locations.
• Wave 4 (Weeks 15-16): Remaining locations + sites that require custom integrations.

Stagger waves to avoid overwhelming your support team. Each wave should follow the same setup/training playbook but compress timelines slightly (pilot offices can now be "super users" helping new cohorts).

Change Management

• Certification Program: Identify 2-3 "champions" per location. Certify them before other staff train. They become local experts and troubleshooters.
• Quick Wins Narrative: After Week 6, communicate one success story from pilot locations: "Pilot office reduced no-show rate from 12% to 6% in 3 weeks." Share in all-hands meetings and location newsletters.
• Resistance Protocols: Some clinicians will say "I'm too busy to learn new software." Acknowledge the concern, then frame it as reducing busy-ness: "Net32 handles your rescheduling—you get the benefit without the work."
• Feedback Loops: Monthly surveys to all users asking what's working and what's painful. Show that DSO leadership is listening and prioritizes fixes (even small ones).

Support Infrastructure

• Dedicated Slack Channel: Create #net32-support for questions. Response time: <2 hours during business hours.
• Tiered Support:
  • Tier 1 (Office Manager): Handle login issues, reschedule patient, explain feature. Response: same-day.
  • Tier 2 (DSO Operations): Handle configuration questions, reporting issues. Response: 24 hours.
  • Tier 3 (Net32 + DSO IT): Handle system outages, API errors, integrations. Response: 4 hours.
• Post-Go-Live Monitoring: Track system performance, error logs, and failed API calls daily for first two weeks. Address latency issues immediately.

ROI Tracking

Key Metrics to Measure