Skip to content
English
Sign in
Submit a Service Request
  • There are no suggestions because the search field is empty.

IDgo "pre-enroll" process overview

Describes the purpose and an overview of the IDgo "pre-enroll" process

The purpose of the IDgo "pre-enroll" process is to enable enterprises to have an alternative to live agent enrollments that:

  • Enables enterprises to leverage consumer mobile phone numbers and consumer data that is already on record with the enterprise druing creation of IDgo accounts.

  • Does not require live agents to enter member data.

  • Can be focused on a subset of consumers, e.g., frequent callers to the contact center, to optimize use of IDgo.

The pre-enroll process has the enterprise securely sharing with the IDgo team data files of their consumer data that have been filtered for criteria established by the enterprise.

The following are the recommended steps to utilize the IDgo Pre-Enroll for an enterprise:

Step 1: The IDgo development team configures a secure FTP site and access credentials for use by the enterprise.

Step 2: The IDgo customer prepares an IDgo Pre-Enroll file based on the IDgo Pre-Enroll specification. The IDgo customer prepares this file by analyzing it’s consumer base with the following in mind:

  • The file should include a mobile phone number on file for each consumer.

  • If the customer would like consumer names to appear when an IDgo authentication is completed, they can include consumer first and last name data in the Pre-Enroll file.

  • The enterprise can include a unique identifier for each consumer in the Pre-Enroll file data to enable identifying which consumers have an IDgo account in the enterprise's database.

  • It is recommended the enterprise choose a timeframe in which to exclude consumer accounts that have had consumer profile information (e.g., mobile phone number) change within the chosen timeframe, e.g., in the past 30 days.

  • It is recommended the enterprise exclude consumer accounts without phone numbers or where one phone number is shared between consumers.

  • It is recommended the enterprise exclude consumer data for accounts where there is a history or concern about fraud.

  • Entries that include bad phone number data or land-line phone numbers will be filtered out by the IDgo Pre-Enroll script and reported as "no IDgo account created".

Step 3: The enterprise can establish the frequency of how often they would like to update the pre-enroll database with additions and deletions of Pre-Enroll consumer data.

Step 4: Upon receipt of the Pre-Enroll file from the customer, the IDgo team runs a IDgo Pre-Enroll script to create IDgo accounts for each consumer. This process produces resultant files stored at the customer’s FTP site that the customer can review and use to identify which consumers have and do not have IDgo accounts and the reasons why accounts were not created.