# Notifications

Choose the Slack channel for Risotto's system notifications, and set when Risotto nudges approvers, passes approval requests on, and auto-resolves inactive tickets

Configure how Risotto communicates with your team. Go to **Settings > Notifications**. Only Org Admins see this page.

All four settings are in the **Organization Preferences** card. Each setting applies to the whole organization. A department can set its own [auto-resolve delay](#department-specific).

*Product example: The Notifications settings page in the Risotto dashboard, with the notifications channel set to #it-alerts and the approval and auto-resolve delays.*

## Set the notifications channel

1. **Open the channel picker**

   Click the picker next to **Notifications channel**. It shows the current
   channel, or **Select channel...** if there is none.

2. **Choose the channel**

   Type part of the channel name, then click the channel. You can also paste
   a channel ID, such as `C0123456789`, and click **Use channel ID**.

   *Product example: The Notifications channel picker open in the Risotto dashboard, searched for it, with #it-alerts highlighted.*

3. **Save**

   Click **Save** in the top-right corner of the card. The message
   "Preferences saved" appears. To discard your changes instead, click
   **Cancel**.

   *Product example: The Organization Preferences card in the Risotto dashboard with #it-alerts chosen, and Save.*

For a private channel, invite Risotto to the channel first. Otherwise the save fails with "Notifications channel … not found. If this is a private channel, make sure to invite Risotto to the channel first."

To stop the notifications, open the picker, click **Clear**, and click **Save**.

The other settings on this page are number fields. Type a value, then click **Save**.

## Organization preferences

### Notifications channel

System notifications related to your organization are posted to this Slack channel, such as indexing progress, knowledge base article creation, and [alerts](https://www.tryrisotto.com/docs/dashboard/alerts).

### Next approval delay

Number of hours that Risotto waits after the nudge before it passes an unanswered approval request on. Defaults to 24 hours. You can enter 0 to 168 hours.

This setting applies only to an approval chain that asks approvers one at a time and needs only one of them to approve. If the current approver does not answer in time, Risotto asks the next approver. If the last approver also does not answer, Risotto escalates the ticket to a human. This escalation uses the department's [escalation routing](https://www.tryrisotto.com/docs/dashboard/settings/departments#escalation-routing), the same as any other escalation.

The approval request then expires. In Slack, Risotto removes the **Approve** and **Deny** buttons from the approval messages that nobody answered and adds "This request expired before anyone decided." Microsoft Teams messages keep their buttons. A click on them records nothing (see [Access approvals](https://www.tryrisotto.com/docs/concepts/ticket-lifecycle#access-approvals)).

Other chains get one nudge and nothing more:

- A chain with one approver
- A chain that asks all approvers at the same time
- A chain in which every approver must approve

Risotto does not pass these requests on or escalate them on its own. The dashboard has no action to send an approval request again.

### Nudge delay

Number of hours after which Risotto nudges the approvers of an approval request. Defaults to 3 hours. You can enter 0 to 168 hours.

When the delay ends, Risotto sends one reminder to the approvers who have not answered, for example "Just a friendly bump on this request!" for an access request. The reminder is a reply in the thread of the approval message. In a chain that can pass on, the reminder also says when Risotto will ask the next approver.

### Auto-resolve delay

#### Organization-wide

Auto-resolve resolves tickets after a number of business days without activity. Business days exclude Saturday and Sunday. The default is 7 business days, which is also the maximum. The minimum is 1 day. To turn off auto-resolve, set the delay to 0.

Before it resolves a ticket, Risotto posts one nudge in the ticket's thread:

- With a delay of 5 days or more, the nudge comes 2 business days before the ticket is resolved.
- With a delay of 2 to 4 days, the nudge comes 1 business day before.
- With a delay of 1 day, Risotto resolves the ticket without a nudge.

The nudge says:

> This is an automated support message.
>
> This ticket will be closed soon due to inactivity. If you prefer to keep it open, just post a reply. Otherwise you can ignore this message.

If the requester replies, the nudge state of the ticket is reset.

Auto-resolve applies only to tickets in the **Open**, **In progress**, and **Awaiting response** statuses. It never resolves a ticket in **Awaiting approval** or **Awaiting support**, however long the ticket is inactive. To move a stale approval on, use [Next approval delay](#next-approval-delay). It also skips a ticket whose access request waits for someone to grant or remove the access by hand.

#### Department-specific

You can set the auto-resolve delay for each department. Set it in **Settings > \<department> > Auto Resolve**. The department delay works the same way as the organization delay. When a department has its own value, that value applies to the department's tickets, not the organization setting. For example, if the organization delay is 0 and a department's delay is 7, that department's tickets still get the nudge and are auto-resolved after 7 business days. Clear the department field to use the organization setting.

Each department can also **skip auto-resolve for agent-assigned tickets** and **escalate tickets waiting on customer** after a set number of hours. See [Auto Resolve](https://www.tryrisotto.com/docs/dashboard/settings/departments#auto-resolve).

Source: https://www.tryrisotto.com/docs/dashboard/settings/notifications
