Clients using Journeys can now assign permissions to determine which Roles can view select Journeys, enabling clients to maintain separate access for their agents based on their organizational structure and business needs.

To get started, navigate to Settings > Roles. To enable access to all Journeys for a given Role, from the Roles section, check the top-level option ‘Journeys’. This means this role will have access to all non-archived Journeys (including draft versions) in the account, in addition to all Applications, Workflows, Evaluations, Reviews, and Entities associated with those Journeys. To restrict access to specific Journeys, choose the Journeys in the drop down – this will allow the user to have access to all Applications, Workflows, Evaluations, Entities, and Reviews that are associated with the Journey(s) selected there. To restrict access to Journeys altogether, deselect the top-level ‘Journeys’ option.

Note: these permissions will not override access for users who have access to ‘All workflows’ in Settings > Workflows.

Clients using the credit panel will now see a broader set of credit report and tradeline data from the credit bureaus in the US, enabling them to conduct holistic and robust credit reviews. Previously, the credit panel only surfaced data from Experian.

The following data sources will now be surfaced in the credit panel:

Equifax

• Consumer credit data
• Business credit data
• Tradelines for Equifax consumer and business credit

Experian

• Tradelines for consumer credit (Experian consumer credit and Experian Netconnect)

Transunion

• Consumer credit
• Tradelines for consumer credit

View and Create Published Attributes Values in the Entity view

Clients using Published Attributes can now view and edit (which includes creating new values) Published Attributes values, allowing for more holistic and flexible decisioning. ‘Published Attributes are custom entity-level attributes that you can define and use in your decisioning throughout the customer lifecycle.

Published attributes can be viewed and edited directly in the Entity view or Entity Side Panel. You can view the most recent 5 values. Please note: in order to create a new Published Attributes value, users must be appropriately permissioned (Settings > Roles > Published Attributes)/

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.

The Alloy SDK web plugin now supports a wider range of business documents with a new document type ‘Business Document’, which allows clients to more flexibly configure their chosen business document (e.g. Articles of Incorporation) without having to choose from a pre-set menu of options.

On the SDK Configuration screen, clients will be able to select the option ‘Business Document’ and optionally enter help text to guide the user during the document upload process (for example: “Please upload your paystub as secondary income verification”.

Dashboard setup instructions for the Alloy SDK 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 the Persona documentation verification flow. Persona provides identity verification with extensive global coverage and liveness detection.

If you’re already using the Alloy SDK, simply select "Persona" 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.

Clients can now view global identity data identifiers (such as national ID # or business registry ID) in the Alloy dashboard in addition to being able to utilize these identifiers in their decisioning, making the Alloy platform more accessible for users across the world.

Starting today, clients can see and leverage global identity attributes on all Alloy dashboards and tools including (but not limited to): Entity page, Entity and Business Evaluations pages, Workflow Rule Builder, Identity Element Velocity, and Allow/Denylists.

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 can now self-service their SDK key directly in the Alloy dashboard. Previously, clients had to rely on Alloy admins to create the SDK key.

Simply select ‘SDK Key’ from the Settings’ menu to view your unique SDK key. To create a new key, click the ‘Generate new key’ button and respond to the prompt to confirm the action. Please note, generating a new key will require you to update any existing code. You will also be able to view and amend Alloy List domains on the same page.

Agents must be appropriately permissioned to view and generate keys.

If you’d like to get set up with Alloy SDK, please reach out to your CSM.