Vyne Dental
Implementation PlaybookDSO · Group Practice

Vyne Dental

Step-by-step implementation guide — pre-implementation checklist, onboarding, staff training, go-live runbook, and ROI tracking.

Vyne Dental — Implementation Playbook (DSO)

Vyne Dental Implementation Playbook

Revenue Cycle AI for Dental Support Organizations


1. Executive Summary

What Vyne Dental Does

Vyne Dental provides a comprehensive revenue cycle management platform that leverages AI-powered automation to streamline claims processing, eligibility verification, electronic attachments, and patient billing workflows. The platform eliminates manual claims submission, automates attachment requests, and reduces claim rejections through intelligent validation before submission.

Why DSOs Specifically Benefit

DSOs operating at scale face exponential complexity in revenue cycle management—each additional location multiplies claims volume, payer relationships, and opportunities for revenue leakage. Vyne Dental delivers three critical scale advantages:

  1. Data Aggregation for Pattern Recognition: Across 15–50 locations, Vyne's AI identifies denial patterns, payer-specific requirements, and submission timing optimization that would be invisible at the single-practice level. A rejection pattern affecting 2% of claims at one location becomes a $200K+ annual recovery opportunity when identified and addressed across 40 locations.

  2. Standardization of Revenue Cycle Execution: Rather than 30 different billing staff members applying 30 different interpretations of payer requirements, Vyne enforces consistent, optimized workflows. This reduces training burden, simplifies compliance, and creates predictable cash flow.

  3. Centralized Visibility: CFOs and VPs of Operations gain real-time dashboards showing claims status, denial rates, and revenue cycle KPIs across all locations—enabling intervention before small problems compound.

Expected Timeline: Decision to Full Deployment

Phase Timeline Scope
Pre-Implementation & Planning Weeks 1–2 Central team alignment, baseline metrics, readiness assessment
Wave 1 Pilot Weeks 3–5 2–3 locations
Wave 1 Evaluation & Optimization Week 6 Learning capture, process refinement
Wave 2 Rollout Weeks 7–10 5–8 locations
Wave 3+ Rollout Weeks 11–16 Remaining locations
Full Optimization Weeks 17–20 Enterprise-wide optimization, advanced features

Total timeline for a 30-location DSO: 16–20 weeks to full deployment


2. Pre-Implementation Checklist (Weeks 1–2)

Technical Requirements

Hardware Requirements

☐ Workstations: Windows 10/11 (64-bit) or macOS 10.15+, minimum 8GB RAM
☐ Dual monitors recommended for billing staff (efficiency gain of 15–20%)
☐ Scanner compatibility verification for attachment capture (if not using digital imaging)
☐ Printer capability for patient statements if using Vyne's patient billing module

Software Requirements

☐ Practice Management System version compatibility confirmed:

  • Dentrix G6.2 or higher
  • Eaglesoft 21.0 or higher
  • Open Dental 22.1 or higher
  • Other PMS: Confirm with Vyne support ☐ Web browser: Chrome (current), Edge (current), or Firefox (current)
    ☐ .NET Framework 4.7.2 or higher (Windows)
    ☐ PDF reader installed for attachment viewing

Network Requirements

☐ Minimum 25 Mbps download / 10 Mbps upload per location
☐ Consistent latency under 100ms to Vyne servers
☐ Firewall whitelist for Vyne domains (obtain list from Vyne implementation team)
☐ SSL/TLS 1.2 or higher enabled

Integration Requirements

☐ PMS API access enabled and credentials documented
☐ Imaging system integration capability verified (Dexis, Schick, Patterson Imaging, etc.)
☐ EDI clearinghouse transition plan (if switching from existing clearinghouse)


🔵 Vendor Onboarding Steps

Step Owner Timeline
☐ Execute enterprise BAA Legal + Vyne Week 1
☐ Complete enterprise onboarding form Central Ops Week 1
☐ Receive dedicated implementation manager assignment Vyne Day 3
☐ Schedule kickoff call with implementation team Central Ops + Vyne Week 1
☐ Obtain vendor escalation contact list (Tier 1, 2, 3 support) Vyne Week 1
☐ Confirm enterprise pricing and location-add process Finance + Vyne Week 1
☐ Establish dedicated Slack channel or Teams instance for implementation IT + Vyne Week 1

