Nothing moves without something noticing.
Signals watch everything that touches your caseload — documents landing, deadlines approaching, replies going quiet, regulation shifting. Triggers turn each one into work that starts itself, on the cases you scope, within the limits you set.
From something happened to something done.
Most case management tells you what happened, eventually. Hendl notices, decides whether it matters, and starts the response — before anyone opens the file.
Everything that touches a case is watched — documents arriving, deadlines approaching, replies going quiet, regulation changing.
Rules you set once: when this happens, on these cases, start that. No one has to notice, remember or forward anything.
A trigger starts real work — a workflow, a digital worker, an escalation — with the case context already attached.
The feed on the left. What fired on the right.
Every signal is matched against your triggers. When one fires, the action starts with the case context attached — and both land on the audit trail.
Eight kinds of signal, one feed.
Even silence counts.Every inbound file, message and attachment, on any channel.
Court dates, regulatory clocks and service promises.
Standing watchers over the rules that govern your caseload.
The reply that never came — waiting is a signal too.
Reserves, stages, parties — any field crossing a threshold.
Clusters and anomalies across the whole book, not one case.
Feeds from registries, sanctions lists and connected systems.
A person marks something worth watching — the system takes it from there.
A trigger is four decisions. You make them once.
Composed in plain language, no code — and dry-run against your case history before it ever goes live.
What has to be true — the event, the threshold, the pattern.
Which cases it applies to — a type, a team, a value band, or all.
What starts — a workflow, a worker, a task, an escalation.
Limits and approvals — how far the action may run unattended.
Powerful, and quiet about it.
Automation you can’t trust gets switched off. Triggers are testable, scoped, logged and instantly pausable — so they stay on.
Signals are deduplicated and thresholded — one event, one action, not forty notifications.
Every signal, every firing and every action lands on the audit trail with its cause.
Dry-run a trigger against history to see exactly what it would have done.
Pause any trigger instantly — per rule, per team or across the workspace.
Questions teams ask about signals.
How is this different from notifications?
A notification asks a person to react. A trigger starts the work itself — the workflow runs, the chaser goes out, the escalation lands — and tells you what happened.
What can a trigger start?
Any process definition or workflow, a digital worker, a task for a named person, or an escalation. The case context travels with it.
Will it flood the team with actions?
No. Signals are deduplicated, thresholds keep small movements quiet, and every trigger has a scope — you decide which cases it may touch.
Can we test a trigger before it goes live?
Yes. Dry-run it against your case history and see every firing it would have produced before you arm it.
Who can create triggers?
Roles you choose. Most teams let leads author triggers and require a second approval before one goes live on regulated case types.
What happens when a trigger misfires?
Pause it with one click. Everything it started is on the audit trail, attributable and reversible — nothing disappears into the background.