Skip down to the research record

SMS 2FA for a rep's sign-in: 3 reasons to avoid it

Quota Forecast Editorial Team · Published · 12 min read

SMS 2FA is a poor default for many rep sign-ins, because text codes can be taken over through SIM hijacking.

Sign-in rules for reps tend to get decided quickly. A leader asks for two-factor login on the CRM, the admin picks whatever the setup screen offers first, and the question is closed. Text-message codes are often that first option.

Convenience makes SMS easy to choose. It does not make it the right choice for every rep's account.

Key takeaways

  • Check whether the CRM requires a second factor on every sign-in path, including single sign-on.
  • Where the tool offers one, use an authenticator app or passkey instead of text codes.
  • Keep text codes only for logins where no other method is available, and write down each exception.
  • Set up a backup method before a phone is lost or replaced.
  • Test every login path with a test account before assuming it works.

A rep's login is worth protecting for practical reasons. It can open the contacts, deal notes, call history and forecast fields that the team relies on. It may also be the route into shared documents, email and pricing tools. When one account is taken over, the damage is rarely limited to one person's inbox.

This post follows one example case from start to finish. The rep works on a sales team that runs its pipeline in a hosted CRM. The rep signs in with a password, then types a code that arrives by text message on a personal phone.

Nothing has gone wrong. The question for the revenue leader is whether that text step should stay the default, and in which situations it should be ruled out.

Reason 1: A phone number can be moved to someone else's device

Text-message 2FA rests on one assumption. Whoever receives the code at a given phone number is the person who should be signing in. The code proves control of a number, and the service treats control of a number as proof of identity.

That assumption is weaker than it looks.

Bitwarden, a password manager, is direct about this. Its help page says that Bitwarden does not support SMS 2FA due to vulnerabilities, including SIM hijacking. Once that happens, the codes meant for the rep arrive with someone else.

This post does not explain how such attacks work. For a revenue leader, the point is simpler. A code sent by text only shows that someone holds the number, and holding a number can be taken.

The example rep's case shows how this plays out. Suppose someone outside the team gets that rep's password, perhaps through an email that looks like a CRM notice. Without a second factor, that password is enough to sign in.

With text-message 2FA, the attacker also needs the code. If the number has been moved, the code goes to them. The password was the weak point to begin with, and text-message 2FA can leave that weak point in place while looking like protection.

Reps are also easy to find. Their phone numbers often appear on business cards, email signatures, event lists and professional profiles. A number that is easy to find is also easy to aim at.

A rule about this does not need to assume an attack is already underway. It only needs to recognize that the code is tied to a phone number, and a phone number can change hands in ways a password never does.

Lost phones belong in the same picture. A phone that is stolen, cracked or replaced can cut a rep off from the code route. The person who has the phone may also be the one who can read the codes. Either way, the account depends on a device that sits in a pocket and changes over the years.

The same reasoning applies with more force to the people who can change the team's settings. A sales manager or an admin who can reset another person's login is a bigger target than a single rep. One takeover can reach many accounts at once.

When the admin role is protected by text codes, the weakest path into the whole team is a phone number that few people think to protect. Admin and manager accounts are often the right place to start a stronger method, even before the rest of the team moves.

Reason 2: SMS is a fallback, not a first choice

One help page gives a rule of thumb that works well in a sales policy. It says that any second factor is recommended over having none, but most alternatives are safer than SMS 2FA. It also says that it does not recommend SMS 2FA for other accounts unless it is the only available method.

Read together, these lines say the same thing from two sides. Text-message codes are better than no second factor. They should not be chosen when a safer method is on offer.

HubSpot, a CRM provider, reaches a similar position from the vendor side. Its help page notes that while SMS text message 2FA is available for Starter, Professional, and Enterprise accounts, HubSpot recommends using a passkey or authenticator app for stronger security.

The vendor offers the text option, which is useful to know. It still points customers toward something stronger. When the company that runs the product says this, a revenue leader has a solid basis for writing a stricter internal rule.

The second problem with SMS is reach. The same page says that the countries that support SMS 2FA are the same as the supported countries for calling. For a rep on a trip, that matters. If the rep's phone is in a country that does not support SMS 2FA, the code may not arrive at all.

A rep who gets locked out during a customer visit, a trade show or a late-night deal review has a real problem on their hands.

Lockouts also create their own risk. A rep who cannot get a code is tempted to borrow a colleague's login, or to turn off a protection just to get back into the tool. Those workarounds leave the account less safe than the rule was meant to make it.

A policy that makes the safe path hard to use will push people toward the unsafe one. The rule has to be checked against what reps will actually do on a bad day.

A single channel also creates a recovery problem. If the phone is lost, broken or replaced, the code route stops working until someone resets it. A rep who waits on an admin to fix a login is a rep who is not selling. This is why the rule should ask whether a second method exists, not only which method is the default.

There is a fair objection to all of this, and it deserves a direct answer. Some reps will say that a text code is quicker. On a good day that is true. A code arrives, it is typed, and the rep is in.

But the speed of the text step is the same speed that makes it easy for a stranger to use. The answer is not to give up speed. It is to make the stronger method just as quick to use.

