Skip down to the research record

2FA enrollment: 4 phone and app checks for reps

Quota Forecast Editorial Team · Published · 11 min read

Before a rep enrolls in 2FA, check the phone's OS version, app installation, main authentication method, and independent backup.

Key takeaways

  • Read the OS version from the rep's actual phone.
  • Confirm the chosen app installs and opens.
  • Test a code from the authenticator app.
  • Set a backup that remains accessible without the phone.

When a rep cannot log in on the morning of the call, that rep's pipeline either goes missing or gets pasted in from a spreadsheet nobody has checked. The trouble is that enrollment tends to happen in a rush. The first problem often shows up only when a rep's phone cannot run the app they were told to install, and by then there is little time left to fix it.

This post covers four checks to make before a rep enrolls. We follow one account executive through all four. Their work iPhone is still on iOS 16.

Each check is simple, and none needs special tools. You need the rep's actual phone, a few minutes with the rep, and one test sign-in before the call. Work through the checks in order, because the first one can make the later ones pointless. If the phone cannot run the app, there is no point testing how the app installs.

Check 1: Confirm the phone's OS version meets the app's minimum

Start with the operating system, because it sets a floor that nothing else on the phone can fix. App makers update their software on their own schedule, and newer releases often drop support for older systems. A rep who has never updated the phone may not know that the app has moved on without them.

Duo's public user guide states that the minimum supported operating system version for Duo Mobile version 4 on Apple devices is iOS 17. It also states that Duo Mobile was removed from the App Stores for iOS 16 and earlier iOS versions.

For this rep, the answer is clear. An iPhone on iOS 16 cannot run Duo Mobile version 4, so enrolling this rep in that app would fail no matter how careful the setup is. The rep has two honest options. The first is to update the phone, if it can take a newer iOS version. The second is to choose an app and method that run on the phone as it is. Which option works depends on the phone itself, not on how much time is left before the forecast call.

Android follows the same pattern with different numbers. The same Duo guide gives Android 12 as the minimum for Duo Mobile version 4 on Android devices. It says Duo Mobile was removed from the Play Stores for Android 11 and earlier versions, and that no Duo Mobile releases are available for Android versions earlier than 7.

Read the version from the phone's settings rather than asking the rep to estimate it. "My phone is pretty new" does not answer the question, but the version number does. Write it down next to the rep's name so the check is recorded and can be reviewed later.

Personal phones need the same check as company phones. Many reps use their own devices for work, and the check does not change because the phone belongs to the rep. If the company expects a rep to use a personal phone for the authenticator, state that expectation in writing before enrollment, together with the minimum version the app requires. That way the rep knows what to look for before anyone is waiting on them.

One caution applies here. Duo's numbers belong to Duo Mobile. Your team may use an app with a different minimum, so find that app's own requirement before you apply this check. Duo is an example in this post, not the rule for every app.

Check 2: Confirm the rep can install the current app from the store

Meeting the OS floor does not finish the job. The app also has to be listed in the store for that phone, and the rep has to be able to install it there. Duo's guide shows that the listing depends on the OS version.

The practical step is to have the rep do the install on the actual device. Do not test on your own phone. An admin's phone often runs a newer system, so a test there can pass while the rep's phone fails. If you cannot sit with the rep, ask them to open the store page for the app and tell you what it offers for their phone. A screenshot works well for the record, if the company allows screenshots of work devices.

For this rep, the store check confirms whether installation is possible. If the store listing and the app's stated minimum disagree, resolve that difference before enrollment.

Also check the phone's storage and the store account it uses. An install can fail for reasons unrelated to the OS, such as a full device or a store account that is not signed in. Those problems are quick to fix on the spot, but only if someone is there to look at the screen with the rep.

Some phones are managed by the company. If this rep's phone is one of them, check that the store is open to the rep before enrollment day. A device policy that blocks installs looks like a broken app, and the error message can send the rep and the admin in the wrong direction while the call gets closer.

Watch for a third case too. Sometimes the install works, but setup stops with a message about the system version. Treat that as a failed check, not a glitch to retry. Retrying the same phone will usually produce the same message, and the rep will lose time they could have spent on a fix.

Check 3: Use a time-based app as the main method, not SMS

Once the phone can run an app, decide which method goes on it. Close's help center says that to enable 2FA for an account, you need an application that manages 2FA codes, and it names Google Authenticator, Authy, and 1Password as examples. GitHub's documentation is more direct. It strongly recommends a time-based one-time password (TOTP) application to configure 2FA, and it recommends security keys as backup methods instead of SMS.

Text messages depend on the rep's number and the network the phone is on, which adds another thing that can fail on the day of the call. A TOTP app generates its codes from the secret set up during enrollment and the phone's clock, so text message delivery does not come into it.

