Send Cloud Voice App Login Credentials to Users

Once you have enabled the Cloud Voice App for your users, they still need their sign-in details before they can start using it. You have two ways to hand those details over: send an automated welcome email for one-tap login, or share the account information so users can sign in manually.

Tip

The welcome email is the easiest path for most users, because it signs them in with nothing to type. Reach for the manual details only when a user cannot receive or open the email.

Send welcome emails for quick login

For most users, a welcome email is the fastest route in. Each email carries a login QR code (QR stands for Quick Response, the square barcode you scan with a phone camera) and a login link that take the user straight into the Cloud Voice App with nothing to type.

Before you begin

• Email delivery: Confirm that the system email server is configured and sending mail correctly.
• Extension setup:
  • Each target extension has an email address on file.
  • Each target extension has at least one Cloud Voice App client enabled.

Caution

Both requirements are easy to miss. If the system email server is not set up, or an extension has no email address on file, the welcome email will not go out and the user simply receives nothing. Check both before you rely on this method.

Send the emails

1. Sign in to the PBX (Private Branch Exchange, your phone system’s admin portal) web portal and open Extension and Trunk > Extension.
2. Select the checkbox for each extension you want to notify, then click Welcome Email above the extension list.

Every selected user receives a welcome email. They can scan the QR code or tap the login link to open the Cloud Voice App already signed in.

Caution

The QR code and the login link each work only once. If a user needs another try after the first use, send a fresh welcome email.

Share login details for manual sign-in

If a welcome email never reaches a user, or they cannot get to their inbox, give them the details to sign in by hand instead.

Provide the following:

• The PBX domain name (this is the network address of your Cloud Voice App server that the client connects to)
• Their username, either the extension number or the email address, depending on the login mode you have set
• The extension’s user password

Note

The username must match the login mode you configured. If the mode expects an extension number and the user enters an email address (or the reverse), the sign-in is rejected. Tell the user which one to use.

With these in hand, users can type the details directly into the Cloud Voice App to sign in.

Caution

An extension’s password lets that account place calls on your system. Send it over a secure channel and avoid leaving it sitting in email or chat threads. Leaked credentials are a toll-fraud risk.