Help Center - improve 'was this article helpful' and allow user to leave reasons



Posted Dec 06, 2016

Continuously improving the Help Center to make sure it has the content that users are looking for is important to us, and getting actionable data on what content is missing or could be improved is very valuable.

To this end we'd like to collect feedback from users when they read a Help Center article, but didn't find it helpful or what they were looking for (or they spot a mistake, etc), why they didn't find it helpful.

Current implementation of Was this article helpful

The current implementation has limitations:

  • user cannot tell us what they where looking for/was missing, they can only vote on 'helpful/not helpful' 
  • reports on feedback are very basic - stuff like page visits vs. votes vs. time period are missing

Example implementation with reasons

Here is example taken from another site that we shows how the end user experience could be:

Data we'd like to collect

Stuff like

  • article name
  • article URL/link
  • the feedback text
  • the user email (optional when leaving feedback, but if provided, would allow us to follow up with that user)
  • date and time
  • and nice to have: Browser type and IP (in case it might be browser related) 

EDIT: When I wrote this feature request, we didn't have anonymous voting. This has since been delivered, so I've updated the request accordingly. 


103

74

74 comments

Got it. :) 

0


Thanks, Nicole!

Just wanted to share the same sentiment of others wanting to have this feature built into the product :)

2


Hi Dennis -

Our product team is aware of how customers do these sorts of customizations; the platform was intentionally built such that any customer can customize and extend the platform in the way that best serves their needs. I don't know the details of those specific customers, but it's also possible that our Professional Services team built those customizations or has done one similar. These kinds of customizations can be performed by any customer on an enterprise plan today.

0


Other Zendesk users like Slack and Clio seem to have hacked/custom coded their own downvote feedback. Their implementation is simple, clean and too the point.

I suggest the Zendesk Product Team reach out to them and find a way to add the same functionality natively. It will bring so much delight for those of us that don't have the resources to custom code this on our own.

 

Source: Slack

 

 

Source: Clio

3


We trialled the Hotjar approach too Scott - seems to be the only thing that offers this level of functionality right now. Afraid to say it but ZD seems very slow to innovate...

2


Thanks for sharing, Scott. We'll share your desire to see functionality like this built in to the product with the appropriate product managers.

In the meantime, would you consider writing a community tip with more detail about how to set this up? I think a lot of users would be interested in your workaround. We would be sure to feature your tip in our monthly roundup

0


I removed the voting option from all our articles and set up a poll using Hotjar to get this feedback. It pops up when the user scrolls halfway down the page. I was able to add in some logic to request more details based on their responses. (https://help.grow.com/hc/en-us)

If this was built into Zendesk that would be great!

1


Thanks for the feedback, Sorcha.

0


I would love to see this feature as well. I don't think you can pitch for knowledge centred support with Guide without supporting an option to see why some articles aren't working. Content cues and all that is great, but how do what users actually need to be changed?

0


Hi Benjamin!

Thanks for the detailed description. So what's happening is that if someone votes No, but opts not to leave a comment, the no vote is still being registered. You don't want that to happen. Is that right?

I'll see if any of our Community Moderators can shed some light on how to change that!

0


Sign in to leave a comment.

Didn't find what you're looking for?

New post