Scott Freeman

Journey Applications created via the Alloy API appear in the Application Queue within the Alloy dashboard. The Journey Application is a single interface where all entities included in an applicatio...

Evaluations within a Journey Application that return a Manual Review outcome can be reviewed via the Alloy dashboard or the API. This article documents how to manually review an evaluation within a...

Similar to rerunning evaluations in Alloy, Journey Applications can also be rerun. Reasons for rerunning both evaluations and Journey Applications can include miskeys, frozen files, and data servic...

Reconciliation logic is needed for Journeys configured to evaluate joint applicants, businesses, or any other type of application which contains multiple entities. It is the high-level logic that d...

Alloy offers a Testing Suite for Journeys which includes Self Serve Batch Testing that can be completed via the Alloy dashboard or the API. Using an Alloy-provided CSV template, a batch of entities...

❗️ PII data in article is all fake for demonstration purposes Similar to the Review Queue for non-Journeys evaluations, the Application Queue is where agents action Journey Applications that requir...

The Journeys Overview states that a Journey Application can be initiated by calling a single API endpoint. You may be thinking, “how will we know the status of the Journey Application programmatica...

When configuring a Journey, there may be times when you want to account for an event that is not directly handled by the Alloy system, such as extending an offer to a customer or making a request t...

Building off of the Journeys Overview, the purpose of this article is to outline the steps to create an example Journey which includes Individual Onboarding, Document Verification, and Credit Under...

A certain tag firing may always trigger a Manual Review outcome based on a client’s workflow-specific outcome logic. During the Manual Review process, an agent may want to rerun an evaluation, igno...