What are Journeys?
Think of Journeys as a workflow of workflows. They enable the linking of multiple workflows together allowing for multi-step applications using a single configuration and endpoint. For example, if an applicant is approved via an Onboarding workflow, they can automatically be passed to a Credit Underwriting workflow. Document verification and other step-ups can also be configured seamlessly in a Journey.
A key benefit of Journeys is clients can run multiple workflows in sequence without having to manage the status of an application between steps. Alloy manages the state of each application, offloading work from client engineering teams. Journeys push applicants from step to step without client teams having to manage the process manually. Clients can still be informed of the status of each application by subscribing to Journey webhooks as every step within a Journey emits a webhook.
Journeys support joint applications and business applications, essentially handling individual onboarding, business onboarding, and a reconciliation outcome all in one API call.
Alloy shows all entity evaluations that are part of the Journey in a single interface, simplifying navigation. For example, Onboarding and Credit Underwriting evaluations for an entity are included in a single interface, as well as Individual Onboarding and Business Onboarding evaluations.
Router functionality is built directly into Journeys with the start node and branches.
In a single Journey, entities can be passed to different branches based on the payload of the entity array. In each entity array, the branch of the Journey to which an entity will be routed can be defined. This can be used for market segmentation across applicants.
Journeys can only be used with Onboarding, Credit Underwriting, and step-up workflows at this time. Transaction Monitoring is not currently supported.
How to Create a Journey
- Journeys must first be enabled in client accounts. If Journeys is not enabled, contact your CSM or firstname.lastname@example.org.