Augnito — Implementation Playbook (DSO)

Augnito AI Scribe Implementation Playbook for DSOs

A Strategic Deployment Guide for Dental Support Organizations

---

1. Executive Summary

What Augnito Does

Augnito is an AI-powered clinical documentation solution that converts provider speech into structured clinical notes in real-time, integrating directly with practice management systems to eliminate manual charting and reduce documentation time by up to 75%. The platform uses medical-grade speech recognition with dental-specific vocabulary to capture patient encounters accurately without requiring template navigation or keyboard input.

Why DSOs Specifically Benefit from AI Scribes

Scale Advantages:

• Documentation time savings multiply across 15–50 locations, translating into significant clinical capacity gains (estimated 2-3 additional patient visits per provider per day)
• Centralized quality control ensures consistent clinical documentation standards across all locations
• Aggregate data from standardized notes enables enterprise-level analytics on treatment patterns, provider productivity, and clinical outcomes

Standardization Benefits:

• Uniform note templates and terminology reduce compliance risk and support defensible documentation during audits
• Consistent charting practices simplify provider onboarding when staff transfer between locations
• Standardized workflows reduce training costs and enable meaningful cross-location benchmarking

Data Aggregation Value:

• AI-generated structured data feeds directly into enterprise reporting systems
• Pattern recognition across locations identifies best practices and operational inefficiencies
• Clean, consistent documentation improves insurance claim accuracy and reduces denials at scale

Expected Deployment Timeline

Phase	Timeline	Scope
Pre-Implementation	Weeks 1–2	Enterprise setup, stakeholder alignment, baseline metrics
Wave 1 (Pilot)	Weeks 3–5	2–3 pilot locations
Wave 2	Weeks 6–9	5–8 locations
Wave 3+	Weeks 10–16	Remaining locations
Optimization	Weeks 17–24	Full deployment refinement

Total time from decision to full deployment: 4–6 months for a 25-location DSO, with variability based on IT infrastructure consistency and change management capacity.

---

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

Technical Requirements

Hardware

☐ Verify workstation specifications at each location (minimum: Windows 10/11, 8GB RAM, i5 processor or equivalent) ☐ Assess microphone infrastructure — Augnito works with built-in mics but performs optimally with noise-canceling USB headsets or array microphones ☐ Inventory existing audio equipment; plan procurement if needed (budget: $50–150 per operatory) ☐ Confirm monitor real estate for Augnito overlay window (secondary monitors recommended for high-volume operatories)

Software

☐ Document PMS versions across all locations (Dentrix, Eaglesoft, Open Dental, or others) ☐ Verify browser versions meet requirements (Chrome/Edge recommended) ☐ Confirm operating system patch levels and update schedules ☐ Document any existing dictation or voice-to-text tools that will be retired

Network

☐ Test internet speed at each location (minimum: 10 Mbps upload/download per concurrent user) ☐ Assess network stability — AI scribes require consistent connectivity ☐ Document firewall rules and proxy configurations ☐ Verify HTTPS traffic is not inspected/blocked for Augnito endpoints

Integrations

☐ Confirm API access availability for each PMS instance ☐ Document current integration landscape (imaging, patient communication, insurance verification) ☐ Identify integration conflicts or dependencies

Vendor Onboarding Steps

Step	Action	Owner	Timeline
1	🔵 Execute enterprise MSA and BAA with Augnito	Legal/Compliance	Day 1–3
2	🔵 Complete enterprise onboarding questionnaire	IT Lead	Day 2–4
3	🔵 Schedule technical discovery call with Augnito implementation team	IT Lead + Operations	Day 3–5
4	Establish primary and secondary vendor contacts	Project Manager	Day 5
5	🔵 Confirm support SLA and escalation procedures	Operations	Day 5–7
6	🔵 Obtain enterprise admin credentials and license keys	IT Lead	Day 7–10

Key Contacts to Establish

• Augnito Implementation Manager: Primary vendor contact for deployment
• Augnito Technical Support Lead: Escalation contact for integration issues
• Augnito Customer Success Manager: Ongoing relationship and optimization
• Internal Executive Sponsor: C-suite owner of the initiative
• Internal Project Manager: Day-to-day deployment coordination

Data/Access Prerequisites

