Clients using Journeys can now more comprehensively test and optimize the performance of their policies by utilizing Champion Challenger to test different versions of their Journey. Champion Challenger is a tool that allows you to A/B test up to 5 different versions of your decisioning logic and evaluate the differences in performance between the decisioning logic. Previously, Champion Challenger was only available for testing at a workflow level.

To get started, navigate to the Journey Versions page for the Journey you wish to test. Click on the vertical ellipsis menu of a draft version that you want to test against the active version (champion), and then click Run Test which will bring you to the Testing Suite.

Select Champion Challenger to start configuring your test.

Next, select up to 4 versions you want to include in your test. The active version of your Journey (aka the Champion) will be selected by default.

Then, configure the percentage allocation for each version. You can also choose to enter a sample size and start and end date on this screen. The Champion Challenger test will automatically end once either the sample size or end date is reached.

On the last screen, confirm the details of your test and click Start Test.

You will then be able to view progress and results of the test on the Journeys Versions page.

Agents using Journeys can now escalate applications to other agents within a specific role type, allowing for more efficient review of applications and streamlined collaboration among teams.

Once the application is escalated, it automatically will be assigned to an agent within that role that has the most bandwidth. Agents who receive the escalated application will be notified in the dashboard and will also see an escalated badge next to the application within the Application Queue.

To get started, navigate to the Application Queue and select an application. In the Application view click the vertical ellipses menu on the top right corner and the click on ‘Escalate Application’.

You will then be prompted to enter the following details: the role type you’d like to escalate to, the reason why you’d like to escalate, and any notes you’d like to leave for the agent that is receiving the escalated application. Click ‘Submit’ once you’ve completed the required fields and you’ll receive a confirmation message that says the “Application escalated successfully”.

Agents can check if they’ve been assigned an application in the Application Queue in the column ‘Assignee’ followed by an orange escalation badge. The escalation badge will disappear once the agent takes an action on the application.

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.

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].

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.

SDK Theme Customizations

Clients using the Alloy SDK can now customize colors and components for Alloy-built plugins in the SDK. This feature allows Alloy clients to style plugins to better match their own branding. For example, this SDK matches the green and grey colors of the company.

There are three ways to pass styling into the SDK, listed in hierarchical order:

1. initParam.colors (the color parameter that previously existed in the SDK init params)
   1. “Primary” will override the color of the buttons
   2. “Secondary” will override the hover color of the buttons
2. initParam.customStyle.componentOverride
3. initParam.customStyle.theme

See API docs for more details here.

Clients can now have applications automatically assigned to agents when they require a Review. This feature evenly distributes applications across all agents that have permission to review an application.

Instructions below

1. If a client wants to use the auto-assignment functionality, they’ll need to add permissions to the specific role types through the ‘Settings’ page

• The ‘Agent can be auto assigned Journey Applications’ permission should be checked off

2. Once that permission is added, anytime an application requires a Review, it’ll be automatically assigned to the agent with the least number of applications assigned to them.