Clearing the unassigned queue
Priya Sharma, a compliance analyst at Northwind, asked which high-risk onboarding cases nobody had picked up. Memtro listed the unassigned cases with their alert counts, highest priority and risk types, oldest first.
Which high-risk onboarding cases are still unassigned?
ComplyAdvantage Mesh holds your AML cases. Memtro reads cases with state, stage, assignee and risk types, the alerts and screening risks on a case, customers by risk level, risk scores and labels, and onboarding results. When asked and granted, it can add notes, assign and move cases, set alert states, decide risks, set customer labels, status and risk, screen or re-screen customers, and release or reject held transactions. ComplyAdvantage can tell Memtro when a case opens or a risk level rises, and a job can start on it. Names, dates of birth and match profiles are never read.
Ask in plain English from chat, your editor, a scheduled job or your own agent. The model picks the right ComplyAdvantage tool, reads what it needs, and answers with the source cited.
These tools change something in ComplyAdvantage. The model is told to use them only when you ask for exactly that, and an administrator grants each one by name to the teams that may use it; a personal connection acts only after its owner allows it.
Turn events on in the connection's Events tab on the Connections page, choose the kinds you want, and Memtro registers its address with ComplyAdvantage for you. Each event can start a job, with the event as its input. ComplyAdvantage signs every delivery, and one whose signature does not check out is refused before it is read.
Events and webhooksOnce ComplyAdvantage is connected, these are the kinds of things people ask. Plain questions, no syntax. If the answer lives partly in another system you have connected, Memtro looks there too.
Which high-risk onboarding cases are still unassigned?
What alerts are on case 3f2a, and has anyone reviewed their risks?
Which customers are rated prohibited or high risk?
What did the screening for the customer we onboarded this morning find?
Assign the oldest open monitoring case to Priya.
Priya Sharma, a compliance analyst at Northwind, asked which high-risk onboarding cases nobody had picked up. Memtro listed the unassigned cases with their alert counts, highest priority and risk types, oldest first.
BigCo turned on the risk-level event so Tom Reilly, its MLRO, sees escalations as they happen. When a customer's risk level went up, a job read their latest risk score and labels and the open cases on them, and put it in front of Tom.
The teams that lean on ComplyAdvantage most, a question each of them asks, and what they connect beside it.
A record in ComplyAdvantage is rarely the whole story. Connect the systems that hold the rest and Memtro checks them together, then remembers what it learned so the next question starts further along.
Using something else for the same job, or both? Each connector has its own tools; connect as many as you like.
In ComplyAdvantage Mesh, open Settings → Access Management → API Credentials and create a credential for Memtro with only the view and update permissions it needs. Copy the access key and the secret, which is shown once.
In Memtro, open Connections → ComplyAdvantage and paste the Access key and the Secret.
Set the Region if your Mesh account is not on the default host. An administrator grants the case, risk and screening actions by name only to the analysts who may decide them. Events are turned on from the connection's Events tab.
Ask which high-risk onboarding cases are still unassigned.
Chat in the dashboard, the OpenAI-compatible API, scheduled jobs, and any MCP client: Claude Code, OpenCode, Cursor, Claude Desktop. The ComplyAdvantage tools are the same everywhere.
Only when you ask, and only what it has been granted: add a note to a case; add a note to an alert; add a note to a customer; assign or unassign a case; move a case to a workflow stage (a decision stage closes it); set an alert's state; record a decision on a screening risk; replace a customer's labels; close or re-activate a customer; override a customer's risk level; create and screen a customer (billable); re-screen a customer (billable); release or reject a held transaction. Every other tool reads, searches or lists. The Connections page labels the tools that act, an administrator grants each one by name to the teams that may use it, and a personal connection acts only after its owner allows it.
A personal connection serves only your own requests. A shared connection serves the organisation: everyone, or only the teams an admin chooses. Admins can always add shared connections; other members need the permission.
Credentials are encrypted at rest. Tool results are cached briefly so agent loops do not repeat identical calls, and the facts the model extracts are saved to your organisation's memory with provenance (system, record and link) so they can be checked and superseded.
Access key and secret. In ComplyAdvantage Mesh, open Settings → Access Management → API Credentials and create a credential for Memtro with only the view and update permissions it needs. Copy the access key and the secret, which is shown once.
Yes. Turn events on in the connection's Events tab on the Connections page, choose the kinds you want, and Memtro registers its address with ComplyAdvantage for you. A job set to start "When an event arrives" then runs once for each matching event, with the event as its input. The run treats the event as outside data, never as instructions, and anything the run remembers is kept as unverified.
Seven-day free trial, then one monthly price per organisation. Connectors, jobs and memory are never metered.
Sign in, add a provider key, create an API key and point your tools at Memtro. It takes about five minutes.
7-day free trial · card on file, nothing charged until it ends · cancel any time