☐ Create enterprise administrator account for Augnito platform ☐ Establish SSO integration requirements (SAML 2.0, OAuth 2.0) ☐ 🟣 Determine centralized vs. location-level user provisioning approach ☐ Prepare user roster with roles, locations, and NPI numbers for all providers ☐ Obtain API credentials for each PMS instance ☐ Document imaging system access protocols if Augnito will interface with imaging

Internal Stakeholder Alignment

Who Needs to Be Informed

Stakeholder	Information Needed	Communication Method
Board/Investors	Strategic rationale, ROI projections, timeline	Board deck
C-Suite	Budget, resource requirements, success metrics	Executive briefing
Regional Managers	Rollout timeline, location requirements, their role	Regional leadership meeting
Office Managers	Operational changes, training requirements, go-live dates	All-manager webinar
Providers	Workflow changes, training schedule, benefits	Provider-specific communication
IT Team	Technical requirements, support responsibilities	Technical planning session

Who Needs to Approve

☐ 🟣 CFO: Budget approval for licensing, hardware, implementation services ☐ 🟣 Chief Dental Officer: Clinical workflow approval and provider change management authority ☐ 🟣 VP of Operations: Timeline approval and resource allocation ☐ 🟣 Compliance Officer: HIPAA compliance verification and BAA execution ☐ 🟣 CIO/IT Director: Technical architecture and integration approach

Enterprise-Level Requirements

Network Standards Across Locations

☐ 🟣 Establish minimum network performance standards (bandwidth, latency, uptime) ☐ Document VPN or private network topology if applicable ☐ Determine whether Augnito traffic will route through central infrastructure or direct to cloud ☐ ⚠️ Verify consistent firewall rules can be applied across all locations

Centralized vs. Location-Level Hosting

☐ 🟣 Augnito is cloud-hosted — confirm cloud architecture meets enterprise security requirements ☐ Determine data residency requirements (if any) ☐ Establish enterprise-level data retention policies

SSO and Centralized Credentialing

☐ Confirm identity provider (Azure AD, Okta, etc.) ☐ 🔵 Engage Augnito on SSO integration requirements and timeline ☐ Establish user provisioning workflow (automated vs. manual) ☐ Define role-based access control structure ☐ ⚠️ Plan for SSO failover — providers must be able to work if SSO is temporarily unavailable

Baseline Metrics to Capture

Capture these metrics at EVERY location BEFORE go-live to enable accurate ROI measurement and cross-location comparison.

Metric Category	Specific Metrics	Measurement Method	Frequency
Clinical Efficiency	Average documentation time per encounter	Time study (sample 20 encounters per provider)	Baseline + 30/60/90 days
	Patients seen per provider per day	PMS report	30-day average pre-launch
	Chair time vs. documentation time ratio	Time study	Baseline sample
Documentation Quality	Chart completion rate within 24 hours	PMS audit	30-day average
	Documentation deficiency rate	Chart audit (sample 50 charts per location)	Baseline audit
	Clinical note character/word count	PMS analysis	Sample of 100 notes
Revenue Cycle	Claim denial rate	Billing system report	30-day average
	Average days to claim submission	Billing system report	30-day average
	Coding accuracy rate	Audit sample	Baseline audit
Provider Experience	Documentation satisfaction (1–10 scale)	Provider survey	Pre-launch survey
	Reported burnout indicators	Anonymous survey	Pre-launch survey
	After-hours documentation time	Self-reported	Pre-launch survey
Operational	Staff turnover rate	HR data	Trailing 12 months
	Training hours per new provider	Training records	Historical average

Standardization Protocol for Metric Measurement

☐ 🟣 Establish central team responsible for baseline data collection ☐ Create standardized data collection templates ☐ ⚠️ Ensure all locations use identical measurement methodologies ☐ Set deadline for baseline capture: minimum 2 weeks before any pilot go-live ☐ Store baseline data in centralized repository for later comparison ☐ Document any location-specific anomalies that may affect baseline interpretation

---

3. Location Readiness Assessment

Scoring Framework

Rate each location on the following factors using a 1–5 scale. Sum the scores to produce a composite readiness score (maximum 25 points).

Factor 1: IT Infrastructure Maturity (1–5 points)

Score	Criteria
5	Network consistently >50 Mbps, workstations <2 years old, current PMS version, no integration issues
4	Network >25 Mbps, workstations <3 years old, PMS within 1 version of current, minor integration gaps
3	Network >10 Mbps, workstations <4 years old, PMS within 2 versions, some integration manual workarounds
2	Network inconsistent or <10 Mbps, workstations aging, PMS significantly outdated, known integration problems
1	Network unreliable, hardware requires immediate replacement, unsupported PMS version

