We have over a dozen products and I'm having a hard time visualizing how to best organize them. Curious to what other clients have done for best practices? Is it better to lean on tags, collections, or a combination of both?
With my clients, I explain the benefit of Collections is that you are able to dictate who on your team is able to see data - which makes it great for sensitive information or teams that would prefer to work in silos.
You didn't mention custom fields - but I would recommend them to any client who wants to organize their content by product line, department, language, etc. Mainly because of their ability to customize (ie using checkboxes, drop-downs) and the option to add them as a filter.
Tags on the other hand can be common themes across both collections and tags.
Let me know what you think!
This is so helpful, Helene! Leveraging Custom Fields is such a great idea to further customize Product data and make it specific to the different Product Lines! I love that you shared the ability of checkboxes and dropdowns, makes it so much more simple to further categorize and organize content where it belongs. Thank you!
I'd echo Helene's comment about collections and custom fields. I think that can be a great way to manage product content. I usually recommend collections if their product teams operate separately (i.e. each team only needs to see content relevant to the product they support). I think custom fields are a great approach if you have teams working across multiple products and/or responses that are spanning multiple products. In both scenarios, if I'm responding to a project for product x and product y, I can set those filters at the project level which allows the team responding to see content relevant to all products proposed on a given project and not irrelevant content. It also allows for layering of your search filters when used in conjunction with your tags (i.e. I want to see functional information for product x and product y).
I recently started using collections for different products and love that content can be separated. What would you recommend for separating content for prospects versus current customers? Collections or custom fields?
@Jackie Barnhart I'd think about who needs to access the content to make that decision - if the same teams need access to both prospect AND customer facing content, then I'd recommend custom fields or tags. But if you have some teams only needing access to prospect-facing content and others only need customer-facing content, then collections are a great choice. Collections are most useful when you need to control who has access to the content whereas custom fields and tags are more useful for categorization and organization regardless of who needs access.
About the event This 60 minute session, part of our two part Foundations series, helps new or returning users understand the full project lifecycle in Responsive and how AI can support faster, more accurate response work from start to finish. What You’ll Learn In this session, we’ll walk through how to bring Projects into…
Discover what is new in the April 2026 release as the Responsive Academy and Product Team spotlight the most important updates and show you how to put them into practice for real impact across your workflows. If you cannot join live, register anyway and we will send the recording to you automatically.
Heading to BPC Denver next month? Come say "hi" to our Responsive team! Visit our booth to learn more about Responsive AI and how teams are using it to get fast, trusted answers. You can also book time to talk with us and create a plan for your next win. (Note: this is only available to BPC Denver registrants) Registrants…
Build or buy: What it takes to monetize organizational knowledge with AI
Understanding Vendor Risk Management
The Promise of Strategic Response Management | Responsive
