Blueprints allow you to define the investigation flow for the selected cases and decide which data will be displayed on the case page.

You can use one of four preset blueprints located on the Blueprints page or create your own blueprint.

Preset blueprints allow you to:

You can enter the selected blueprint template by clicking on it and adjust it to your needs by changing its name, adding assignees, or escalating the case to another blueprint.

Create custom blueprints

To create a new blueprint:

1. Navigate to Blueprints.
2. Click Create new blueprint. You will be directed to the General settings tab.
3. Enter the blueprint’s name and description (optional).
4. Select how the case assignment will be done. You can either manually pick compliance officers from your list or use the automated (load-based) assignment feature. If you selected automated assignment, pick officers from the list and set the number of cases that make automated assignment applicable. For example, you can decide to assign cases with a specific blueprint to the officers with fewer than 10 active cases. Then, the system will pick an officer from this group with the fewest cases and assign the next case to them. If the number of cases assigned to all selected officers exceeds the limit, new cases will be placed in a queue and assigned to an officer whose load falls below the limit first. These cases will also be available for manual assignment.

   📘

   Note

   If the operator you selected for load-based assignment is offline, they will not get any cases regardless of their current workload.

5. Set up case routing.
   • 4-eyes review allows you to have selected cases processed by two officers, the Maker and the Checker.
     

   📘

   Note

   • To enable the 4-eyes review flow, you need to have both Maker and Checker blueprints. The Checker blueprint needs to be created first, as it serves as a prerequisite for the Maker blueprint routing.
   • By enabling this functionality you enforce the strict system logic that blocks default escalation for the Checker.

   • Default escalation lets you automatically escalate the case to the selected blueprint. The blueprint defines who will process the case, so default escalation lets you send the case to the dedicated officer in a click.

   • Transfer to lets you move the case to one of the blueprints within the list.

6. Enter the blueprint’s name and description (optional).
7. Select the blueprint for case escalation. This will let the officer use another blueprint to process the case if more information is needed.
8. Select how the case assignment will be done. You can either manually pick compliance officers from your list or use the automated (load-based) assignment feature.
9. If you selected, load-based assignment, pick officers from the list and set the number of cases that make automated assignment applicable. For example, you can decide to assign cases with a specific blueprint to the officers with fewer than 10 active cases. Then, the system will pick an officer from this group with the fewest cases and assign the next case to them. If the number of cases assigned to all selected officers exceeds the limit, new cases will be placed in a queue and assigned to an officer whose load falls below the limit first. These cases will also be available for manual assignment.

📘

Note

If the operator you selected for load-based assignment is offline, they will not get any cases regardless of their current workload.

7. Switch to the Case page content tab.
8. Activate the Overview by Summy toggle if you want the AI case overview to be displayed.
9. Activate the Checklist toggle to create a Case checklist. Add checklist items as described in this article.
10. Select the data to be displayed on the case page and click Create to use the blueprint in your rules and levels.

You can include the following data: