Trixie is the AI agent that analyzes the unusual transactions your monitoring rules and scenarios flag. It works on transaction monitoring cases like any other analyst: it reviews the transaction against the customer's profile, leaves the evidence behind and writes its report. Your team makes the final call.
This article walks through the five sections you fill in to get it running.
Where to configure it
Settings > AI & Agents > Agents configuration.
That screen lists your organization's agents. To create a new one, click "Create".
If you cannot find the section, your organization does not have AI agents enabled yet. Write to Support to turn them on.
The form starts with the first section only. The other four appear once you pick the agent type, because all of them depend on it.
1. AI agent type
Pick the Trixie card and give it a name.
The name is what shows up as the analyst on every case Trixie works on, so make it one your team recognizes at a glance. Two agents cannot share a name.
You can create several Trixie agents with different setups. One for threshold alerts and another for layering patterns, each with its own instructions and triggers.
If you change the agent type after filling things in, you lose the instructions, the tools and the triggers you loaded. The platform asks you to confirm first.
2. Roles and groups
Roles define what Trixie can do. Groups define which resources it works on.
Both assignments are required: at least one role and at least one group. An agent with no roles has no permission to act. With no groups, it has no cases to work on.
Give it the same roles you would give an analyst doing this job. Trixie never does more than its roles allow. Neither the instructions nor the tools widen that limit.
3. Instructions
Instructions give Trixie context on how your organization works. They apply to this agent only. The section is optional: leave it blank and Trixie runs with its default behavior.
You have two paths:
Instructions library. The dropdown on the top right offers ready-made instructions for Trixie, in your organization's language and country. Load one and edit it.
Custom. Pick this option and write your own text from scratch.
The editor supports basic formatting and accepts up to 50,000 characters.
Loading an instruction from the library replaces whatever you already wrote, and you cannot undo it. The platform warns you first.
Be specific about what you expect from Trixie. Set the tone and the format of the report. Add examples when they help clarify.
A few examples for Trixie:
Always compare the transaction amount against the declared transactional profile. If it goes over, state in the report by how much and over what period.
For outflows to third-party accounts with no declared relationship, leave the case pending review and list the recipients.
For customers with cash activity, check for amounts split below the reporting threshold and document the sequence.
Two things to keep in mind:
These instructions add to the AI Instructions you set on each case template. Both combine when Trixie works.
Do not write sensitive information. Any user with access to the settings can read them.
4. Tools
Tools extend what Trixie can do on the cases you assigned to it. The section is optional.
Each tool is a switch. Some also ask you to choose what you enable:
Write report. Trixie writes and saves the case report. Comes on.
Change case status. Trixie moves the case only to the statuses you select: Open, Pending review or Closed. Comes on with Open and Pending review. Add Closed only if you want Trixie closing cases without prior review.
Send requirements. Trixie requests documentation from the customer using the requirement templates you select. Useful for asking for proof of source of funds. Comes off.
Manual triggers. Trixie runs the manual triggers you select during its work. Comes off.
If you turn on a tool that asks for options, you have to pick at least one. To enable none, leave the tool off.
5. Triggers
Triggers define when Trixie runs automatically. This section is required: an agent with no triggers would never run, so the platform does not let you save it.
Click "Add trigger" and pick the event and the case template:
When a case is created. Trixie starts as soon as the monitoring rule generates the case.
When an analyst is assigned. Trixie starts once it is assigned as the case's analyst.
When the stage changes. It also asks for the stage. Only the active stages of the template you picked are offered.
You can load several triggers for the same agent. Each one is listed with its event and its template.
Saving
Click "Create". If you try to leave with pending changes, the platform asks you to confirm before discarding them.
Turning agents on and off, and editing them
The list shows each agent's name, roles, groups and creation date.
Edit: the settings icon opens the same screen you used to create it.
Turn off: the switch on the row stops the agent. It stops running and the row dims. You turn it back on with the same switch.
On an agent that already exists, triggers save instantly: you add, edit, turn off or delete one, and the change is applied. The name, the roles, the groups, the instructions and the tools save with the "Save" button.
If you deactivate a case stage that has a trigger pointing at it, the platform warns you first. It deletes that trigger, because a deactivated stage never changes and the agent would never run.
Worth knowing
Trixie shows up as the analyst on every case it works on, with the same traceability as any team member.
Permissions win. If an instruction asks for something its roles do not cover, Trixie does not do it.
Trixie gathers evidence and recommends. The decision to report stays with your compliance team.