Key Vyne Contacts to Establish:

  • Implementation Manager (your primary contact)
  • Technical Integration Specialist
  • Enterprise Account Executive
  • Support Escalation Contact
  • Training Coordinator

Data/Access Prerequisites

☐ Admin credentials for each PMS instance
☐ 🔵 API keys or integration tokens generated (coordinate with Vyne)
☐ Payer ID list with current enrollment status
☐ Historical claims data export capability (12 months recommended)
☐ Current clearinghouse portal credentials (for transition coordination)
☐ Provider NPI list with taxonomy codes
☐ Location NPI list
☐ Tax ID documentation for each location


Internal Stakeholder Alignment

🟣 Approval Required

Stakeholder Decision/Approval Needed Timeline
Board/Investors Budget approval, strategic alignment sign-off Before Week 1
CFO ROI targets, success metrics, budget allocation Week 1
CEO/COO Rollout timeline approval, resource allocation Week 1
Chief Dental Officer Clinical workflow impact acknowledgment Week 1
VP of Operations Rollout sequence, location selection Week 1
General Counsel BAA review, data governance approval Week 1

Informed (No Approval Required)

Stakeholder Communication Needed Timeline
Regional Managers Rollout timeline, expectations, resource needs Week 2
Office Managers High-level overview, timeline for their location Week 2
Billing Staff Change is coming, training schedule forthcoming Week 2
Clinical Providers Awareness only at this stage Week 2

Baseline Metrics to Capture

⚠️ Critical: Capture these BEFORE go-live. Without baselines, ROI measurement is impossible.

Standardized Metrics Framework (Capture Identically Across All Locations)

Metric Definition Capture Method Target Frequency
Clean Claim Rate % of claims accepted on first submission PMS report + clearinghouse report Weekly for 4 weeks pre-launch
Days to Payment Average days from service to payment posting PMS aging report Monthly average, 3 months
Claim Denial Rate % of claims denied (initial + final) Clearinghouse report Monthly average, 3 months
Denial Recovery Rate % of denied claims successfully appealed Manual tracking or PMS Monthly average, 3 months
Time to Submit Hours from procedure completion to claim submission PMS timestamp analysis Weekly average
Attachment Request Volume # of attachment requests received monthly Manual count or portal Monthly, 3 months
Attachment Response Time Days from request to submission Manual tracking Monthly average
Eligibility Verification Accuracy % of eligibility checks matching actual benefits Manual audit sample 50-claim sample
Staff Time on RCM Tasks Hours/week per billing FTE on claims Time study or estimate 2-week time study
AR Over 90 Days % of AR in 90+ day bucket PMS aging report Monthly snapshot

Metric Collection Protocol

☐ Create standardized Excel template with metric definitions
☐ Assign central analyst to aggregate data from all locations
☐ 🟣 Designate official "baseline period" (recommend: 4 weeks pre-implementation)
☐ Store baseline data in secure, version-controlled location
☐ Document any known anomalies (e.g., "Location 7 had a billing manager vacancy in Month 2")


Enterprise-Level Requirements

Network Standards Across Locations

☐ Audit current network performance at all locations (use standardized speed test)
☐ Identify locations below minimum thresholds (25/10 Mbps)
☐ 🟣 Approve network upgrade budget for underperforming locations
☐ Establish standard firewall rules for Vyne access
☐ Document VPN requirements if applicable

Hosting Model Decision

🟣 Centralized vs. Location-Level Decision

Factor Centralized Per-Location
Data sovereignty All data flows through central Data stays at location
Network dependency Higher dependency Lower dependency
Admin overhead Lower Higher
Compliance management Simplified Complex
Vyne Recommendation ✓ (For DSOs 15+ locations)

☐ Confirm hosting model with Vyne and IT leadership

Single Sign-On (SSO)

☐ Confirm Vyne SSO compatibility (SAML 2.0 supported)
☐ Provide IdP metadata to Vyne
☐ 🔵 Configure SSO in Vyne admin portal
☐ Test SSO with pilot users before rollout

Centralized Credentialing

☐ Compile master provider list with NPI, license, DEA (if applicable)
☐ Verify current payer enrollment status for all providers
☐ Identify providers requiring re-credentialing
☐ 🔵 Submit bulk credentialing package to Vyne for payer enrollment
☐ ⚠️ Begin credentialing 4–6 weeks before planned go-live (payer timelines vary)


