Authentication

On this panel, you can configure the user authentication for this voice application.

Turn on the toggle to allow user authentication by their phone number (ANI). If authentication is successful, the user is not asked to enter a PIN and can dial the destination number right away. See more details in the PINless dialing handbook.

This option is available if the ANI authentication is enabled. It is useful when multiple users make outgoing calls under a single caller number (e.g., the company’s main phone line). With this option enabled, users will need to enter their unique authentication code to identify themselves.

When a user calls the voice application, the application finds the company’s main phone number (ANI) and the “company ID” value defined as Associated number), e.g., 534564. The application asks the user to enter their personal authentication code, e.g., 555. The call is then authorized and billed to the personal account with an ID consisting of the “company ID” followed by the # symbol and the authentication code, e.g., 534564#555. Refer to the Corporate PINless dialing IVR handbook for more details.

Specify the minimum length of the authentication code (by default, four digits).

Specify the maximum length of the authentication code (by default, four digits).

By default, this option is enabled and the voice application prompts the users to dial their PINs. If you are using ANI authentication, and it fails for some reason, this option allows authenticating the user by their PIN number.

Specify the maximum number of attempts for a user to enter a PIN (by default, three attempts).

If you enable this option, a user’s phone number (ANI) that is not found will be automatically added as an account alias. The next time a call is made from that phone number, it can be authenticated by the ANI.

This option is available when the Auto registration option is enabled. Turn on this option to allow registering a user’s ANI as an alias without confirmation. Otherwise, the voice application will ask the user to confirm adding the ANI number as their account’s alias.

Using this option, you can configure the voice application to additionally check an account’s service password, e.g., to increase the security of a PINless dialing service.

• None
  • For ANI authentication – the IVR application will never prompt the user for their service password after successful authentication by ANI.
  • For PIN authentication – the authentication will be successful only if the user’s account doesn’t have a service password specified. This is a common use case for prepaid card services.
• Always
  • For ANI authentication – the IVR application will always prompt the user to dial their service password.
  • For PIN authentication – the IVR application will prompt the user for their service password as long as the password is defined.
• Only PIN
  • For ANI authentication – the IVR application will never prompt the user for their service password. This is a common use case for ANI services.
  • For PIN authentication – the IVR application will prompt the user for their service password as long as the password is defined.
• Only ANI
  • For ANI authentication – the IVR application will always prompt the user for their service password.
  • For PIN authentication – it will be successful only if the user’s account doesn’t have any service password defined. This is a common use case for PIN services.

For example, in case of the Always or Only ANI options, the IVR will do the following: upon collecting an ANI number, the IVR prompts the user for their password and uses it for account validation (the password provided must match the account’s service password).

Specify the minimum number of characters for the valid service password (by default, 4 digits) that is used when creating the account in the Service password field.

Specify the maximum number of characters for the valid service password (by default, 4 digits) that is used when creating the account in the Service password field.