When the Phone Admin Leaves: A Handover Checklist for UK Small Firms
There is usually one person in a small firm who knows where the phone system lives. They can reset a forgotten voicemail PIN, add a new starter to the hunt group, and find the setting that stops the after-hours message playing at lunchtime. Then they hand in their notice, and everyone discovers that the knowledge was stored in their head rather than anywhere useful.
That is not a criticism of them. Small teams are busy, and phone admin tends to be the sort of job that gets done quietly by whoever is nearest. But when that person leaves, the risk is not just a gap in the rota. It is locked admin portals, mystery billing contacts, call routing that nobody can explain, and a new manager trying to fix a broken queue while the phones ring.
The answer is a proper handover, not a rushed Friday afternoon download. This checklist is designed for UK SMEs who want the phone system to stay boringly reliable while the keys change hands.
Start With a Map, Not a Password List
Before anyone touches permissions, write down what you actually have. Not the sales brochure version, but the working setup.
List the provider or providers, the main account number, the support portal address, and the names on the account. Then go a level deeper: which sites have phone service, which handsets or softphones are in use, and which parts of the system are cloud-based, on-site, or a mix of both. Include any separate tools that touch calls, such as call recording, voicemail-to-email, CRM integrations, or an auto-attendant.
Next, map the call flows in plain English. Where does a call go at 9am on a Tuesday? What happens at 5:30pm? Which numbers ring the sales team, and which go to a shared voicemail? Note the greetings, out-of-hours messages, holiday closures, and any temporary diversions that someone set up months ago and forgot to remove.
This map does not need to be beautiful. A shared document with a few bullet points and a simple diagram is enough. The point is that the next person can understand the system without reverse-engineering it from call logs.
Treat Admin Access as a Role, Not a Person
One of the most common problems is that the phone system admin login belongs to an individual. The password reset goes to their work email. The multi-factor authentication code goes to their mobile. The support contract lists them as the contact. When they leave, the firm has to negotiate its own system from the outside.
Before the leaving date, create named admin accounts for at least two people who are staying. Give them the right level of access for their role, not everyone as super-admin. Check that password reset emails go to a shared inbox or a role-based address rather than one person's mailbox. Make sure the authenticator method is something the business controls, such as a shared password manager or an admin phone that stays with the company.
Then review the smaller permissions that are easy to forget: billing access, ticket-raising rights, number management, call recording settings, API keys, and any integrations with your CRM or helpdesk. The leaver may not need all of these, but someone staying does.
Capture the Billing and Support Trail
You do not need to renegotiate the contract during a handover, but you do need to know how the account is paid and who the supplier will speak to. Record the invoice email address, the purchase order process, the direct debit details, and the name of the account manager or support contact. If the provider uses a support PIN or account security question, store it somewhere sensible and tell the right people.
Check that invoices are still reaching the finance team after the leaver's mailbox is closed. It sounds obvious, but a surprising number of SMEs discover a missed invoice only when the service is restricted. Add a calendar reminder to review the first two bills after the handover. It is also worth checking that any approved spend limits or change approvals sit with a role rather than a person.
Do a Dry Run Before the Last Day
The best handover happens while the outgoing admin is still around to answer questions. Pick a quiet hour, sit the new owner down at the admin portal, and get them to make a change themselves. Add a test user to a ring group. Change a voicemail greeting and change it back. Raise a low-priority support ticket and see where the reply lands.
Then test the phones from the outside. Call the main number from a mobile, try a transfer, leave a voicemail, and check the after-hours routing. If you have a queue, call it and listen to the whole journey. This is not about catching the leaver out. It is about finding the gaps while there is still someone to fill them.
The Leaving-Day Sequence
On the final day, keep it simple and follow a fixed order. First, confirm the new admins can log in and pass any security checks. Second, transfer the billing and support contacts. Third, remove the leaver's admin access and any personal authentication methods. Fourth, forward or redirect their old email for a short period if your IT policy allows it, so password resets do not disappear into a closed mailbox.
Do not delete the leaver's mailbox on the same afternoon as the handover. Give the business a short window to catch any stray reset emails. Then revoke access properly and record the date. If the leaver had a softphone on a personal device, remove that too.
Keep the New Owner Supported
A handover is not finished when the notice period ends. For the first month, ask the new admin to review call quality, check the bill, and look at any support tickets. Keep the system map in a shared folder and update it when something changes. A short monthly note of what was changed, by whom, and why is worth more than a perfect document written once and never opened again.
The goal is not to make phone admin glamorous. It is to make sure your business phones do not depend on one person's memory, one inbox, or one mobile. If the keys change hands cleanly, your team can get on with the calls that matter.
