Using Call

Turning On Two-Factor Sign-In in Call: A Step-by-Step Guide

Why a password alone is not enough, how two-factor sign-in works with an authenticator app, how to set it up, store recovery codes and handle lost phones.

Call editorial team · Published · 5 min read

Passwords fail in boring ways. People reuse them across sites, type them into fake pages, share them with colleagues and write them on notes. When a call system holds recordings, transcripts and customer details, a stolen password is a serious problem. Two-factor sign-in adds a second step so that a password alone is not enough.

A person holding a phone showing a six-digit code next to a laptop sign-in screen
Illustrative image

This guide explains how it works, how to turn it on, what to do with recovery codes and how to handle the awkward moments: a new phone, a lost phone, or a colleague who is locked out. It pairs with roles and permissions, which decide what a signed-in person can do.

How two-factor sign-in works

Sign-in normally checks one thing: the password. With two-factor sign-in it checks two kinds of evidence. The first is what you know, your password. The second is what you have, a phone that produces a short code. Anyone who steals your password still cannot sign in without your phone.

What happens at sign-in

  1. Enter email and passwordYou sign in as usual.
  2. The page asks for a codeA screen titled Two-factor authentication appears.
  3. Open your authenticator appIt shows a six-digit code that changes every half minute or so.
  4. Type the codeEnter it in the Authenticator or recovery code box.
  5. ContinuePress Verify and continue and you are in.

An authenticator app generates codes on your phone from a secret that you share with the service once, during setup. Because the codes come from the app and change constantly, they are of no use to someone who sees one over your shoulder a minute later.

Why it is worth the extra step

What two-factor protects against

  • Reused passwordsA leak from another site no longer opens your account.
  • GuessingA guessed password is not enough without the code.
  • Phishing, partlyA fake page may capture a password, but not your phone.
  • Shared loginsIt makes people notice when a login is shared, because the phone is personal.
  • Departed staffA former colleague who remembers the password still cannot sign in.

No measure is perfect. Two-factor does not help if the phone itself is compromised, or if a person is tricked into reading a code to a stranger. Treat it as a strong layer within a wider habit of care, not a magic shield. The most important accounts, especially those with admin rights, benefit most.

Setting it up in Call

You turn on two-factor in Admin, in Security, on the Two-factor authentication card. You need an authenticator app, such as Google Authenticator, 1Password or similar, installed on your phone.

  1. Open Admin, then Security, and press Turn on two-factor.
  2. The page shows a secret under Add this to your authenticator app. Enter it into your app, as the app instructs.
  3. The app now shows a six-digit code. Type it into the page and press Confirm.
  4. The page shows your recovery codes. Save them somewhere safe, then press I have saved them.

To switch two-factor off later, press Turn off on the same card, enter the current code from your app, or a recovery code, and press Turn off again. It cannot be switched off without a code, which means a person at an unlocked computer cannot quietly remove it.

Recovery codes: your spare key

Recovery codes are one-time codes that stand in for the app code if your phone is lost, broken or wiped. You type one into the same box at sign-in. Treat them as spare keys.

The people problems: new phones, lost phones and shared roles

Most trouble with two-factor is not technical. It happens at the edges of ordinary life.

SituationWhat to do
New phoneBefore wiping the old phone, move your authenticator accounts across, or turn two-factor off and on again on the new phone. Check the new one works before you retire the old one.
Lost phoneSign in with a recovery code, then set up two-factor again on a new device. With no codes, ask a colleague with the right role to help.
Shared loginGive each person their own account; a shared account cannot sensibly share a phone. See roles for what each person needs.
Colleague on leaveDo not share codes. When they return, they sign in with their own phone as usual.

Choosing an authenticator app

Any reputable authenticator app that generates time-based codes will do. A few practical points help you choose.

If codes are rejected, the first thing to check is the phone clock. A phone whose time is even a minute out can produce codes the service does not accept. Switch on automatic time, wait a moment and try the next code.

Rolling it out to a team

A good time to introduce two-factor is before an incident. Do it calmly and give people a reason.

Rollout checklist

  • Start with owners and admins, whose accounts can do the most
  • Explain why, in plain words, and show the setup steps
  • Ask everyone to save their recovery codes the same day
  • Agree who people contact if they are locked out
  • Remove accounts of people who have left
  • Re-check a few weeks later who has not completed setup

Remember that two-factor is set up by your workspace's administrators and owners from the Security page, not from the sign-in page. If a colleague cannot find the option, ask an administrator to check their role. Other habits add to the protection: unique passwords, a password manager, and a short regular check of who still has access.

Habits that make it work

A control that people resent gets worked around. Keep two-factor sensible. Explain that the extra step takes a few seconds, that it protects customers as well as the business and that nobody is being singled out. Make the recovery plan visible so a locked-out person knows whom to ask without embarrassment.

A hypothetical small agency with a dozen staff could roll it out on a Monday: five minutes at the start of a team meeting to set it up together, with everyone saving their recovery codes while the admin watches the clock. By lunchtime it is done, and the questions that followed in the first week were about new phones, not about sign-in. For the question of who can do what once signed in, continue with roles in Call.

Frequently asked questions

Which authenticator apps work?

Any app that creates time-based six-digit codes should work, such as Google Authenticator or 1Password. Use one you already trust and keep it backed up.

What if I lose my phone?

Sign in with one of your recovery codes, then set up two-factor again on a new device. Keep the codes somewhere other than the phone.

Can I turn two-factor off?

Yes, from the same card in Admin, in Security, but you need the current code from your app or a recovery code. It cannot be switched off without a code.

Are the secret and recovery codes shown again?

No. They are shown only once during setup, so save them before you leave the page.

Does two-factor replace my password?

No. You still sign in with your email and password. The code is an extra step after that.

Who should use it first?

Owners and admins, because their accounts can change settings and see the most data. Then roll it out to everyone else.

Turn on two-factor sign-in for your Call account

In the demo console you can try incoming calls in a simulation.

Related guides