Review alerts

By the end of this guide you can work your alerts queue: open an alert, judge its hits, record your decision, and resolve it. It takes about ten minutes.

An alert is raised whenever CryptoComply detects something that needs a human decision — a new sanctions or watchlist hit, a change in risk level, or new exposure. Alerts come from two sources: Watchlist Screening (a profile matched a sanctions, PEP, or watchlist entry — PEP means Politically Exposed Person) and Address Screening (a monitored wallet's on-chain risk changed).

Work the alerts queue

Open Alerts from the sidebar. This is your queue of everything awaiting review.

Each row shows the alert ID, status, the name of the profile or address it concerns, the source, when it was created, and who it's assigned to and reviewed by. Search, filter, sort, or Export Table as needed. Sort by status or created date to work oldest-open-first.

Open an alert

Click any alert to see the full picture.

The summary across the top gives you the alert type and status, the linked Profile ID, and the counts that matter: Total Hits, Total False Positives, and Total True Matches. Below it:

• Profile Information — who the alert is about (name, date of birth, citizenship, ID), so you can compare against the hit.
• New Hits Needing Attention — each potential match with a score (match confidence), the matched entity name, the source list it came from, and a category. Expand a row to see the details behind the match.
• Notes — record your review reasoning.
• Previously Resolved Hits — what's already been judged on this alert.

Investigate and decide

For each hit, compare the matched entity against your profile's information — name, date of birth, citizenship — and decide whether it's a true match or a false positive. A common false positive is a shared or similar name with a different date of birth or country.

Record what you concluded in Notes so the decision is auditable later.

Assign, escalate, or close

• Assign the alert to a teammate to investigate (use the Assign control in the summary).
• Escalate Alert when it needs senior review.
• Close Alert once it's resolved — for example, all hits confirmed as false positives.

What just happened?

You didn't create these alerts — CryptoComply's ongoing screening did, the moment a hit or risk change appeared. When you assign, note, escalate, or close one, that action is recorded in the audit trail and the right teammates are notified, so the whole review is defensible to an auditor or regulator.

What's next?

• Manage profiles — open the profile behind a watchlist alert.
• Screen a blockchain address — the address-screening alerts and monitoring side.
• Connect an AI assistant — ask an AI tool to summarize and triage open alerts.

Troubleshooting

Problem	Fix
Too many alerts	Filter by status or source, and sort by created date to work the oldest first. Tighten screening cadence or thresholds if a source is too noisy.
Can't close an alert	Resolve its hits first; the Close action stays disabled until the alert is in a closeable state.
Not sure if a hit is real	Compare date of birth and citizenship, not just the name. Document your reasoning in Notes before closing.
An alert isn't assigned to anyone	Use Assign to give it an owner so it doesn't fall through the cracks.