Setting up an authenticator app or passkey during onboarding, rather than in the middle of a busy week, means the rep never has to choose between a fast login and a safe one. Once the setup is done, the daily sign-in can be just as fast. Device checks to run first are in phone and app checks for reps before enrollment.

Reason 3: Stronger options are already in the tools reps use

The sources show this in several places.

The two options sit side by side on the same page.

A TOTP app is a code generator that runs on the rep's own device. The choice is between options the service already offers, not between SMS and some new system the team has to adopt.

Authenticator apps also have a practical side. The password manager's page explains that only the standalone app allows you to setup 2FA for your Bitwarden account, but you can use either app to store and generate verification codes for all your other accounts.

That sentence has a lesson beyond one product. A service may limit which app can set up its own 2FA, even though a general authenticator app can hold codes for many other accounts. Before a written rule names an app, check the setup requirements for each tool the team uses.

Third-party sign-in is the other gap. The CRM vendor's page says that if you're logging in with a third-party provider such as Google or Microsoft, you will not be automatically prompted to set up 2FA.

This is easy to miss. A rep may assume that the company's single sign-on covers them, while the CRM itself may not ask for a second factor on that login path. A leader who writes a 2FA rule should ask whether it applies to single sign-on too, and where the second factor is set.

Here are the options these sources name, side by side.

Sign-in optionWhat the sources sayWhere to read it
Authenticator app (TOTP)Recommended over SMS by the CRM vendor for stronger security. Listed by the code host as a TOTP option on mobile or desktop.CRM setup guide, Account docs
PasskeyRecommended over SMS by the CRM vendor for stronger security.CRM setup guide

For the example rep, the change is simple to describe. If the CRM offers an authenticator app or a passkey, the rep switches to it.

Writing the rule for reps

Start with what the tool requires, then set a preference, then close the gaps.

First, check the requirement before setting the preference. The vendor's page says that for Starter, Professional, and Enterprise accounts, 2FA is required for all users logging in with a username and password.

If the CRM sits on one of those plans, the real question is not whether reps use 2FA. It is which method they use. Writing the rule around that question avoids a policy that the tool would override anyway.

Second, set the preferred method. Ask reps to use an authenticator app or a passkey wherever the tool supports one. Allow text messages only where no other method is available.

Third, write down each exception. If a tool must keep SMS on for some logins, record which tool, which logins, and why. A short written reason makes it easier to revisit the exception later, when the tool adds a better option or the team changes its CRM. Exceptions that nobody can explain tend to become permanent.

Fourth, check every login path. Include single sign-on, and confirm that a second factor is required on those logins as well. Test the path yourself with a test account before assuming it works.

Fifth, plan for travel and lost phones. Make sure every rep has a backup method, so that one lost or replaced phone does not lock someone out of the account for days. The steps are set out in two-factor recovery steps before a rep loses a phone.

Sixth, explain the reason to reps. A rule people understand is more likely to be followed than one they only receive. Describe the phone-number problem in plain words, show the setup steps, and say who to contact when a code does not arrive.

A short walkthrough with screenshots from the actual tool is worth more than a long policy document nobody opens.

The rule also needs a clear scope. Decide whether it covers every rep, every manager and every admin. Decide whether it applies to contractors or part-time staff who use the same tools.

Shared logins deserve a separate line in the policy. A login that several people use cannot be tied to one person's phone, so a shared account should be replaced with individual accounts where the tool allows it. Where it does not, the policy should name who holds the second factor and how it is passed on, so that the team is not guessing during a handover. For a change to a shared login, see access log checks after a shared login changes.

Illustrative example: a 10-rep team

Suppose a team of 10 reps has 3 admins. The admins move to an authenticator app first, because a takeover of an admin login can reach many accounts. The reps follow, and each reads the same short walkthrough. Any login that still uses text codes gets a written reason, which is reviewed at quarter close. A lost phone then blocks one person's sign-in, and the backup method is already set up.

The outcome for the example rep, once these steps are done, is easy to state. The rep sets up an authenticator app, keeps a backup method in case the device is lost, and no longer depends on a number that can change hands or fail in another country. The password is still needed. The second step, though, no longer rests on the phone network.

Text-message codes are not the enemy. They are better than a password alone, and for some accounts they may be the only option a tool offers. The point of the rule is to stop treating them as the default for every rep, especially when a stronger option is already on the screen.

Next step today: open the security settings for your CRM account, list the sign-in methods it offers, and note whether an authenticator app or passkey is among them.

Related guides: Bulk-edit sales records: 4 checks before saving changes · Check 6 caption settings before the weekly sales call · Check 8 data rules before the weekly sales call.

Frequently asked questions

Should a rep's account ever use SMS 2FA?

Only as a fallback. The Bitwarden help page says it is not recommended for other accounts unless it is the only available method.

Which second factor should reps use instead?

Use an authenticator app or a passkey wherever the tool offers one, since HubSpot recommends either for stronger security.

Do single sign-on logins need a second factor?

Check them separately: the vendor says third-party logins such as Google or Microsoft are not automatically prompted to set up 2FA.

Sources