Review deferral requests
Deferral request review is part of Isaac’s workflow, where analysts handle exceptions manually in the Workspace application. Isaac generates manual review tasks as part of the Transaction Monitoring Alert Investigation flow, if you enable the Human-in-the-loop step during configuration. Each case or entity receives one task.
When setting the Human-in-the-loop step for Isaac, you can pre-assign tasks from a specific variation to a user. You can also set the AI Agent to notify the assignee and stakeholders when a deferral request is ready for review in Workspace.
You can enable or disable the Human-in-the-loop step per variation. If the step is disabled, a batch summary report is created instead of a manual review task and sent to the specified email (if any). For more information, read the Review output topic.
To review a deferral request, do as follows:
- Locate the manual review task generated by Isaac in the Workspace assignment list.
- Review the alerts in the deferral investigation and update their statuses and comments as needed.
- Complete the investigation.
Locate assignment
Once the Transaction Monitoring Alert Investigation Business Process creates a manual review task, it appears as an assignment in the Workspace application.
For easier management and prioritization, add assignments to a custom queue as described in the guide.
To ensure manual review tasks reach the right team member promptly, you can pre-assign them to a specific user during configuration. If there is no pre-assignment, you can assign tasks to a specific user in Workspace according to the guide.
Review deferral request
To open an assignment, click it in the list. As it opens, you see a deferral request with a structure similar to the one shown below. Review the alerts and update statuses and comments as needed. To skip the assignment, click the button in the top right corner.
The following numbers correspond to those in the image above:
Header information: contains information about the open case for a specific entity or customer.
Alert information: contains information about the alerts in the deferral request.
a. Reviewer: the last user who edited the status or comment. The default reviewer is Auto, which means Isaac was the last to review the alert.
b. Status: defines the current status of alerts in the deferral request.
- Needs review: assigned to each alert by default.
- Approved for deferral: use to indicate the alert is eligible to be deferred to an open investigation.
- Not approved for deferral: use to indicate the alert is not eligible to be deferred to an open investigation.
- Pending: use to approve an alert conditionally based on the outcome of another investigation.
c. Comment: an editable comment for the alert.
Bulk change: allows users to update more than one alert at a time with the same status and decision comment.
Close Investigation: closes the investigation and completes the task. Upon clicking the button, users can select a status for the entire investigation and enter a comment.
Close investigation
Once you finish your review, you can click Close Investigation to complete the task. You are then prompted with a dialogue box to confirm the email address you want to use to receive the final alert summary report.
After the confirmation, you are either redirected back to the assignment list in the queue or, if the appropriate setting is enabled during configuration, to the next assignment in your queue.
The Close Investigation button is disabled if alert review is not completed.
When the assignment is complete, the final decision is saved to a dedicated Data Store. You can also configure Isaac to generate a final alert summary report and email it to the specified address after the batch is completed.
If you want to escalate the review before generating the report to include comments from another analyst, click Save and Continue. Your progress will be saved, and the task can then be reassigned to another user in Workspace.