Skip to content
Back to the lab

A two-ledger cutover for switching medical answering services

Use two linked ledgers to prepare the new answering service while keeping every unresolved patient request assigned through completion.

Super Genius Labs Editorial · 5 min read

Switching medical answering services calls for two linked records. A configuration ledger prepares the new service to receive and route tomorrow’s calls. An open-request ledger keeps yesterday’s unresolved messages and callbacks attached to an accountable owner until completion.

The split matters because technical readiness and unfinished patient work can move on different timelines. A migration guide from Ambs Call Center covers number and route inventories, scripts, delivery settings, unresolved requests, external test calls, staffed cutover, rollback responsibility, record access, and account closure after acceptance (source). NHS England separately advises practices to clear outstanding communication tasks, log calls that require record updates, preserve messages and out-of-hours reports, plan workarounds, involve both suppliers, and arrange post-go-live support (source). The two-ledger structure below is our operating interpretation of those documented concerns.

Ledger one: configuration readiness

The configuration ledger describes the call-handling state intended for cutover. One row can cover each phone number, call route, schedule, script, contact, delivery destination, access dependency, or fallback setting.

Useful fields include:

  • Configuration item and current value.
  • Intended value at the new service.
  • Source of truth.
  • Person responsible for configuration.
  • Test method and expected result.
  • Test result, time, and tester.
  • Rollback value and person authorized to restore it.
  • Remaining exception or dependency.

A copied script is not yet a tested route. The ledger becomes useful when each important configuration has an observable check: which service answers, which greeting plays, where a message arrives, what happens outside normal hours, and which fallback activates when the primary destination is unavailable.

This record can also cover access to the former provider’s messages and reports. Ambs includes record access and closing obsolete accounts only after acceptance in its migration scope (source). That sequence supports keeping access available through reconciliation rather than treating account closure as the cutover itself.

Ledger two: unfinished patient work

The open-request ledger follows work rather than configuration. Give each unresolved message, callback, scheduling question, or record-update request its own row.

Useful fields include:

  • Request identifier and original channel.
  • Date and time received.
  • Request category.
  • Current status.
  • Named owner.
  • Next action and target time.
  • Source system or message location.
  • Last verified update.
  • Completion evidence or documented disposition.

The owner field is the controlling element. A message exported from the old service or imported into a new queue has changed location; that movement alone does not establish that anyone has accepted responsibility for it.

NHS England’s guidance explicitly covers clearing outstanding communication tasks, logging patient calls that need record updates, and preserving messages and out-of-hours reports during cutover (source). The proposed ledger turns those categories into a practice-level reconciliation record. It does not establish clinical priority or replace the practice’s own escalation rules.

Prepare the cutover from both ledgers

Begin with an inventory of published numbers and every route that can receive a call. For each route, record business-hours behavior, after-hours behavior, schedules, approved scripts, contacts, delivery destinations, credentials, and fallback settings. Put unresolved work in the second ledger as soon as it is found; do not bury it in a configuration note.

Next, run external test calls. Ambs includes external testing and a staffed cutover window in its checklist (source). Calls placed from outside the practice environment can exercise the public path rather than only the provider’s administrative preview.

A compact test set can cover:

  • Each published number.
  • Open-hours and closed-hours greetings.
  • A routine message delivered to its intended destination.
  • A request that follows an escalation or fallback route.
  • A failed or unavailable delivery destination.
  • Retrieval of a message from the former service.

Record the observed result in the configuration ledger. If the test creates a real follow-up item, add it to the open-request ledger and mark it clearly as a test so it cannot be mistaken for a patient request.

Practices comparing the new provider’s call path can also use the broader AI answering service guide to frame questions about reception and handling behavior.

Make rollback an owned decision

Before changing the live route, name the person who can call rollback and the person who can execute it. Record the exact prior routing values, the trigger for restoring them, and the latest point at which rollback remains practical.

Ambs identifies rollback responsibility as part of migration planning (source). NHS England advises planning workarounds and involving both the current and new suppliers (source). Our derived recommendation is to place those responsibilities directly beside each affected configuration instead of leaving them only in a general project plan.

Rollback changes the active call route. It does not resolve requests already captured by either provider. Keep the open-request ledger active whichever service answers the next call.

Reconcile after the route changes

After cutover, compare evidence from four places: test-call results, the new provider’s received messages, the former provider’s remaining records, and the practice’s own work queues. The aim is to locate mismatches while both providers and relevant records remain accessible.

For configuration, confirm that every published number reaches the intended service and that schedules, scripts, delivery routes, access, and fallback behavior match the accepted values. For unfinished work, inspect every open row and verify a named owner, next action, and current status.

Post-go-live support appears in NHS England’s planning guidance (source). Ambs places obsolete-account closure after acceptance (source). Together, those points support a reconciliation interval between routing the calls and ending access to the old service; the appropriate duration remains a practice decision.

The final acceptance question is concrete: did each pending message reach an accountable owner, with its next action visible? A clean configuration ledger answers whether the new service is ready. A reconciled open-request ledger answers whether unfinished work survived the change.

For practices evaluating a new voice-reception option, Genius Care provides additional product context. Teams planning a broader implementation can also build with Super Genius Labs.