Screening Agent User Guide

The Screening Agent

The Screening Agent is an intelligent, autonomous solution designed to reduce the operational burden of resolving screening hits. By applying match resolution logic, generating explainable rationales, and automating hit closure in real time, the Screening Agent significantly reduces manual workload, accelerates onboarding, and ensures consistent, auditable outcomes.

The Screening Agent offers:

• Match Resolution Logic: Automatically processes screening results from third-party providers (e.g., LexisNexis, Grid, WCO, custom providers).
• Auto-Resolution: Resolves hits as either true match or false positive based on screening provider data. This reduces the volume of unresolved hits requiring analyst intervention.
• Agent Autonomy: Supports multiple autonomy levels (manual, semi-autonomous, fully autonomous), allowing organisations to tailor the Screening Agent to their risk appetite.
• Decision Rationale: Provides full transparency on the decision made for each match or non-match, with rationale recorded for each decision.

Configuring the Screening Agent

The Screening Agent can be managed and monitored through the Central Agents Configuration area.

note

In order to use the Screening Agent, screening must first be configured in your tenant. Refer to the Configuring Screening Functionality User Guide for setup instructions.

To enable and configure the Screening Agent

1. Navigate to Agents

   • In the left-hand navigation menu, click Agents.
   • Select Screening Agent from the available list.

   

   

2. Create a Screening Agent Instance

   • Click Add Instance.
   • Enter a name and description for the Screening Agent Instance.
   • Assign the agent Instance to the relevant Journey Type(s).
   • You can create a maximum of five Screening Agent Instances.
   • A Journey Type can only be assigned to one Screening Agent Instance.
   • To disable the Screening Agent for a specific Journey Schema while keeping it active for the overall Journey Type, use the Disable Agent toggle within the Screening Match Resolution task.

   

3. Set Autonomy Level Within each agent instance, select the Autonomy Level appropriate for your organisation’s needs.

   Autonomy Levels Explained

   • Manual

     • The agent does not take any resolution action.
     • All hits must be manually reviewed and resolved by an analyst.

   • Semi-Autonomous

     • The agent resolves hits where possible but leaves the task open for analyst confirmation.
     • Recommended as the default rollout mode, as it reduces workload while maintaining human oversight.

   • Fully Autonomous

     • The agent resolves all hits it can and automatically completes the task.
     • Provides the highest efficiency gains but should be enabled only once confidence in the agent’s performance is established.
     • All agent decisions and rationale are available in the Audit drawer.

4. Enable the Agent

   • Toggle Agent Enabled to activate the agent.
   • If required, you can disable the toggle at any time while retaining your configuration (e.g., to pause agent activity temporarily).

5. Save Configuration

   • Click Save to apply your settings.
   • The Screening Agent will now run according to the selected configuration for the specified journeys.

Using the Screening Agent

Once the Screening Agent has been enabled and configured, analysts can interact with its results directly in the Screening Results task.

1. Open the Screening Results Task

   • When a screening request is initiated, the Search Status will display as “Agent Processing” while the Screening Agent analyses the results from the selected provider and compares them with the entity’s Search Criteria (name, date of birth, entity type, etc.).
   • Once processing is complete, all screening hits are displayed in the Screening Results table.

   

2. Review Agent Decisions

   Expand each hit in the Screening Results table to view the Agent’s decision and rationale.

   Each resolution includes:

   • Resolution (e.g., No Match, Match, Unresolved)
   • Reason (e.g., Auto-Resolved by Agent)
   • Comments (e.g., Different first name, different gender)

   The Last Actioned By column indicates whether the hit was handled by:

   • The Screening Agent
   • A user/analyst (for example, re-used resolutions from previous screening runs)
   • The screening provider in some cases, if auto-resolution of false positive hits is enabled

   This ensures analysts can always verify how and by whom a decision was made.

3. Resolve Any Outstanding Hits

   In Semi-Autonomous mode, the Agent will attempt to resolve screening hits but will leave the task open for review. To override an Agent decision:

   • Expand the hit, update the Resolution, add the Reason, and record Comments.

   In Fully Autonomous mode, if all hits are resolved by the Agent, the task will auto-complete without analyst intervention. Analysts must resolve any remaining unresolved hits before the task can be completed.

4. Audit Trail & History

   Every decision made by the Screening Agent is fully auditable.

   Open the Audit view to see:

   • Event type and entity name
   • Who last updated the match (Agent, User, or Provider)
   • Timestamp of the change
   • A detailed history of changes (e.g., status updated from Unresolved → Match, reason recorded as Auto-Resolved by Agent)

   This provides full transparency and accountability for compliance purposes.

   

Best Practices for Adoption

• Start with Semi-Autonomous mode to maintain oversight while reducing analyst workload.
• Monitor early outcomes using the Audit drawer before switching to Fully Autonomous mode.

Ongoing Screening

The Screening Agent can be used in Ongoing Screening (OGS) journeys to automatically analyse and resolve hits generated, allowing organisations to maintain continuous monitoring without increasing manual workload for their operations teams.

How It Works When an OGS journey is triggered, the Screening Agent evaluates the resulting hits using the same resolution logic applied in on-demand screening journeys.

Depending on the autonomy level configured for the agent instance, it may:

• Automatically resolve matches,
• Leave them open for analyst confirmation (Semi-Autonomous), or
• In Fully Autonomous mode, complete the task automatically.

Configuration Requirements To enable the Screening Agent for OGS:

1. Create a Screening Agent Instance

   • Navigate to Agents → Add Instance, and create a new instance dedicated to OGS journeys.
   • Assign the instance to the Journey Type that represents your OGS process.
   • A Journey Type can only be linked to one agent instance, so Ongoing Screening should have its own instance, separate from on-demand screenings.

2. Set the Autonomy Level

   • Choose between Manual, Semi-Autonomous, or Fully Autonomous, depending on organisational risk appetite and oversight needs.

3. Enable the Agent

   • Turn on the Agent Enabled toggle to activate automated match resolution for the assigned OGS journeys.

Once configured, the Screening Agent will automatically evaluate and resolve hits for all ongoing screening events associated with that journey type.

note

• Unlike On Demand Screening, for OGS the Screening Agent resolves hits before the journey launches.
• Therefore, no initial audit record is created.
• An audit entry will only appear if a user later reviews and changes the agent’s decision.