Confirmation Use Case

Occasionally our customers want their end users to be able to confirm if the information extracted from a Gov ID is correct. For example, with long names on passports the format limitations of the Machine Readable Zone (MRZ) might lead to their full first name being shortened in the MRZ. Having a confirmation screen where the end user can flag the incorrect name and provide the correct name, allows corrections to be flagged for manual review.

This guide covers two ways to modify an inquiry flow with a confirmation screen without affecting verification results.

Goals

Create a confirmation page that will:

• Display extracted PII
• Allow end users to flag the PII as incorrect
• Allow end users to input the correct PII
• Preserve extracted PII

Starting Point - Gov ID (front side) Solution

For this walkthrough our shared starting point is the Gov ID (front side) solution. We’ll be making some quick additions to this solution in the form of 1 new confirmation screen step and 1 branching logic step.

Creating the new Screen

By the end you’ll have a new confirmation screen that will ask the end user if their extracted first and last names are correct. If incorrect, it will provide fields to input the corrected versions.

Steps

1. Add new Step. Click the add Step node in between the Update Account Fields step and the Success screen.
2. From the available Steps, select Screen.
3. A new Screen will be populated. Mouse over it and when the edit button appears at the bottom left, click it.
4. This will open the Screen Editor. At the top right, where is says New Screen, click the edit icon and rename the screen to something more descriptive like “Name Confirmation”.
5. On the left is the Component Library. In the Basic section, note the Tile and Text components. Click and drag out the Title component and place it above the Continue button, and then place a Text component between them. When you have Title component selected, the properties window on the right will show the editable text window. Update it to something like “Verify Data”.
6. Note that any time you modify the test field, the Edit translations button below it will flag an alert. Click the Edit translations button. Within the widget, you can manually update the test in a variety of languages and/or click Translate All for the system to handle those updates for you.
7. Repeat step 6 for the Text component between the Title and Continue button. Enter a message / instruction to your end users like “Does the extracted information match what is on you ID?”. The question you ask should reflect your specific use case. In the use case of a Passport MRZ shortening the first name, the question might be “Is your first name longer than what is displayed?”.
8. To display the extracted PII from the Gov ID, we’ll go back to the Component Library and scroll to the bottom of the Forms section for the Text input component. Drag two of them above the Continue button.
9. Select the top Text input. We’re going to modify it to display the extracted First Name. On the right in the Properties, scroll down to the Translations and update the Label from “Text Input” to “First Name”. Then edit the translations as we did previously.
10. Since we want this input to populate with data from the “name first” field, we next need to navigate to the Fields section on the right.
11. For the Fields section, first set Required to No so we don’t force the end user to make any changes. Then we want to update the Field, via the drop down, to the existing field of “Name First”.
12. Repeat the same process for the second Text Input component, updating it’s Label, Required, & Field.
13. Since the end user needs to be able to respond to your prompt / question, we’ll next add a Checkbox component from the Forms section. Place it above the Continue Button. For clarity, you should update the checkbox’s label, under Properties, to specify what they are checking off. We can then build logic for other components on the screen and for after the inquiry.
14. In the case that the information is incorrect and you want the end user to provide the correct names, we’ll next add two additional input fields, link them to new inquiry fields and make the input only appear when the checkbox is selected. Start by dragging out two new Text input components and placing them between the checkbox and the Continue button.
15. For the first Text input, update the Label to something like “Correct First Name”.
16. In the Fields, we’re going to set the Required to Conditional. If the checkbox isn’t checked, we don’t want to require it. Then click in the Required Rule below to open the Logic Rule editor. Configure the rule as below:
17. For the Field, go to the Field Label and enter a new field name like “CorrectFirstName”. This will also update the field dropdown above to “CorrectFirstName (New Field)” indicating its is creating an new inquiry field. This is important as we don’t want to update the existing “Name First” inquiry field with the extracted first name.
18. To start with this field hidden, and then to reveal it after checking the checkbox, switch from Fields to Logic on the right. On Screen Load we want to Hide the component. Click in the On Screen Load logic rules to add a rule.
19. In the Logic Rule editor, in the Apply Component Update select Hide Component.
20. For the Rule, select the “field_values” object. Then type “in” to search for “input_checkbox”. Then set the Value to “true”.
21. To make the Component appear when the checkbox is check, we next need to move down to the On Screen Update, and place a near identical rule. The key difference is that the value needs to be set to “true” instead of false.
22. 22. For the other Text input component for the Correct Last Name, repeat steps 15-21, making sure to switch the Label and Field to reference Last Name instead of First.
23. Within your screen editor your new screen should look like this:
24. Nav back to the flow. Next we need to add some branching logic that will use that checkbox from the Confirmation screen and will Tag the inquiry. Click in the Node between the Name Confirmation screen and the Success screen.
25. Select Branching. And then click into “Route 1”.
26. Rename route 1 to “Correct” or “Name Correct”. Set the logic to “trigger.fields.input_checkbox” equals “false”.
27. Along the “Else” branch, click the Node to the right of it.
28. Select “Action Sequence”.
29. Click the edit icon on the Placeholder Action.
30. In the Action configuration, in the Action field type “Tag Object”.
31. You’ll then be prompted to select an existing Tag or create a new one. When creating new Tags make them descriptive like “NameCorrected”. Close the Action and nav back to the Flow.
32. Click the node to the right of the Tag Object Step. Select Connector. Then Select the Success screen. Now this else branch will Tag the inquiry and then move to the Success screen to finish the Inquiry.
33. Save and Publish the Inquiry.

Testing with Preview

To ensure your template is providing the experience you want for your end users, you can switch to your Sandbox environment and Preview your inquiry flow.

Tagging for Manual Review with Workflows

After the inquiry is complete how can you efficiently process the inquiries with corrected names? With a workflow, you can create branch that checks for the Tag you applied to the Inquiry. Then within the branch, you can update the status of the inquiry from Completed to Needs Review. And if you have Cases enabled, you can create a case to help facilitate that manual review process.