Skip to main content

The possibility for community members to subscribe on products

Related products: CC Ideation CC Notifications & Subscriptions CC Product Updates

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 @anirbandutta . We’ve planned to improve Subscriptions and System Emails later this year, and being able to subscribe to Product Areas is one of the most critical improvements we can make to improve our subscriptions.

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


The following idea has been merged into this idea:

All the votes have been transferred into this idea.

Hi @Sebastian did you mean next quarter? :)


Our community just launched, and the ability to subscribe to tags has already become our top request. @Sebastian Can we we get an update on this since the last update was 7 months ago?

 


Can anyone provide an update on this one? This is very important to us and our users.

 


 

Absolutely @anirbandutta . We’ve planned to improve Subscriptions and System Emails later this year, and being able to subscribe to Product Areas is one of the most critical improvements we can make to improve our subscriptions.

Later this quarter, we’ll reach out again in this thread to kickstart discovery and better understand use cases we need to cover.

@Sebastian  Any updates on this? It’s been almost a year since the last status.


@mmue Yes, we’re actually very close to working on this. Looping in the Product Manager @Sudhanshu working on this to provide more context.

Can you share some particular use cases? How would you(r users) use it?


Hi @Sebastian

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 @Sudhanshu 

Do you have a estimated timeline for when the feature might get implemented?

CC / @olimarrio 


Hey @Grzegorz Byrski 👋,

We are aiming to have the ability to subscribe to individual Product Areas in Q3/Q4 this year. I’ll let @Sudhanshu confirm this though!


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!


OpenDiscovery

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.