Asprodental
Step-by-step implementation guide β pre-implementation checklist, onboarding, staff training, go-live runbook, and ROI tracking.
Asprodental β Implementation Playbook (DSO)
Asprodental Implementation Playbook
Practice Management AI for Dental Support Organizations
1. Executive Summary
What Asprodental Does
Asprodental is an AI-powered practice management platform that automates front-office operations including intelligent scheduling optimization, automated patient communications, real-time insurance verification, and predictive analytics for production forecasting. The system learns from practice patterns to reduce no-shows, maximize chair utilization, and streamline administrative workflows across multi-location dental organizations.
Why DSOs Specifically Benefit
Practice management AI delivers exponential value at scale. Where a single practice might save 10 hours per week on scheduling and verification tasks, a 30-location DSO captures 300+ hours weeklyβtranslating to significant labor cost reduction without proportional implementation complexity. More critically, Asprodental enables operational standardization across your portfolio: consistent patient communication protocols, unified scheduling logic, and centralized analytics that reveal performance variations between locations you'd never detect manually. The aggregated data across all locations also trains the AI more effectively, improving prediction accuracy for no-shows, treatment acceptance, and production forecasting in ways impossible for standalone practices.
Expected Timeline
| Phase | Duration | Milestone |
|---|---|---|
| Decision to Contract | 2β3 weeks | BAA signed, SOW finalized |
| Pre-Implementation | 2 weeks | Technical readiness, baseline metrics captured |
| Pilot Wave (2β3 locations) | 4 weeks | Validated deployment, refined playbook |
| Scaled Rollout | 8β12 weeks | All locations live |
| Optimization | Ongoing | Quarterly reviews, continuous improvement |
Total timeline from decision to full deployment: 16β20 weeks for a 30-location DSO. Organizations with mature IT infrastructure and strong change management capabilities may compress this by 3β4 weeks.
2. Pre-Implementation Checklist (Weeks 1β2)
Technical Requirements
Hardware (Per Location)
β Workstations: Windows 10/11 or macOS 12+, minimum 8GB RAM, SSD storage β Network: Minimum 50 Mbps download/10 Mbps upload per location (100/20 recommended for locations with 8+ operatories) β Displays: 1920x1080 minimum resolution for dashboard visibility
Software
β Practice Management System: Compatible versions confirmed (see Section 5) β Browser: Chrome 90+ or Edge 90+ (Firefox supported but not recommended) β Imaging software: Confirm integration pathway with vendor π΅
Network
β Static IP or reliable DHCP with MAC address reservation β Firewall rules: Whitelist Asprodental domains (vendor provides list) π΅ β VPN compatibility confirmed if centralized hosting model selected
Vendor Onboarding Steps
| Step | Owner | Timeline | Vendor Contact |
|---|---|---|---|
| β Execute Master Services Agreement | Legal/C-Suite | Day 1β3 | Enterprise Sales Rep |
| β Sign Business Associate Agreement | Compliance | Day 1β3 | Legal Team π΅ |
| β Complete enterprise security questionnaire | IT/Compliance | Day 3β5 | Security Team π΅ |
| β Schedule kickoff call | Operations | Day 5 | Customer Success Manager π΅ |
| β Confirm implementation project manager | Both parties | Day 5β7 | π΅ |
| β Establish Slack/Teams channel for implementation | IT | Day 7 | π΅ |
Key Vendor Contacts to Establish:
- Enterprise Customer Success Manager (primary contact)
- Technical Implementation Specialist
- Integration Engineer (for PMS connectivity)
- Support escalation path (Tier 1 β Tier 2 β Engineering)
Data/Access Prerequisites
β Admin credentials for all PMS instances across locations β API keys generated for PMS integration (see vendor documentation) π΅ β Read access to 24+ months of historical appointment data β Patient contact database export capability confirmed β Insurance verification portal credentials (if separate from PMS) β Phone system admin access (for SMS/call integration) β Email domain DNS access (for DKIM/SPF configuration)
Internal Stakeholder Alignment
Stakeholder Alignment Map π£
| Stakeholder | Role in Implementation | Communication Cadence | Approval Required For |
|---|---|---|---|
| Board/Investors | Informed of strategic initiative, ROI expectations | Quarterly update, major milestone alerts | Budget approval, vendor selection |
| CEO/COO | Executive sponsor, removes blockers | Weekly during pilot, bi-weekly during rollout | Go/no-go decisions between waves |
| Chief Dental Officer | Clinical workflow validation | Weekly | Clinical workflow changes, AI interpretation protocols |
| VP of Operations | Implementation owner, day-to-day decisions | Daily during active waves | Rollout sequence, resource allocation |
| CTO/IT Director | Technical architecture, security | Daily during integration, weekly during rollout | Security protocols, infrastructure decisions |
| Regional Managers | Cascade to locations, monitor adoption | Bi-weekly briefings, daily during their region's wave | Location-level staffing for training |
| Office Managers | Local implementation lead | Daily during their location's go-live week | Local champion nomination |
| Providers | End users, clinical validation | Training sessions, feedback loops | None (but engagement critical) |
| HR/Training | Training logistics, compliance tracking | Weekly | Training schedule, completion verification |
β οΈ Common Failure Point: Skipping regional manager buy-in. If regional managers view this as "another corporate mandate," they'll undermine adoption passively. Invest time in their briefingsβshow them how this reduces their daily firefighting.
Baseline Metrics to Capture
Critical: Standardize measurement methodology across all locations BEFORE implementation. Inconsistent definitions make ROI measurement impossible.
| Metric | Standard Definition | Capture Method | Target Source |
|---|---|---|---|
| β Chair utilization rate | Scheduled production hours Γ· Available chair hours | PMS report | Last 12 months, monthly |
| β No-show rate | No-show appointments Γ· Total scheduled appointments | PMS report | Last 12 months, monthly |
| β Same-day cancellation rate | Cancellations within 24 hours Γ· Total scheduled | PMS report | Last 12 months, monthly |
| β Time to schedule (new patient) | Days from initial inquiry to first appointment | Manual audit or CRM | Sample 50 patients/location |
| β Insurance verification time | Minutes from appointment creation to verification complete | Time study | Sample 20 appointments/location |
| β Front desk FTE hours | Total weekly hours worked by scheduling/admin staff | Payroll/HR system | Last 3 months average |
| β Patient response rate | % of outreach (confirmation, recall) that receives response | Current system data | Last 6 months |
| β Production per provider hour | Collections Γ· Provider clinical hours | PMS + Payroll | Last 12 months, monthly |
| β Recall effectiveness | % of due recall patients who schedule within 30 days | PMS report | Last 12 months |
π£ Executive Decision Required: Confirm budget authority for cross-location data analyst or BI resource to compile baseline metrics consistently.
Enterprise-Level Requirements
Hosting Decision π£
| Model | Pros | Cons | Recommended For |
|---|---|---|---|
| Centralized Cloud (Vendor-Hosted) | Simpler management, automatic updates, lower IT burden | Dependency on vendor uptime, less customization | Most DSOs, especially those without robust IT teams |
| Hybrid (Centralized management, local processing) | Better performance for high-volume locations, some data locality | More complex, higher IT involvement | DSOs with 40+ locations or strict data residency needs |
Recommendation: Start with vendor-hosted cloud for pilot wave. Evaluate hybrid only if latency issues emerge in high-volume locations.
Network Standards Across Locations
β Minimum bandwidth requirements documented and verified per location β Network segmentation policy: Asprodental traffic isolated from general office WiFi β Backup internet solution identified for critical locations (cellular failover recommended for locations with 6+ operatories) β Standard firewall rules documented for IT to apply uniformly
Enterprise Authentication
β SSO integration scoped (SAML 2.0 or OAuth 2.0 supported) π΅ β Determine SSO provider (Okta, Azure AD, Google Workspace) β Role-based access control matrix defined:
- Corporate Admin: All locations, all functions
- Regional Manager: Assigned region, limited admin functions
- Office Manager: Single location, operational functions
- Provider: Single location, clinical dashboard only
- Front Desk: Single location, scheduling/communication functions
β Centralized credentialing process documented for new employee onboarding β Termination workflow documented for access revocation
β οΈ Common Failure Point: Delaying SSO integration until post-launch. Retro-fitting SSO creates credential chaos and security gaps. Insist on SSO from Wave 1.
3. Location Readiness Assessment
Scoring Framework
Rate each location on the following factors using a 1β5 scale. This assessment should be completed by regional managers with IT input.
Factor 1: IT Infrastructure Maturity (Weight: 25%)
| Score | Network Speed | Hardware Age | PMS Version | Evidence |
|---|---|---|---|---|
| 5 | 100+ Mbps | < 2 years | Current | Speed test results, asset inventory |
| 4 | 75β99 Mbps | 2β3 years | Current-1 | |
| 3 | 50β74 Mbps | 3β4 years | Current-2 | Minimum viable |
| 2 | 25β49 Mbps | 4β5 years | Current-3 | Upgrades needed |
| 1 | < 25 Mbps | 5+ years | Unsupported | Not ready |
Factor 2: Staff Tenure and Adaptability (Weight: 20%)
| Score | Turnover Rate (Annual) | Tech Comfort | Recent Tech Training | Evidence |
|---|---|---|---|---|
| 5 | < 15% | High | Yes, within 6 months | HR data, survey results |
| 4 | 15β25% | Medium-High | Yes, within 12 months | |
| 3 | 26β35% | Medium | Some experience | |
| 2 | 36β50% | Low-Medium | Limited | |
| 1 | > 50% | Low | None | High risk |
Factor 3: Patient Volume (Weight: 15%)
| Score | Daily Patients | Interpretation |
|---|---|---|
| 5 | 50β80 | High impact, manageable complexity |
| 4 | 35β49 | Good volume, lower risk |
| 3 | 80β100 | High volume, moderate risk |
| 2 | 20β34 | Lower impact, may not justify priority |
| 1 | > 100 or < 20 | Extreme volume = high risk; low volume = low priority |
Factor 4: Tech Stack Compatibility (Weight: 25%)
| Score | PMS | Imaging System | Other Integrations | Evidence |
|---|---|---|---|---|
| 5 | Tier 1 (Dentrix, Eaglesoft, Open Dental) | Certified integration available | All standard | Vendor compatibility list |
| 4 | Tier 1 | Integration available, not certified | Most standard | |
| 3 | Tier 2 (Dentrix Ascend, Curve, etc.) | Custom integration required | Some custom | |
| 2 | Legacy/Unsupported | Limited integration | Multiple custom | |
| 1 | Proprietary/Unknown | No integration path | Incompatible | Not ready |
Factor 5: Local Champion Availability (Weight: 15%)
| Score | Champion Profile | Evidence |
|---|---|---|
| 5 | Tech-forward Office Manager + engaged lead provider | Named individual, expressed interest |
| 4 | Strong Office Manager OR engaged provider | One reliable champion |
| 3 | Office Manager willing but not enthusiastic | Cooperation expected |
| 2 | No clear champion, passive management | Will require external support |
| 1 | Active resistance from management or providers | Address before proceeding |
Scoring Worksheet
| Location | IT (Γ0.25) | Staff (Γ0.20) | Volume (Γ0.15) | Compatibility (Γ0.25) | Champion (Γ0.15) | Composite Score |
|---|---|---|---|---|---|---|
| Location A | 4 (1.0) | 5 (1.0) | 4 (0.6) | 5 (1.25) | 5 (0.75) | 4.60 |
| Location B | 3 (0.75) | 4 (0.8) | 3 (0.45) | 4 (1.0) | 4 (0.6) | 3.60 |
| Location C | 2 (0.5) | 2 (0.4) | 5 (0.75) | 3 (0.75) | 2 (0.3) | 2.70 |
Rollout Sequence Recommendations
| Composite Score | Recommendation | Wave Assignment |
|---|---|---|
| 4.0β5.0 | Ideal pilot candidate | Wave 1 |
| 3.5β3.9 | Strong rollout candidate | Wave 2 |
| 3.0β3.4 | Standard rollout | Wave 2β3 |
| 2.5β2.9 | Requires remediation before rollout | Wave 3 (with interventions) |
| < 2.5 | Not readyβaddress blockers first | Hold for Wave 4 or exclusion |
π£ Executive Decision Required: Approve final wave assignments and any locations requiring capital investment (hardware, network upgrades) before proceeding.
4. Rollout Strategy
Wave Structure
Recommended Wave Approach
| Wave | Locations | Duration | Purpose |
|---|---|---|---|
| Wave 1 (Pilot) | 2β3 locations | 4 weeks | Validate deployment, refine playbook, build internal expertise |
| Wave 2 | 5β8 locations | 3 weeks | Scale learnings, stress-test support model |
| Wave 3 | 10β15 locations | 3 weeks | Full operational scale |
| Wave 4 | Remaining locations | 3β4 weeks | Complete deployment, address remediated locations |
Buffer Between Waves: Minimum 1 week between waves for:
- Retrospective and playbook updates
- Champion debrief sessions
- Support queue clearance
- Go/no-go assessment
Wave 1 Pilot Selection Criteria π£
Select 2β3 locations that are:
β High readiness (score 4.0+) β Sets up for success, builds confidence β Representative of portfolio diversity β Include one urban/suburban, one smaller market if applicable β Geographically accessible β At least one within easy travel distance for central team site visits β Different PMS if portfolio is mixed β Validate integration across your PMS variants β Strong local champion identified β Named Office Manager and/or provider who will co-own the pilot β Not your highest-volume locations β Manageable risk if issues arise
β οΈ Common Failure Point: Choosing only your "flagship" locations for pilot. If something goes wrong, the reputational damage internally is severe. Pick locations that are representative but recoverable.
Timeline Per Wave
Wave 1 (Pilot): 4 Weeks
- Week 1: Configuration, integration, training
- Week 2: Soft launch (limited patient-facing features)
- Week 3: Full launch, intensive support
- Week 4: Stabilization, metrics capture, retrospective
Waves 2β4: 3 Weeks Each
- Week 1: Configuration, training (champion-led with central support)
- Week 2: Go-live, intensive support
- Week 3: Stabilization, handoff to standard support
Go/No-Go Criteria Between Waves π£
| Criteria | Measurement | Threshold to Advance |
|---|---|---|
| System uptime | Asprodental dashboard | > 99% during business hours |
| Integration success rate | Failed syncs Γ· Total syncs | < 1% failure rate |
| Staff adoption | Active daily users Γ· Expected users | > 85% |
| Patient communication delivery | Sent Γ· Attempted | > 95% delivery rate |
| Support ticket resolution | Tickets resolved within SLA | > 90% |
| No critical workflow disruptions | Incident reports | Zero Category 1 incidents |
| Champion confidence | Champion survey | Average 4+ out of 5 |
β οΈ Mandatory: Do not proceed to next wave if ANY of the following occur:
- Critical integration failure affecting appointments or patient data
- Security incident or potential HIPAA breach
- Champion resignation or withdrawal from role
- Provider revolt (3+ providers refusing to use system at single location)
Rollback Plan
If a wave fails go/no-go criteria:
Immediate (Within 24 Hours): β Pause all scheduled go-lives for next wave β Notify all stakeholders of pause (template below) β Activate incident response team (IT lead, vendor contact, VP Ops)
Assessment (Days 2β5): β Root cause analysis with vendor π΅ β Document all failure points and contributing factors β Determine if issue is systemic or location-specific β Assess remediation timeline
Decision Tree:
Is the issue location-specific?
βββ YES β Continue wave, exclude affected location, remediate separately
βββ NO β Is remediation < 2 weeks?
βββ YES β Pause, remediate, resume with extended buffer
βββ NO β Executive escalation for project replanning π£
Rollback Execution (If Needed): β Revert to previous workflows (document current state first) β Disable patient-facing AI communications β Revert scheduling to manual/PMS-only mode β Preserve all data and logs for analysis β Communicate to staff: "We're pausing to get this right, not abandoning"
Isolation Protocol: A rollback at one location does NOT automatically trigger rollback at successfully-deployed locations. Isolate failures to prevent organizational panic.
5. Configuration & Integration (Weeks 2β3)
Practice Management System Integrations
Dentrix (G6/G7)
Timeline: 3β5 business days π΅
β Step 1: Enable Dentrix API access via Office Manager module (Settings β API Integration) β Step 2: Generate API credentials (record securely in password manager) β Step 3: Provide credentials to Asprodental implementation team via secure portal π΅ β Step 4: Asprodental configures webhook endpoints π΅ β Step 5: Test connection: Verify bi-directional sync of appointments β Step 6: Validate patient demographics sync (name, DOB, contact info) β Step 7: Test insurance information pull β Step 8: Verify appointment status updates flow correctly
β οΈ Known Issue: Dentrix G6 versions prior to 16.5 have intermittent webhook failures. Confirm version and update if needed.
Eaglesoft (21+)
Timeline: 2β4 business days π΅
β Step 1: Access Eaglesoft Practice Manager β Tools β System Integrations β Step 2: Enable Patterson API module (may require Patterson support call) β οΈ β Step 3: Create service account for Asprodental (do not use individual user credentials) β Step 4: Share credentials via secure method with Asprodental π΅ β Step 5: Test read access to schedule, patients, insurance β Step 6: Test write-back of appointment confirmations β Step 7: Verify operatory mapping between systems
β οΈ Known Issue: Eaglesoft Patterson API activation can take 24β48 hours. Do not schedule testing until confirmation received.
Open Dental (20.1+)
Timeline: 1β3 business days π΅
β Step 1: Setup β Advanced Setup β API/Third Party β Step 2: Enable API access, generate API key β Step 3: Set appropriate permissions (read appointments, patients, insurance; write appointment status) β Step 4: Provide API key and practice database URL to Asprodental π΅ β Step 5: Asprodental configures integration π΅ β Step 6: Test full data sync β Step 7: Verify recall list integration
Open Dental Advantage: Most straightforward integration. If piloting with mixed PMS portfolio, prioritize Open Dental locations for Wave 1.
Imaging System Integration
If your imaging system will integrate with Asprodental for enhanced scheduling workflows (e.g., flagging patients with pending imaging):
β Confirm imaging system model and version with vendor compatibility list π΅ β Establish DICOM gateway requirements (if applicable) β Test imaging archive query from Asprodental β Validate patient matching between imaging and PMS
Note: Full imaging integration is optional for core practice management features. Prioritize PMS integration first.
Test Environment Setup
Centralized Test Environment (Recommended)
β Asprodental provisions sandbox environment with sample data π΅ β Configure SSO for test environment (separate from production) β Create test users for each role type β Establish test location with synthetic patient data β Document test environment URL and credentials
Validation Checklist
| Test | Steps | Expected Result | Pass/Fail |
|---|---|---|---|
| β Patient sync | Create patient in PMS, verify in Asprodental | Patient appears within 5 minutes | |
| β Appointment sync | Create appointment in PMS | Appointment appears in Asprodental | |
| β Bi-directional status | Confirm appointment in Asprodental | Status updates in PMS | |
| β Insurance verification | Trigger verification for test patient | Verification completes, results visible | |
| β Patient communication | Send test confirmation | SMS/email delivered to test number | |
| β Recall campaign | Generate recall list, send test batch | Communications delivered correctly | |
| β Reporting | Generate daily production forecast | Report generates with accurate data | |
| β User permissions | Test each role's access restrictions | Users see only permitted functions |
Data Migration / Historical Ingestion
β Determine historical data scope (recommendation: 24 months minimum for AI training) β Export historical appointment data from PMS β Export historical patient communication logs (if available) β Asprodental ingests historical data π΅ β Validate AI predictions against known historical patterns β Flag any data quality issues (missing fields, duplicates)
β οΈ Common Failure Point: Garbage in, garbage out. If historical data is incomplete or inconsistent, AI predictions will be unreliable. Spend time on data cleanup before ingestion.
Security and HIPAA Compliance Verification
Enterprise-Level HIPAA Checklist
| Requirement | Evidence | Owner | Verified |
|---|---|---|---|
| β BAA executed | Signed agreement | Legal | |
| β SOC 2 Type II report current | Vendor provides | Compliance π΅ | |
| β Data encryption at rest | Vendor attestation | IT π΅ | |
| β Data encryption in transit | TLS 1.3 confirmed | IT | |
| β Access logging enabled | Audit log sample reviewed | Compliance | |
| β PHI retention policy aligned | Policy comparison | Legal | |
| β Incident response plan reviewed | Vendor provides | Compliance π΅ | |
| β Minimum necessary access | RBAC configuration verified | IT | |
| β Employee training verification | Vendor provides | HR π΅ | |
| β Subcontractor agreements | Vendor provides list | Legal π΅ |
Standardized vs. Location-Specific Configuration
Standardize Centrally
| Setting | Standard Configuration | Rationale |
|---|---|---|
| Appointment confirmation timing | 48 hours, 24 hours, 2 hours before | Consistent patient experience |
| Communication templates | Corporate-approved messaging | Brand consistency, compliance |
| No-show policy messaging | Standard language | Legal consistency |
| Insurance verification triggers | Automatic at scheduling, 3 days before | Operational efficiency |
| Recall intervals | Per ADA guidelines | Clinical standards |
| Data retention | 7 years | Compliance |
| User role definitions | Standard RBAC matrix | Security |
| Reporting cadence | Daily, weekly, monthly standard reports | Comparability |
Allow Local Discretion
| Setting | Customization Allowed | Guardrails |
|---|---|---|
| Provider schedule templates | Match provider preferences | Must use standard time blocks |
| Operatory naming | Local convention | Must map to standard types |
| Communication "from" name | Local practice name | Must be accurate |
| Recall messaging tone | Slight localization | Must use approved template base |
| Holiday schedules | Local market | Must update 30 days ahead |
| Specialty-specific workflows | If applicable | Must not conflict with core logic |
6. Team Training Plan
Train-the-Trainer Model
Champion Selection Criteria π£
Each location requires ONE certified champion (Office Manager strongly preferred) and ONE backup champion (clinical lead or senior front desk).
| Criteria | Minimum Requirement |
|---|---|
| Tenure at location | 1+ year |
| Role | Office Manager, lead provider, or senior front desk |
| Tech comfort | Demonstrates proficiency with current PMS |
| Influence | Respected by clinical and admin staff |
| Availability | Can dedicate 4+ hours for initial training, 2 hours/week ongoing |
| Communication skills | Can explain concepts clearly, addresses questions patiently |
| Commitment | Expressed willingness (do not voluntell) |
Champion Responsibilities
- Complete certified champion training (6 hours total) π΅
- Deliver role-specific training to all location staff
- Serve as first point of contact for location questions
- Participate in daily check-ins during go-live week
- Escalate issues beyond their scope to regional manager
- Collect and submit staff feedback
- Train new hires on Asprodental within 2 weeks of start
Champion Certification Process π΅
Format: Virtual live training with vendor (2 sessions Γ 3 hours)
Session 1: Technical Foundation
- System architecture and data flow
- Integration troubleshooting basics
- Configuration options and when to escalate
- Admin functions and user management
Session 2: Training Delivery
- Adult learning principles for peer training
- Role-specific workflow walkthroughs
- Handling resistance and questions
- Day 1 cheat sheet usage
- Certification quiz (80% pass required)
Standardized Training Materials
Centrally Created: β Role-specific slide decks (provided by vendor, customized by DSO) π΅ β Day 1 cheat sheets (one per role) β Video library for self-service reference π΅ β FAQ document (updated after each wave) β Troubleshooting decision tree
Champion Customizes: β Local examples and workflow specifics β Provider schedule nuances β Location-specific terminology β Patient population context
Role-Specific Training Outlines
Dentists/Providers
Training Time: 45 minutes initial + 15 minutes follow-up after Week 1
Format: Champion-led demo with hands-on practice; video backup available
Content:
- What changed and why (executive summary of benefits)
- Dashboard overview: Your daily view
- AI-predicted no-shows: How to interpret, what actions to take
- Production forecasts: Daily, weekly, monthly views
- Schedule optimization suggestions: Accept/decline workflow
- Patient communication history: Seeing what patients received
- When the AI is wrong: Override and feedback process
- Mobile access (if applicable)
Common Resistance Points:
- "I don't trust AI predictions" β Show accuracy data from pilot; emphasize it's a tool, not a replacement for judgment
- "This adds to my workload" β Demo how it REDUCES interruptions from front desk
- "My schedule preferences won't be respected" β Show local customization options
Day 1 Cheat Sheet: Providers
βββββββββββββββββββββββββββββββββββββββββββββββββββ
β ASPRODENTAL QUICK REFERENCE - PROVIDERS β
βββββββββββββββββββββββββββββββββββββββββββββββββββ€
β LOG IN: [SSO URL] β Use your network credentialsβ
β β
β DAILY VIEW: Dashboard β Today's Schedule β
β β
β β οΈ FLAG ICONS: β
β π΄ High no-show risk (>50%) β
β π‘ Moderate no-show risk (25-50%) β
β π΅ Insurance issue flagged β
β β
β TO OVERRIDE AI SUGGESTION: β
β Click suggestion β "Dismiss" β Select reason β
β β
β NEED HELP? β Ask [Champion Name] or click ? iconβ
βββββββββββββββββββββββββββββββββββββββββββββββββββ
Hygienists
Training Time: 30 minutes initial
Format: Champion-led overview (can combine with front desk training)
Content:
- What changed in patient communication (so you can answer questions)
- Accessing patient communication history
- Flagged patients: What the icons mean
- Recall campaigns: How patients are being contacted
- Your role is unchangedβthis is mostly front-office impact
Common Resistance Points:
- "Patients are getting too many messages" β Show communication frequency limits; provide feedback channel
- "I need to see what patients were told" β Demo patient history view
Day 1 Cheat Sheet: Hygienists
βββββββββββββββββββββββββββββββββββββββββββββββββββ
β ASPRODENTAL QUICK REFERENCE - HYGIENISTS β
βββββββββββββββββββββββββββββββββββββββββββββββββββ€
β WHAT THIS IS: AI helping front desk with β
β scheduling, confirmations, and recalls β
β β
β IF PATIENT ASKS ABOUT TEXTS/EMAILS: β
β "We've upgraded our reminder system to better β
β keep you informed about your appointments." β
β β
β TO SEE WHAT PATIENT RECEIVED: β
β PMS patient record β Communication History β
β β
β NOTICE SOMETHING WRONG? β Tell [Champion Name] β
βββββββββββββββββββββββββββββββββββββββββββββββββββ
Front Desk / Office Manager
Training Time: 90 minutes initial + 30 minutes advanced features
Format: Champion-led hands-on workshop (maximum 4 staff per session)
Content:
- System overview and login
- Dashboard navigation and daily tasks
- Scheduling workflow changes: AI suggestions, accepting/modifying
- Patient communication management: Templates, manual sends, opt-outs
- Confirmation tracking: Who
AI-generated implementation guide based on public vendor information. Verify specifics directly with Asprodental.