> For the complete documentation index, see [llms.txt](https://herd-security.gitbook.io/herd-security-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://herd-security.gitbook.io/herd-security-docs/campaigns/nudges.md).

# Nudges

Send reminder nudges to users with incomplete assignments and review per-nudge delivery history for your compliance campaigns.

## Nudges Overview

Nudges are reminder notifications Herd sends to users who still have outstanding work—an incomplete training, an unfinished track, or a policy that hasn't been acknowledged yet. They come in two flavors: **automatic** nudges that Herd schedules around each item's due date, and **manual** nudges you trigger yourself to prompt everyone who's behind in a single action. Either way, you can track exactly what was sent and how people responded.

Herd delivers each nudge through the user's preferred platform—**Slack**, **Teams**, or **Email**—so reminders reach people where they already work. For audit and follow-up purposes, every nudge is recorded, giving you a per-nudge history of who was reminded, when, whether delivery succeeded, and what the user did next.

{% hint style="info" %}
"Nudge" is Herd's word for reminders about its **own** content: trainings, tracks, policies, and campaign items. A training's automatic reminder schedule is set on the training's **Nudges** tab and manager follow-up on its **Escalations** tab (see [Assigning Users to Training](/herd-security-docs/trainings/getting-started-with-trainings/assigning-users-to-training.md#due-dates-nudges-and-escalations)). To chase something people must finish *outside* Herd, use the separate [Reminders](/herd-security-docs/messaging/reminders.md) page under **Messaging**.
{% endhint %}

***

## Nudging Incomplete Users

From the **Reports** page, open the **Activity** tab and choose the **Training** section to remind every user who has incomplete, non-queued training assignments at once. (This surface used to live under **Settings → Monitoring**; old links redirect to the new location.)

### Step 1: Open the Nudge Incomplete Users Section

In the **Training** section of **Reports → Activity** you'll find the **Nudge Incomplete Users** section. It shows how many users currently have incomplete training and would benefit from a reminder, alongside the **Nudge All Incomplete** button.

The button is only enabled when there's at least one user who needs a nudge.

### Step 2: Review Who Will Be Nudged

Select **View details** to expand a list of the users who will be reminded, along with the specific incomplete trainings each one still has open. Choose **Hide details** to collapse the list again.

This gives you a chance to confirm the scope before anything is sent.

### Step 3: Confirm and Send

Select **Nudge All Incomplete** to open the **Confirm Nudge All Users** dialog. The confirmation explains what the action will do:

* Send nudge notifications through each user's preferred platform (Slack/Teams/Email)
* Only nudge users with incomplete, non-queued trainings
* Skip users who have already completed all assigned trainings
* Show detailed results after completion

Select **Send Nudges** to confirm. While the nudges are sending, the button shows a **Nudging...** state, and Herd reports detailed results once it finishes.

{% hint style="info" %}
Nudges are only sent to users who have an incomplete, non-queued assignment. Anyone who has already finished their assigned trainings is skipped automatically.
{% endhint %}

***

## Campaign Nudges

Each compliance campaign has its own **Nudges** tab in addition to its **Overview**. From a campaign you can prompt users on specific items and review the full delivery history for that campaign.

### Automatic Nudges (Auto-Nudge)

Campaign items remind incomplete users **automatically** — no action needed. Herd checks for due reminders **every hour** and delivers each one inside the recipient's own business hours, in their time zone (people without a time zone on file fall back to your organization's business hours). Nobody is reminded more than once per day.

For campaigns with an end date, auto-nudge by default:

* starts **3 business days before** the item's due date,
* repeats **daily** (every business day) until the user completes the item, and
* stops **5 business days after** the due date (so long-overdue users aren't messaged forever).

The first reminder follows the same cadence, counted from the day the person was assigned, so nobody is nudged on the day they join a campaign. Someone added close to the due date still gets their first reminder no later than the due day.

**Ongoing campaigns** (built by the agentic wizard) have no due-date window: they repeat on the **Nudge frequency (days)** you set at launch until each person is compliant. You can also turn **Automatic reminders** off there entirely.

Automatic reminders are delivered as direct messages on Slack or Teams (in Teams, a reminder for a training also re-posts the learner's current step and carries a **Resend current step** button) and appear in the campaign's Nudge history alongside manual nudges. A delivery that fails is retried on a later hourly check, and each attempt is listed in the history.

### Sending Campaign Nudges Manually

From the **Overview** tab of an active campaign, you can nudge the users who haven't finished a given training, track, or policy acknowledgement. Herd records each nudge and, where notifications are enabled, delivers them through the user's preferred platform and reports how many users were nudged.

### Reminder setup

The **Nudges** tab opens with a **Reminder setup** table: one row per campaign item (training, track, or policy) showing how its **Nudges** and **Escalations** are configured, with **Edit** links that jump to the item's own Nudges or Escalations tab. Reminders are set on each training or track and apply to everyone assigned it, so this table is the one place to check that every item in the campaign actually has a reminder schedule. Items a template will add when the campaign starts are marked **When the campaign starts**.

### Reviewing Nudge History

Below the setup table, the **Nudge history** for the campaign (labelled **Beta** in the app) begins with three summary cards that give you an at-a-glance view:

* **Total sent** — How many nudges have been sent for this campaign.
* **Delivered** — How many were successfully delivered, with the delivery rate.
* **Completed after nudge** — How many nudges were followed by the user completing the outstanding work.

Below the summary, the history table lists each individual nudge with the following columns:

* **User** — The person who was nudged. Select a user to filter the history down to just their nudges, or open their email to jump to their profile.
* **Channel** — The platform the nudge was sent on: **Slack**, **Teams**, or **Email**.
* **Sent** — When the nudge was sent.
* **Status** — The delivery outcome, shown as a labelled badge:
  * **Delivered** — The nudge was sent successfully.
  * **Failed** — Delivery did not succeed. Hover the badge to see the error detail.
  * **Skipped** — The nudge was intentionally not attempted (for example, the user has no Slack or Teams ID).
* **Action taken** — What the user did in response:
  * **Completed** — The user finished the outstanding work.
  * **—** — No response has been recorded yet.

The table starts with the most recent nudges. Use **Load more** to page through older entries.

### Filtering by User

Selecting a user's name in the history table filters the table to that single user and updates the summary cards to reflect just their nudges. A filter pill appears at the top—choose **Clear** to return to the full campaign history.