3. Location Readiness Assessment

Scoring Framework

Score each location 1–5 on the following factors. A composite score determines rollout priority.

Factor 1: IT Infrastructure Maturity (Weight: 25%)

Score Criteria
5 Network >50 Mbps, hardware <2 years old, PMS current version, IT support on-site or <1 hour response
4 Network 25–50 Mbps, hardware 2–3 years old, PMS within 1 version of current
3 Network 15–25 Mbps, hardware 3–4 years old, PMS within 2 versions, IT support same-day
2 Network 10–15 Mbps, hardware 4–5 years old, PMS outdated, IT support next-day
1 Network <10 Mbps, hardware >5 years, PMS significantly outdated, no reliable IT support

Factor 2: Staff Tenure and Adaptability (Weight: 20%)

Score Criteria
5 Billing manager tenure >3 years, turnover <10%, prior tech rollout success, proactive learners
4 Billing manager tenure 2–3 years, turnover 10–20%, adequate tech adoption history
3 Billing manager tenure 1–2 years, turnover 20–30%, mixed tech adoption
2 Billing manager tenure <1 year, turnover 30–40%, some resistance to change
1 Billing manager new or vacant, turnover >40%, significant change resistance

Factor 3: Patient Volume (Weight: 20%)

Score Criteria Rationale
5 400–600 patients/month High impact, manageable volume for pilot learning
4 300–400 patients/month Good impact, lower risk
3 200–300 patients/month Moderate impact
2 600–800 patients/month High impact but high risk for pilot
1 <200 or >800 patients/month Too low impact or too high risk

Factor 4: Existing Tech Stack Compatibility (Weight: 20%)

Score Criteria
5 PMS with native Vyne integration, digital imaging, existing clearinghouse with clean transition path
4 PMS with supported integration, digital imaging, standard clearinghouse
3 PMS supported but requires configuration, digital imaging, some integration complexity
2 PMS supported but outdated version, mixed imaging, complex clearinghouse situation
1 PMS requires significant workaround, limited digital capabilities, multiple clearinghouses

Factor 5: Local Champion Availability (Weight: 15%)

Score Criteria
5 Office manager or lead billing staff is tech-forward, enthusiastic, has led prior implementations, respected by peers
4 Capable staff member willing to champion, some prior tech leadership
3 Staff member identified but limited experience, willing to be trained
2 No obvious champion, but no active resistors
1 No champion available, or key staff actively resistant

Scoring Calculation

Composite Score = (IT × 0.25) + (Staff × 0.20) + (Volume × 0.20) + (Tech Stack × 0.20) + (Champion × 0.15)

Rollout Tier Assignment

Composite Score Tier Rollout Recommendation
4.0–5.0 Tier 1 Wave 1 pilot candidates
3.0–3.9 Tier 2 Wave 2 deployment
2.0–2.9 Tier 3 Wave 3 deployment, may require pre-work
<2.0 Tier 4 Remediation required before deployment

Sample Scoring Sheet

Location IT (×0.25) Staff (×0.20) Volume (×0.20) Tech (×0.20) Champion (×0.15) Composite Tier
Phoenix Central 4 (1.00) 5 (1.00) 4 (0.80) 4 (0.80) 5 (0.75) 4.35 1
Dallas North 5 (1.25) 4 (0.80) 5 (1.00) 4 (0.80) 4 (0.60) 4.45 1
Austin Downtown 3 (0.75) 3 (0.60) 3 (0.60) 3 (0.60) 3 (0.45) 3.00 2

Rollout Sequence Recommendation

Wave 1 Selection Criteria (2–3 locations):

  • Composite score 4.0+
  • Geographic diversity (different regions for broader learning)
  • Practice type diversity (at least one GP, one specialty if applicable)
  • Strong champion availability (score 4+ on this factor specifically)
  • ⚠️ Avoid highest-volume location for Wave 1 (risk too high)

Wave 2 Selection Criteria (5–8 locations):

  • Composite score 3.5+
  • Include one "stretch" location (score 3.0–3.5) to test remediation playbook
  • Regional clustering recommended (reduces travel for support)

Wave 3+ (Remaining locations):

  • All remaining Tier 2 and Tier 3 locations
  • Tier 4 locations only after remediation complete

4. Rollout Strategy

Wave Structure

