Inside Desk Implementation Playbook (DSO)

Executive Summary

Inside Desk is avized's revenue cycle management hub—consolidating patient billing, insurance verification, claim tracking, and payment posting across all DSO locations into a single dashboard. For a 10+ location DSO, this eliminates siloed billing operations, surfaces claim leakage instantly, and standardizes collection workflows that typically recover 3–7% of missed revenue per location. Without it, you're managing billing via spreadsheets, email, and location-specific systems; with it, you're running revenue cycle like a unified enterprise.

Pre-Implementation Checklist

• Audit current billing stack. Document every system in use across locations (practice management software, clearinghouses, billing service vendors, spreadsheets). Identify gaps, redundancies, and data export capabilities. This prevents integration dead zones later.

• Assign a DSO-level Revenue Cycle Lead. This person owns rollout, trains location managers, and drives adoption. Without single ownership, rollout stalls at the first location friction point.

• Verify data export readiness. Confirm your PMS can export A/R aging, claim status, and patient payment data in formats Inside Desk accepts. Test with one location first. Failed exports kill timelines.

• Establish baseline metrics. Pull 90 days of historical data on Days in A/R (DSO total and by location), claim acceptance rate, claim denial rate, and average time-to-payment. You need this to measure lift post-launch.

• Schedule IT infrastructure review. Confirm network bandwidth, user access protocols, and any compliance requirements (HIPAA, state regs) that affect how data flows into Inside Desk. Get IT approval in writing before pilot.

• Define user access structure. Decide who at each location gets what access (office manager sees all claims; hygiene coordinator sees none, etc.). Map roles before training starts—role confusion creates support tickets.

• Plan for location-by-location rollout or big bang. For 10+ locations, staggered rollout (2–3 locations in phase 1) reduces implementation risk. Document this decision and communicate it to all stakeholders now.

Implementation Timeline

Phase 1: Pilot & Training (Weeks 1–3)

• Select 2–3 anchor locations (high billing volume, engaged managers). Export their A/R data, load it into Inside Desk sandbox. Run parallel billing operations for one full week—staff uses Inside Desk alongside their existing workflow, comparing outputs.
• Conduct hands-on training for pilot location staff (office managers, billing coordinators). Focus on claim status lookup, payment posting, and exception handling. Record sessions; you'll reuse this footage for other locations.

Phase 2: Rollout to Remaining Locations (Weeks 4–8)

• Migrate locations in cohorts of 3–4. Stagger by 1 week per cohort to prevent support overload. Each location gets a 90-minute onboarding call plus 2 weeks of daily check-ins from the Revenue Cycle Lead.
• Run parallel operations for 2 weeks at each location. Staff must confirm claim counts, aging buckets, and payment posting reconcile between Inside Desk and old system before going live.

Phase 3: Integration & Optimization (Weeks 9–12)

• Connect Inside Desk to your clearinghouse and PMS via API (if available). Eliminate manual exports; automate daily claim feeds.
• Establish weekly DSO-level reporting cadence. Revenue Cycle Lead runs a 30-minute Monday call reviewing claims submitted, denials, and payment trend by location. This keeps attention on the system and surfaces drift early.

Phase 4: Continuous Improvement (Ongoing)

• Monitor KPIs weekly. Flag locations underperforming on Days in A/R or claim acceptance rate. Dig in, coach, and adjust workflows.
• Schedule quarterly reviews with location managers to identify process gaps and update collection protocols based on claim denial patterns.

Key Metrics to Track

• Days in A/R (DSO-level). Target: reduce by 5–8 days within 90 days of full rollout. Baseline this before launch. This metric proves cash velocity improved.

• Claim Denial Rate (by location & denial reason). Target: <5% of submitted claims. Track denials by reason (eligibility, coding, missing info) and create location-specific action plans for high-denial outliers.

• Claim Acceptance Rate (clean claims on first submission). Target: >85% within 60 days. This is where Inside Desk visibility drives behavior change—staff fix eligibility issues before submission.

• Time-to-Payment (claim submission to patient payment posted). Target: reduce by 10–15 days. Measure from date claim submitted to date EOB received and payment applied. Inside Desk's claim status tracking accelerates follow-up.

• Gross Collection Rate (collected revenue ÷ adjustable charges). Target: >96%. Inside Desk unearths write-off errors and stale patient balances that artificially depress this figure.

• Staff Productivity (claims processed per FTE per month). Target: increase 15–20%. Automation and visibility eliminate time spent hunting claim status via phone or email.

Common Pitfalls

1. Skipping the pilot phase. Practice: "We have 12 locations—let's just flip the switch." Reality: You'll encounter unexpected PMS export issues, training gaps, and staff resistance that cripple 10+ locations simultaneously. Mitigation: Run a 3-week pilot no matter what. The operational knowledge gained is worth the timeline delay.

2. Neglecting location buy-in. Billing staff see Inside Desk as surveillance or extra work initially. Without early wins and clear communication about how it helps them (faster claim follow-up, fewer denials, easier posting), adoption stalls. Mitigation: Have the Revenue Cycle Lead spend time at each location in person, not just Zoom calls. Show staff how inside Desk reduces their chase-down time. Celebrate first win (e.g., caught eligibility error, prevented denial).

3. Treating all locations the same. High-volume locations and solo-operatory offices need different workflows and support. Mitigation: Customize training and workflows by location size. Offer weekly group coaching calls for small offices; biweekly for large ones.

4. Failing to integrate with existing PMS. If you keep exporting claims manually and re-entering data, Inside Desk is just another data entry tool. Mitigation: Prioritize API setup after pilot phase. Even partial integration (claims feed only, initially) saves 5–10 hours per week DSO-wide.

5. Ignoring denial patterns. Inside Desk shows you denials; many DSOs collect the data but don't act on it. Mitigation: Assign a single person to review denial trends monthly and coach locations on the top 3 denial reasons. This activity alone can improve claim acceptance by 5–8%.

Cost & ROI Framework

Costs

• Inside Desk subscription (avized SaaS): ~$500–$1,200/month depending on claim volume and user seats. Budget $6,000–$15,000 annually.
• Implementation services (optional): $3,000–$8,000 for avized professional services to handle data migration, API setup, and custom reporting.
• Internal labor: 80–120 hours from Revenue Cycle Lead and IT during phases 1–3. At fully-loaded cost ($50/hr), ~$4,000–$6,000.
• Total Year 1 investment: $13,000–$29,000.

Payback Period

A 10-location DSO with ~$15M annual patient revenue and current Days in A/R of 42 days can expect:

• Reduce Days in A/R by 6 days (conservative estimate) = $247K in recovered cash flow in month 4.
• Improve clean claim rate by 6% = 3,600 additional claims accepted per year, equivalent to ~$180K in accelerated revenue.
• Payback on $20K Year 1 investment: <6 weeks (driven primarily by days reduction).

ROI Drivers

1. Days in A/R reduction (~60% of benefit). Each day of DSO-level A/R reduction = $41K+ in freed cash flow. Inside Desk's visibility and automated follow-up triggers drive this.

2. Claim acceptance improvement (~25% of benefit). Staff catch and fix errors before submission. 5–8% increase in clean claims = $150