What To Do After Receiving a Notificaiton

A notification from Stat Temp means that a sensor or monitor has detected a condition that requires awareness or review. Some notifications require action, while others are informational. Understanding what to do next helps ensure events are handled efficiently and documented correctly.

This guide walks you through what happens after a notification is received and how to respond using the Events data grid and Event Page.

What Happens When an Event Is Triggered

As soon as a condition meets the rules of its assigned notification, Stat Temp:

1. Creates an event in your portal

The event includes:

Device name
Condition that triggered the event
Time the issue began
Current status
History of temperature or communication

The event remains open until the issue clears or the required actions are completed.

2. Sends notifications based on the notification chain

Notifications are delivered:

If still active after the notification delay period has passed
In the order defined by the chain
Using the delivery methods chosen (email, SMS, phone)
Only to recipients whose schedules allow alerts at that time (if conditional alerting is used)

3. Records everything in the event’s log

Every action related to the event is recorded in the event’s activity log, including:

Notification delivery
Acknowledgments
Snooze activity
Notes
Resolution actions

This ensures a complete and auditable history.

4. Continues Sending Alerts (if repeat is enabled)

Repeat behavior continues until the event is:

Acknowledged
Cleared by condition recovery
If repeat is not set to repeat forever, it will repeat the designated number of times

You will never lose visibility into an active issue.

What To Do When You Receive a Notification

Actions vary depending on the notification configuration, but the general flow is the same:

Step 1. Review the Event

After receiving a notification, you can access the event in one of two ways:

Option 1: Open the Event from the Notification

Click the link included in the notification message.

Depending on how the notification is configured, clicking the link may:

Open the Event Page directly, where further action can be taken, or
Automatically acknowledge the event and then open the Event Page

In either case, the event details will be displayed so you can review the condition, history, and available actions.

Option 2: Review the Event from the Events Data Grid

Navigate to Events at the top of the Stat Temp portal.

By default, the Events data grid displays open events only, allowing you to quickly focus on items that may still require attention. From the grid, you can:

Assess the event’s status using the bell icon and status columns
See whether acknowledgment or resolution is still required
Take actions such as acknowledge, resolve, or add notes directly from the grid

In many cases, the data grid provides enough information to determine next steps without opening the full event.

Step 2. Acknowledge the Event (If Required)

Acknowledging an event confirms that someone is aware of the issue and has taken responsibility.

When an event is acknowledged:

Notifications stop for that notification
Escalation stops (if configured)
The event remains open until the condition clears

Acknowledgment can occur:

Directly from the Events data grid (including bulk acknowledgment)
From the Event Page
Automatically, if the notification uses an auto-acknowledge link

Once acknowledged, additional actions (such as Resolve or Snooze) may become available, depending on the notification’s settings.

If Auto-Acknowledge is enabled, simply clicking the event link acknowledges the event automatically.

Step 3. Review What Happened

Once inside the event:

Look at the latest readings
Check the event log for changes in status
Confirm when the condition started
Check any notes added by teammates
Evaluate whether the condition is still active

This helps you determine the right next step.

Step 4. Take the Appropriate Action

Depending on the situation and the notification’s settings, you may:

Action	When It Applies	What It Does
Acknowledge	You received an alert and need to stop repeat notifications for yourself You are taking responsibility for the event The event requires acknowledgment before additional actions can occur	Stops alerts for you and stops escalation. Marks the event as acknowledged and unlocks additional options (such as Resolve or Add Notes) if they are enabled in the notification settings.
Snooze	The notification is configured with Snooze enabled Snooze applies after acknowledgment	Automatically pauses notifications for the defined snooze period. Alerts resume if the event is still active when the snooze ends. Snooze is controlled by notification settings.
Resolve	The notification requires resolution (common for excursions) The issue has been corrected and needs documentation Compliance or workflow requires recording how the issue was addressed	Closes the event after acknowledgment. Prompts the user to select a resolution status and add notes when required.
Add Notes	You want to document corrective actions You need to record observations or environmental details You are providing shift-to-shift communication or internal updates You need additional context for audits or compliance	Adds a written entry to the event log. Notes can be added at any time—before, during, or after resolution—and remain as part of the event’s permanent record.

How Events Close

An event cannot close until it has cleared. Events can close in one of the following ways:

1. Auto-Close (notification setting)

Notifications will automatically close if they clear before reaching their notification delay.

2. Required Actions

If the notification requires acknowledgment or resolution, the event closes only after those conditions are met.

What To Expect After an Event Is Closed

Once closed:

The event is archived for reporting
All notes, actions, and timestamps remain in the log
You can continue to review it for audits or trend analysis

Next Steps

Now that you know what happens when an event triggers and how to respond, the next section explains how Stat Temp manages alert frequency over longer periods.

Continue to:

→ Notification Throttling (Long-Running Events)