Bulk Mention Management - Mark as Read and Clear All Options | Community
Skip to main content
Submitted

Bulk Mention Management - Mark as Read and Clear All Options

Related products:Core Inbox

Currently managing large volumes of mentions (3,000+) requires opening each conversation individually to clear the unread count. There's no bulk functionality for mention management.

Requested features:

  • Bulk 'mark as read' option for mentions
  • Bulk 'clear all mentions' functionality
  • Mass selection tools for mention management (similar to conversation bulk editing)

Current limitation: Only way to clear unread mentions is going to Inbox → Mentions → Unread mentions, then opening conversations one by one.

This would significantly improve efficiency for users with high mention volumes who need streamlined inbox management.

4 replies

Forum|alt.badge.img
  • Connector
  • July 30, 2026

We badly need this too! Can this be added? If not an actual option in the mention view in inbox, at leas an API option?
I saw it was requested in less details a little while ago here 

 


  • New Participant
  • August 27, 2026

We need this so badly - a colleague has thousands of mentions and with no way to clean it up there isn’t a way to start fresh


Forum|alt.badge.img
  • Connector
  • October 16, 2026

our workflows @ team inboxes for reminders on unassigned tickets, upcoming SLAs, breached SLAs… as a manager and admin I therefore have a ton of unread mentions and the real mentions get lost. looking at 1k of mentions that i can in no way clear out. bulk would be great, or any way to filter out!


Forum|alt.badge.img+3
  • Intercom Team
  • October 16, 2026

Hii Hedi! Reina from the Dublin technical team here.

Yeah, for now at least, there's no bulk mark-as-read or clear-all for mentions right now. The only way is opening each one individually, which obviously doesn't scale when you're looking at thousands. No API option for it either.

Gemma's point about workflow-generated mentions burying real ones is a good one too. However I can see that this has been raised with our product team, and fingers crossed that it'll be implemented down the line! :)