Skip down to the research record

2FA recovery: 5 steps before a rep loses a phone

Quota Forecast Editorial Team · Published · 12 min read

Set up a separate second sign-in method and store recovery codes off the phone before a rep loses access to forecast files.

Key takeaways

  • Check which recovery options each service offers.
  • Keep a second sign-in method separate from the everyday phone.
  • Store recovery codes where the firm can reach them.
  • Test access to the forecast file before a lockout.

A rep is on a flight, the phone that receives sign-in codes is gone, and the forecast file that the leadership call starts from sits behind a login nobody can pass. The fix is not hard to set up, but it has to exist before the phone is lost. Once the rep is locked out, every option is slower and more awkward.

This post is for leaders who manage a rep's account login at a small firm. The goal is simple: forecast files stay reachable even when a 2FA device is lost. Along the way we follow one example. The example rep is a field rep who keeps the firm's forecast workbook and the CRM login that feeds it. The rep is the only person who has ever signed in to the CRM, and the rep's only second factor is a text message sent to a personal phone. We will use this rep to show how the choices fit together.

Why a single phone is a weak point

The rep's setup feels safe. A stranger who guesses the password still cannot get in without the code sent to the rep's phone. The trouble is the reverse case. When that phone is lost, broken, or out of service, the same rule that blocks strangers also blocks the rep. Nobody else at the firm can open the workbook that feeds Monday's pipeline review.

GitHub's guidance on account recovery states the problem plainly. It says that we strongly recommend configuring two or more authentication methods to avoid losing access to your account. That advice is written for GitHub accounts, but the reasoning carries over to any login that guards forecast files. A second method protects against losing the first one. The rep has a first method and nothing else.

Think of the second method as insurance on the first. If both policies are kept in the same place, a single incident can claim both. The rep's text message is the first policy, and a second authenticator app on the same phone would be a copy of it, not a backup.

It also helps to remember what the login protects. The sign-in is only the gate. The thing leadership needs during a review is the forecast file behind it. Keep that in view and the setup becomes clearer: the goal is a route to the workbook that the firm can take even when the rep's phone is gone, and each login is just one way along that route.

Know what each method depends on

Before you choose a second method, find out what each one needs in order to work. Microsoft's conditional access documentation sorts sign-in methods into categories by what the user has. It lists text message, voice, push notification, and software and hardware OATH methods in this category. Use that list as a starting point for checking the rep's setup.

Read that list with this rep in mind and the trap is visible. The rep's text message and any authenticator app both live on the personal phone. Losing the phone takes out both at once, so the firm would still be locked out even though it appears to have more than one method.

For each method you are considering, ask these questions. What physical thing or account does it depend on? Would that thing still be available if the rep's phone were gone? A hardware sign-in device kept in a locked drawer at the office passes that test better than an app on the phone. A recovery code saved on the phone fails it completely.

Choose a second method that lives somewhere else

Good second methods for this purpose live on a different object from the everyday phone. A few kinds fit most small firms, and they can be combined.

The first is a hardware sign-in device. Microsoft's category includes hardware OATH methods. A device like this can sit with the firm, not with the rep, which is the point of the exercise.

The second is a security key or a passkey. Bitwarden's help page explains that "Non-discoverable FIDO2 credentials are typically used for 2FA after entering your password." Check which kind of credential the service offers rather than assuming every key or passkey follows the password. The useful question is where the credential is stored. A physical security key is only useful if someone can get hold of it. Pick based on where the credential will be when the phone is gone, not where it is today.

Recovery codes and other recovery methods are separate fallbacks, covered in the next two sections. They are not usually a second sign-in method. They are the fallback that gets the rep back in when the sign-in methods are unavailable.

The rep's answer is a hardware sign-in device kept at the office, plus a set of recovery codes stored in the firm's password vault. The text message remains the everyday method because the rep uses it every day. The device and the codes are the way back in when the phone is gone.

Writing the choice down matters as much as making it. A short note in the vault entry should say where the device is kept, where the codes are kept, and who may use them. That note saves the next leader from rediscovering the arrangement under pressure, and it is the first place to look when the setup is reviewed. For a readable record, see the guide to forecast handoff.

Store recovery codes where a lost phone cannot take them

GitHub describes its recovery codes file in direct terms. It explains that the recovery codes file includes one-time codes for account recovery if you can’t access your two-factor authentication method. The same page notes that if you lose access to your phone, you can authenticate to GitHub using your recovery codes. That sentence describes the rep's exact situation, which is why the codes matter so much.

Two things follow from this. First, the codes are one-time codes. Each one is used up when it is entered, so they are a fallback for emergencies, not a daily method. Second, codes are useful only if they are reachable. A file saved on the lost phone, or in a note that only the rep can open, fails the same test as the phone itself. The codes need to sit somewhere the firm can reach them without the rep's device.