Wave # Locations Week Purpose
Wave 1 2–3 Weeks 3–5 Pilot: validate integration, refine training, identify issues
Wave 2 5–8 Weeks 7–10 Scale: test at moderate scale, refine support model
Wave 3 8–10 Weeks 11–14 Expand: broader deployment with proven playbook
Wave 4 Remaining Weeks 15–18 Complete: final locations, hardest cases

Wave 1: Pilot Phase (Weeks 3–5)

Selection Criteria for Pilot Locations

🟣 Executive Decision Required

Criterion Rationale
Composite readiness score 4.0+ Minimizes implementation friction
Not the flagship/highest-revenue location Reduces risk of disruption to critical revenue
Office manager with tenure and respect Champion can troubleshoot and advocate
Geographic proximity to central support Enables in-person support if needed
Representative specialty mix Learnings apply to similar locations
Stable staffing (no imminent turnover) Avoids training staff who will leave

Wave 1 Timeline

Week Activity
Week 3, Day 1–2 🔵 Integration configuration and testing
Week 3, Day 3–4 Champion training (in-person or intensive virtual)
Week 3, Day 5 Staff training
Week 4, Day 1 Go-Live
Week 4, Day 1–5 Daily check-ins, intensive support
Week 5 Stabilization, workflow refinement

Success Metrics for Wave 1

Metric Target Measurement
System uptime 99%+ Vyne monitoring dashboard
Claims submitted via Vyne 90%+ by Day 5 Vyne dashboard
Staff adoption (using system daily) 100% Login tracking
Clean claim rate No degradation from baseline Weekly comparison
Critical issues requiring vendor escalation <3 Issue log
Staff satisfaction (quick pulse) 3.5/5 or higher End-of-week survey

Wave 2: Scale Phase (Weeks 7–10)

Timeline per Location Within Wave

Day Activity
Day 1 Integration configuration (can be done in parallel for multiple locations)
Day 2 Testing and validation
Day 3 Champion trains staff (using standardized materials refined from Wave 1)
Day 4 Shadow day (staff uses system alongside old workflow)
Day 5 Go-Live
Days 6–10 Daily check-ins, support

Buffer Between Waves

☐ Minimum 1-week buffer between waves
☐ Buffer used for: lessons learned documentation, training material updates, process refinements
☐ 🟣 Formal go/no-go decision at end of buffer week


Go/No-Go Criteria

Criteria to Advance to Next Wave

Category Go Criteria No-Go (Pause) Criteria
Technical 95%+ system uptime, <5 critical bugs open >2 hours cumulative downtime, unresolved critical bugs
Adoption 85%+ claims processed through Vyne <70% claims through system
Staff No unresolved training gaps, champion effective Champion overwhelmed or ineffective
Financial No revenue degradation observed Revenue decline attributable to system
Support Vendor responsive, issues resolved <24 hours Vendor backlog, issues unresolved >48 hours

⚠️ Pause Trigger: If any No-Go criterion is met, pause rollout, conduct root cause analysis, implement fix, and re-evaluate in 1 week.


Rollback Plan

If a Wave Fails

Immediate Actions (Within 24 hours):

☐ Notify Vyne implementation manager
☐ Activate rollback at affected location(s) only
☐ Revert to previous clearinghouse/workflow
☐ Document all claims in-flight through Vyne (ensure none lost)
☐ Communicate to staff: temporary pause, not abandonment

Rollback Does NOT Affect:

  • Successfully deployed locations in prior waves
  • Scheduled locations in future waves (pending root cause analysis)

Root Cause Analysis:

☐ Vyne + internal team joint session within 48 hours
☐ Document issue, impact, root cause, remediation
☐ 🟣 Present findings to VP of Operations / COO
☐ Define criteria to re-attempt at affected location

Re-Attempt Timeline:

  • Minor issue (training gap, config error): Re-attempt in 1–2 weeks
  • Moderate issue (integration bug, process flaw): Re-attempt in 3–4 weeks after fix validated
  • Major issue (fundamental compatibility, vendor limitation): Escalate to executive review, may require contract renegotiation

5. Configuration & Integration (Weeks 2–3)

Practice Management System Integration

Dentrix Integration

Pre-Configuration Steps:

☐ Verify Dentrix version G6.2+
☐ Confirm Dentrix Service Bundles enabled (eServices)
☐ Obtain Dentrix eCentral admin credentials
☐ Back up Dentrix database

