SuperDial — Implementation Playbook (DSO)

Executive Summary

SuperDial is an AI-driven revenue cycle management platform that automates patient outreach, payment collection, and account resolution across distributed practice networks. It intelligently routes calls, manages callbacks, and surfaces high-value accounts in real-time, enabling centralized revenue operations at scale.

Why DSOs Benefit Specifically: DSOs operate across 5–50+ practice locations with fragmented billing systems, inconsistent collection protocols, and decentralized revenue staff. SuperDial consolidates this chaos into a single command center, applying uniform processes to thousands of patient accounts simultaneously while maintaining local clinical relationships.

Expected Timeline: 14–16 weeks to full deployment across a typical 15-location DSO; 8–10 weeks for smaller networks (3–5 locations).

Pre-Implementation Checklist (Weeks 1–2)

Technical Requirements

Systems Integration

• Verify API connectivity between SuperDial and your primary EHR/PM system (athenahealth, Kareo, eClinicalWorks, Medidata, etc.)
• Confirm patient data extract capability: demographics, insurance eligibility, outstanding balances, appointment history
• Identify single-source-of-truth for patient identity to prevent duplicate outreach
• Test data refresh frequency requirements (real-time vs. 24-hour batch)

Network & Phone Infrastructure

• Confirm bandwidth capacity at centralized revenue hub (minimum 10 Mbps dedicated; redundant ISP recommended)
• Provision dedicated phone lines or SIP trunks for automated outreach (typically 5–15 concurrent channels per 1,000 active accounts)
• Validate internal phone system compatibility (PBX, VoIP provider)
• Set up call recording and compliance logging infrastructure

User Access & Security

• Establish role-based access controls (revenue director, collector, supervisor, read-only reports)
• Enable Single Sign-On (SSO) via your corporate directory (Okta, Azure AD)
• Audit current HIPAA compliance posture and update Business Associate Agreements

Stakeholder Alignment

Cross-functional Kickoff Meeting (Day 1)

• CFO/COO: budget owner, ROI expectations, timeline acceptance
• Medical Director: clinical workflow impact, patient communication tone/timing
• Practice Managers: operational capacity, staff retraining capacity
• IT Director: technical ownership, integration testing timeline
• Compliance Officer: audit requirements, state/federal calling regulations

Define Decision-Making Authority

• Establish Steering Committee (meets weekly during implementation)
• Designate SuperDial Implementation Lead (full-time, 8–12 weeks)
• Assign EHR/PM system champion at each location

Baseline Metrics Capture

Critical Measurements (Before Day 1 of Pilot)

• Current Days Sales Outstanding (DSO) across all locations
• Outstanding A/R aging: 30, 60, 90+ days
• Current collection rate by location and payer type
• Patient contact attempt rate (calls, texts, mail) and success rate
• Staff FTE hours spent on collections per location
• Complaint/compliance incidents (last 12 months)
• Average time-to-collection for resolved accounts

Action: Export 90 days of historical data into a shared analytics repository (Google Sheets, Tableau, or your BI platform). SuperDial will use this as the baseline.

Pilot Wave (Weeks 3–6)

Location Selection Criteria

Select 2–3 pilot locations representing:

• Geographic diversity: One urban, one suburban, one rural (if applicable)
• Operational maturity: Locations with above-average IT readiness and staff cooperation
• Volume representation: ~15–25% of total DSO patient population
• Staff willingness: At least one location whose revenue manager is enthusiastic about change

Avoid:

• Locations with active staff turnover or leadership instability
• Facilities undergoing significant clinical renovation
• Practices with legacy PM systems not yet scheduled for upgrade

Configuration and Setup

Week 3: System Configuration

1. SuperDial implementation specialist configures call workflows:

   • Outreach priority rules (high-balance past-due accounts first)
   • Timing windows (business hours, evening, Saturday calls separated by patient preference)
   • Message templates (IVR scripts, SMS templates, voicemail drops) — review with Compliance for state-specific calling laws

2. EHR/PM data integration testing:

   • Run full patient load extract and validate account balance accuracy
   • Map insurance eligibility data feeds
   • Test daily refresh logic

3. Phone system integration:

   • Route SuperDial outbound caller ID to match practice location (improves answer rates 8–12%)
   • Configure call transfer logic to live collectors during business hours

Week 4: User Environment Setup

• Create user accounts and assign roles for 4–6 pilot staff members
• Customize dashboard views by role (collectors see task queue; supervisors see performance analytics)
• Set up quality assurance workflows (supervisor call monitoring, 5–10% sample weekly)

Training Approach

Hands-On Classroom Training (4 hours, in-person at hub location)

• SuperDial product overview and user interface walkthrough
• Collections best practices (empathy, regulatory compliance, objection handling)
• Live simulation: collectors practice with mock patient accounts

Ongoing Support

• Assign a SuperDial Customer Success Manager as primary contact (daily standups first 2 weeks)
• Establish Slack channel for real-time troubleshooting
• Record all training sessions for future staff onboarding

Staff Messaging

• Frame SuperDial as workflow automation not job replacement (it eliminates manual dialing, data entry, and callback scheduling)
• Highlight collector benefits: higher connection rates, better work-life balance, performance visibility

Scaled Rollout (Weeks 7–16)

Wave Planning

Wave 2 (Weeks 7–10): Medium-risk locations

• 4–6 additional practices
• Leverage pilot lessons learned to accelerate onboarding
• Assign pilot location staff as peer mentors

Wave 3 (Weeks 11–14): Remaining locations

• Final 5–10 practices onboarded in parallel
• Streamlined 2-day onsite training model
• SuperDial handles technical integration; DSO IT validates connectivity

Wave 4 (Weeks 15–16): Optimization & Hypercare

• Fine-tune collection rules based on 8 weeks of pilot data
• Address location-specific edge cases (specialty practices, high-Medicaid clinics)
• Transition to steady-state support model

Change Management

Weekly Steering Committee Meetings

• Review pilot metrics (collection rate, contact success, call handling time)
• Address staff concerns and workflow friction
• Approve any messaging or policy changes before Wave 2

Staff Resistance Mitigation

• Identify champions at each location who actively use SuperDial and mentor peers
• Celebrate quick wins: Publish weekly dashboard showing accounts resolved, dollars collected by location
• Address job security openly: Project staffing model post-launch; identify expansion opportunities (appeals management, insurance verification tasks)

Communication Timeline

• Week 5: Announce Wave 2 locations; share pilot results
• Week 9: Announce Wave 3 locations; share financial impact data
• Week 14: Celebrate DSO-wide launch; outline continuous improvement roadmap

Support Infrastructure

Centralized Revenue Operations Hub

• Establish 24/5 help desk (or 24/7 if 24-hour outreach is in-scope)
• Dedicated SuperDial power user on staff (1 FTE per 100 staff members collecting)
• Weekly training refresher sessions for new hires

Escalation Protocol

• Level 1: SuperDial in-app help docs and chat (typical resolution: <15 min)
• Level 2: Local practice manager escalation (1–4 hour SLA)
• Level 3: SuperDial Customer Success Manager (4–8 hour SLA for bugs; 24 hours for feature requests)

Knowledge Management

• Build internal wiki with location-specific workflows
• Record screen-capture videos for common tasks (building patient contact lists, running compliance reports)
• Quarterly feedback sessions with users to refine training materials

ROI Tracking

Key Metrics to Measure