Skip across the chapter
Quota Playbook

Device and 2FA checks: 4 fixes before reps call

Quota Playbook Editorial Team · Published · 11 min read

Before a rep's first live call, check their phone's app support, laptop lock time, recovery options, and second-factor prompts.

Key takeaways

  • Confirm the phone used for 2FA supports the required app.
  • Ask IT about laptop lock time and approved recovery methods.
  • Rehearse sign-in on the actual call device before the first live call.

Most managers think about a new rep's first live call in terms of pipeline, talk track, and demo flow. Those things matter, but a surprising number of first calls go sideways for a reason that has nothing to do with selling. The rep's laptop locks in the middle of a discussion. The phone that receives the login code is not the phone the rep is holding. The CRM asks for a second step that nobody set up ahead of time.

These problems are boring, and they are easy to prevent. They are also easy to miss, because the rep often does not know what is wrong until the moment it happens. This post covers four device and two-factor authentication (2FA) mistakes that front-line managers can check before a rep's first live call. For each one, you will find what to look for, why it matters, and a simple way to close the gap.

Nothing here replaces your company's IT policy or your security team's standards. Treat this as a checklist for the manager's side of the handoff: making sure the rep can sign in, stay signed in while working, and get back in quickly if something goes wrong.

Why this lands on the manager

In many B2B companies, IT provisions the account and the rep is expected to sort out the rest. The rep has a laptop, a set of logins, and a phone for two-factor prompts, and everyone assumes it all works. Then the first live call arrives, and the rep discovers that the authenticator app will not install, the screen locks every few minutes, or the second factor is tied to a device they no longer carry.

You are the person closest to the rep's first real use of these tools. You know when the first call is booked. You are the one who can ask the right questions well before the call, when there is still time to fix things. Waiting until the morning of the call turns a quick fix into a missed meeting.

A simple habit helps. Build a short device-and-login check into your onboarding, and run it with the rep well before their first live call. Keep it in the same place for every rep so you can see patterns across the team. If a problem shows up for one rep, it may show up for the next one too.

Mistake 1: Assuming the phone for 2FA is current enough

Duo's guide says that Duo Mobile was removed from the Play Stores for Android 11 and earlier versions. So if a rep's Android phone is on one of those older versions, Duo Mobile may not be available to install from the usual store.

The same guide also says that users are encouraged to upgrade to the latest version of Android supported by their phones and to install the current Duo Mobile release on newer versions. In practice, this means the fix is often a phone update or a phone change, not a settings tweak. That is a bigger job than most reps expect, so find out early.

What to check:

  • Which phone the rep will use for second-factor prompts. Ask them directly. Do not assume it is the one they use for personal messages.
  • The phone's operating system version. The rep can usually find this in the phone's settings.
  • Whether the required authenticator app is installed and opens correctly. Have the rep open it while you watch, if you can.
  • Whether the rep has a second approved way to get a code, such as a backup method your company allows.

If the phone is too old, the decision is not yours alone. Bring in IT, explain the first-call date, and ask what the approved replacement path is. The worst outcome is a rep who spends the first morning of their first week waiting on a phone order.

Mistake 2: Leaving the laptop's auto-lock to chance

The second mistake is about the screen, not the phone. Reps often work in short bursts: a call, a few notes, a glance at the CRM, then another call. If the laptop locks while they are on a live call, the rep has to unlock it, sometimes with a second factor, while the prospect waits. That is a bad first impression, and it is avoidable.

Windows has a built-in setting for this. Microsoft explains that beginning with Windows Server 2012 and Windows 8, Windows detects user-input inactivity of a sign-in (logon) session by using the security policy setting Interactive logon: Machine inactivity limit. That setting is what decides when a session is treated as inactive. The same page notes that the setting allows you to control the locking time by using Group Policy.

Microsoft also notes that the policy setting can only be set locally on those computers that contain this policy setting, but it can be set and distributed through Group Policy to any computer running the Windows operating system that supports Group Policy. For a sales manager, the useful point is this: ask IT how the lock time is managed. You cannot assume the setting is the same across every laptop your team receives.

Here is the practical part. Do not try to set policy yourself unless your company gives you that authority. Instead, ask IT two questions before the rep's first call:

  1. What is the lock time on the rep's laptop, and is it set by Group Policy?
  2. If the rep needs more time during a live call, what is the approved way to handle it?

Some teams find that the answer is fine. Others find that a laptop is locking far faster than anyone realized, and they fix it before the first call. Either way, you have learned something you can act on. Also ask the rep to tell you if the screen locks during any practice session. A lock during a role-play is a useful warning. Include this in your sales demo screen-share rehearsal.

Remember that a lock that is too short is annoying, but a lock that is too long can also be a problem. Shared spaces, client visits, and hybrid offices all change how much idle time is acceptable. Your IT team and your security team should set the rule. Your job is to make sure the rep knows what it is before they are on a call.

Mistake 3: Enrolling in 2FA on one device and hoping nothing changes

The third mistake is a single point of failure. The rep sets up 2FA on one phone, on one day, and then never thinks about it again. That works until the phone is lost, replaced, reset, or left at home on the morning of the first call.

A good first step is to walk through the enrollment with the rep, rather than trusting that it was done correctly during provisioning. Ask the rep to show you that they can sign in to each tool they will use on day one. Do this on the device they will actually use for calls, not on a test laptop you keep in the office.

Next, find out what recovery looks like. Your company's identity system and your tools may each handle recovery differently. Some offer backup codes. Some allow a second authenticator. Some depend on the help desk. Write down the answer for each tool. A short table in your onboarding notes is enough. Include the tool name, the second factor the rep uses, where the backup information is stored, and who to contact if the rep is locked out. For a lost device, see the seller phone recovery steps.

Two notes of caution:

  • Do not ask the rep to store backup codes in a shared document or a chat thread. Store them somewhere the rep controls and that your company's policy allows.
  • If the rep must replace a phone during the first few weeks, treat that as a planned change, not an emergency. Confirm that the new phone can receive codes before the old one is wiped.

This is the kind of step that feels like overkill until it saves a call. A rep who can recover quickly from a lost phone is a rep who can keep talking to a prospect. A rep who cannot may lose the day.

Mistake 4: Forgetting that 2FA can ask for a check later

The fourth mistake is about timing. A rep signs in successfully during onboarding, and everything looks fine. Then, days or weeks later, a system asks for a fresh second factor at the worst possible moment, often right before a call.

Some vendors make this behavior explicit. GitHub's documentation on two-factor authentication describes a check-up period, and it says that you can leave the check up period by successfully performing 2FA in those 28 days. That example is about GitHub, not your sales tools, and you should not assume your tools work the same way. The lesson still applies. Ask every vendor on your rep's list how and when they re-check a second factor, and what the rep should do if the check appears during a call.

Here is a simple way to handle this across the team:

  • Make a list of every tool the rep will open on the first call. Include the CRM, the calendar, the video meeting platform, the sales engagement tool, the call recording tool, and any shared data sources.
  • For each one, note whether it uses 2FA, how often it asks again, and whether the rep can complete the step quickly on their phone.
  • Before the first call, have the rep sign in to each tool, in the order they will use them on the call. Watch for any prompt that appears.
  • Set a rule that the rep does not start a live call until the morning sign-in check is clean.

If a tool asks for a second factor every single time, raise it with IT and confirm the approved sign-in process.

Putting the four checks into one routine

You do not need a complicated system. A short routine, run the same way for every rep, covers all four mistakes. Here is one to use:

  1. Phone check. Confirm the phone used for 2FA is on a supported operating system and has the right authenticator app installed and working.
  2. Screen check. Confirm the laptop's lock time with IT, and ask whether it is managed by Group Policy. Ask the rep to report any unexpected lock.
  3. Recovery check. Confirm the rep has a backup method for each tool and knows who to call if they are locked out.
  4. Sign-in rehearsal. Have the rep sign in to every tool they will use on day one, in the order they will use them, on the device they will use for calls.

Run the routine well before the first live call. Then run a shorter version on the morning of the call, just to confirm nothing has changed overnight. Note any issues in a shared log so you can see whether the same problem keeps coming up for different reps.

Illustrative example: a lock during rehearsal

In an illustrative 10-minute rehearsal, a rep's laptop locks while they explain a demo. The manager notes the interruption and asks IT to confirm the lock policy and approved response. The rep then practices unlocking the laptop and returning to the demo before taking a live call.

What to do when something fails anyway

Even with a good routine, something will sometimes go wrong. The goal is to make the failure small and short. Here are a few practical moves:

  • Have a fallback call plan. If the rep cannot sign in to the CRM, can they still take notes on paper and log them afterward? Decide this before the call, not during it.
  • Know your help desk path. Find out how to reach IT quickly on a call day, and write the number or channel down where the rep can see it.
  • Protect the prospect's time. If a delay is unavoidable, a short, honest message to the prospect is better than a long silence. Something like "I am sorry, I am resolving a login issue and will be right with you" works.
  • Debrief after the call. Ask what slowed the rep down and fix it for the next person.

Keep your tone calm. A rep who sees a manager stay steady during a technical problem learns that these problems are normal and fixable. A rep who sees panic learns to hide problems, which is worse.

Your next step today

Start with the next rep on your calendar. Pick a day, book the sign-in rehearsal, and ask the phone question first.

Common objections

Should IT handle all of this?

IT should own the settings, and you should not try to change them yourself. But IT usually does not know when a rep's first live call is booked. You do. Your job is to bring the date and the rep's real workflow to IT early, so the right people can act.

Is this too much process for a new rep?

Keep the list short and reuse it. It also gives a new rep a clear picture of what their day-one tools look like, which reduces stress.

Should reps be responsible for their own devices?

Reps should know their devices and their logins. But the first live call is a shared responsibility. A quick check with a manager is not micromanaging. It is making sure the rep can do the job they were hired for.

What if we already have a checklist?

Compare it to the four areas above. Check whether it covers the phone used for 2FA, the lock time behavior during live use, recovery, and the sign-in rehearsal on the actual call device.

Sources

  1. New-rep training rollout figures: 4 to read first
  2. Microsoft 365 usage: 4 windows for seller check-ins
  3. New seller pay: 3 checks before the first paycheck
  4. CRM call review files
  5. Passkey sign-ins: 4 checks before reps switch

More plays