🔵 Integration Steps (Vyne Involvement Required):

☐ Install Vyne Connector module
☐ Configure Vyne-Dentrix bridge settings
☐ Map procedure codes to claim formats
☐ Configure provider and location mappings
☐ Enable automatic claim generation from Treatment Complete status
☐ Test: Submit 5 test claims
☐ Validate: Confirm claims appear in Vyne dashboard with correct data

⚠️ Common Issues:

  • Procedure code mismatch: Ensure CDT codes in Dentrix match Vyne's code library. Update any custom codes.
  • Provider NPI not populating: Verify NPI entered correctly in Dentrix provider setup, not just in Vyne.
  • Multi-location database: If using Dentrix Enterprise, ensure location identifiers map correctly.

Eaglesoft Integration

Pre-Configuration Steps:

☐ Verify Eaglesoft version 21.0+
☐ Confirm Eaglesoft API access enabled
☐ Obtain Eaglesoft admin credentials
☐ Back up Eaglesoft database

🔵 Integration Steps:

☐ Install Vyne integration agent
☐ Configure API connection with credentials
☐ Map procedure codes and fee schedules
☐ Configure provider NPI and taxonomy mappings
☐ Set claim generation triggers
☐ Test: Submit 5 test claims
☐ Validate: Confirm data accuracy

⚠️ Common Issues:

  • Fee schedule conflicts: Eaglesoft fee schedules must match Vyne expectations. Run reconciliation report.
  • Slow sync: Large databases may experience slow initial sync. Schedule during off-hours.

Open Dental Integration

Pre-Configuration Steps:

☐ Verify Open Dental version 22.1+
☐ Enable Open Dental API (requires API module purchase if not already enabled)
☐ Generate API key in Open Dental
☐ Back up database

🔵 Integration Steps:

☐ Enter Open Dental API key in Vyne admin portal
☐ Configure endpoint connections
☐ Map provider information
☐ Enable claim push triggers
☐ Test: Submit 5 test claims
☐ Validate: Confirm accuracy

⚠️ Common Issues:

  • API rate limiting: High-volume practices may hit rate limits. Coordinate with Open Dental support for limit increase.
  • Custom fields not transferring: Only standard fields sync. Document custom field workarounds.

Imaging System Integration

Digital Imaging Integration for Attachments

Supported Systems:

  • Dexis (native integration)
  • Schick (native integration)
  • Patterson Imaging (native integration)
  • Apteryx (supported with configuration)
  • Others: Contact Vyne for compatibility

🔵 Configuration Steps:

☐ Identify imaging software and version at each location
☐ Enable imaging export API or TWAIN integration
☐ Configure Vyne to access image storage location
☐ Set up automatic attachment detection (X-rays, periapical, panoramic)
☐ Test: Submit claim with attachment
☐ Validate: Confirm attachment visible to payer

⚠️ Common Issues:

  • Image format incompatibility: Vyne accepts JPEG, PNG, PDF. Some systems export in proprietary formats. Enable conversion.
  • Large file sizes: Panoramic X-rays may exceed size limits. Configure compression settings.

Test Environment Setup

☐ 🔵 Request Vyne sandbox/test environment access
☐ Configure test environment to mirror production settings
☐ Create test patients (use standardized test patient profiles: "Test Patient A," DOB 01/01/1980, etc.)
☐ Submit test claims to each major payer
☐ Test eligibility verification with known active and inactive patients
☐ Test attachment submission with multiple image types
☐ Document test results and resolve issues before production deployment

Validation Checklist:

Test Case Expected Result Pass/Fail
Submit clean claim Claim accepted, status "Pending"
Submit claim with attachment Attachment visible in Vyne, sent to payer
Submit claim with missing info Validation error surfaced before submission
Verify eligibility (active patient) Eligibility confirmed, benefits displayed
Verify eligibility (inactive patient) Eligibility shows inactive/terminated

Data Migration & Historical Data Ingestion

⚠️ Historical data migration is optional but recommended for continuity.

☐ Export outstanding claims from current clearinghouse (open AR)
☐ Export 12 months of claims history for analytics baseline
☐ 🔵 Provide data files to Vyne in specified format (CSV, XML, or EDI)
☐ Vyne imports historical data into dashboard (analytics only, not resubmission)
☐ Validate historical data accuracy in Vyne dashboard

