Codent — Implementation Playbook (DSO)

Strategic Implementation Playbook: Codent AI Treatment Coordinator

Executive Summary

Codent is an AI-powered treatment coordination platform that automates personalized patient follow-ups via SMS for unscheduled treatment recommendations, dynamically addressing cost barriers, insurance eligibility, and direct scheduling friction. For DSOs operating 15–50 locations, this tool delivers immediate standardization of patient communication across markets, eliminates manual coordinator bottlenecks, and creates a scalable data layer to track treatment acceptance trends at both location and portfolio levels—critical advantages when managing heterogeneous patient populations and staffing constraints across geographies. Expected deployment timeline: 8–12 weeks from contract execution to full adoption across all locations (4–6 weeks for pilot wave, 2–3 weeks for Wave 2, 2–3 weeks for Wave 3 and stabilization).

Pre-Implementation Checklist

Technical Infrastructure

• ☐ Verify PMS integration compatibility (validate Codent's certified connectors against all PMS platforms in use across DSO)
• ☐ Confirm bi-directional API connectivity and testing protocols with IT/PMS vendor support teams
• ☐ Assess SMS delivery infrastructure (carrier agreements, message throughput capacity, failover protocols)
• ☐ Validate network architecture for HIPAA compliance (encryption in transit, secure credential storage)
• ☐ Test VPN/firewall rules permitting Codent webhooks and data synchronization

Data Readiness

• ☐ Audit PMS data quality across all locations: patient phone numbers (coverage %), insurance fields, treatment notes, fee schedules
• ☐ Establish baseline treatment acceptance rates per location (% of recommended treatments scheduled within 30 days)
• ☐ Confirm insurance plan database is current and aligned with payer fee schedules in PMS
• ☐ Identify data normalization requirements (e.g., inconsistent treatment codes, fee schedule formats)
• ☐ Create patient opt-out audit trail and consent documentation process

Stakeholder Alignment

• ☐ Secure sign-off from CDO/VP Ops, IT Director, Compliance Officer, and Finance/Controller
• ☐ Conduct kickoff call with all location managers; set expectations for staff training and change management
• ☐ Designate enterprise-level project manager and establish weekly steering committee (IT, Ops, Compliance, Codent)
• ☐ Brief clinical team on AI message tone/clinical appropriateness; define escalation protocols for edge cases

Baseline Metrics

• ☐ Document current treatment acceptance rate, average days-to-schedule, and patient response channels per location
• ☐ Capture staffing metrics: FTE hours spent on manual follow-ups, coordinator productivity, overtime trends
• ☐ Establish SMS opt-in rates by location and identify patients with no valid phone number

Compliance & Legal

• ☐ Confirm BAA (Business Associate Agreement) is fully executed with Codent and covers all use cases
• ☐ Review Codent's SOC 2 Type II certification and HIPAA risk assessment
• ☐ Audit message templates for compliance with CAN-SPAM, TCPA, and state-specific telehealth regulations
• ☐ Establish audit logging and retention policies for SMS records (minimum 7 years per ADA/state requirements)

Location Readiness Assessment

Use the following 5-point scoring framework to rank each location across five dimensions. A location scoring 20+ is Wave 1-ready; 15–19 is Wave 2; below 15 requires remediation before rollout.

Rollout Sequencing Recommendation:

• Wave 1 (Weeks 1–6): Pilot at 2–3 locations scoring 22–25 (typically high-volume, tech-forward markets with strong IT support)
• Wave 2 (Weeks 7–10): Deploy to next cohort scoring 18–21 (mid-tier readiness; benefit from pilot learnings)
• Wave 3 (Weeks 11–14): Roll out to remaining locations and provide extended support for scores 15–17; delay sites below 15 until data quality/infrastructure improvements are made

Rollout Strategy

Wave 1: Pilot Locations (2–3 Sites, Weeks 1–6)

Selection Criteria:

• Highest readiness scores (22–25 per assessment above)
• Geographically dispersed (to surface regional SMS/carrier issues early)
• Willing to participate in weekly feedback loops and message testing
• Strong IT and operations leadership on-site

Timeline:

• Week 1: Kick off meetings, PMS integration testing, IT credential setup
• Week 2: Staff training (clinicians, coordinators, front desk), message template review and customization
• Week 3–4: Soft launch with limited patient cohort (e.g., 50–100 treatment cases); monitor SMS delivery, opt-in, and clinician feedback
• Week 5: Full launch at pilot locations; daily check-ins on delivery metrics and patient response
• Week 6: Retrospective; document learnings, refine message templates, identify process changes

Go/No-Go Criteria for Wave 2:

• ✓ SMS delivery rate ≥95%
• ✓ Patient opt-in rate ≥70% of active patient base
• ✓ Zero critical data breaches or HIPAA violations
• ✓ Treatment scheduling uplift of ≥10% vs. baseline (target: +15%)
• ✓ Clinician feedback score ≥4/5 on usability and message appropriateness
• ✗ If any criterion fails, extend pilot by 2 weeks; escalate to Codent for technical or content remediation

Wave 2: Secondary Rollout (Next 5–8 Locations, Weeks 7–10)

• Deploy to locations scoring 18–21; leverage pilot learnings to compress training from 2 days to 1 day
• Implement refined message templates; establish local coordinator "super-users" to troubleshoot
• Weekly metric reviews across Wave 1 + Wave 2; adjust message cadence or timing based on aggregate response data
• Go/No-Go Criteria: Same as Wave 1; if aggregate metrics across Waves 1–2 show <8% uplift, pause Wave 3 and conduct root-cause analysis

Wave 3: Full Deployment (Remaining Locations, Weeks 11–14)

• Deploy to all remaining locations; prioritize those scoring 15–17 (with targeted IT support)
• Defer locations with critical IT/data quality issues; create remediation plan for Q2 rollout
• Implement tiered support model: Codent + enterprise team → location champions → clinicians
• Month-end assessment: aggregate metrics, identify high-performing vs. struggling sites, plan optimization sprints

Rollback Plan

If critical issues emerge (e.g., HIPAA breach, 50%+ message delivery failure, clinician safety concerns):

1. Immediate halt of new message deployments; notify all locations and Codent within 24 hours
2. Isolate affected locations; switch back to manual follow-up protocols
3. Root-cause analysis with Codent, IT, and Compliance (48-hour SLA)
4. Resume deployment only after remediation is validated and documented; communicate all changes to clinical and IT teams

Key Metrics to Track

Per-Location Metrics (Tracked Weekly)

1. Treatment Acceptance Rate (%)

   • Definition: % of unscheduled treatment recommendations followed by Codent SMS that result in a scheduled appointment within 14 days
   • Baseline: [Document pre-implementation rate per location]
   • Target: +12–18% improvement vs. baseline within 12 weeks of deployment

2. SMS Delivery Rate (%)

   • Definition: % of SMS messages successfully delivered to patient carriers
   • Target: ≥95% (failures typically due to invalid phone numbers; <5% expected churn)

3. Patient Opt-In/Engagement Rate (%)

   • Definition: % of active patients who have provided valid phone numbers and have not opted out of SMS
   • Target: ≥70% of active patient base within 60 days; track opt-in channel (initial signup, in-office, online)

4. Average Days to Schedule (DTS)

   • Definition: Median number of days from treatment recommendation to scheduled appointment
   • Baseline: [Document pre-implementation; typically 7–21 days depending on treatment urgency and location]
   • Target: Reduce DTS by 2–5 days (e.g., from 14 to 10 days)

5. Coordinator Time Savings (Hours/Month)

   • Definition: Total manual follow-up hours per coordinator before vs. after Codent; calculate FTE reduction potential
   • Target: 20–30% reduction in coordinator follow-up time (typically 8–16 hours/month per full-time coordinator)

Portfolio-Level Metrics (Tracked Monthly)

6. Treatment Revenue Impact ($)

   • Definition: Incremental revenue from increased treatment acceptance across all deployed locations
   • Calculation: (New appointments from Codent × conversion rate × avg. treatment fee) - Codent licensing costs
   • Target: Positive ROI within 12–16 weeks post-full-deployment

7. Patient Satisfaction (CSAT) on SMS Communication (Score 1–5)

   • Definition: Post-appointment survey asking patients to rate clarity, helpfulness, and tone of Codent SMS
   • Target: ≥4.0/5.0 (indicates message personalization and clinical appropriateness are resonating)

8. Compliance Audit Score (%)

   • Definition: % of message logs passing audit for HIPAA, TCPA, and clinical appropriateness per quarter
   • Target: 100% (zero violations; any failure triggers immediate message template review)

Reporting Cadence: Weekly dashboards shared with location managers; monthly steering committee review with variance analysis and action items.

Common Pitfalls

1. **Underestimating Data Quality Dependencies**

Pitfall: Deploying Codent without auditing PMS data; invalid/incomplete patient phone numbers, outdated insurance, inconsistent treatment codes result in silent failures and low engagement.

Mitigation: Conduct pre-implementation data audit (identify coverage gaps, data cleanup requirements); establish data governance process whereby locations validate phone numbers and insurance at each patient visit; set minimum 90% data completeness threshold before rollout.

2. **Insufficient Clinician Buy-In on AI Messaging**

Pitfall: Clinicians perceive Codent as depersonalizing patient communication or question clinical accuracy of AI-generated messages, leading to override/disengagement.

Mitigation: Involve clinical advisory group in message template design; train clinicians on how Codent personalizes tone based on patient history and cost barriers; establish clinician dashboard showing which messages drive highest acceptance (social proof). Frame as "coordinator enabler," not replacement.

3. **Weak Pilot-to-Scale Transition**

Pitfall: Pilot locations achieve results but message templates, workflows, or data assumptions don't translate to Wave 2/3 sites with different PMS versions, patient demographics, or staff maturity.

Mitigation: Document all pilot configuration decisions (message cadence, timing windows, insurance logic) in a standardized "deployment playbook"; require Wave 2 locations to adapt playbook to local context but restrict ad-hoc message changes. Use Wave 1→Wave 2 transition meeting to validate assumptions with location leadership.

4. **Inadequate SMS Compliance Framework**

Pitfall: Locations send SMS without proper patient consent audit trails or fail to comply with TCPA/CAN-SPAM timing rules, exposing DSO to FTC enforcement or class-action liability.

Mitigation: Implement centralized SMS compliance audit (monthly) covering consent documentation, opt-out processing, and message timing; use Codent's built-in compliance logging; establish clear escalation protocol for opt-out requests. Assign Compliance Officer as Codent stakeholder.

5. **Unrealistic ROI Expectations / Delayed Metric Visibility**

Pitfall: Leadership expects immediate revenue uplift; lack of real-time metric dashboard causes frustration and premature project termination.

Mitigation: Set expectations clearly: treatment acceptance uplift typically visible within 4–6 weeks of deployment, but revenue impact (after cancellations/no-shows) materializes over 12–16 weeks. Implement live dashboard accessible to all location managers; celebrate early wins (e.g., "Clinic A gained 23 treatment cases in Week 4").

6. **Neglecting Feedback Loop and Continuous Optimization**

Pitfall: Message templates are set at launch and remain static; no mechanism to test variations or adjust cadence based on seasonal trends, leading to declining engagement over time.

Mitigation: Establish monthly "optimization sprint" where Codent, Ops, and pilot locations review engagement trends, test 1–2 message variations, and document learnings in shared playbook. Empower locations to propose localized messaging adjustments (within brand guidelines) and measure impact.

Cost/ROI Framework

Enterprise Cost Model

Licensing (Typical for 15–50 locations):

• Per-location model: $800–$1,500/month per location (includes up to 2,000 monthly SMS + API access)
• Enterprise model: Flat fee $15,000–$25,000/month for unlimited locations + dedicated support + custom integrations
• Typical DSO 30-location portfolio: $18,000–$25,000/month enterprise license (assuming enterprise model cost savings vs. per-location model)
• Annual commitment: 15–20% discount if signed

Implementation & Professional Services (One-time):

• PMS integration + API configuration: $3,000–$5,000
• Message template development + compliance review: $2,000–$4,000
• Staff training (enterprise + location): $1,500–$2,500
• Total first-year cost: $24,500–$40,500 (licensing + onetime services)

Ongoing Costs (Year 2+):

• Annual licensing: $18,000–$25,000
• Optimization/support: $2,000–$4,000/year
• Total Year 2 cost: $20,000–$29,000

ROI Measurement & Targets

Revenue Uplift Calculation:

• Baseline: Average unscheduled treatment revenue per location/month
• Expected uplift: 12–18% increase in treatment acceptance → incremental revenue of $1,500–$3,500 per location/month (varies by patient demographics, avg. treatment fee, baseline acceptance rate)
• Portfolio impact (30 locations): $45,000–$105,000/month incremental revenue at full deployment
• Conservative estimate for typical DSO: $600,000–$1.2M annual incremental revenue

Cost Offset Calculation:

• Coordinator time savings: 20–30% reduction in follow-up labor → $8,000–$15,000 per location-year in FTE cost avoidance
• Portfolio savings (30 locations): $240,000–$450,000/year in labor reductions
• Total portfolio benefit: $840,000–$1.65M/year (revenue + labor)

ROI Timeline: