Skip across the chapter
Quota Playbook

Lost seller phone recovery: 4 steps for 2FA lockouts

Quota Playbook Editorial Team · Published · 12 min read

When a seller loses or swaps a phone, recover access by verifying the request, rebuilding the second factor, and having an administrator reset the account. In practice, it quietly becomes part of the login. Sellers use it to receive one-time codes, approve sign-in prompts, and check mail between calls. So when a seller upgrades to a new phone, drops the old one in a parking lot, or hands it back to a carrier, the login path can break at the exact moment they need to reach a prospect.

Key takeaways

  • Verify the request through a channel you already trust, not only the contact details the seller just sent.
  • Remove or neutralize the old device, and check for signs of compromise.
  • Rebuild the second factor on the new phone, transferring codes or updating apps where possible.
  • Have an administrator reset access through the product's own tools, never through shared logins.
  • Test the CRM and email from the new phone and a desktop, then update the recovery inventory.

The problem is rarely the CRM or the mail service itself. It is the second factor. Two-factor authentication (2FA) asks for something the person has, such as an app code, a text message, or a prompt on a device. If that device is gone and nobody planned for it, the account still exists, but the seller cannot get into it. Deals stall while everyone waits for someone to find the right administrator.

This post gives sales managers a four-step recovery sequence. It is written for teams that run a CRM such as HubSpot or Close alongside a business email service. The exact options depend on the product, the subscription, and the country or region, so treat the steps as a checklist to adapt rather than a fixed script. Where a vendor publishes a specific rule, we link to the official page so you can check the current wording yourself.

Step 1: Verify the request and contain the old device

Before anyone resets anything, confirm who is asking. Account lockouts are a common route for account takeover, and a message that says "I got a new phone, please reset my login" is exactly what a bad actor would send. Confirm the request through a channel you already trust, such as a call to a number you have on file or a message in your team's internal chat. A new email address the person just provided is not enough on its own.

Next, decide what happens to the old phone. If the device was lost or stolen, it may still be able to receive codes or approve sign-ins. Ask the seller to remove it from their account security settings if they can reach them, or ask an administrator to do it. For a wider view of removal, see seller login removal checks. If the old phone is simply retired and still in the seller's hands, the same rule applies: it should stop being a way into the account.

Also look for signs that the lockout is not innocent. Unexpected sign-in alerts, new forwarding rules, or a password reset email the seller does not recognize are reasons to pause and escalate to whoever handles security for your company, even if the request itself sounds ordinary. A quick check now is cheaper than cleaning up after an intruder later.

Then write down the scope. A typical seller touches a CRM login, a mailbox, a calendar, a dialer, and often a sequencing or document tool. Some of these may share one sign-in provider, and some may not. A short list keeps you from fixing email and forgetting the CRM, which can let lockouts drag on. Record the time you started, what you verified, and who is handling each account. This log becomes the basis for the prevention work in step 4.

Finally, tell the seller what to expect. Say who is handling the request, what they need to do on their side, and when you will check back. Keep the message short and avoid guessing at the cause in writing. A seller who knows the next step is far less likely to try a workaround, such as sharing a colleague's login, that creates a bigger problem.

Decide, too, how much the seller can do while they wait. Some tasks, such as reviewing open deals or reading existing notes, may need little more than a read-only view. Others, such as sending outbound sequences from a shared address, should wait. Writing that decision down now keeps the team from improvising under pressure, and it gives the seller something concrete to plan around while the reset is in progress.

Step 2: Rebuild the second factor on the new phone

This is the step that takes the longest, and the details depend on which method the account used. Start by answering one question: what was the second factor?

If it was an authenticator app, check whether the codes can move. HubSpot's guidance covers one such path. If a user set up 2FA with Google Authenticator and then switched to a new Android phone, they can transfer their Authenticator codes to the new device. Confirm the transfer requirements on HubSpot's page, and teach sellers to do it at the time of the switch, not after a phone is lost.

If the old device is gone, you need a recovery route that an administrator controls. HubSpot's own 2FA setup page states that the available methods for setting up 2FA "may vary depending on your HubSpot subscription level and country or region." Do not assume your plan offers the same options as a peer team. Have your administrator check which options are actually available to your account before you plan around them.

Text messages are one fallback option, and they have a geographic limit. The same HubSpot page states that the countries that support SMS 2FA are the same as the supported countries for calling. A seller who has relocated, or who is using a number from a country that is not supported, may not receive a text code at all. Confirm that the number on the account can receive the codes you plan to use before the seller is stuck waiting for a message that never arrives.

Google's guidance follows a similar pattern. For Google Workspace accounts, Google sends a 2-Step Verification code to mobile devices in a text message or voice call. The same page lists the phone's built-in security key as an option, available on phones running Android 7+ or iOS 10+. If your sellers carry phones in that range, check with your administrator whether that option is enabled for your domain and whether it suits the phones your team actually uses.

Microsoft's guidance shows why app versions matter. If your team signs in with Microsoft Authenticator through Microsoft Entra ID, note that Android users with Company Portal versions below 2111 (5.0.5333.0) can't register Authenticator until they update Company Portal. A seller on a new phone may find that registration fails for a reason that has nothing to do with their password. Update first, then register.

Finally, document the method you used. The next person to face this lockout should not have to rediscover it. A one-line note on the seller's record, such as "Authenticator codes transferred on the day of the phone switch; backup route handled by admin," saves a lot of time and keeps the answer in one place.

Pay attention to whose phone holds the codes. Some teams issue company devices to sellers, and others allow personal phones for work. The answer changes who can retire a device, who owns the transfer, and what your company's device policy requires. Settle that question before the next lockout, not during it.

It also helps to ask each seller a few questions before a phone is retired. Which app or method do they use for codes? Is the number on the account the one they carry today? Do they have a second device that already works with the account? The answers take a few minutes to collect in a quiet week and can save a long delay during a lockout.

Step 3: Restore CRM and email through the admin path

Once the second factor is rebuilt, or if it cannot be rebuilt, an administrator needs to reset access. This is where small teams most often improvise. Avoid two common mistakes: sharing a password with a colleague so they can sign in as the seller, and keeping a shared login for the whole team to use during the gap. Both create problems that outlast the lockout. Use the product's own admin tools and keep the change inside the account's audit trail. A backup admin checklist for sales tool logins can help if more than one person holds admin rights.

Start with the CRM. In Close, two-factor settings live on the Account Settings page. Close's help center explains that to disable 2FA, you go back to the Account Settings page and click the Disable button. Knowing where that control is matters, but turning off a second factor weakens the account. Treat it as a deliberate administrator decision, record it, and re-establish a working factor as soon as the seller is back in. If you are unsure how a control behaves, Close's 2FA page says that if you have any questions about enabling or using 2FA, you should contact its Support Team.

Now check email. Confirm the mailbox is active and that the seller's sign-in method for it has been re-enrolled. Check that forwarding rules, delegated access, and shared folder permissions did not change while the seller was locked out. A lockout is a good time to clean up delegations that no longer make sense, but do not make unrelated changes during the recovery itself. Changing five things at once makes it hard to tell what actually fixed the problem.

Then test. Ask the seller to do three things on the new phone and at a desktop browser: sign in to the CRM, send a short email to an internal address, and log a call or note in the CRM. These checks cover the two paths that matter most to a seller, which are the CRM and the mailbox. They also confirm that the new phone can complete the second factor on its own, without the old device. Once all three pass, close the ticket and update your log.

When the reset is done, close the loop with the seller and with the wider team. Tell the seller which steps were completed and which remain, such as re-enrolling a second device or removing an old one. Note in your log whether the vendor's support team was needed and how long it took. That detail will matter the next time you plan a phone swap.

Keep the admin's role narrow. The administrator who resets the account should not also be the person who approves the seller's new device without a second look, if your team has more than one admin. Two people involved in a sensitive change is a simple habit that catches mistakes and makes unusual requests easier to spot.

Illustrative example: a seller swaps phones

A seller on a team of 10 upgrades to a new phone and cannot sign in to the CRM or mailbox. The manager confirms the request by calling the number on file, not the email address the seller just sent. The old device is removed from the account security settings. An administrator resets the mailbox sign-in and checks forwarding rules. The seller then signs in to the CRM from the new phone and a desktop browser, sends a short internal email, and logs a note. Each check passes, so the manager closes the ticket and updates the recovery inventory.

Step 4: Prevent the next lockout

Recovery is cheaper when the team has already decided how it will work. Use the lockout as a reason to build a few habits.

Start with a recovery inventory. For each seller, record which second factor the account uses, which device holds it, which administrator can reset it, and what alternate route exists. Keep it in a place the management team can find, but restrict access to the people who need it. A spreadsheet with access controls is usually enough for a team of this size. Review it when someone joins, leaves, or changes phones.

Next, make phone changes a scheduled event. Put phone replacement on the same checklist as onboarding and offboarding. A sales rep exit form is one place to start for offboarding. Ask sellers to set up the new device while the old one still works, so transfers such as the Authenticator move in step 2 are possible. Then set a date to remove the old device from every account. The goal is that retiring a phone is a planned step, not something that happens in the middle of a quarter when a seller needs to send a proposal.

Use more than one route where your product allows it. HubSpot's 2FA page says that one part of its setup helps you keep access to your account if you lose your 2FA device. Read that page for your plan, identify the setup step it describes, and confirm that every seller has it in place before they need it. Remember that the options vary by plan and region, so check your own account rather than relying on a general article.

Check app and operating system versions on managed phones. The Microsoft example shows how an outdated companion app can block registration even when everything else is correct. Add a version check to your quarterly routine, so a seller with an old app does not discover the problem during a phone swap. The same goes for the phone's own operating system if your team relies on a built-in security key.

Finally, practice the process. Once a quarter, pick one volunteer seller and walk through a simulated lockout with an administrator. Time how long it takes, note where the steps stalled, and update the inventory. A rehearsal finds gaps that a written checklist will not, such as an admin who no longer has access or a phone number that changed without anyone noticing.

Make ownership explicit as well. Assign one person on the management team to own the recovery inventory and the quarterly check, and name a backup for when that person is away. A process that depends on one person's memory is fragile, and small teams are especially exposed when the one person who knows the setup goes on leave.

Start before the next phone changes hands

A phone change is ordinary. A multi-day lockout is not inevitable. Knowing which factor the account used, who can reset it, and whether the new phone can complete the sign-in makes the next lockout shorter. If you answer those three questions for each seller now, the next swap becomes a routine task rather than an open-ended search.

Next step for today

Today, write down which second factor each seller's account uses and which phone holds it. Keep the list in one place; it becomes the first version of the recovery inventory in step 4.

Frequently asked questions

What should I do first when a seller loses their phone?

Verify the request through a channel you already trust, then remove or neutralize the old device from the account.

Can authenticator codes move to a new phone?

For Google Authenticator on HubSpot, codes can be transferred to a new Android phone, so check HubSpot's page for the transfer requirements before you plan around it.

Can a 2FA text code go to any number?

Not always. HubSpot's page says the countries that support SMS 2FA are the same as the supported countries for calling, so confirm the number can receive codes.

Sources

  1. Who is protected in pay talks: 4 facts for sales managers
  2. Equal pay for sellers: 5 official sources to compare
  3. Sales rep exit form: 8 fields for file requests and access
  4. Seller daily time
  5. Commission overpayment: 5 checks before you recover it

More plays