Set up blueprints
Standardize and automate case processing.
Blueprints are the foundation of Case Management. They define the investigation steps for a case and specify which data appears on the case page.
Sumsub provides four preset blueprints that you can customize to fit your needs.
| Blueprint | Description |
|---|---|
| Screening hit | Manage watchlist alerts and PEP screening results. |
| AML investigation | Investigate potential money laundering cases. |
| Suspicious activity | Prevent fraud and resolve flagged behavior situations. |
| KYC | Ensure regulatory compliance during customer onboarding. |
To edit a blueprint, click it and edit its settings.
Create custom blueprints
Blueprint configuration covers General settings, which define how a case is handled, and Case content settings, which determine the data displayed to your compliance officers.
Step 1. Enter basic blueprint data
- Navigate to Blueprints.
- Click Create new blueprint.
- Enter the blueprint’s name and description (optional).
Step 2. Decide how case assignment will be done
You can either manually pick compliance officers from your list or use the load-based assignment feature.
- Select Manually to be able to assign specific compliance officers each time a case is created.
- Select Automatically to use load-based assignment. This feature allows you to pick a number of officers from your list and set the number of cases they can have in their queues.
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.
NoteIf the operator you selected for load-based assignment is offline, they will not get any cases regardless of their current workload.
Step 3. Set up case routing
Case routing automates the process of directing cases to the most appropriate review path.
4-eyes review
The 4-eyes review flow ensures that selected cases are processed by two separate officers responsible for investigation and the approval activities. In this workflow, the investigator analyzes the case and submits their actions, while the approver reviews and validates those actions before they take effect and the case is finalized.
To set up 4-eyes review:
- Create an Approval blueprint: This blueprint grants designated officers the exclusive right to review, approve, or reject actions taken on a case.
- Create Investigation blueprint: This blueprint automatically routes processed cases to the Checker queue.
NoteBoth Investigation and Approval blueprints are required to enable the 4-eyes review flow.
You must create the Approval blueprint first, as it is a prerequisite for configuring routing in the Investigation blueprint.
Default escalation
Default escalation allows officers to escalate a case to a specific blueprint with a single click.
The destination blueprint determines who handles the escalated case, so, this provides a fast way to hand off work to dedicated teams.
NoteSystem logic strictly prevents combining 4-eyes review with default escalation for the Checker.
You must choose one of these routing options.
Transfer to
Transfer allows officers to manually move a case to any blueprint selected from a predefined list.
Step 4. Select content for case page
- Switch to the Case page content tab.
- Activate the Overview by Summy toggle if you want the AI case overview to be displayed. This summary will contain an intelligent overview of the case, which you can use to accelerate decision-making and help your team work faster.
- Activate the toggles that control the visibility of the dedicated data on the case page.
You can include the following information:
|
Preset |
Data |
|---|---|
|
Identity |
|
|
Reporting |
|
|
Verifications |
Applicant verification summary. |
|
AML Control |
AML screening results. |
|
Financial data and sources |
|
Step 5. Define case resolution flow
The Checklist feature allows you to define standard resolution steps and require compliance officers to complete them before resolving a case.
For example, you can require officers to:
- Review the case trigger and customer profile.
- Verify document authenticity.
- Confirm the customer's risk level.
- Review previous case history.
- Document internal notes and actions taken.
- Escalate the case if a policy violation is detected.
- Finalize the resolution decision.
To create a case checklist:
- Enable the Checklist toggle.
- Select the Make checklist optional for case resolution box if you want to allow officers to resolve cases without completing every item.
- Add and define your checklist items: click Add field to create items; click the trash icon to remove an item.
- Drag and drop items to reorder them and adjust the resolution workflow.
- Click Create blueprint to apply your updates.
Updated 10 days ago