---
title: "Mark an inbox thread unread again"
description: "You can now mark a read inbox thread as unread again, so it comes back into your unread queue and count for later follow-up when you have time."
canonical: "https://firstsales.io/changelog/mark-inbox-thread-unread/"
---

1. [Home](/)
2. [Changelog](/changelog/)
3. Mark an inbox thread unread again

[All updates](/changelog/)

NewJuly 28, 20265 min read

# Mark an inbox thread unread again

You can now mark a read inbox thread as unread again, so it comes back into your unread queue and count for later follow-up when you have time.

New

Mark an inbox thread unread again

Inbox thread options menu with the mark unread action

Sometimes you open a reply, realize you cannot deal with it right now, and want it to come back into view later. You can now put it back in your unread queue on purpose.

## What changed

The inbox previously only moved one direction: a thread became read once you opened it, and there was no way to undo that. If you opened a reply to skim it, got pulled away, and came back later, you had to remember it existed on your own, because it no longer showed up anywhere as needing attention. Given how many replies can land in a busy inbox on any given day, relying on memory alone is a real way for things to fall through the cracks.

Now you can mark any thread as unread again from the inbox. Doing so puts it back into your unread count and your unread view, exactly as if you had never opened it. This works on any thread regardless of how it got marked read in the first place, whether you opened it yourself, a teammate opened it, or it was marked read automatically as part of some other inbox action.

This is a small change on paper, but it fills a real gap in how the inbox tracked state. Read and unread are the two states most people use to triage a queue, and until now, FirstSales inbox only supported moving from unread to read. Adding the reverse direction makes the read state something you control fully, not something that only ever moves forward.

The change applies consistently across the inbox, regardless of how many mailboxes you have connected or how a thread first arrived. A reply routed to a shared team inbox behaves the same way as a reply in a personal mailbox: once you mark it unread, it shows up as unread everywhere that view is shown, including any unread counters in navigation or notifications tied to that mailbox.

## How to use it

Open your inbox and find the thread you want to flag for later. From the thread's options, choose the action to mark it unread. The thread immediately reappears in your unread filter, and your unread count updates to include it, the same as if a brand new reply had just landed.

There is no limit on how many times you can toggle a thread between read and unread, so you can use this as a lightweight way to bookmark conversations you need to revisit, not just a fix for threads you opened by accident. If a reply needs input from someone else on your team before you can respond, marking it unread again is a simple way to signal that it still needs attention, without setting up a separate task or reminder system.

You can do this from the thread list view or from inside an open thread, depending on where you are in your workflow. If you are triaging a batch of replies in the list view, you can mark several as unread in sequence without opening each one individually. If you are already inside a thread reading it closely and decide midway that you need to come back to it later, you can mark it unread from there instead of navigating back out first.

This pairs naturally with however you already filter or sort your inbox. If you sort by unread first, marking a thread unread again brings it back to the top of that view, keeping your highest-priority conversations visible without you having to manually track which ones still need a response.

Because the action is reversible, there is little downside to using it liberally. If you mark a thread unread and later decide it did not actually need to come back into view, you can simply open it again, which returns it to read the normal way. There is no separate confirmation step or warning to click through, since toggling read state is a low-stakes action you should be able to do quickly and often.

## Why it matters

An inbox that only tracks read state one way does not match how you actually work through replies. You skim, you triage, you come back. Being able to mark a thread unread again means your unread queue can double as a real to-do list for conversations, not just a record of what you have not clicked on yet. That distinction matters more than it sounds: a queue that only tells you what you have not seen is less useful than one that tells you what still needs action from you.

This is especially useful when a reply needs a thoughtful response you cannot write in the moment, like a prospect asking a detailed question, raising an objection, or requesting something specific that takes research to answer properly. Instead of relying on memory or a separate note, you can put the thread back where you will see it, right alongside every other reply that is waiting on you.

For teams, this also creates a shared signal. If someone else on your team opens a thread, skims it, and marks it unread again because it needs a response from a specific person, that state is visible to everyone looking at the shared inbox, not just to the person who made the change.

Over time, a habit of using unread state deliberately, rather than just as a byproduct of what you have and have not opened, tends to make an inbox easier to trust. You stop wondering whether an unread thread is actually new or just something nobody has looked at in a while, because you are the one deciding what stays flagged as needing attention.

This is a small feature, but small gaps like this tend to be the ones people notice the most in daily use, precisely because the workaround was always awkward: keeping a separate note, leaving a browser tab open, or just trying to remember. Closing a gap like that does not change how the inbox looks or how campaigns run, but it changes how much you can rely on the inbox to actually hold your attention list for you, instead of you having to hold it yourself.

## Availability

Marking a thread unread is available in the inbox for every connected mailbox.

[ PreviousAdd contacts to a paused campaign](/changelog/add-contacts-to-paused-campaign/)[Next Chat sets up a whole Autopilot campaign](/changelog/chat-sets-up-autopilot-campaign/)