Skip to content
Operating Packs

Build each process once. Fit it to every entity.

Start from a working process, not a blank canvas. Our team fits it to each entity, on the tools you already run. Customers see 45% fewer licenses and 96% fewer execution issues.

All Operating Packs

KYC refresh

Reviews opened by events or the due date, risk rated by your model and every decision confirmed by an analyst.

Run this Operating Pack in your trial

The rail

  1. 01Review opensEvent or due date
  2. 02Collect documentsRegisters by API · outreach
  3. 03Screening alertsYour screening engine · APISLA 1h
  4. 04Risk ratingYour model · agent explainsSLA 2h
  5. 05Analyst decisionEvery review · ApprovalSLA 2d
  6. 06Record updatedCLM and core banking · API

What it replaces

A backlog of reviews worked oldest-first by a team that also handles escalations.

What changes

Reviews open when something changes, not only when they fall due. Analysts spend their time on judgment, not collection.

Works with

  • Fenergo
  • Pega
  • Your screening engine
  • Your risk model

Routed by risk, not by queue

The checks and who decides follow the customer's risk rating. A review also opens when something changes, such as a new director, an alert or adverse media.

  1. Low riskAt least every 5 years

    What runs

    1. Company and ownership data refreshed from registers
    2. Alerts since the last review checked
    3. Compared with the last review

    Who decides

    No material change: the agent prepares the comparison, an analyst confirms it in one step, and a sample goes to quality control.

    SLA 5 days
  2. Medium riskAt least every 3 years

    What runs

    1. Documents collected from the customer
    2. Alerts since the last review checked
    3. Risk rated by your model, the file prepared

    Who decides

    An analyst decides on the prepared file.

    SLA 2 days with the analyst
  3. High riskAt least every year

    What runs

    1. Documents and source of wealth corroborated
    2. Screening and adverse media
    3. Enhanced due diligence drafted

    Who decides

    A senior analyst decides and a second confirms. Keeping a politically exposed person needs senior management approval, and an exit needs compliance sign-off.

    SLA 5 days with the analysts

The file an analyst opens

By the time a review reaches a person, the documents are requested and the alerts are triaged. The analyst's time goes to judgment, not collection.

C-8815Opened on a register change · Medium risk · Opened 2 days ago

Why it opened

  • New director registered this week, from the company register
  • Transaction volume above the expected range for six weeks

Screening

  • 1 possible sanctions match on the new director, from your screening engine
  • The engine flags a different date of birth and nationality. Proposed as a false positive, for the analyst to confirm.

Documents

  • 4 of 5 on file
  • Proof of address requested from the customer, reminder in 7 days

Risk rating

  • Medium, unchanged, from your risk model
  • Drivers: country low, product medium, activity rising
Confirm refreshRequest informationEscalate to enhanced review

Confirm refresh opens once the match is cleared and the proof of address is in.

An illustrative case. The analyst's decision is recorded with its reason.

Inside each stage

Choose a stage to see who does each step and what it leaves on the case.

Analyst decision

After triage · SLA by risk tier
Steps
  1. PeopleFile reviewed Documents, alerts, rating and the comparison in one place
  2. PeopleDecision recorded Confirm, request information or escalate, with a reason
  3. PeopleSecond approval For high risk, and senior management for a politically exposed person

Left on the case: the decision, its reason, the analyst and any second approver.

What your reviewers will ask

IT security, compliance, model risk and audit each sign off before go-live. Their first questions, answered.

  • IT security

    Where does customer data go?

    Nowhere. Optomo runs on-premise, in your network, so customer documents, screening alerts and agent reasoning stay in it. Optomo is ISO 27001 certified.

  • Compliance

    Does an AI decide on a customer?

    No. An analyst confirms every review. High risk needs a second analyst, keeping a politically exposed person needs senior management approval, and an exit needs compliance sign-off.

  • Model risk

    Whose model rates the risk?

    Yours. The agent explains what drove the rating but never sets or overrides it. The rating, its inputs and the explanation are recorded on the case.

  • Audit

    Can we show a regulator why?

    Each decision is recorded with its reason, the analyst and the evidence on file. Enterprise contracts give your auditor direct access to the controls Optomo runs.

Where your data lives

Where your processes differ, we close the gap with you

Inconsistent processes are normal. Our team and our partners map how each version runs and fit the Operating Pack to it.

Included in Enterprise. Our team fits the Operating Pack in the trial and the rollout, at no extra cost.

  1. Optomo team

    Fits the Operating Pack

    • A version per entity or country
    • Stages connected to your systems
    • Thresholds and approvers set as policy
  2. Partner

    Aligns the process

    • The process mapped as it runs today
    • Which differences to keep
    • The change led with the process owners

How an Operating Pack becomes your process

We connect it to your systems, then run real cases in the 5-week trial.

  1. 1

    Map the systems

    Each stage pointed at your systems.

  2. 2

    Set the policy

    Set once, inherited by every case.

  3. 3

    Run it in the trial

    Real cases, with a cost baseline by week 4.