Allow Specific Feedback on Knowledge Base Articles

Status: In Development

Status history

At the end of Knowledge Base articles the reader is asked if this article was helpful. It would be amazing if this function

  • could be turned on and off
  • could be customizable
  • could be shown in different ways, e.g. a pop up or something like that

Thank you

This looks like something that has been in demand for years and keeps getting bumped up every few months.

We have a new KB and would like to improve it for our customers, but we can’t improve it if we don’t know why they have found the content helpful (or unhelpful). I’d be happy with a comment box that pops up to provide some context and, if possible, the ability to add an email so we could respond to whatever query they have and ensure it is added to the KB.

Agree this seems a big miss in terms of functionality for a knowledge base. Any that I have used, gives you the ability to provide feedback after rating.

How can I have access to this feature?

We have a new KB and would like to improve it for our customers, but we can’t improve it if we don’t know why they have found the content helpful (or unhelpful). I’d be happy with a comment box that pops up to provide some context and, if possible, the ability to add an email so we could respond to whatever query they have and ensure it is added to the KB

Hello Team,

It would be great if we could have an Option to either toggle on/off the Was this Article Helpful in Use Cases where we are already sending Custom Survey to get Feedback on the Articles. This is so that there isn’t a double up on asking for Feedback. Thank you!

Excellent suggestion to the comment:
“It would be great if we could have an Option to either toggle on/off the Was this Article Helpful in Use Cases where we are already sending Custom Survey to get Feedback on the Articles. This is so that there isn’t a double up on asking for Feedback. Thank you!”

I just joined the Hubspot community specifically to come advocate for this feature. I am intrigued by this feature not even being considered (at least from what I’ve seen in this thread, unless I’ve missed an update saying otherwise) since it feels relatively uncomplicated from a development and implementation standpoint and would be a huge value-add for clients and end users. Receiving “This article was not helpful” feedback is useless since it doesn’t guide content writers toward any kind of clear improvement or solution. The fact that there is not a form field provided to elaborate on why an article isn’t helpful makes the current feature seem half-baked. I would really like to know from a moderator or some other Hubspot authority as to why this has not been considered or prioritized despite it being a desired feature.

so it looks like there is 256 votes, how many is needed to get this onto the product roadmap? This is very basic functionality that other knowledge bases have standard.

Great question. Since I am new here, I don’t know the protocol or process for how HubSpot selects features. Can anyone explain what the criteria is for that? Is it based on the number or votes or something else? Thanks in advance for any insights.

It appears as though @goconnor mentioned this was in Beta years ago, but I am not seeing anything that has hit general availability. Did this not go beyond Beta? Maybe I am missing something, but I cannot find a way to collect feedback when someone submits that an article was unhelpful.

Four years later and still no progress or change in this idea’s status. This is very disappointing for something that is basic, has a lot of votes and HubSpot is doing on their own KB. It doesn’t exactly build confidence that this is going to be a solution we can grow with. :pensive_face:

Hi HubSpot team,

Can you please let me know, do we have a feature to provide comments in the Knowledge Articles that are yet to be published?

I want my articles should be reviewed by the internal team before publishing (similar to the ‘comment’ feature in Confluence).

Also, any plans to implement Versioning of the Knowledge Base articles? This will help to track/ revert to previous versions.

Thanks.

I was revisiting this issue and was inspired by HubSpot’s solution on their knowledge base and AStaffordFMN’s solution.

I thought I’d share the solution that I came up with:

1. Create a HubSpot form with no header.

2. The first question is a radio button field type and it’s required, and then add conditional questions, mimicking the logic on HubSpot’s knowledge base articles (e.g., Analyze custom events).

3. Turn off the default feedback widget.

4. Embed the form in knowledge base articles.

It’s still not perfect, because I have to enlist a developer to add JavaScript to my form to capture the page URL the user was on when they submitted the feedback. I also haven’t figured out a way to make the “Submit feedback” button only appear when someone engages the initial required question. But it lets us capture more actionable feedback about the resources and keeps the user on the page.

I would still like to see HubSpot build this functionality. It seems so simple and would be meaningful for folks managing support and training content in HubSpot.

@EricaMT complementing your answer, it’s possible to add the Feedback Form using the embed code to all the article pages at once.

We just need to edit the Knowledge Base’s Template and put the script in the last footer config.

The document.addEventListener(‘DOMContentLoaded’, function() {} is necessary because the target element must be on the screen to be able to replace.

I think its necessary to keet the default feedback enabled, because it’s this configuration that creates the hs_cos_wrapper_feedback

Thanks for the tip, @renanceratto! I really appreciate it; I will talk with my web developer about this option.

Yes, please implement a way to track when contacts have viewed an article.

One way is to allow insertion of a checkbox property where the reader checks off that they read the article.

I’m not sure when this change occurred, but we’ve lost the ability to turn off the default feedback form. This is practically useless beyond gathering a general sentiment of how happy or unhappy people are with an article.

Forcing us to use the lackluster feedback form is a step in the wrong direction. I realize there are additional consent settings, but that’s not a great experience, because we aren’t capturing their feedback at the moment. It also creates more work, because we have to reach out to the customer and ask for their feedback and hope they remember and respond.

We want a solution like HubSpot has on their knowledge base, and this is not it. :tired_face::weary_face:

hi everyone! we’re planning work on our feedback survey on the knowledge base and i’d love to hear what kinds of features you’re looking for!

We’re working on adding comment functionality to the knowledge base feedback survey. Stay tuned!