AirPay — Implementation Playbook (DSO)

Executive Summary

AirPay is a cloud-based revenue-cycle platform that automates patient billing, payment collection, and accounts receivable management for dental practices. It integrates with leading practice management software to reduce manual work, accelerate cash flow, and improve patient payment experiences. For Dental Service Organizations (DSOs), AirPay delivers network-wide standardization, centralized visibility into revenue metrics, and economies of scale in collections operations—transforming how multi-location organizations manage their most fragmented revenue processes.

Why DSOs Benefit: DSOs manage 15–200+ locations with inconsistent billing workflows, variable collection rates, and siloed financial data. AirPay unifies payment processing, automates patient reminders and statements, enables corporate revenue teams to monitor KPIs in real-time, and eliminates redundant staff across locations.

Expected Timeline: 16 weeks from kickoff to full deployment across all locations, with ROI visibility by Week 12.

Pre-Implementation Checklist (Weeks 1–2)

Technical Requirements

• Practice Management Integration: Verify AirPay certification with your primary PMS (Dentrix, Eaglesoft, Open Dental, etc.). Request technical specification documents from AirPay's integration team.
• Network Infrastructure: Confirm HIPAA-compliant hosting, SSL encryption, and API endpoint capacity at corporate and location levels.
• Single Sign-On (SSO): Coordinate with IT to map Active Directory or Okta credentials for centralized user provisioning across locations.
• Data Warehouse Readiness: Ensure your BI/reporting infrastructure can consume AirPay's daily data feeds (patient aging, collections, payment trends).
• Payment Processing: Audit current merchant processors (Heartland, First Data, etc.). Determine if AirPay will replace, integrate, or run parallel with existing processors during pilot.

Stakeholder Alignment

• Sponsor Alignment: CFO, COO, and VP of Operations must co-sign implementation timeline and success criteria.
• Clinical vs. Admin: Schedule separate kick-off meetings with clinical leadership (DDS/DMD) and administrative staff (office managers, billing coordinators). Frame AirPay as a patient experience tool, not a cost-cutting measure.
• Location Readiness: Send pre-launch survey to all pilot locations asking about current PMS version, staff turnover rate, and billing complaints. Flag locations with outdated PMS—these require migration or workarounds.
• Corporate Finance Team: Assign a dedicated finance liaison to reconcile AirPay payments with GL accounts during transition.

Baseline Metrics to Capture (Week 1–2)

Document these metrics for all pilot and non-pilot locations before launch:

Store these in a shared baseline scorecard. You'll measure delta at 30/60/90 days.

Pilot Wave (Weeks 3–6)

Location Selection Criteria

Choose 2–4 pilot locations based on:

• Revenue Volume: Select locations generating $150K–$300K/month (large enough to show ROI, small enough to contain risk).
• PMS Currency: Prioritize locations running current/supported PMS versions.
• Staff Stability: Avoid high-turnover locations; you need consistent billing staff to own the transition.
• Openness to Change: Select office managers known for embracing operational improvements. Their enthusiasm will cascade to staff.
• Data Quality: Run a PMS audit: do locations properly code procedures, capture insurance info, and maintain updated patient contact data? Poor data = poor automation results.

Configuration and Setup

Week 3: Data Extraction & Mapping

• AirPay's implementation team extracts 90 days of historical patient, insurance, charge, and payment data from your PMS.
• Map your internal billing codes, insurance carriers, and fee schedules to AirPay's taxonomy.
• Validate patient contact data (mobile numbers, emails). Flag records with missing/invalid contacts for manual cleanup.

Week 4: Sandbox Testing

• AirPay deploys a production-clone sandbox environment. Corporate finance and 1–2 location staff run 50 test patient accounts through end-to-end workflows: statement generation, payment posting, aging reports.
• Test payment reconciliation to your GL. Confirm AirPay deposits map to correct cost centers (by location, by provider).
• Pilot staff stress-test the patient portal: Can patients view statements, make payments, and update insurance?

Week 5: Soft Launch

• Go live with pilot locations on a Wednesday (midweek avoids weekend support gaps).
• Go-live cutover: Establish cutoff date. All charges before cutoff remain in legacy system; all new charges post through AirPay.
• Post parallel run period: legacy and AirPay run side-by-side for 2 weeks. Billing staff verify payment posting matches and no records are orphaned.

Week 6: Stabilization & Iteration

• Conduct daily huddles (15 min) with pilot locations to surface blockers: integration lag, staff confusion, process gaps.
• Iterate on statement templates, reminder cadence, and payment workflows based on real usage.
• Document playbooks: "How to refund a payment," "How to adjust A/R for insurance write-off," etc.

Training Approach

• Role-Based Curriculum:

  • Office Managers: Dashboard navigation, patient payment workflows, reporting (90 min session).
  • Billing Coordinators: Statement generation, aging follow-up, payment posting, dispute resolution (4 hrs, 2-day spacing).
  • Clinical Staff: Patient payment options at checkout, texting payment reminders (30 min).

• Delivery: Hybrid model—AirPay conducts 1 live group session per location; follow-up one-on-one support via Slack for 2 weeks post-launch.

• Certification: Billing staff must pass a 10-question competency quiz before live launch. Retrain anyone scoring <80%.

Scaled Rollout (Weeks 7–16)

Wave Planning

Roll out in 4 waves of ~25% of locations each (staggered 2 weeks apart). This prevents support overload and allows corporate teams to isolate issues by cohort.

Change Management

• Weekly Sponsor Steering: CFO/COO reviews rollout dashboard (% locations live, DSO trend, support tickets) every Monday.
• Location Liaisons: Designate a "billing champion" per location (office manager or senior coordinator) as single point of escalation. They attend bi-weekly corporate syncs to share blockers and best practices.
• Communication Cadence: Weekly email newsletters highlighting success stories ("Location X reduced DSO by 8 days!") and FAQs.
• Resistance Management: If a location pushes back, offer a 1-week delay + dedicated on-site training. Avoid force-fits; buy-in matters more than speed.

Support Infrastructure

• Tier 1 (Locations): AirP