Customer verification as a workflow step
  • 28 Mar 2023
  • 3 Minutes to read
  • Dark
  • PDF

Customer verification as a workflow step

  • Dark
  • PDF

Article Summary

At any point in your workflow you can include a step that verifies the identity of the customer and determines whether the customer is qualified to proceed with the steps that follow.

Using the ID verification results

You can use the verification pass/fail results in the following ways: 

  • Connect the verification step to two different elements, one for a pass result and the other for a fail result. For example, if the customer passes the verification they advance to an eSign step and if they fail, the workflow ends.
  • Map the pass/fail result to a boolean attribute (see below) and use the result in the workflow as a condition.

Types of customer verification

Lightico supports the following types of identity verification: 

Photo ID verification

Photo ID verification enables you to:

  • Verify that a photo ID is authentic.
  • Verify the customer identity by comparing a capture of their photo ID to a selfie taken during this verification step.
  • Extract data from the photo ID.
More information:

To add a photo ID verification step to a workflow:

  1. Drag the Photo ID Verification element from the right pane.
    The Photo ID  Verification dialog box opens.
  2. Select one or more of the Photo ID Verification documents.
    Verification is performed on only one of the documents, selecting more than one document enables the customer to choose one of the options. 
  3. To verify the identity of the customer by comparing their ID photo with a selfie, turn on the Compare identity with selfie toggle.
  4. To enable the agent to download an image file of the photo ID, turn on the Enable photo ID download toggle.
  5. To bind the pass/fail result of the verification to a Boolean attribute, select an attribute from the Authentication result dropdown.
  6. Click Done.
  7. Connect the Photo ID element to one element for a Pass result and one for a Fail result.
    If you would like the workflow to advance to the same step regardless of the verification result, connect both the Pass and the Fail connection to the same step.
  8. After adding the Photo ID Verification element to the workflow canvas, you can select it and edit it as follows:

  • To edit any of the settings, click the edit button and make the changes in the Photo ID Verification dialog box.

  • To duplicate or delete the document request, select it, click the 3 dots and select the relevant action from the context menu.

  • To rename this step in the workflow, click the Step Name and edit it. This is the step name that is displayed for the agent and customer during the session. 

Photo ID Verification has been successfully added to the workflow.

Phone-based verification

You can use phone-based identity verification in a workflow to authenticate the customer before entering the workflow or before performing a specific step in the workflow. You can also define what happens if the verification fails and bind the pass/fail result to an attribute for use in some other part of the workflow. For example, you can use the pass/fail result in a switch element further on in the workflow or create a condition in a dynamic document.

To add a phone-based verification step to a workflow:

  1. From the Add Item tab, add the Phone Verification element. The Bind verification... dialog box appears.
  2. Optionally, select a boolean (true/false) attribute or select None from the dropdown and click Done.By default, the Phone Verification element is added and connected to the start of the workflow.
  3. Connect the Phone Verification element to one element for when the customer passes the verification and to another one for when they fail.
    Pass = phone number is valid and the customer entered the correct OTP; Fail = phone number is not valid OR phone number is valid but the customer entered the wrong OTP (number of tries is defined in the integration hub.)

Alternatively, you can connect to the same element for pass and fail - then use the boolean attribute from the previous step to define how the verification result affects the workflow. 

Phone-based verification has been added to the workflow.

Was this article helpful?