Clients using Journeys can now set and save filters as a Saved Search within the Application Queue to create more simplified and efficient custom review queues for different role types.

A Saved Search can be assigned to a specific role within the Settings page. Once assigned, users with this role type will automatically see applications with the pre-set filters from the Saved Search. For example, if a Saved Search is created with filters for applications that require a fraud review and then assigned to the fraud team, this team will only see applications that require a fraud review without needing to manually filter for them each time.

To get started, navigate to the Application Queue and set the filters you want. Next, click the ‘Save Search’ button on the top right.

You will then be prompted to enter details about the Saved Search such as name, description, and whether the search is to be viewable by all employees. Click Save once you’ve completed the required fields.

To view all the Saved Searches in a particular account, navigate to Settings > Searches.

To assign a Saved Search to a role, navigate to Settings > Roles and click on the role. Next, click on the Default Searches tab and you’ll see a dropdown for the Application Queue. If you click on the Application Queue drop-down, you’ll see a list of all the saved searches and you can select the one you’d like to assign to that role type.

Clients can now set custom review types and outcomes in Journeys to fit their risk policies and allow their teams to work more efficiently. Previously, only the default Manual Review type and Approved and Denied outcomes were available.

To configure a custom review type, go to the Journeys page and click on ‘Manage Actions’ on the top right. Click ‘Add Action’ on the Actions page.

Indicate the name of the custom review type in ‘Action Name’ and select ‘Review’ as the Action Type. To configure a custom outcome, click ‘Create New Outcome’ at the bottom of the window. Once you’ve completed the prompted fields, click ‘Save’ and this review type and its associated outcomes will now be saved and ready for you to use within a Journey.

The new review type can then be configured in a Journey under the ‘Review’ dropdown menu. Please note: the Manual Review option will still be accessible by default and will only have an approved and denied outcome.

The Alloy SDK now supports the Prove Pre-fill flow. Prove Pre-fill pre-populates application forms with verified identity information, and displays it to the user for confirmation or further edits, reducing consumer friction and fraud.

To get started, simply select "Prove" as a plugin option in your workflow if you are already using the Alloy SDK. Dashboard setup instructions are here and API docs are here. Reach out to your CSM if you'd like to get it set up.

Transaction Monitoring clients can now set up sanctions screening checks for the counterparties that their users are transacting with to ensure ongoing compliance and mitigate counterparty risk. The transacting counterparties will be checked for exact and ‘fuzzy’ matches (e.g. abbreviations, misspellings, transliterations) against the most up-to-date watchlists using our data providers.

As with entity sanction screening, results are surfaced in Case Management to allow agents to take prompt action upon suspicious activity.

To get started with ongoing sanction screening, please reach out to your CSM or [email protected].

The Alloy SDK now supports the Vouched document verification flow. Vouched leverages proprietary artificial intelligence to fully verify identity and onboard users in seconds.

If you’re already using the Alloy SDK, simply select "Vouched" as a plugin option in your workflow.

No code changes are required. Dashboard setup instructions are here and API docs are here. Reach out to your CSM if you'd like to get it set up.

The Alloy SDK now supports Socure's document verification flow. If you’re already using the Alloy SDK, simply select "Socure" as a plugin option in your workflow. No code changes are required. Dashboard setup instructions are here and API docs are here. Contact your CSM if you'd like to get it set up.

If you’d like to see a demo or learn more about the Alloy SDK watch our “Using the Alloy SDK to optimize customer onboarding” webinar.

Clients can now set expiration dates for Journeys which will move applications to an end state based on the configured time-frame. This ensures applications do not remain in a pending state indefinitely and enables more accurate reporting on application decisioning.

To set an expiration time-frame for a Journey, navigate to the Journeys page and click on the ellipsis menu for the Journey and select ‘Set Application Expiration’.

Toggle the ‘Expiration Off’ button and set the expiration timeframe in the ‘Days to Expiration’ field before clicking ‘Save’.

If an application then runs through this Journey and hits the expiration date, the application will automatically move to a ‘Expired’ terminal node and end state.

The login page now has a new look and feel. When navigating to your Alloy instance, you’ll notice a newly designed experience with the same reliable login functionality.