---
key: check-team-message-history
title: Check team message history
audience: staff
section: settings/communications
routes: ["/settings/org/team-message-log"]
permissions: ["communications.team_messages.read"]
features: ["settings.org.team_messages"]
since: 0.0.1
updated: 0.0.1
status: published
summary: Preview upcoming team messages and check each teammate's delivery results without changing their notification inbox.
keywords: [team messages, what went out, notification log, tomorrow work, failed delivery, technician notifications]
related: [tell-your-team-about-tomorrows-jobs, see-what-customers-are-being-sent]
---

In the sidebar, open **Settings**, then **Team Message Log** under **Communications**. The page address is `/settings/org/team-message-log`.

## Steps

1. Choose **Coming up** to preview expected messages and messages already scheduled. Expected messages use the current Schedule and delivery settings; they can change before they go out.
2. Choose **History** to see recorded messages, or **Needs attention** to find failed, overdue or unconfirmed deliveries.
3. Search by teammate or message. Open **Filters** to narrow the message, channel or status. On a computer, press a teammate's name to show their messages.
4. Click anywhere on a row to open the message, or press **Preview** or **View**. On a phone, tap the message card. With a keyboard, move to the row and press Enter or Space. Pressing a teammate's name in a row still filters the list instead. The drawer shows the recipient, time, content, each channel's result and why anything didn't go out. Reading it here does not mark that teammate's notification as read. The open message has its own address, so Back closes it.
5. Use **Message settings** to change future messages in **Team messages**.

## What you see

Times in the list use your organization's timezone. The drawer also shows the recipient's local time when it differs. History covers up to 60 days; message content is kept for 30 days.

Sent means the provider accepted the message. Delivered means the provider confirmed delivery. Available in Nova means it was made available in the recipient's Nova inbox. Delivery unconfirmed means Nova does not have a reliable answer; opening this page does not send another copy.

A day list or team overview with nothing scheduled at its send time appears as skipped straight away, with the reason "Not sent: this teammate had nothing on the Schedule that day, and this message only goes out when something is scheduled." Work added later that evening does not send it; "Your schedule changed" tells people about later changes. The message's settings decide whether an empty list should be sent. Someone who gets "Tomorrow across the team" sees their own "Tomorrow's schedule" for that evening as skipped, with the reason "Not sent: this teammate gets Tomorrow across the team that evening instead, so a second list would repeat it." Personal notification preferences still apply.

## Why a message or channel didn't go out

Every skipped, cancelled or failed message says why in one sentence, and so does each channel in the open message. For example:

- "Not sent to the phone: this teammate isn't signed in to the Nova app with notifications on."
- "Not sent to the browser: this teammate hasn't turned on browser notifications on any computer."
- "Not sent: what this message was about was removed or changed before it went out."
- "Cancelled: the visit moved, so the reminder for the new time replaces this one."

When Nova has no sentence for a reason yet, the message says "Nova didn't send this one. Open it to see what happened on each channel."

People with permission to see other teammates' message history can review those teammates. Everyone else sees their own messages. Your branch access still applies.