Bloomington Caregivers has replaced its legacy Contact Center application with Health Cloud. During user acceptance testing (UAT), the call center team is reporting differences between current Identity Verification business processes and what was built in Health Cloud.
The call center manager has requested the following changes:
* Birth Date be available in results and as an optional verifier, but no longer required for verification purposes
* Add 'Bloomington ID', a custom field on Account, to search results and as a required verifier
What should a consultant do to meet these requirements?
To meet the requirements of the call center manager for identity verification, a consultant should do the following:
Add two new Identity Verification Process Field records for 'Bloomington ID'; one with Field Type set to Result Field and one with Field Type set to Required Verifier: This step allows the consultant to add 'Bloomington ID' as a custom field on Account to the identity verification process.The Result Field record type makes the field appear in the search results, while the Required Verifier record type makes the field mandatory for verification purposes5.
Change the Birth Date record with Field Type value Required Verifier to Optional Verifier: This step allows the consultant to change the status of Birth Date from a required field to an optional field for verification purposes.The Optional Verifier record type makes the field appear in the verification screen, but does not require a match for verification6. Adding 'Bloomington ID' to the picklist choices within the Identity Verification flow, removing Birth Date from the required fields picklist, adding Birth Date to the optional verifiers picklist, deleting Birth Date record, or adding new record to Lightning component parameters are not valid steps for this task.