Skip to content
WICSWATCHLIST INTELLIGENCE& COMPLIANCE SCREENING
Notification centre

The right person told, at the right time.

Every WICS module sends its events to one notification centre. Your rules decide who hears about what, by e-mail or in the in-app bell. A critical alert climbs, level by level, until someone acknowledges it.

Book a demoSee how it works

Its own application, menu and licence. Nothing sends until a second person approves the rule.

wics.your-bank.internal/notifications
WICSNotifications
3AK

Notifications3 unread

Critical10:00

Payment held — sanctions match

MT103 · Northwind Trading LLC · 2,400,000.00 USD

Level 1Level 2 in 2 min
How it works

From event to person in five steps.

Something happens in WICS. A rule picks who must know. A template writes the message. A channel delivers it. The person acts.

  1. 01

    Event

    A payment is held, a deadline nears, a list download fails. Each module publishes its events in one common envelope.

    CatalogueAPI key

  2. 02

    Rule

    Your rule picks the events, checks the conditions and names who must hear about it.

    ConditionsFour eyes

  3. 03

    Template

    An approved template turns the event into words, in English, French or Arabic.

    EN · FR · ARFields

  4. 04

    Channel

    E-mail and the in-app bell are built in. SMS and Microsoft Teams come through a connector built for your bank.

    E-mailBellSMSTeams

  5. 05

    Person

    Only people who can open the item are told. One click on the message opens the case, the payment or the file.

    UnitPermission
One envelope

Every module speaks the same language.

Screening, lists, cases and user management publish their events in one shape. One set of rules, one template library and one sending history serve them all.

  • Each module registers its events in a catalogue.
  • You pick events from a tree — application, module, event — with a search box.
  • Outside systems can send catalogued events through a secured API, with an API key.
  • Who acted, who owns it, the status before and after, the deadline and a link travel with every event.
Event envelopeIn the catalogue
Event
PAYMENT_HELD
Module
SCREENING.PAYMENTS
Unit
Head Office
Priority
Critical
Item
MT103 · TRX-88412
Who acted
WICS
Assignee
—
Status
NewHeld
Decision
—
Deadline
14:30
Link
/payments/TRX-88412
Rules

You decide who hears about what.

Pick the events, add conditions, choose the people and the channels. A second person approves before anything sends.

  • Conditions on event fields: amounts and dates with greater or less than, or “only when rule X fired”.
  • Recipients by name, by permission, by unit, the assignee, or “who can work it now”.
  • Rules, templates, and switching a rule on or off all go through four eyes.
  • Mandatory or optional: people may mute or re-channel optional rules in “My choices”.
wics.your-bank.internal/notifications/rules/RULE-0012
WICSNotifications · Rules
AK

RULE-0012

Payment held — tell who can work it now

MandatoryDraft

Events

  • Screening

    • Payments

    • Files

  • Lists

    • Downloads

  • Cases & workflow

    • Workflow

  • Notifications

    • Channels

Several events, one module per rule.

Conditions

  • Amount>1,000,000.00 USD
  • Deadline<30 min
  • Only when rule“High-risk corridor”fired

Recipients

Channels

Priority

Sending

In wordsWhenPayment heldDeadline nearTellWho can work it now · Permission: Release paymentsByE-mail · BellHigh
Try it: search the events, switch channels, send the rule for approval.Illustrative — invented names and figures.
Templates

Write it once. Read it in every channel.

A library of templates for each event, reused by every rule. Type the text, drop in fields, and see the e-mail, SMS and bell versions as you write.

wics.your-bank.internal/notifications/templates
WICSNotifications · Templates
AK

Payment held

WICS defaultUsed by 3 rules

Editor

Subject

Payment held — Reference

Message

A payment from Party for Amount is held for review.

Please decide before Deadline.

Button

Open the payment

Insert a field

Live preview

Sample data
WWICS NotificationsPayment held — Reference14:02
Your logo

A payment from Party for Amount is held for review.

Please decide before Deadline.

Open the payment

Compliance Operations

For the named recipient only. Please do not forward.

One layout per company: logo, colours, footer, disclaimer.

Switch the channel or the language to see the same template.

Three languages, ready

WICS ships default templates in English, French and Arabic. The Arabic one reads right to left.

Your look, set once

One e-mail layout per company: logo, colours, footer and disclaimer.

Sensitive fields guarded

An amount may show in the bell and the e-mail. SMS and Teams hide it unless a company-wide switch is approved.

Critical alerts

A critical alert climbs until someone answers.

Critical messages carry an Acknowledge button. If nobody presses it, the alert moves up a level, then another. Each level has its own wait and its own people.

  • Level 1, level 2 and more, each with its own wait time and recipients.
  • One acknowledgement stops the climb for everyone.
  • Only critical alerts escalate. The rest arrive once.

Not everything is urgent

Turn on summaries every few minutes or once a day. “No hit” events only ever arrive as a summary.

Summary · every 60 min11:00
  • 412payments screened — no hit
  • 14files screened — no hit
  • 37names screened — no hit
Critical

Payment held — sanctions match

MT103 · Northwind Trading LLC · 2,400,000.00 USD

10:15

  1. Sent

    Told 10:00
    Who can work it now
  2. 1

    Level 1after 10 min

    Told 10:10
    Team leads · by permission
  3. 2

    Level 2after 20 min

    in 15 min
    Head of Compliance
  4. 3

    Level 3after 30 min

    Waiting
    Chief Compliance Officer

Nobody has acknowledged yet

Delivery & control

A message is never lost quietly.

If e-mail fails, WICS tries again for about thirty minutes. Still failing? The message waits in the bell, marked “not delivered by e-mail”, and the administrator is told the channel is down.

  • Retries for about thirty minutes
  • Never lost: the bell keeps it
  • The administrator hears at once
wics.your-bank.internal/notifications/history
WICSNotifications · Sending history
AK

Payment held — TRX-88412

To Omar R.

10:00
BellDelivered 10:00
E-mailTrying 1/5
  1. 110:00
  2. 210:01
  3. 310:06
  4. 410:16
  5. 510:31

Retries for about 30 minutes

Never the wrong person

Nobody is told about an item they could not open. Unit, per-list permission and workflow access are checked when the message is sent.

Not your own action

The person who acted is not told about it, unless the rule asks for it.

One message, not two

Two rules that reach the same person for the same event send one message.

Sending history

Every message sent, and every person skipped, is kept — with an archive for older ones.

Send me a test

Try any rule with sample data. It goes to you only, with “[TEST]” in the subject.

Your time zone

Each company sets its time zone, so the times in messages read right.

Day one

Ready-made rules, waiting for your approval.

A new bank starts with draft rules for the alerts every team needs. Nothing sends until a second person approves them.

Ready-made rules

Viewing as the checker

0/5 live
  • Screening channel downChannel managers
  • Deadline nearWho can work it now
  • List download failedList managers
  • Notification channel downNotification managers
  • Payment heldWho can work it now

Nothing sends until approved.

Four channels

E-mailBuilt inIn your company layout.
In-app bellBuilt inUnread count, mark as read, one click to the item.
SMSConnectorThrough a connector built for your bank.
Microsoft Teams / webhookConnectorThrough a connector built for your bank.

Keep exploring