Hand over company numbers when someone leaves
When someone leaves, keep the company number and change who can use it. Then check that the next owner can sign in without asking anyone for a code.
Phonekit team Updated
List what depends on them
While the person still has access, go through your account list, password manager and number labels. Look for accounts that text their personal phone, and for connections or keys they set up. Pick a new owner for each account before anything changes.
An account on a company number keeps the same number. Only the people and software that can read it change.
Prove the new owner can sign in
Ask the new owner to complete the sign-in or verification step themselves, reading the code from their own inbox access or email. This catches the common gap: they can read the number but don't yet have the admin role in the account.
In the number's access settings, give the new owner access and turn on email for them if they want it. Then remove the person from the workspace. Phonekit takes them off every number's email list and rechecks access before sending any queued email. Emails they already received follow your normal email offboarding.
Review keys and connections
Removing someone revokes the command-line approvals and assistant connections they made in that workspace. Shared API keys they created keep working. Find those keys and the CI secrets that hold them, note each workflow's owner and numbers, then replace or revoke them.
Removing someone from Phonekit doesn't end their sessions or roles in other accounts. Handle those in each account's own settings.
Close each item with an owner
| Action | Owner | Done when |
|---|---|---|
| List affected accounts | Operations | Each account has a new owner |
| Confirm account admin role | Account admin | New owner can manage the account |
| Check the code reaches them | New owner | They completed sign-in themselves |
| Remove workspace access | Workspace admin | Membership and number access reviewed |
| Update number emails | Workspace admin | New owner added; departing person removed |
| Review API, CLI, CI and agent access | Workflow owner | Each key revoked or replaced |
| End sessions and update recovery | Account admin | Each account's own checks done |
| Close open number changes | Offboarding lead | Owner and due date for anything left |
Keep this record with your normal offboarding notes, so the next admin knows what's left without digging through old texts.
Questions
Do we need to replace the company number?
Usually not. A company number can stay in place when a person leaves. Change who can read it and review the accounts that use it. Replace it only when an account or your security process requires it.
Does removing someone revoke every key they made?
No. Their own command-line approvals and assistant connections are revoked. Shared API keys they created keep working, because CI or another team may rely on them. Review each one and record whether you revoked it, replaced it or gave it a new owner.
Does deleting a message cancel the code?
No. The service that sent the code decides when it expires. Deleting the copy in Phonekit doesn't invalidate it there.
What if an account still uses the person's own phone?
Move that account to a company number while the person can still approve the change, using the account's own settings for changing a phone number.
Keep reading
- Shared company numbersMove your company's verification codes and texts off personal phones. Shared US numbers, including real SIM lines, delivered to a shared inbox, email or Slack, with per-number access and a record of who opened what.
- Keep or release a numberA plain comparison of VoIP numbers and real SIM lines for SMS verification, with when to choose each, when to keep or release a number, and a checklist.
- API keys and scopesDiscover allowances, manage authorized lines, immediately read fresh SMS, send texts inside your own closed loop, and subscribe to selected-line webhooks through one API.