We often get the question from our community members if they can subscribe to products (product areas) since we have multiple products. Some customers want to follow specific topics about 1 or more products. In my opinion, this is a very important community b2b functionality.
Absolutely
Later this quarter, we’ll reach out again in this thread to kickstart discovery and better understand use cases we need to cover.
Later this quarter, we’ll reach out again in this thread to kickstart discovery and better understand use cases we need to cover.
Awesome… forward so much
All the votes have been transferred into this idea.
Hi
Our community just launched, and the ability to subscribe to tags has already become our top request.
Can anyone provide an update on this one? This is very important to us and our users.
Absolutely
Later this quarter, we’ll reach out again in this thread to kickstart discovery and better understand use cases we need to cover.
Can you share some particular use cases? How would you(r users) use it?
Hi
In our case we publish regular product updates. Each product update is a new article, therefore end user can’t be notified whenever new product update (article) is published within specific category.
Hello
Do you have a estimated timeline for when the feature might get implemented?
CC /
Hey ,
We are aiming to have the ability to subscribe to individual Product Areas in Q3/Q4 this year. I’ll let
Being able to subscribe to Product Updates for a specific product is critical for user engagement. It is rare for a user to have a login for more than one of the products we cover in our community, so they wouldn’t be interested in at least 80% of the the notifications they’d get for Product Updates.
After they click subscribe, a secondary question asking if they want ALL or a specific product area would be ideal!
Hi all, Thanks for your suggestion about subscribing to product areas. We're currently working on adding a hierarchy to product areas. Soon, members will be able to subscribe to one or more specific product areas, allowing for more tailored notifications.
I can’t wait!!!
Hi everyone!
We're excited to announce that we will be conducting research interviews for “subscribing to product areas” over the next two weeks. If you are interested in contributing to this initiative and helping us make it a reality, please use this link to schedule a call with us.
Thank you for your support!
This would be fantastic for our use cases!
One example:
We have product teams that currently share updates via mail merges or CSV distro lists. These updates are for a specific product with a wide range of sub-products. There are different types of updates sent out (monthly, ad-hoc), which would require numerous emails each month.
It would be far easier if customers were able to subscribe in a group for that product, based on which sub-product(s) they owned and which updates they would want to receive.
Hello
What is the current status of the IDEA “to subscribe to product areas”?
Thank you
Grzegorz
Thank you for the prompt response :)
Hey I see the focus of this conversation as switched to Products. But is it still in the vision to allow end-users to subscribe to tags?
I can imagine that when you have larger categories it can be overwhelming to subscribe to them… and allowing end-users to subscribe to specific tags can be a way to reduce the noise and only receive notifications on topics of interest!
Is it still in the vision to allow end-users to subscribe to tags?
I can imagine that when you have larger categories it can be overwhelming to subscribe to them… and allowing end-users to subscribe to specific tags can be a way to reduce the noise and only receive notifications on topics of interest!
Tag subscriptions would be fantastic!
Yet another use case for the example I posted above (7 months ago):
We have product teams that currently share updates via mail merges or CSV distro lists. These updates are for a specific product with a wide range of sub-products. There are different types of updates sent out (monthly, ad-hoc), which would require numerous emails each month.
It would be far easier if customers were able to subscribe in a group for that product, based on which sub-product(s) they owned and which updates they would want to receive.
Issue:
We don’t want to have to create 10s upon 10s of groups so users can be notified for every update within that group. If we could allow users to subscribe to specific tags, that would solve what I imagine to be a very common need.
Hey everyone! We’re working on subscriptions for Ideas and Product Updates. Our approach is to allow members to subscribe to product areas so they receive updates related to specific products they use.
At the same time, we’re also introducing categories in Ideas and Product Updates (similar to Forums & KB, which already allow category subscriptions). This brings up an important question:
- Would you prefer to subscribe to updates at the product level (Product Area) or more granular categories within Ideas & Updates? Why?
- What types of notifications would you want—new ideas, status changes, product updates, or everything?
- Can you share examples where subscribing at the product level vs. category level would be most helpful?
We’d love to hear your thoughts so we can design this the right way. Thanks.
At the same time, we’re also introducing categories in Ideas and Product Updates (similar to Forums & KB, which already allow category subscriptions). This brings up an important question:
- Would you prefer to subscribe to updates at the product level (Product Area) or more granular categories within Ideas & Updates? Why?
- What types of notifications would you want—new ideas, status changes, product updates, or everything?
- Can you share examples where subscribing at the product level vs. category level would be most helpful?
Tagging in
From my perspective (as an Email Operations focused admin with access to CS and CC), there are only a few categories within both CS and CC that I’m actually interested in getting notifications about. It’d be nice to be able to have granular level controls for types of notifications (ex: status changes, product updates, but not new ideas).
For overall admins (CS admins, community managers, etc.), I can see it being more helpful to subscribe at the overarching product area, but those of us who have those more focused positions may not necessarily need to hear about every new feature.
Hey everyone! We’re working on subscriptions for Ideas and Product Updates. Our approach is to allow members to subscribe to product areas so they receive updates related to specific products they use.
At the same time, we’re also introducing categories in Ideas and Product Updates (similar to Forums & KB, which already allow category subscriptions). This brings up an important question:
- Would you prefer to subscribe to updates at the product level (Product Area) or more granular categories within Ideas & Updates? Why?
- What types of notifications would you want—new ideas, status changes, product updates, or everything?
- Can you share examples where subscribing at the product level vs. category level would be most helpful?
We’d love to hear your thoughts so we can design this the right way. Thanks.
Great questions,
We are still fine tuning our hierarchy, but it would essentially be something like this
Modems & Wifi
- Modem type 1
- Modem type 2
- Modem type 3
- Accesspoint 1
- Accesspoint 2
TV
- set top box 1
- set top box 2
And so on
With such a hierarchy, most people would prefer to subscribe to only those devices they have, and not the others. But we also have super users who are more widely interested and would like to be able to subscribe to an entire product area.
Sign up
If you ever had a profile with us, there's no need to create another one.
Don't worry if your email address has since changed, or you can't remember your login, just let us know at community@gainsight.com and we'll help you get started from where you left.
Else, please continue with the registration below.
Welcome to the Gainsight Community
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.