# Referral Follow Up Notifications Source: https://docs.astalty.com.au/guide/notifications/referral-follow-up-notifications > Nudge your team when a referral has been sitting in the same status for a set number of days. Astalty Premium - This feature is part of the Astalty Premium plan. See What Premium includes. ## Overview [Referral Follow Up](https://app.astalty.com.au/notifications/referral-follow-up) notifications alert your team when a referral has been sitting in the same status for a set number of days without progressing - so referrals stop quietly stalling between acceptance and completion. This is different from [Referral Notifications](https://docs.astalty.com.au/guide/notifications/referral-notifications-1), which alert your team the moment a **new referral is submitted**. Referral Follow Up notifications are about referrals that have **already been received** and haven't moved since. Only **Admins** can open **Notifications** and create, edit, clone or delete these notifications. Managers, Team Members and Support Workers can't open the Notifications page. This can't be changed per user. ## Finding the notification 1. Go to [Notifications](https://app.astalty.com.au/notifications) in the main menu. 2. Open the **Forms** group. 3. Select **Referral Follow Up** (just below **Referrals**). ## Creating a Referral Follow Up notification On the Referral Follow Up page, click **Create Notification**. ![The Create Referral Follow Up Notification form with Days set to 7, Statuses set to Accepted, an empty Notification email content editor, Assigned user ticked under Notification recipients, and User Groups and Users drop-downs.](https://docs.astalty.com.au/assets/referral-follow-up-notification-form.png) ### Days Enter how many **Days** a referral can sit in one of the monitored statuses before Astalty alerts you. The default is **7**, and you can enter anything from **1** to **365**. The count starts from the **last time the referral's status changed** - not from when the referral was created. Moving a referral to a new status resets the clock. > **The alert is sent once, on the day the referral hits the threshold** > > Astalty checks once a day, at about 8:50am Brisbane time, and alerts on referrals that reached your threshold **that day**. It is a one-off nudge, not a daily reminder: a referral set to 7 days is alerted on day 7 and then never again, even if it sits in that status for another month. > > If a referral moves out of a monitored status and later moves back in, the clock restarts and it can alert again once it reaches the threshold a second time. ### Statuses Choose which referral statuses to monitor. You must select at least one. The available statuses are: - **New** - **Under Review** - **Waitlist** - **Accepted** - **Declined** - **Completed** A referral stops triggering the notification once it moves out of the statuses you've selected. > **Start with the statuses that stall** > > **Accepted** is the default, and is usually the most useful - it catches referrals that were accepted but never converted or completed. **Under Review** and **Waitlist** are also good candidates. Bear in mind that **Declined** and **Completed** are selectable too, so avoid picking those unless you genuinely want to be nudged about finished referrals. ### Notification email content Optional. If you send email notifications, this rich-text content is **added to** the email body (for example, the steps your team should take when chasing a stalled referral). It doesn't replace the standard message, and it doesn't appear in the in-app notification. ### Notification recipients Select at least one of: - **Assigned user** - the user the referral is assigned to. On by default. - **User Groups** - one or more staff [User Groups](https://docs.astalty.com.au/guide/settings/users-settings/user-groups) - **Users** - specific team members > **Unassigned referrals** > > If **Assigned user** is your only recipient, referrals that aren't assigned to anyone won't notify anybody. Add a user group or specific users as a safety net if you want every stalled referral picked up. > > Re-assigning a referral doesn't restart its clock, so a referral that has already passed the threshold won't alert its new assignee. ### Notification methods - **Within Astalty**: in-app notification. On by default. - **Email**: email to each recipient. Off by default. You can enable either or both, but at least one is required. When you are ready, click **Add Notification** (or **Update Notification** if you are editing an existing one). ## Managing notifications You can create more than one Referral Follow Up notification - for example, one for **Under Review** at 3 days and another for **Accepted** at 14 days. The list shows each notification's **Threshold**, monitored **Statuses**, **Delivery** methods, and **Recipients**. There's no name field: rules are identified by their threshold and statuses. Click a row to edit it. From the actions menu on a notification you can: - **Edit**: change the days, statuses, recipients, methods, or email content - **Clone**: start a new notification from an existing one - **Delete**: remove the notification **Delete** is also available inside the edit drawer. There's no way to pause a notification, so delete it if you no longer want it to run. > **Overlapping rules both send** > > If a referral matches two notifications on the same day, both are sent. Keep an eye on overlapping thresholds and status sets to avoid over-notifying your team. ## What recipients see ### In Astalty The in-app notification is titled **Referral Follow Up**. The message reads *"Referral {reference} has been {status} for {number} days and needs following up."* with a **View Referral** link that opens the referral. ### Email The email subject is **Referral Follow Up - {reference}**. The body carries the same message, followed by any custom content you configured, and a **View Referral** button. Deactivated users are not included as recipients, even if they are in a selected user group. Recipients are also de-duplicated by email address, so a user who is both the assignee and in a selected group only gets one notification. ## Things to know - **Archived referrals are skipped** - they never trigger a follow up notification. - **Referrals that existed before this feature shipped** use the last time their record was updated as the starting point, rather than a true status-change date. Because the alert only fires on the exact day a referral reaches your Days threshold, an older referral that was already past that threshold won't trigger one - it will only start behaving normally after its status changes again. ## Related - [Referral Notifications](https://docs.astalty.com.au/guide/notifications/referral-notifications-1) - alert your team when a new referral is submitted. - [Referral Follow Up](https://docs.astalty.com.au/guide/referrals/referral-follow-up) - how to work through and progress a referral. - [Waitlist](https://docs.astalty.com.au/guide/referrals/waitlist) - park referrals you can't take on straight away. - [Incident Follow Up Notifications](https://docs.astalty.com.au/guide/notifications/incident-follow-up-notifications) - the same idea for incidents that stop progressing.