Clearing the review queue
Sarah Chen, compliance lead at Acme Ltd, asked which cases were open and past their SLA. Memtro listed each with its queue, assignee, SLA and linked inquiries, oldest first.
Which identity cases are past their SLA, and who has them?
Persona runs your identity checks, and Memtro reads their progress without the personal details collected. It reads inquiries by status, template, account and date, and cases with their status, assignee and SLA. It reads screening reports and whether they matched, accounts, and the event log. When asked and granted, it can comment on, assign, re-status and tag cases. It can also approve, decline, expire or send inquiries for review, and permanently redact an inquiry or account. Persona can tell Memtro when an inquiry needs review or a case passes its SLA, and a job can start on it.
Ask in plain English from chat, your editor, a scheduled job or your own agent. The model picks the right Persona tool, reads what it needs, and answers with the source cited.
These tools change something in Persona. 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 Persona for you. Each event can start a job, with the event as its input. Persona signs every delivery, and one whose signature does not check out is refused before it is read.
Events and webhooksOnce Persona 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 cases are past their SLA, and who is assigned?
How many inquiries were declined this week?
Which inquiries are waiting for manual review?
Did the screening reports on account ACC-2231 match anything?
Assign case 8812 to Maya Okafor.
Sarah Chen, compliance lead at Acme Ltd, asked which cases were open and past their SLA. Memtro listed each with its queue, assignee, SLA and linked inquiries, oldest first.
When Persona told Memtro a watchlist report had matched at Northwind, a job started. It read the linked case and, as granted, tagged it for escalation and assigned it to Dan Fletcher, who was notified by Persona.
The teams that lean on Persona most, a question each of them asks, and what they connect beside it.
A record in Persona 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 the Persona Dashboard, an Admin opens API, then API Keys, picks sandbox or production and creates a key. Under Permissions, add the read and write permissions you need and leave document.read off.
In Memtro, open Connections → Persona and paste the API key. Connect sandbox and production separately.
An administrator grants the case, inquiry and redaction actions by name only to the compliance team. Events are turned on from the connection's Events tab.
Ask which cases are past their SLA.
Chat in the dashboard, the OpenAI-compatible API, scheduled jobs, and any MCP client: Claude Code, OpenCode, Cursor, Claude Desktop. The Persona tools are the same everywhere.
Only when you ask, and only what it has been granted: add a comment to a case; set a case's status; assign a case to a Persona user; add a tag to an inquiry, case, account or report; remove a tag from an inquiry, case, account or report; approve an inquiry; decline an inquiry; mark an inquiry for manual review; expire an inquiry; permanently redact an inquiry or account. 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.
API key. In the Persona Dashboard, an Admin opens API, then API Keys, picks sandbox or production and creates a key. Under Permissions, add the read and write permissions you need and leave document.read off.
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 Persona 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