This article aims to highlight the supported modes and common issues with 2FA codes during the setup of chat networks on Beeper.

Supported Modes

Currently, for chat apps requiring 2FA during setup on Beeper, we support SMS or TOTP-based Authenticator apps such as Google Authenticator. One exception is the Telegram app, where Telegram sends a code within the app in one of the already logged-in Telegram client sessions. 

We do not support security key mode (e.g. YubiKey) at the moment.

Common Issues with 2FA Codes

Often, if you're using SMS for 2FA, there might be delays in receiving the code; if you request another code, the codes might get mixed up. Check for the latest code and make sure you enter the right one.

Also, SMS is heavily dependent on carrier networks, countries, services used by the sender, etc., and is not very reliable from a delivery standpoint. Here are a few things to look for:

• If you use a VOIP number like Google Voice, note that not all apps send 2FA SMS codes to a VOIP number. Try with regular SMS or Authenticator in case of issues.
• If you use SMS for 2FA and did not receive one, try switching to Authenticator.
• If you still have any issues, get in touch with Beeper Support via help@beeper.com or submitting a Report. How do I report a problem?