Store them in a location the firm controls, such as its approved password vault, and limit access to the people who truly need it. Agree in writing with the rep about who may use the codes and under what circumstances. This is a short conversation, but it prevents the scramble that happens when nobody remembers whether anyone else had them.

Timing is simpler than many people expect. The same GitHub page notes that you can also download your recovery codes at any point after enabling two-factor authentication. The rep does not have to wait for a special moment. Download the codes right after setup, store the copy, and refresh the stored copy whenever the codes change.

Add the recovery methods the service offers

Recovery codes are not the only fallback. GitHub's guidance lists several options. It lists the account's recovery codes file, SSH keys, PATs and verified devices as recovery methods. The same guidance says it would strongly suggest setting up some 2FA recovery methods which may be helpful if you were ever to lose your authentication methods.

The page also explains how to set up two of these options. It says that to set up 1 or more SSH keys that can be used to recover access to your 2FA-enabled account, see Adding a new SSH key to your GitHub account, and gives setup guidance for PATs that can be used to recover access. These options are specific to GitHub. Other services offer different fallbacks, so check the security settings of each tool the rep uses rather than assuming the same list applies.

The general pattern still carries over. Where a service lets you register a verified device, pick one the firm controls, such as an office computer, rather than the personal phone. Where a service offers a key-based recovery option, store the key the same way you store the codes. Each addition is a separate route back in, so the goal is to make sure no single device or person is the only route.

Set up the example from start to finish

Here is the rep's setup in the order it should happen. The steps are short, and most can be done in a single sitting.

  1. List every login that holds forecast data. For this rep that means the CRM and the shared drive account where the workbook lives. Check whether the forecast file can be opened through a route the firm owns. If the only way in is through the rep's personal login, the file is not reachable in the way this post means.

  2. For each login, check which second methods the service offers. Choose at least one additional sign-in method on a separate device, then add recovery codes stored off the phone. Use the test from the earlier section: what does each method depend on, and would that thing still be available if the phone were gone?

  3. Turn on the second method, then download the recovery codes right away. Store the copy in the firm's vault, and record where it is kept.

  4. Register any additional recovery method the service offers, such as a verified device or an SSH key, using a device or key the firm controls wherever the service allows that choice.

  5. Write down who may use the codes, the circumstances in which they may be used, and how the rep will be told afterward. Keep that note with the vault entry so it is found when it is needed.

The list is not complicated, and that is the point. Most of the work is deciding where things live. Once that is settled, the setup is mostly a matter of recording it.

Test the recovery before anyone needs it

A recovery method that has never been used is an assumption. Before any real lockout, the rep and the revenue leader should run a test together. Start by signing in with the second factor and opening the forecast file. Then sign out, and test the fallback. Sign in with a recovery code, confirm that the forecast file opens, and note that the code you used is now spent.

Run the test in a planned window, not during a quarter-end push when every login is in active use. Afterward, check whether the service issued new codes, and update the vault entry if it did. If something failed, fix it while the phone still works. A broken fallback discovered during an emergency costs far more time than the same problem found on a quiet afternoon.

The test also trains the person who will do the recovery. The leader who has signed in once with a recovery code will not be surprised by the screen the next time, and will know where the vault entry lives and who to contact.

Illustrative example: a recovery test

An illustrative setup has two sign-in methods: the everyday phone and an office-held device. Leave the phone unused and try the office-held second method. Open the forecast workbook, then test a recovery code. If the vault cannot be opened without the phone, the storage arrangement fails the test. Fix that dependency before relying on it.

Keep the setup current

The setup will drift over time. The rep will change phones, and the new phone may not carry over the text message method. The firm may switch CRM tools, which changes every login on the list. A rep may leave, and with them may go the only working key or the only person who knows where the codes are kept.

Every change should also be written into the same note, so the record matches reality. A note that describes a phone that no longer exists is worse than no note at all, because it invites a false sense of security. Treat the note as part of the setup, not as paperwork that lives in a folder and gets forgotten.

Make the review a routine event rather than something anyone has to remember. Review the setup whenever a rep changes phones, changes role, or leaves the firm. At each review, confirm that every forecast file still has a route the firm controls, that the second method still lives on a different object from the everyday phone, and that the stored codes are the current set.

Departures deserve the most care. When a rep leaves, the firm should be able to reach the account and the forecast data without the rep's cooperation. Handle the handover in the same way you set up the recovery methods: a route the firm owns, recorded in a place the firm can find. Include departing-rep folder sharing checks in that handover.

Start today

Pick a forecast-data login today and check whether its second sign-in method and recovery codes remain reachable without the rep's phone.

Related guides: Deleted mail before rep exit: 2 periods to check · AE capacity planning: 4 checks before a review · AI call scorecard checks: 5 rules before the forecast.

Questions about account recovery

Do recovery codes count as the second sign-in method?

Treat recovery codes as a separate fallback when sign-in methods are unavailable.

When should the firm review the setup?

Review it when a rep changes phones, changes role, or leaves the firm.

Sources