Factor 2: Staff Tenure and Adaptability (1–5 points)

Score	Criteria
5	Turnover <10%, team has successfully adopted 2+ new technologies in past year, strong tech comfort
4	Turnover 10–20%, 1 successful tech adoption recently, generally tech-positive attitude
3	Turnover 20–30%, mixed results with past tech changes, some resistance but manageable
2	Turnover 30–40%, history of difficult tech adoptions, significant resistance likely
1	Turnover >40%, failed tech implementations in past, active resistance to change expected

Factor 3: Patient Volume (1–5 points)

Score	Criteria
5	Medium-high volume (25–35 patients/day/provider) — high impact, manageable complexity
4	Medium volume (15–25 patients/day/provider) — solid impact, lower risk
3	High volume (>35 patients/day/provider) — high impact but also higher risk if issues arise
2	Low volume (<15 patients/day/provider) — lower impact, may not justify early prioritization
1	Volume highly variable or location in ramp-up phase — not suitable for early waves

Factor 4: Existing Tech Stack Compatibility (1–5 points)

Score	Criteria
5	PMS with documented Augnito integration, imaging system compatible, no conflicting software
4	PMS supported with standard integration, imaging integration possible, minimal conflicts
3	PMS supported but may require custom work, some integration gaps, workarounds needed
2	PMS integration uncertain, imaging system incompatible, multiple workflow workarounds needed
1	PMS not on Augnito supported list, significant tech stack conflicts, major rework required

Factor 5: Local Champion Availability (1–5 points)

Score	Criteria
5	Tech-forward provider AND office manager, both enthusiastic, track record of leading change
4	Either provider or office manager is strong champion, other is supportive
3	Potential champion identified but not yet developed, general willingness to participate
2	No clear champion, leadership neutral to skeptical, will require significant support
1	No champion, leadership actively resistant or disengaged, significant change management risk

Readiness Assessment Template

Location	IT Infrastructure	Staff Adaptability	Patient Volume	Tech Stack	Local Champion	Total Score	Tier
Location A	_/5	_/5	_/5	_/5	_/5	_/25	_
Location B	_/5	_/5	_/5	_/5	_/5	_/25	_
...

Tier Classification

Score Range	Tier	Rollout Wave Recommendation
21–25	Tier 1: Excellent	Wave 1 pilot candidates
16–20	Tier 2: Good	Wave 2 candidates
11–15	Tier 3: Moderate	Wave 3 candidates with targeted remediation
6–10	Tier 4: Needs Work	Delay until remediation complete; Wave 4+
1–5	Tier 5: Not Ready	Significant intervention required before deployment

Recommended Rollout Sequence Methodology

1. Identify Wave 1 candidates: Select 2–3 locations with scores of 21+ that also represent diversity in:

   • Geographic region
   • Practice type (general, specialty mix)
   • Provider personality types (early adopter + skeptic if possible)

2. Balance risk and representation: Wave 1 should be high-readiness but also generate learnings applicable to the broader portfolio

3. Address Tier 3–5 locations: Create remediation plans with specific milestones; do not schedule these locations until they reach Tier 2 minimum

4. Document exceptions: If a strategic location (e.g., flagship office) scores below Tier 1, it may still be included in Wave 1 with additional support resources

---

4. Rollout Strategy

Recommended Wave Structure

Wave	Locations	Timeline	Purpose
Wave 1: Pilot	2–3 locations	Weeks 3–5	Validate integration, refine training, identify issues
Wave 2: Early Expansion	5–8 locations	Weeks 6–9	Scale learnings, stress-test support model
Wave 3: Broad Deployment	8–15 locations	Weeks 10–14	Parallel deployments, champion network activated
Wave 4+: Completion	Remaining locations	Weeks 15+	Full deployment, remediated locations

Wave 1 Selection Criteria

Must-have characteristics: ☐ Composite readiness score ≥21 ☐ PMS with proven Augnito integration ☐ Network stability documented for 30+ days ☐ Identified and committed local champion (provider or office manager) ☐ Office manager willing to participate in daily check-ins during pilot

Strongly preferred characteristics: ☐ Geographic proximity to central support resources (enables on-site support if needed) ☐ Mix of provider types (GP, specialist, different documentation styles) ☐ Representative of common tech stack configurations in the portfolio ☐ History of successful technology adoption ☐ Patient volume sufficient to generate meaningful usage data (20+ patients/day)

⚠️ Avoid for Wave 1:

• Locations with pending PMS migrations or major IT projects
• Locations with leadership transitions in progress
• Highest-volume locations (too much risk if issues arise)
• Locations with known staff morale or turnover issues

Timeline Per Wave with Buffer

Phase	Wave 1	Wave 2	Wave 3
Pre-wave preparation	5 days	3 days	2 days
Configuration & testing	5 days	3 days	2 days
Training	3 days	2 days	1 day
Soft launch (limited usage)	3 days	2 days	N/A
Full go-live	Day 1	Day 1	Day 1
Intensive support period	5 days	3 days	3 days
Buffer before next wave	7 days	5 days	3 days

Buffer period activities:

• Document lessons learned
• Update training materials based on feedback
• Refine configuration templates
• Assess wave success against go/no-go criteria
• Communicate results to stakeholders

Go/No-Go Criteria

Criteria to advance from Wave 1 to Wave 2:

Criterion	Threshold	Measurement
System uptime	≥99% during pilot period	Augnito dashboard
Provider adoption	≥80% of pilot providers using daily by end of Week 2	Usage logs
Integration stability	Zero critical integration failures	Incident log
Training completion	100% of pilot staff trained	Training tracker
Documentation accuracy	≥90% provider satisfaction with note quality	Provider survey
Support escalation volume	<5 critical tickets per location per week	Support system

🟣 Go/no-go decision owner: VP of Operations with input from Chief Dental Officer and IT Director

⚠️ If criteria not met: Extend Wave 1 by 1–2 weeks, implement corrective actions, reassess

Criteria to Advance from Wave 2 to Wave 3

Criterion	Threshold	Measurement
System uptime	≥99.5% across all Wave 2 locations	Augnito dashboard
Provider adoption	≥85% of providers using daily	Usage logs
Champion readiness	Wave 3 champions trained and certified	Certification tracker
Support capacity	Central team can handle 2x current ticket volume	Capacity model
Workflow stability	No major workflow changes required in past 7 days	Change log

Rollback Plan

Triggers for rollback consideration:

• Critical integration failure affecting patient care

• 25% of providers reporting they cannot complete documentation

• System downtime >4 hours during clinical hours
• Data integrity issues affecting multiple patient records

Rollback procedure:

1. Immediate containment (0–1 hour) ☐ Revert to manual documentation workflow ☐ Notify all affected staff via location champion ☐ Escalate to Augnito support with critical priority ☐ Document all open patient encounters for manual completion

2. Assessment (1–4 hours) ☐ Identify root cause with Augnito support ☐ Determine if issue is location-specific or systemic ☐ Assess impact on other waves

3. Decision (4–24 hours) ☐ 🟣 Executive sponsor decides: pause, rollback, or continue with workaround ☐ If rolling back: disable Augnito access at affected locations ☐ Communicate decision to all stakeholders

4. Recovery (24–72 hours) ☐ 🔵 Work with Augnito on root cause resolution ☐ Develop re-deployment plan with additional safeguards ☐ Update risk register and rollout plan

Isolation principle: Rollback at one location should NOT automatically trigger rollback at other locations unless the issue is systemic.

---

5. Configuration & Integration (Weeks 2–3)

Step-by-Step Integration with Practice Management Systems

Dentrix Integration

Step	Action	Owner	Est. Time
1	🔵 Confirm Dentrix version compatibility with Augnito	IT + Augnito	30 min
2	Enable Dentrix API access (may require Henry Schein support)	IT	1–2 hours
3	🔵 Install Augnito connector application on Dentrix server	Augnito + IT	1 hour
4	Configure API credentials in Augnito admin portal	IT	30 min
5	Map provider profiles between Dentrix and Augnito	IT/Office Manager	1 hour
6	⚠️ Configure clinical note templates to align with Dentrix chart sections	IT + Clinical	2–3 hours
7	Test connection with sample patient encounter	IT + Provider	30 min
8	Verify note appears correctly in patient chart	IT + Provider	30 min

Eaglesoft Integration

