Most dental and primary care practices with a supported PMS go live on an AI receptionist within seven days of signing. That includes number configuration, PMS integration, script build, staff training, a shadow-mode observation period, and formal go-live. Enterprise deployments (multi-location, custom EHR, DSO-style rollouts) run longer — typically 3–6 weeks — because more stakeholders and more review cycles are involved.
Here's what actually happens on the standard seven-day timeline. Vendors who promise "live in 24 hours" are usually skipping the shadow period, which matters.
Days 0–1: Account Setup and Discovery
- Contract and BAA signed
- Practice profile captured: name, address, hours, providers, services, insurance accepted, key FAQ
- Admin dashboard provisioned
- PMS credentials configured (read-only test first, then full access)
- Discovery call (30–60 min): your team walks through current call volume, common patient requests, scheduling rules, known pain points
Days 2–3: Integration and Script Build
- PMS integration is installed and tested end-to-end (create a test appointment, modify, cancel)
- Scheduling rules imported: provider availability, appointment types, chair/operatory assignments, insurance carrier list
- Scripts drafted: greeting, common Q&A, emergency routing, escalation paths
- SMS templates drafted: appointment confirmations, reminders, follow-ups
- Staff shown a preview and given review access
Day 4: Staff Training and Dry Run
- 30–60 min training session: dashboard walkthrough, how to review AI calls, how to handle escalations
- Dry-run calls: team members call the AI, run through scenarios — booking, rescheduling, insurance question, emergency triage
- Script refinements based on dry-run observations
Days 5–6: Shadow Mode
This step is where quality vendors separate themselves from shortcut shops. Shadow mode means the AI listens to live calls but doesn't speak or act. Your team monitors transcripts in real time and flags anything the AI would have done incorrectly.
Typical shadow-mode findings: the AI might mishear a specific doctor's name, get confused by a regional accent, miss a local landmark patients reference. These get fixed before go-live.
Day 7: Go-Live
- Number forwarding is configured — typically a staged rollout: first overflow/after-hours only, then full 24/7
- Monitoring dashboards active
- Daily check-ins with the vendor for the first week post-launch
What Takes Longer Than Seven Days
- Legacy or custom PMS: add 1–2 weeks for connector work
- Multi-location practices: add 3–5 days per location (though much of the work parallelizes)
- Complex insurance verification setup: add 1 week if you need multi-carrier real-time eligibility
- Number porting: if you want the AI to answer your main number (rather than forward), porting adds 3–10 business days depending on your current carrier
- Enterprise security review: DSOs and large practices often have a 2–4 week procurement review
What You Should Prepare Before Day Zero
To hit the seven-day timeline:
- A written list of your most common FAQ (you can capture this in a 15-minute team standup)
- Current provider schedule policies (who sees new patients when, block scheduling rules)
- List of insurance carriers accepted, out-of-network policy
- Emergency protocol: who the on-call dentist is, how they're reached
- Designated internal owner on your side — not the dentist, not the owner — usually the office manager or lead front-desk person
FAQ
Can we go live in 24–48 hours?
Technically yes, if you skip shadow mode. Don't. The shadow day catches issues that would otherwise surface in real patient calls — mispronunciations, missed local context, scheduling-rule misunderstandings. The cost of rushing through is lower patient satisfaction in the first month.
Who on my team needs to be involved during setup?
An office manager or lead front-desk person (the internal owner) for 2–3 hours total across the week. The dentist/owner usually joins the first and last call. Everyone else gets 30 minutes of training.
What if our PMS isn't on the supported list?
Expect 2–4 extra weeks for a custom connector. Some vendors charge a one-time integration fee; others fold it into the monthly. Ask upfront.
Do we need to stop our existing answering service immediately?
No — run them in parallel during shadow week. Many practices keep their answering service as a backup for the first 30 days, then cancel once confidence builds.
What if go-live doesn't go smoothly?
Good vendors have a rollback plan. Numbers forward back to your existing system within minutes. The shadow day exists precisely to make go-live boring.