Gargle — Implementation Playbook (DSO)

Executive Summary

Gargle is a marketing-acquisition platform that automates patient discovery, appointment booking, and practice attribution across multi-location dental networks. It captures unscheduled patient demand, routes leads to available capacity, and integrates with practice management systems to reduce no-shows and leakage. For DSOs specifically, Gargle eliminates the fragmentation of patient acquisition across autonomous locations—enabling centralized demand capture, standardized conversion workflows, and margin-optimized capacity allocation.

Why DSOs benefit: Unlike single-location practices, DSOs operate with variable patient flow, inconsistent lead capture, and competing locations. Gargle creates a unified patient funnel that treats the group as a single entity, dramatically reducing CAC variance and improving location utilization.

Expected timeline: 16 weeks to full deployment (50+ locations); smaller DSOs (10–25 locations) typically achieve production readiness in 10–12 weeks.

Pre-Implementation Checklist (Weeks 1–2)

Technical Requirements

• PMS Integration Mapping
  Audit all systems in use across the DSO (Dentrix, Eaglesoft, Open Dental, Ortho Organizer, etc.). Identify which practices use which PMS and whether you have a single unified instance or distributed ones. Gargle requires direct API access or HL7 feeds; confirm your IT team has credentialing authority.

• Network & Security Infrastructure
  Verify your firewall rules permit outbound HTTPS connections to Gargle's cloud API endpoints. If you use a proxy or egress filtering, whitelist api.gargle.io, events.gargle.io, and *.gargle.io subdomains. Conduct a security review with your compliance/privacy team (HIPAA Business Associate Agreement must be signed before any PHI touches the platform).

• Phone & SMS Carrier Setup
  Gargle sends appointment reminders and follow-up texts; provision dedicated Twilio numbers or use your existing carrier. Confirm SMS delivery rates in your geography (critical for rural DSOs). Test inbound call routing from lead ads.

• Practice Management Access
  Create service accounts with appropriate read/write permissions in each location's PMS. Avoid shared login credentials; use role-based access. Document all credentials in a secure vault (1Password, Vault, etc.).

Stakeholder Alignment

• Clinical & Operational Buy-In
  Host 90-minute workshops with front-office managers, clinical leads, and practice owners from 3–5 representative locations. Clarify that Gargle surfaces demand they're already losing, not adding artificial volume. Address concerns about workflow disruption (answer: minimal—it integrates into existing booking).

• Finance & Analytics Leadership
  Define DSO-wide CAC baseline, target patient LTV, and desired payback period. Agree on how lead attribution and cost-per-acquisition will be calculated across locations (critical for accurate ROI). Align on whether Gargle's recommendation engine can auto-assign leads or if humans approve all routing.

• Marketing Team Ownership
  Assign a single point person (typically your marketing director or VP of acquisition) as DSO sponsor. This person owns campaign strategy, budget, weekly reporting, and escalation. Communicate that Gargle is a distribution tool, not a replacement for your ad strategy.

Baseline Metrics to Capture

Document these before Gargle launches:

Pilot Wave (Weeks 3–6)

Location Selection Criteria

Choose 4–6 locations that represent your DSO's diversity:

• 1–2 high-volume urban practices (easy to generate statistically valid results)
• 1–2 mid-size suburban practices (realistic average case)
• 1 under-performing location (test Gargle's capacity-filling benefit)

Exclusion criteria:

• Practices in active leadership transition
• Locations with PMS implementations <6 months old (unstable data)
• Practices with broken phone systems or staff turnover >50% in past year

Configuration & Setup

Phase A: Integration Setup (Week 3)

• Run PMS API connectivity tests; validate 48-hour data sync lag is acceptable
• Map lead source taxonomy (Google Local Services Ads → LSA, Facebook → FB, etc.)
• Configure appointment type routing rules: e.g., "Exams under 30 min → online booking; Complex cases → human review"
• Load 90 days of historical data to train Gargle's attribution model

Phase B: Campaign Staging (Week 4)

• Launch Gargle-connected lead campaigns to pilot locations only (use geofencing or location ID targeting)
• Configure SMS templates for confirmations, reminders, and follow-ups (compliance-checked by legal)
• Set up Gargle dashboard access for location managers; test role-based permissions
• Create feedback form for staff (simple Google Form) to capture UX friction

Phase C: Soft Launch (Week 5)

• Go live with 20–30% of normal ad budget to pilot locations
• Monitor real-time leads in Gargle dashboard; observe booking conversion
• Have a daily standup (15 min) with pilot location managers to surface blockers same-day
• Track no-show rate pre/post for early signal of SMS effectiveness

Phase D: Full Pilot & Analysis (Week 6)

• Scale pilot ad spend to 100% of typical budget
• Capture video screen-recordings of staff using Gargle (for training rollout)
• Run final PMS sync audit; confirm zero data loss
• Conduct exit interviews with pilot location staff

Training Approach

• Role-based modules (30 min each): "Front desk booking," "Manager dashboards," "Clinical lead reporting"
• Recorded walkthroughs from your pilot locations (staff recognize familiar faces/accents)
• Cheat sheets (laminated, posted at front desk): "How to handle a Gargle lead," "What if the patient texts back?"
• Shadow day for rollout locations: assign one staff member to visit a pilot location before their launch

Scaled Rollout (Weeks 7–16)

Wave Planning

Wave 1 (Week 7–8): 10–12 locations (include 2 existing pilot sites as "success anchors")
Wave 2 (Week 9–11): 15–18 locations
Wave 3 (Week 12–16): Remaining locations

Rationale: Each wave allows you to identify configuration patterns and retrain support staff based on real-world friction.

Change Management

• Weekly rollout calls with location managers 1 week pre-launch, 2 weeks post-launch
• "Gargle champion" per location: designate one staff member to be the expert (give them a small bonus/recognition)
• Monthly all-hands webinar for first 3 months: share wins, answer questions, celebrate early adopters
• Monthly DSO-level reporting to executive team; highlight CAC improvement and capacity utilization gains

Support Infrastructure

• Dedicated Slack channel (#gargle-support) for real-time troubleshooting
• Escalation matrix:
  • Tier 1 (location manager) → troubleshoot basic workflow issues (30 min SLA)
  • Tier 2 (DSO marketing team) → lead routing logic, campaign config (4 hr SLA)
  • Tier 3 (Gargle CS) → PMS integration, API issues (24 hr SLA)
• Monthly office hours: 1 hr video call with Gargle product team for DSO-wide strategy
• Success playbook wiki (Notion or Confluence): accumulated solutions, workarounds, best practices

ROI Tracking

Key Metrics to Measure

1. **