TL;DR
Before changing dental agencies, rehearse where every appointment inquiry will go. Map public phone numbers, forms and booking links to practice-controlled receiving systems, test the intended journey and document rollback. An account-access handoff alone does not prove that the new-patient examination queue will keep working.
Treat the inquiry destination as the cutover unit
A domain can transfer successfully while a form continues notifying a former agency. A campaign phone number can remain printed on an old page after its routing changes. A familiar booking button can open the wrong office or appointment type. Check these as possible dependencies rather than assuming they exist in your setup.
Begin with the practice's current agreement and a system inventory. Ask which phone numbers, landing pages, form services, integrations and data exports the practice can retain, and which depend on the agency relationship. Payment for a service does not by itself establish ownership or portability; obtain the actual written terms and the relevant provider's transfer process.
Keep the dental workflow explicit. Separate new-patient examination requests, existing-patient recall, billing questions and requests for services requiring a different scheduling process. Do not route every contact to an unmonitored inbox for the convenience of the website change.
Build the destination register
Operations, the outgoing provider and the incoming provider should identify the boundary each controls. The register is an original cutover tool. It should contain references and acceptance evidence, not passwords or patient details.
| Public entry point | Current destination | Replacement or retained destination | Required continuity evidence |
|---|---|---|---|
| Main office number | ___ | ___ | Correct greeting, live routing and approved fallback |
| Campaign tracking number | ___ | ___ | Written retention or replacement plan; current route tested |
| New-patient form | ___ | ___ | Correct team receives a labeled synthetic request |
| Service consultation link | ___ | ___ | Correct office and appointment request type |
| Existing-patient route | ___ | ___ | Recall or administrative queue remains distinguishable |
| Profile appointment link | ___ | ___ | Public link opens the approved current destination |
| Notification or integration | ___ | ___ | Named receiver verifies receipt and next-action ownership |
For every row add the responsible system owner, planned change, approval, test reference, fallback and removal trigger. Record unknown dependencies as unresolved. Do not schedule a cutover on the strength of “the new website looks fine.”
Attach the practice-approved dental appointment map to the register. Where examination and hygiene are separate requests, test them separately and verify that the replacement scheduler does not silently combine them. Where a combined visit is genuinely offered, verify that its label and receiving queue survive the change. Keep returning-patient recall out of the new-examination route. For an insurance-participation question, confirm the billing destination without inventing a coverage answer. A working general contact form is insufficient acceptance evidence for these distinct paths.
Rehearse without entering real patient details
Agree the test with reception and the scheduling owner first. Use clearly labeled synthetic information and practice-controlled contact details. Prevent test submissions from reserving unwanted appointments, triggering real outreach or entering a clinical work queue unnoticed. If the live system cannot support a safe rehearsal, agree a controlled test route with its owner and record what remains untested.
Follow the journey from the actual public page. Confirm the office, appointment type, visible acknowledgement, receiving system and person responsible for the next action. Check whether the form promises a confirmed visit when it has only submitted a request. W3C's forms guidance recommends clear success or error feedback after submission; operational receipt still needs its own check. W3C notification guidance.
Test a reception-coverage gap through an agreed scenario, without pretending to be a patient. What happens if the designated receiver is absent? Does the practice know who handles an examination request differently from a billing inquiry? Save the result and correction owner in the register.
Separate number continuity from reporting continuity
Ask the phone provider to explain the exact process for retaining, transferring or replacing each relevant number. Get written confirmation of who is authorized to request the change. Do not cancel the old service while a required transfer or replacement remains unresolved.
If a number cannot be retained, map the approved replacement across controlled pages and advertising assets, then identify external references needing a correction request. Do not promise that every directory or old printed item can be updated immediately. Keep a pending list and a practical receiving route under the actual agreement.
Preserve reporting definitions through the change. A new form or call service may start a different data series. Label the break so the next report does not describe a tracking change as a gain or loss of patients. Keep received inquiries and confirmed appointments separate.
Remove access after the required continuity work
Use the website access handoff to assign capabilities and removal responsibility. Google notes that a removed verified Search Console owner may regain access while its verification tokens remain. Have the responsible administrator use the documented process and assess dependencies before token removal. Google's permissions guidance.
Apply each other system's own process. Do not assume that removing a website login cancels a phone subscription, disconnects an integration or transfers a domain. Have the responsible parties determine any retention, deletion and sensitive-data transfer obligations for the actual arrangement.
Finish with a go, repair or hold record. List the tested routes, unresolved destinations, cutover owner, acceptance evidence and rollback action. If receipt fails, use the booking failure triage guide and repair the specific boundary before retiring its working predecessor.
Frequently asked questions
Can we launch the new site before every external listing changes?
Assess the unresolved routes and maintain an approved working destination where possible. A pending listing correction and a dead appointment path have different implications. Record the remaining dependency and its owner.
Does a successful form confirmation prove reception received it?
No. Check the receiving system and next-action owner as part of the rehearsal. The visible message and the operational receipt are separate acceptance evidence.
Should we remove the outgoing agency immediately after notice?
Follow the agreed access and cutover plan after verifying practice control and required dependencies. A current security incident belongs in the practice's incident process rather than this routine planned-transition workflow.