← Back to Product overview

Notifications

Nobody has to go looking for what's theirs to act on

The moment a contract reaches a step someone can actually act on, they're notified — immediately, not on a delay, and whether that's the person named on the policy or a delegate currently standing in for them.

A woman checking her phone while standing in an office

Fires the instant a step is reachable

Two moments trigger a notification: a contract getting routed and a step becoming reachable for the first time, and an earlier step clearing and unblocking the next one. Either way, whoever's now eligible to act finds out right away — not the next time someone happens to check.

Recipients

Only people who can genuinely act right now

Recipient computation reuses the exact same eligibility logic the approval engine itself uses to decide who's allowed to act on a step — delegation included. Nobody gets notified for a step they can't actually touch, and nobody eligible is missed.

Today

An in-app bell, not a page you have to remember to check

Live unread count

A badge that reflects what's actually waiting, kept current by automatic polling.

Jump straight to the contract

Click a notification and land on the contract itself, marked read on the way.

Mark all read

Clear the list in one action once you're caught up.

Slack and Teams

Notifications don't stop at the browser tab

An org admin connects a Slack workspace or a Teams channel once, from notification settings — every eligible step change posts there too, alongside the in-app bell, not instead of it.

Slack: see it, click through

A message lands in the channel the moment a step is ready — who's being asked, and a link straight to it in Contrayo.

Slack: act without leaving the message

Turn on in-chat approve/reject buttons and a click resolves through the same eligibility check, segregation-of-duties rule, and audit trail as clicking Approve inside Contrayo — nothing about the decision is handled differently because it came from Slack.

Microsoft Teams

The same link-out notification lands in a Teams channel. Teams' own current webhook mechanism doesn't render buttons — that's Microsoft's own design, not a limit we chose — so Teams gets the notification, not the in-chat button.

One real limitation, named plainly: a Slack click still has to resolve to a real person for the audit trail, so an admin maps each teammate's Slack account to their Contrayo membership once — there's no bulk import for that yet, and no in-chat interactivity on Teams at all today.Why we built it this way →

Where it plugs in

What decides when to notify

The DoA engine

A step becoming reachable, or clearing and unblocking the next one, is what triggers a notification.

See the approval engine →

Contract records

Every notification links straight back to the contract it's about.

See contract records →

Notifications come with every seat

There's no separate add-on price to check. See what a seat costs across all three tiers.