It runs the investigation.You keep the filing.
The alert queue is the anchor: the case assembled, the network mapped, the pattern tested against the customer's own baseline, then a narrative and a recommendation. Periodic KYC and screening review fill the rest. No customer record leaves the bank.
One matter, end to end.
The role is wider.
One typical matter, start to finish. The steps illustrate the job, they do not bound it. What the agent will not do is a list of decisions, not a list of tasks.
Assembles the case file
Transactions around the trigger, prior alerts and filings on this customer, the KYC file, the onboarding profile, and beneficial ownership. Eleven systems, one file.
Builds the network around it
Shared counterparties, addresses, devices, and beneficiaries. The alert names one account, but the typology usually lives across several.
Tests the hypothesis both ways
Structuring, or a cash business banking its takings? It compares against the customer's own twelve months and against their peer group before it says either.
Chases what is missing
Drafts the request for information, reads the answer when it lands, and re-runs the case rather than closing it because the queue is long.
Writes it to the standard
A chronology in plain language, every fact tied to its source, with what was ruled out and why. Not a summary of the alert in bullets.
Feeds the rule back
It reports which rule produced the alert and how many of its siblings closed as noise, so threshold tuning is argued from your own numbers.
The work between alerts
The six steps are one alert. The same agent runs periodic KYC refresh, sanctions hit review, onboarding due diligence, and the quarterly typology review. New work is a line in the brief, not a new deployment.
What lands
on your desk.
The deliverables, named. Each arrives as a draft with a person's name on the review, and every line in it carries the source it came from.
The narrative
A chronology written to the standard your regulator reads, each fact tied to the statement, document, or screening hit behind it.
The recommendation, with reasoning
Close, request information, or escalate for filing, with what was ruled out. Your analyst agrees or overrules, and both are recorded.
The evidence pack
Statements, documents, screening hits, and network links, attached to the case in the order the narrative refers to them.
The queue report
Which rules are producing noise, at what volume, and what a threshold change would have done to last month's queue.
The limit is authority,
not the task list.
It will take any work the role covers. These decisions still reach a person, regardless of how confident the model is.
Anything that looks like a filing
Where the evidence supports escalation the agent stops at a drafted recommendation. A person decides to file, and signs it under their own name.
Sanctions and PEP hits
Screening matches route to the sanctions team the same day, directly, regardless of how innocent the surrounding transaction pattern reads.
Customer contact
Requests for information reach the customer through your existing channel, sent by your staff. The agent drafts correspondence, it never conducts it.
From brief
to live matters.
The same four steps for every agent, because the runtime underneath does not change between them.
- 01
The brief
We write down the job, the sources it may rely on, and the calls it never makes alone. You sign it before the agent connects to anything.
- 02
Reading rights
Read-only access to the corpus it needs: the contract archive, the data room copy, the case system. Nothing is written back during onboarding.
- 03
Supervised run
It works a matter your team has already closed. You compare its output against what your people produced, line by line, and the brief is tuned on the disagreements.
- 04
Live matters
It starts real work behind the thresholds you set, and they widen as the numbers hold. A named engineer stays on call for 90 days.
Same runtime,
different job description.
Each agent is a brief and a set of reading rights on infrastructure you have already deployed and already had reviewed.
“Give us a matter you have already closed. The agent works it cold, and you compare its issues list against what your team actually filed. That comparison is the whole sales process.”
Sebastian Mondragon, Founder of Particula Tech