Every Act signal starts out unread. Some genuinely need action, but others only need acknowledgement, for example a minimum price hit during a period of known low demand that you have already decided not to touch. Without a way to set these aside, they keep drawing your attention and inflating the counts the Signals Calendar is meant to help you cut through.

Marking signals as read is how you turn the calendar into a routine rather than a one-off check. Once you have reviewed everything currently on it and marked it read, the calendar's indicators and counts only reflect what is genuinely new since your last pass, so the next time you open it, you are looking at what changed rather than re-reading what you already handled. This article covers how to mark Act signals as read, individually or in bulk, including across several days at once from the calendar itself, and what changes once you do.

Note: the Signals Calendar is currently available to pilot and select accounts only. If you do not see it on your Optimization screen and would like it enabled for your account, reach out via the in-app chat.

For what each Act signal means and how to act on it, see Act Signals and the Signals Tab in Quick View. For an overview of the Signals Calendar itself, see Signals Calendar Overview.

From the Signals tab of the property-level Quick View, each Act signal card carries its own small checkbox-style control. Selecting it marks that one signal as read, without affecting any other signal for the day.

Note: this sets the read state for the property, not just for you. See Who sees the change below, it is the single most important thing to know about this feature.

Next to the Act (n/n) heading in the Signals tab, a Mark All as Read action marks every Act signal for that day as read in one go.

You do not need to open each day's Quick View one at a time to catch up. Select multiple dates directly on the Signals Calendar, then mark every Act signal across that selection as read in one action. This is the fastest way to clear a backlog or catch up the calendar to today before you start relying on it for what is new.

The footer highlights the period this is being applied as well as the count and type of signals marked as read.

A read signal can be returned to unread, so marking something as read is never a one-way action. If a signal resurfaces as worth a second look, or you marked it read by mistake, you can reverse it the same way you set it, from an individual card, from Mark All as Read for a day, or from a multi-date selection on the calendar.

Note: a multi-date selection can only be marked as unread in bulk when every signal across that selection is already read. If your selection mixes read and unread signals, clear the read ones individually or day by day instead.

On the Signals Calendar, a read signal's indicator changes appearance rather than disappearing, so it recedes without being hidden. Read signals are also left out of the per-type counts shown in the Act dropdown; a day whose only signal of a given type is read no longer counts toward that type, while a day that still has unread signals keeps its normal indicator and count for those.

In the Signals tab, the card stays visible in its read state, but cards are ordered so unread ones remain the focus. The Act (n/n) heading reflects this directly, the first number is how many signals are still unread against the total for the day, for example Act (2/2) when both are unread, so you can tell at a glance whether there is anything left to review.

Read state is set at property level, not for the person who marked it. Once a signal is marked read, every user with access to that property sees it as read too, and the same is true in reverse, if a colleague marks something read, you will see it that way as well. It persists across sessions and page reloads, so it stays set until someone marks it unread or the underlying issue resolves on its own.

When whatever triggered the signal is no longer true, for example the price setting is edited so the threshold is no longer hit, or a freeze is lifted, the signal disappears on its own, regardless of whether it was marked read or not. There is no cleanup to do afterward.

A good habit is to clear your backlog once, using the bulk option on the calendar if you are starting fresh, and then review and mark signals as read as part of your daily check-in. From that point on, the counts and indicators you see are a reliable signal of what is actually new, rather than a running total of everything that has ever come up, which is what makes the calendar worth scanning quickly rather than re-reading in full every time.