For this rep, this means choosing an authenticator app that passes checks one and two on the rep's iPhone. Name that app before enrollment starts, not during it. A rep who is partway through setup while the team argues about which app to use is a rep who will be on the phone with support when the call arrives.

During setup, have the rep enter a code from the app and confirm that the sign-in succeeds before the enrollment is considered finished. Setup screens can look complete even when the code was never checked, and a rep who finds that out on the day of the call has no time to recover. The same goes for any recovery codes or backup details the service shows. Have the rep save them somewhere safe at the moment they appear, because many services show them only once.

Pick one app for the whole team if you can. A single app means one setup guide, one set of troubleshooting steps, and fewer support requests while the team enrolls. Reps who already use an app they like can keep it if it passes the checks, but a mix of apps makes every support question take longer to answer. If some reps' phones cannot run the team's app, you need a second option. Decide what it is before enrollment starts, not while a rep is waiting to get in.

Check 4: Set a backup that does not depend on the same phone

The last check asks what happens when the phone is lost, replaced, or left at home. An authenticator app on one phone is a single point of failure, and a rep who loses that phone just before a forecast call needs a way in quickly. A backup method covers that gap.

A security key is a separate physical device, so losing the phone does not take the key with it.

Google's Workspace guide adds an option for some phones. It describes the phone's built-in security key as "Your phone's built-in security key (available on phones running Android 7+ or iOS 10+)." That is a feature of Google Workspace, so check whether the service your team uses offers the same option before you count on it.

For this rep, the iPhone on iOS 16 clears the iOS 10 floor in Google's guide. That makes the built-in option worth testing, but it still depends on the phone. It cannot cover losing that same phone; test a separate backup for that situation.

Write down two things for every rep: which backup they have, and who can reset their enrollment if the phone is lost. A reset path nobody can reach is about as useful as no backup at all. These answers matter most on the day something goes wrong, and it is far better to know them in advance than to work them out during a call. Keep them in the same record as the phone checks, so one document shows each rep's status from start to finish. Use the recovery planning guide to review that record before a phone goes missing.

When a check fails

A failed check is information, not a crisis. Most failures can be handled before the call, as long as they are found early. Set one rule before you start: a rep who fails a check does not enroll until the check passes. Do not let a rep enroll on a workaround and hope it holds. A workaround that works once can break during the forecast call, when the rep needs it most.

Three responses cover most failures.

  • Update the phone, if the OS version is the failing check and the phone can take the update.
  • Change the app or the method, if the app's minimum is above the phone's version. For this rep, that means a different authenticator that passes checks one and two on the same phone.
  • Use a separate security key as the backup, if the company's service supports it. Test access without the rep's phone.

Tell the person who owns the forecast as soon as you know about a failure. That person can plan around a delayed rep, for example by asking the rep's manager to confirm the numbers for that account. Waiting until the day of the call removes every option except the most awkward one.

Talk to the rep directly, too. Explain which check failed and what happens next, in plain words. A rep who understands that the phone is the problem, and not their own carelessness, is more likely to report the next problem early. Keep the tone practical. The goal is a working login, and a rep who feels blamed will be slower to ask for help when the next check fails.

Keep a note of each failed check and how it was resolved. The same failure tends to come back with the next group of reps, and a short record saves time on the next enrollment. A note such as "iOS 16 phones need a different authenticator" is more useful than a memory of a bad week.

Running the four checks before the call

Here is the order we recommend:

  1. Record each rep's phone model and OS version from the phone's settings.
  2. Compare that version with the minimum on the app's own page.
  3. Have the rep install and open the app from the store on their own phone.
  4. Enroll with an authenticator app as the main method, not SMS.
  5. Add a separate backup, and test a sign-in without the phone.
  6. Run one more sign-in before the forecast call, so a problem shows up on a quiet day rather than at the start of the call.

Run this rep through the same order. The version check comes first, and its answer shapes every step after it. The phone's OS decides which apps are possible, the store confirms that the install works, and the separate backup must work without that phone. If the iPhone stays on iOS 16, the team picks a different authenticator and tests it on that phone. This rep's enrollment then starts from facts rather than guesses.

The four checks take far less time than a rep locked out during a forecast review. Start them early, and keep a record of what each rep's phone can do, so the next enrollment starts from the same known facts.

Illustrative example: Check access before the call

An illustrative team has 10 reps awaiting enrollment. The admin checks each phone before choosing the app. A failed install pauses that rep's setup while the phone or app choice is reviewed. Each rep then tests an app code and a separate backup before the forecast call.

For today's next step, check a rep's actual phone version and compare it with the chosen app's minimum. Then include a test sign-in in your forecast call setup.

Questions before enrollment

Does meeting the OS minimum finish the checks?

No, the rep must also install the app, test a code, and test an independent backup.

Can the same phone cover its own loss?

No, a backup stored only on that phone is unavailable when the phone is lost.

Sources