Skip to main content
Airdun notifies your team two ways: an in-app notification bell and Slack. There is no email notification channel. On top of these, escalation flags individual cases that need a human and can stop the automated sequence for them.

​
The notification bell

The bell in the app is always on. It receives case events (below), escalations, and one-off system notices such as “Stripe import complete.” It is the default destination — you don’t need to connect anything for it to work.

​
Case events

Four recovery events can notify you. Each can be routed to Slack, the in-app bell, or both, from a per-event matrix. Configure these under Settings → Notifications. A master toggle turns all case-event notifications on or off; below it, the matrix sets Slack and in-app delivery per event. Defaults: in-app on, Slack off.

​
Connect Slack

Slack is connected by installing the Airdun Slack app through Slack’s OAuth flow — not by pasting an incoming webhook URL.
1

Install the Slack app

Go to Settings → Channels → Slack and start the connection. You are sent to Slack’s authorization screen to approve the app for your workspace; Airdun stores the resulting bot token (encrypted).
2

Pick a channel

Back in Settings → Notifications, choose which Slack channel Airdun posts to, and optionally the teammates to @-mention. Airdun lists your workspace’s channels for you to pick from.
3

Turn on the events you want in Slack

In the events matrix, enable Slack for the case events you care about. You can send a test message to confirm the connection.
Slack messages about a recovery case include a Mark as sent action, so a teammate can record a manual follow-up from Slack. Disconnecting the app from Settings → Channels → Slack revokes the token and stops all Slack posts.

​
Escalation

Escalation is separate from case-event notifications. It looks at each new case and, when it matches, stops the automated recovery sequence for that case and alerts your team — the idea being that some cases are better handled by a person than by dunning. Two things trigger it:
  • Suspected fraud — a lost/stolen-card failure or a fraud-related decline code escalates immediately, before any rules are evaluated. This is on by default.
  • Your escalation rules — conditions you define on the case.
When a case escalates, Airdun sets it to an Escalated state, records the reason, always writes a notification to the in-app bell, and posts to Slack (to the matching rule’s channel, or your default alert channel).

​
Escalation rules

Configure rules under Auto-Pilot → Configuration → Escalation. A rule is a set of conditions plus the Slack channel (and optional @mentions) to notify.
  • Conditions within a rule are combined with AND; multiple rules act as OR — the first matching rule wins.
  • Each condition is field operator value.
Operators: EQ, NEQ, GT, GTE, LT, LTE, IN, NOT_IN, CONTAINS. Fields you can match:
A rule that references an enrichment.<field> is skipped for a case that has no enrichment snapshot (for example, if your endpoint timed out). Rules that don’t reference enrichment still evaluate normally. See Enrichment.
There is no weekly report or email digest. Merchant-facing recovery notifications are the in-app bell and Slack only.