(Please note that all PII shown in this document is fictitious and for demonstration purposes only.)
Outcome reasons are functionally tags that are tied to outcomes to shed light on why a specific evaluation ended up with a specific outcome. They can also be used to convey to the client the following actions that need to be taken within the review process. For example: if you know that when an evaluation is in Manual Review due to a KYC tag not being triggered, and you know that it will require a document to be uploaded for verification, we can create a more descriptive tag and attach an outcome reason to it.
Here's an example of our current best practices workflow - the additional blue tags at the far right are outcome reasons:
The logic here is that when certain KYC elements aren't verified, different documents will be required by the applicant. Using outcome reasons makes this easier to understand. Below, I've run an evaluation that triggered both "Name Not Verified" and "DOB Not Verified" tags, and created an outcome reason, "Driver's License Required", to flag when this combination of tags is returned. That way, when the application is being reviewed, the next course of action is clearer. Note: the tags returned remained in the "Tags" section, but the outcome reason is in its own section - this is an array, similar to the tags array below it.
In the raw response, the outcome reasons array can be parsed as well to signal further action:
This will also be visible in the Review Queue:
How to Create Outcome Reasons
Navigate to Settings > Tags
Click on the tag you wish to use as an outcome reason, and assign it an outcome.