A team finds out its account recovery phone number is dead only when it tries to use it, usually while locked out of something. The number was never taken away by an employee leaving. It stopped working because a carrier port went through, a device was lost or wiped, or a line was canceled when a plan changed. The question that follows is what a dedicated verification service costs, and whether setting one up before the next number change is worth doing.
The failure mode this piece is about
There are three separate ways a recovery phone number stops working, and none involve someone leaving the company. The first is a carrier port: the number moves to a different carrier, and once that completes, the old line no longer receives calls or texts sent to it. The second is a lost or wiped device, where the SIM or eSIM profile is gone even though the number itself may still be active elsewhere. The third is a canceled or reassigned line, which happens when a company trims a phone plan or a number is recycled after a contract ends.
This differs from the piece on authenticator app offboarding, which deals with device custody: what happens to a locked account when the person holding the 2FA app leaves. A phone number failing has nothing to do with who works where.
The result is that a recovery flow built on SMS or voice codes has exactly one point of failure, the number itself, and it is usually not on anyone’s audit list. Nobody checks whether the recovery number on file still belongs to the team that’s supposed to control it, until the code does not arrive.
How number porting actually breaks a recovery flow
Wireless local number portability lets a subscriber keep their number when switching carriers. A port request tells the new carrier to take over routing for that number, and the general premise is that once the transfer completes, the losing carrier stops delivering calls and texts to it on the old SIM or line. A readable first-party source confirming the mechanical detail and typical completion timing could not be fetched in this session, so that part is marked accordingly. [EVIDENCE NEEDED: a readable first-party regulatory or carrier source describing wireless local number portability mechanics and typical completion timing.]
What can be stated without that source is the practical shape of the outcome, which does not depend on timing: once a number is ported away, it does not return to whoever set it up originally. If that number was the recovery contact for a social account, the team no longer controls the channel the account depends on for verification, and there is no undo.
What the platforms themselves document about SMS based recovery
Instagram and Facebook both publish help pages meant to cover what happens when the phone number on an account is no longer reachable, but neither returned readable article text in this session, only client-side shells, so neither is quoted or paraphrased here. [EVIDENCE NEEDED: Instagram’s documented behavior for account recovery when the phone number on file is unreachable, from a page that returns readable article text.] [EVIDENCE NEEDED: Facebook’s documented behavior for the equivalent scenario.] X and LinkedIn are not addressed here for the same reason: neither had a first-party help URL verified in this session.
What a dedicated verification service actually centralizes
Services like Twilio Verify and Plivo Verify sit between an application and the end user’s device to send a one-time code by SMS, voice, or another channel, and confirm the user entered it correctly. Because the team owns the integration, the outbound number can be swapped, pooled, or rotated by country without touching the login flow.
That flexibility applies only to systems the team builds: a custom login page, an internal admin tool, a client portal. It does not extend to the recovery flow Instagram or Facebook run internally on their own accounts. There is no way to route their SMS recovery code through a third-party API. A verification service does not touch a locked-out Instagram account, only the logins and tools the team actually owns.
What it costs: Twilio Verify vs. Plivo Verify
The two vendors price this in structurally different ways. Twilio Verify charges a flat per-verification fee on top of the channel cost. Plivo Verify charges no separate verification fee, billing only the underlying channel rate.
| Vendor | Per-verification fee | Channel cost (US SMS) | Pricing model |
|---|---|---|---|
| Twilio Verify | $0.05 per successful verification | $0.0083 per SMS (US), billed in addition to the verification fee | Flat fee plus channel rate |
| Plivo Verify | $0 per verification | Standard SMS, voice, or WhatsApp channel rate for the destination country | Channel rate only, no platform fee |
Twilio’s Verify pricing page states the base rate as “$0.05 per successful verification plus standard channel fees,” with the SMS line item listed as “$0.05 per successful verification + $0.0083 per SMS (US).” Plivo’s pricing page states that OTP verification and Fraud Shield cost $0, and a team pays “only SMS, Voice, or WhatsApp channel charges,” with country-specific rates for each channel. Neither page states a monthly total for any volume, and no team-specific figure exists in this site’s facts file, so none is computed here.
What this does not fix
Buying a verification service does not change the phone number Instagram or Facebook has on file as an account’s recovery contact. That field still has to be updated through the platform’s own account settings while the old number still receives codes. Once the number is gone and the account is locked out, no service bought that day gets a team back in through the phone number field. The fix has to happen before the number is lost, not after.
A short checklist for auditing recovery numbers before the next port or cancellation
- List every account and tool that uses a phone number for recovery, and identify who controls that phone line, not just whose name is on the account.
- Confirm with whoever holds each line that it is not scheduled to be ported, canceled, or reassigned as part of a carrier change, a device upgrade, or a plan trim.
- Update the recovery number on file with each platform while the old number still receives codes, rather than waiting for a lockout.
Talk to followed about wire coverage that isn’t a ranking
followed tracks the social media management tools market, sourced and dated. followedapp is published by the team behind RecurPost, and RecurPost is covered vendor #34 under the same rules as every other vendor. This blog covers adjacent tooling questions outside that coverage. No signup form or CTA link is configured for this post at this time.
FAQ
Does porting a phone number to a new carrier break SMS-based account recovery?
The general premise of number porting is that once a port completes, the losing carrier stops delivering calls and texts to that number on the old line. [EVIDENCE NEEDED: a readable regulatory or carrier source confirming completion mechanics and timing.] If that number was the recovery contact on a social account, the account is affected the same way regardless of the exact timing.
Can Twilio Verify or Plivo Verify take over Instagram’s or Facebook’s account recovery for a team?
No. Both let a team run its own SMS or voice verification for tools and logins it controls. Neither can intercept or reroute the recovery flow Instagram or Facebook run internally on their own phone number field, because that flow is not exposed to a third-party API.
What does Twilio Verify charge per SMS verification in the US?
Twilio’s Verify pricing page states $0.05 per successful verification, plus $0.0083 per SMS for US messages, billed as a separate channel fee on top of the verification charge.
What does Plivo charge for the same thing?
Plivo’s Verify pricing page states there is no separate per-verification platform fee. A team pays only the underlying SMS, voice, or WhatsApp channel rate for the destination country, with OTP delivery and Fraud Shield included at no additional cost.
Is this the same problem as an employee leaving with the 2FA device?
No. A phone number becoming unreachable through a port, a lost device, or a canceled line is an infrastructure failure unrelated to staffing. Device custody, what happens to a locked account when the person holding an authenticator app leaves, is a separate failure mode covered in this site’s piece on authenticator app offboarding.
Sources
- Twilio Verify pricing, fetched 2026-09-08.
- Plivo Verify pricing, fetched 2026-09-08.
- Twilio SMS pricing, United States, fetched 2026-09-08.
Back to Blog