Escalations

Notify the right people when a high-criticality finding needs attention.

What Is an Escalation?

Most traces are handled by your agents without anyone needing to step in. An escalation is a notification: Velatir tells the right people through your connected channels that something happened.

This is not a hold. The person’s prompt is not paused waiting for someone to click Approve in the dashboard. An Enforcer has already allowed or blocked the trace. The escalation is how reviewers find out.

Human review that does change access lives on the agents themselves: Gatekeeper access requests and Data Protector false-positive challenges.

When a Trace Is Escalated

A high-criticality finding on an Enforcer notifies your channels. You decide which findings are high criticality through your Data Protector categories and your instructions. Observer agents flag for review in Assessments; they do not notify channels.

Connect a Channel

Escalations are sent to the channels you connect under Settings → Channels.

Slack

Connect Slack from the dashboard, then add Velatir to the channel where your reviewers work. Escalations arrive there.

Microsoft Teams

Connect Teams from Settings → Channels. Velatir generates a one-time code.

1. Add the Velatir app to the channel, group chat, or personal chat that should receive escalations.
2. In a channel or group chat, mention the bot with the code: @Velatir connect <code>.
3. In a personal chat, send the code on its own. A reply from the bot confirms the connection.

The code expires after a short window; generate a new one if it lapses.

Text message

Add a phone number to receive escalations as SMS. The number must be verified. Text-message channels are an entitlement — if the option is locked, contact us to turn it on.

You can send a test notification from the channel card to confirm delivery without waiting for a real finding.

Delivery

Each channel is notified independently. One channel failing does not stop the others. On the trace you can see whether a notification was sent.

Every high-criticality finding, and the channels it was sent to, stays on the session record.

---

Trace lifecycle

Where notification fits in a trace’s journey.

Data Protector

Set which findings are high criticality.