Timeline: Historical data ingestion typically takes 5–10 business days depending on volume.


Security & HIPAA Compliance Verification

Enterprise-Level HIPAA Checklist

☐ 🟣 Executive review and signature of BAA with Vyne
☐ Confirm Vyne SOC 2 Type II compliance (request current report)
☐ Verify data encryption at rest (AES-256) and in transit (TLS 1.2+)
☐ Review Vyne's subprocessor list and data handling practices
☐ Confirm data residency (US-based servers)
☐ Document data retention and deletion policies

Access Control Configuration

☐ Define user roles in Vyne (Admin, Billing Manager, Billing Staff, View-Only)
☐ Configure role-based permissions
☐ Enable SSO integration (eliminates password management risk)
☐ Set session timeout policies (recommend: 15-minute inactivity timeout)
☐ Enable audit logging for all claim submissions and data access
☐ Document access review process (recommend: quarterly access audit)

Data Governance

☐ 🟣 Designate HIPAA Privacy Officer responsible for Vyne data
☐ Document data flow: PMS → Vyne → Payers
☐ Establish breach notification procedures with Vyne
☐ Include Vyne in annual HIPAA risk assessment


Enterprise Configuration Standards

Standardized Configuration Template

These settings MUST be identical across all locations:

Setting Standard Value Rationale
Claim validation rules Enable all pre-submission checks Ensures clean claim rate consistency
Automatic attachment prompts Enabled Reduces attachment request delays
Eligibility verification timing 24 hours before appointment Standardizes verification workflow
Claim status refresh frequency Every 4 hours Balances visibility with system load
Denial alert notifications Email to location billing manager + central team Ensures visibility at both levels
User role definitions Standardized role templates Consistent access controls
Report scheduling Weekly summary, daily exceptions Consistent monitoring cadence

Location-Specific Configuration

These settings MAY vary by location:

Setting Variation Allowed Approval Required
Provider-specific code preferences Yes, within payer guidelines Office manager
Statement mailing schedule Yes, based on local mail timing Office manager
Specialty-specific workflows Yes, for ortho/perio/oral surgery locations Regional manager
Patient payment plan options Yes, within corporate policy Regional manager
Local payer-specific rules Yes, for regional payers Central billing team

Testing Approach: Centralized vs. Per-Location

Recommendation: Hybrid Approach

Phase Approach Rationale
Integration testing Centralized test environment Efficient, one-time effort
PMS-specific testing Per-PMS (not per-location) Same PMS = same config
Location-specific validation Per-location "smoke test" Catches local anomalies

Per-Location Smoke Test (15 minutes):

☐ Log in with location user credentials
☐ Submit one test claim
☐ Run one eligibility verification
☐ Verify location name and provider info displays correctly
☐ Confirm reports show correct location data


6. Team Training Plan

Train-the-Trainer Model

Champion Selection Criteria

Criterion Weight Description
Role suitability Must Billing manager, office manager, or senior billing staff
Tenure Preferred 2+ years at location
Tech comfort Must Comfortable with current systems, learns new software quickly
Peer respect Must Team listens to and trusts this person
Communication skills Must Can explain concepts clearly, patient with questions
Willingness Must Genuinely interested, not voluntold

Champion Responsibilities

☐ Complete champion certification training (4 hours, delivered by Vyne or central team)
☐ Deliver role-specific training to location staff (2–4 hours total)
☐ Serve as first-line support for staff questions during rollout
☐ Escalate unresolved issues to regional manager or central team
☐ Report daily on adoption progress during first week
☐ Conduct 30-day refresher training for any struggling staff

Champion Certification Process

Step Duration Delivered By
🔵 Vyne platform overview 1 hour Vyne trainer
Integration & configuration 30 min Vyne trainer
Workflow walkthrough (claims, eligibility, attachments) 1 hour Vyne trainer
Troubleshooting common issues 30 min Vyne trainer
Training delivery practice 30 min Internal L&D or Vyne
Certification quiz (80% to pass) 30 min Vyne

Standardized Training Materials

Materials to Create Centrally

☐ Role-specific training slide decks (PowerPoint)
☐ Workflow cheat sheets (single-page PDFs)
☐ Short video tutorials (2–5 min each, screen recordings

AI-generated implementation guide based on public vendor information. Verify specifics directly with Vyne Dental.