Persona logo

Persona + Memtro

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.

In Memtro

What you can do with Persona in Memtro

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.

What it does

  1. 01Reads inquiries by status, template, account and date, with every lifecycle date and who or what decided them.
  2. 02Reads cases with status, resolution, queue, assignee and SLA, and screening reports with whether they matched.
  3. 03Reads accounts and the event log. Names, ID images, selfies, documents and what matched are never returned.
  4. 04When asked and granted, comments on, assigns, re-statuses or tags a case. A status change can fire your Persona workflows.
  5. 05When asked and granted, approves, declines, expires or marks an inquiry for review. Approval and decline are final and trigger downstream systems. It can also permanently redact an inquiry or account.
  6. 06With events on, an inquiry needing manual review, a case passing its SLA or a watchlist match can start a job.

Acts when asked

When you ask it to

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.

  1. 01Add a comment to a case
  2. 02Set a case's status
  3. 03Assign a case to a Persona user
  4. 04Add a tag to an inquiry, case, account or report
  5. 05Remove a tag from an inquiry, case, account or report
  6. 06Approve an inquiry
  7. 07Decline an inquiry
  8. 08Mark an inquiry for manual review
  9. 09Expire an inquiry
  10. 10Permanently redact an inquiry or account

Events

When it happens

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 webhooks
  • 01An inquiry was created
  • 02Someone started a verification flow
  • 03Someone finished a verification flow
  • 04An inquiry was approved
  • 05An inquiry was declined
  • 06An inquiry failed
  • 07An inquiry expired
  • 08An inquiry needs manual review
  • 09An inquiry moved to another step
  • 10An inquiry was redacted
  • 11A case was created
  • 12A case was assigned
  • 13A case changed status
  • 14A case was resolved
  • 15A case was reopened
  • 16A case passed its SLA
  • 17A comment was added to a case
  • 18An account was created
  • 19An account changed status
  • 20An account was redacted
  • 21A watchlist report matched
  • 22A PEP report matched
  • 23An adverse media report matched
  • 24A transaction was created
  • 25A transaction changed status
In practice

Ask it like you would a colleague

Once 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.

Persona logoPersona + Memtro
  • 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.

01

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.

02

A watchlist match

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.

Teams

Where it fits

The teams that lean on Persona most, a question each of them asks, and what they connect beside it.

Better together

Works with

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.

Setup

How to connect

Connect withAPI key
  1. 1

    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.

  2. 2

    In Memtro, open Connections → Persona and paste the API key. Connect sandbox and production separately.

  3. 3

    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.

  4. 4

    Ask which cases are past their SLA.

Also works from

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.

FAQ

Questions

Can Memtro change anything in Persona?+

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.

Who can use a Persona connection?+

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.

Does Memtro store my Persona data?+

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.

How do I connect Persona?+

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.

Can Persona start a job?+

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.

Connect Persona in a few minutes

Seven-day free trial, then one monthly price per organisation. Connectors, jobs and memory are never metered.

Where agents remember your company

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