Step	Action	Owner	Est. Time
1	🔵 Confirm Eaglesoft version compatibility	IT + Augnito	30 min
2	Enable Patterson technical support access if needed	IT	As needed
3	🔵 Install Augnito connector application	Augnito + IT	1 hour
4	Configure database connection string (Eaglesoft uses SQL Server)	IT	1 hour
5	Map provider and operatory IDs	IT/Office Manager	1 hour
6	⚠️ Configure note output format for Eaglesoft clinical notes	IT + Clinical	2–3 hours
7	Test bidirectional data flow	IT + Provider	1 hour
8	Verify patient demographics pull correctly into Augnito	IT	30 min

Open Dental Integration

Step	Action	Owner	Est. Time
1	🔵 Confirm Open Dental version and API module enabled	IT + Augnito	30 min
2	Generate API key in Open Dental (Program Links → API)	IT	15 min
3	Enter API key and endpoint in Augnito admin portal	IT	15 min
4	🔵 Configure FHIR or proprietary API connection	Augnito + IT	1–2 hours
5	Map provider IDs and procedure codes	IT	1 hour
6	Configure note template to populate clinical note module	IT + Clinical	2 hours
7	Test with sample encounters across procedure types	IT + Provider	1 hour
8	Verify procedure codes populate correctly	IT + Billing	30 min

Step-by-Step Integration with Imaging Systems

Note: Augnito's primary function is clinical documentation, not imaging. Integration with imaging systems typically involves pulling imaging metadata or allowing voice commands to reference images.

Step	Action	Owner	Est. Time
1	Document current imaging workflow and software (Dexis, Schick, etc.)	IT	1 hour
2	🔵 Confirm Augnito imaging integration capabilities for your system	Augnito	30 min
3	If supported: Configure imaging server connection	IT	1–2 hours
4	Test voice-activated image reference in clinical notes	Provider	30 min
5	If not supported: Document manual workflow for referencing images	Clinical	30 min

Test Environment Setup and Validation

☐ 🔵 Request Augnito sandbox/test environment credentials ☐ Create test patient records (do not use real PHI in testing) ☐ Assign test provider accounts to IT staff for configuration testing ☐ Develop test script covering common clinical scenarios:

• New patient exam with findings
• Hygiene visit with periodontal documentation
• Restorative procedure documentation
• Emergency visit documentation
• Treatment plan dictation

Validation Checklist: ☐ Audio capture functions correctly (test in each operatory environment) ☐ Speech-to-text accuracy meets provider expectations (>95% accuracy) ☐ Clinical terminology recognized correctly ☐ Notes populate correct patient chart ☐ Notes populate correct sections of clinical record ☐ Provider can edit AI-generated text before finalizing ☐ Notes save correctly and are visible in PMS ☐ Multiple providers can use system simultaneously without conflict ☐ ⚠️ System recovers gracefully from network interruption

Data Migration / Historical Data Ingestion

Augnito is primarily forward-looking; historical note migration is typically not required. However:

☐ 🔵 Confirm with Augnito whether historical note ingestion is available/recommended ☐ If migrating templates: Export existing note templates from PMS ☐ 🔵 Work with Augnito to configure template equivalents ☐ ⚠️ Do NOT migrate historical patient notes unless specifically required — focus on forward documentation

Security and HIPAA Compliance Verification

Enterprise-Level HIPAA Checklist

Requirement	Verification	Owner	Status
Business Associate Agreement	BAA executed with Augnito covering all locations	Legal	☐
Data encryption in transit	Confirm TLS 1.2+ for all data transmission	IT + Augnito	☐
Data encryption at rest	Confirm AES-256 encryption for stored data	Augnito	☐
Access controls	Role-based access configured; minimum necessary standard	IT	☐
Audit logging	User access and actions logged and retained 6+ years	Augnito	☐
Unique user identification	Each user has unique credentials; no shared accounts	IT	☐
Automatic logoff	Session timeout configured per policy	IT	☐
Workforce training	Staff trained on Augnito-specific HIPAA considerations	Compliance	☐
Incident response	Augnito breach notification procedures documented	Compliance	☐
Data governance	Data ownership, retention, and deletion policies established	🟣 Compliance	☐
Subcontractor review	Augnito's subcontractors reviewed for compliance	Legal/Compliance	☐

Standardized Configuration Template

The following settings should be IDENTICAL across all locations:

Setting	Standard Configuration	Rationale
Note template structure	Enterprise-approved template set	Consistency, compliance, analytics
Terminology/vocabulary	Enterprise dental term library	Documentation standardization
Auto-punctuation settings	Enabled	Consistent note formatting
Clinical abbreviation expansion	Enterprise-approved list	Clarity and compliance
Signature/attestation format	Standard attestation language	Legal consistency
Session timeout	15 minutes (or per enterprise policy)	HIPAA compliance
Audit log retention	Minimum 6 years	Compliance requirement
Export format	Match PMS import requirements	Integration consistency

Location-Specific Configuration

The following settings CAN/SHOULD vary by location:

Setting	Variation Allowed	Decision Owner
Provider voice profiles	Each provider creates their own	Provider
Specialty-specific templates	Configured per location specialty mix	Regional Manager + Clinical
Microphone sensitivity	Adjusted per operatory acoustics	Local IT/Champion
Custom vocabulary (provider-specific)	Provider can add personal terms	Provider
Workflow preferences	When/how notes are reviewed and signed	Office Manager
Operatory assignment	Mapped per location floor plan	Office Manager

Centralized Test Environment Approach

Recommended: Establish a single centralized test environment for configuration development, with per-location validation testing before go-live.

☐ Create central test environment mirroring production architecture ☐ Develop and validate configurations centrally before pushing to locations ☐ ⚠️ Each location conducts abbreviated validation testing before go-live (1–2 hours) ☐ Document any location-specific deviations for troubleshooting reference

---

6. Team Training Plan

Train-the-Trainer Model

Core principle: Identify and certify 1 champion per location who delivers training to their team. This scales efficiently and creates local ownership.

Champion Selection Criteria

Criterion	Weight	Assessment Method
Technology comfort	High	Self-assessment + manager input
Respected by peers	High	Manager input
Communication skills	High	Observation
Willingness to participate	Critical	Direct conversation
Schedule availability	Medium	Manager confirmation
Experience with prior tech rollouts	Medium	HR/training records

Ideal champion profiles:

• Office manager with strong tech skills
• Lead hygienist or dental assistant with training background
• Associate dentist enthusiastic about efficiency tools

Champion Responsibilities

1. Complete central certification training (4–6 hours)
2. Conduct role-specific training for all staff at their location
3. Serve as first-line support during go-live and first 30 days
4. Participate in weekly champion calls during rollout
5. Communicate issues to regional/central team
6. Track training completion for their location
7. Collect and relay staff feedback

Champion Certification Process

Phase	Content	Duration	Format
1: Platform Mastery	Deep dive on Augnito functionality, configuration, troubleshooting	3 hours	🔵 Live virtual training
2: Training Delivery	How to train each role, addressing resistance, adult learning principles	1.5 hours	Virtual training
3: Support Protocols	Escalation paths, documentation, daily check-in requirements	1 hour	Virtual training
4: Certification	Knowledge assessment + mock training delivery	30 min	Assessment

Standardized Training Materials

Create centrally:

• Training slide deck per role
• Video demonstrations (embed Augnito screen recordings)
• Day 1 cheat sheets (see below)
• FAQ document
• Troubleshooting guide
• Training completion tracker template

Champions customize locally:

• Location-specific workflow examples
• Provider-specific voice profile setup
• Operatory-specific microphone instructions

Role-Specific Training Outlines

---

**Dentists/Providers**

Estimated training time: 60–90 minutes

Recommended format: Live demonstration + hands-on practice with shadow support

Training content:

1. Why Augnito: Time savings, reduced after-hours documentation, better note quality
2. Workflow change overview: Voice-first documentation during/after patient encounter
3. Starting a session: Opening Augnito, selecting patient, positioning microphone
4. Dictation best practices: Pace, enunciation, clinical terminology
5. Reviewing AI output: Reading transcription, making edits, confirming accuracy
6. Finalizing notes: Signing off, pushing to PMS
7. Special scenarios: Complex procedures, multiple findings, treatment planning
8. When to override: Recognizing AI errors, manual corrections
9. Voice commands: Shortcuts for navigation and editing
10. Troubleshooting: Audio issues, connectivity, escalation

Common resistance points and responses:

Resistance	Response
"I type faster than I talk"	"Once trained, most providers find dictation 2–3x faster. Let's try for one week and measure."
"The AI won't understand dental terms"	"Augnito is trained on medical/dental vocabulary. Let's test it with your common terms."
"I don't want to change my workflow"	"We'll customize the workflow