Required Tagging | Community
Skip to main content
Submitted

Required Tagging

Related products:Core Inbox
  • January 20, 2025
  • 3 replies
  • 31 views

Ben Griese

When setting up tags, I’d really like the ability to toggle on requiring tags in order to close a conversation. I saw this conversation from a few years ago that asked for something similar:

However, as mentioned in that convo above, setting up a keyword-based auto-tagging system would be quite a lift for us, considering ever-changing tags + trying to ensure we got all relevant keywords to trigger the auto-tagging workflow. That, versus having a simple toggle to require the team to tag each conversation with the most relevant tag. I really just want that ability so we can have more robust data by having ALL conversations tagged 😅

3 replies

Trevor
Innovator ✨
Forum|alt.badge.img+4
  • Innovator ✨
  • January 21, 2025

I’ve moved a lot toward the “Topics” for reporting, and setting up a lot of topics based on keywords and specific phrases. It’s powerful, and can be used in custom reports as well. The great thing about it, is it works with previous conversations, and isn’t future-only like setting up auto-tagging rules/workflows. 

I bet Intercom will also come out shortly with some AI based reporting that makes tags obsolete as well. As great as tag reporting can be, I’ve strayed away recently because of too much human error, missing tags. 


Forum|alt.badge.img
  • Connector
  • January 21, 2025

Hey Ben,

I just saw this and thought of something that might be helpful for you!

If I understand correctly, you’re looking to make it mandatory for agents to tag a conversation before closing it, right?

If that’s the case, we’ve implemented something similar on our team. We’ve separated our metrics into two categories: tags and root causes. We use Intercom tags to flag key words and bot replies, but to generate more accurate reports and better understand the conversations, we created root causes.

Essentially, we have a predefined list of contact reasons, and agents are required to select one before closing a conversation. To set this up, you just need to create a custom attribute, which you can make a mandatory field in the conversations.

The great thing is that these root causes also appear in reports, and you can customize them based on the complaints or topics you receive most often. It’s been super useful for our team, and I think it could work well for you too!

Let me know if you’d like any help setting it up or have any questions. :)

Here an example of how it looks to the agent:

So it can only be closed once selected


ericgriff
Forum|alt.badge.img+2
  • Active User
  • May 6, 2025

@Ben Griese Totally understand where you’re coming from with building and maintaining a keyword-based system is a huge lift, especially with evolving tags and language of various conversation topics. 

That’s actually why we built our integration for Intercom: it auto-tags every conversation based on the full context, so you get consistent, structured tagging without having to manage keywords or rely on the team to do it manually. We’re on the Intercom App Store under Dimension Labs.