Great news and excited to see the results on my community.
So happy to see this!
Cool! However, we have several users complaining that this hurts the usability of the forum on mobile and tablet. Anyone else getting this feedback?
Quotes:
Telfort Forum
"I might be the only one but on a tablet this is quite annoying. Unnecessary space use in my eyes, the idea that someone can click on the smiley if a topic has answered a question is something, but this is something I get to see too often."
"Annoying is an understatement, so I agree with you"
"The same here, quite annoying indeed when you use the tablet in landscape it looks like this. The popup jumps along with the rest of the page while scrolling until you click it away at the cross."
"I agree with your words to gentlemen. I also get to see this on tablet and phone, not just on this forum. QUITE a bit too often".
KPN Forum
"Every time you open a topic that has already been answered, that popup comes. And as always, people have not thought about when that popup should be shown. Even before you have been able to read a piece, that popup is already there and then you have not been able to determine 'the answer to your question'."
"I'm sick of it as well, I get it constantly! I did not notice that that it does when a topic is answered. But that aside, Insided simply shouldn't do this on the forum. Forum members find that irritating, at least I do."
"I also get sick of it, I also see these popups continuously. We do not need that, we help KPN, we are not faced with questions or problems. Then I do not want to constantly get the message whether it is the answer to my question. Insided should see our user roles [Superuser] and not ask us that question. Can they do this anyway?
"
My other feedback: please enable users to choose/upload their own icons. When using emoji, users will qualify topics that provide an answer they don't like as 'bad'. Letting customers upload their own icons is also another way to diversify forums.
My other feedback: please enable users to choose/upload their own icons. When using emoji, users will qualify topics that provide an answer they don't like as 'bad'. Letting customers upload their own icons is also another way to diversify forums.
Totally agree with you Jurgen!
Thanks for sharing. Topic helpfulness panel + keyboard on smaller viewports doesn't look pretty indeed, we'll investigate usability on smaller viewports.
When using emoji, users will qualify topics that provide an answer they don't like as 'bad'.
I don't understand why this is a bad thing. A topic can be solved but when it collects a lot of unhappy votes the topic, answer or it replies are apparently not helping. This could be an indicator that the topic needs a new answer or some adjustments in order to become helpful.
Custom icon upload is not in scope. We might want to provide different icon sets where you can choose from, this way you can diversify and pick the icons that suit your scenario the best.
I don't see a need for custom icon uploads - not sure how that can help.
Thanks for sharing. Topic helpfulness panel + keyboard on smaller viewports doesn't look pretty indeed, we'll investigate usability on smaller viewports.
When using emoji, users will qualify topics that provide an answer they don't like as 'bad'.
I don't understand why this is a bad thing. A topic can be solved but when it collects a lot of unhappy votes the topic, answer or it replies are apparently not helping.
People who cast unhappy votes might be dissatisfied with a policy that's being described, while the content itself may be very helpful in providing an answer. People tend not to read, so when they see the emoji they'll just give a knee jerk reaction of how they feel after reading the answer.
If the goal is simply to gauge people's feelings when reading an answer, then 'content helpfulness' is a misnomer in my opinion. It's rather something like a sentiment measurement.
Thanks for sharing. Topic helpfulness panel + keyboard on smaller viewports doesn't look pretty indeed, we'll investigate usability on smaller viewports..
Great. As you can see in the feedback, regular visitors also think it's annoying they get this question/banner in every single topic. Superusers are not the intended audience for the question anyway, seeing as they're often the ones providing the answer. They could be excluded by role, the banner could only be displayed for visitors that aren't logged in, or the banner could pop up at the first topic that's visited only.
Custom icon upload is not in scope. We might want to provide different icon sets where you can choose from, this way you can diversify and pick the icons that suit your scenario the best.
So if we turn this on, we're stuck with the smiley's you've chosen? I'm pretty sure branding is going to have a fit if we can't change them.
Superusers are not the intended audience for the question anyway, seeing as they're often the ones providing the answer. They could be excluded by role, the banner could only be displayed for visitors that aren't logged in, or the banner could pop up at the first topic that's visited only.
Great suggestions
So if we turn this on, we're stuck with the smiley's you've chosen? I'm pretty sure branding is going to have a fit if we can't change them.
That is correct. You can configure where and if you want to display them. If branding is a big thing you can disable our content helpfulness solution and inject a third-party solution.
Superusers are not the intended audience for the question anyway, seeing as they're often the ones providing the answer. They could be excluded by role, the banner could only be displayed for visitors that aren't logged in, or the banner could pop up at the first topic that's visited only.
Great suggestions
So if we turn this on, we're stuck with the smiley's you've chosen? I'm pretty sure branding is going to have a fit if we can't change them.
That is correct. You can configure where and if you want to display them. If branding is a big thing you can disable our content helpfulness solution and inject a third-party solution.
We're on a platform that InSided is calling "branded templates", so yes, branding is a big thing, and I'll take a wild guess that that isn't exclusive to Sonos 🙂 .
Fair point 😉
@Yoeri
Two quick questions:
The first just for me to understand: as we were participating in the pilot, in GA the helpful-count goes back to when the pilot was started. In the console, however, the numbers reflect only the votes since the release - correct?
Example:
- https://otwo-de.insided.com/mailbox-email-sms-mms-41/sms-zahlungsaufforderung-mit-tan-213263)
- Total votes console 35,
- in google 181 upvotes
The second is more of a question/suggestion:
- for the above topic I have 181 upvotes
- Why don't we show that to the users?
- E.g.
Cheers,
Florian
Hey Florian,
in GA the helpful-count goes back to when the pilot was started.
Correct
In the console, however, the numbers reflect only the votes since the release - correct?
Also correct
We have plans to show the
helpfulness score to your end users. This will be a configuration setting that you can show or hide.
@Yoeri , thanks for the confirmations!
And the mock-up looks good 🙂
We deployed the ability to toggle on/off content helpfulness on individual topics. It is now possible to enable or disable content helpfulness on individual topics despite the generic setting.
- Use default (inherits default visibility setting for this topic type)
- Enable (will show content helpfulness regardless the default setting)
- Disable (will hide content helpfulness regardless the default setting)
People who cast unhappy votes might be dissatisfied with a policy that's being described, while the content itself may be very helpful in providing an answer. People tend not to read, so when they see the emoji they'll just give a knee jerk reaction of how they feel after reading the answer.
If the goal is simply to gauge people's feelings when reading an answer, then 'content helpfulness' is a misnomer in my opinion. It's rather something like a sentiment measurement.
I think this could be triggered by how the helpful is currently implemented:
a) using smileys: while I like their universality, emojis are typically frequently in sentiment gauging analyses, and, as the term "emoji" suggests, they are more about emotion than about objective assessment. Emotions might be the right thing to rate for some type of content, but not for all. So ability for configuration is necessary.
b) floating: the floating of the "helpful-emojis" somehow creates a feeling of them being detached from the content, i.e. users are more likely to just relate to their overall emotions instead of seeing them in context of the topic. That said, on our previous platform the helpful-voting was clearly associated with a single topic/post.
In short: I think the helpful-solution is still much in beta and not a ready feature.
Florian
We shipped an improvement on the usability of the content helpfulness panel: The panel will no longer appear when the user is scrolling down (and reading). The panel will only appear when the users stops scrolling down and starts scrolling back to the top (this is often an indicator that the users stopped reading). This improvement should solve the issue with showing the helpfulness panel in combination with your mobile keyboard as well.
Hey,
to provide some more points for discussion - with the update we clearly see a drop in the amount of votes cast. That itself is in line with the expectation that through the reduced exposure, less votes are cast.
Also it looks like the "neutral" vote looses the most. It could be an indicator that rating is happeining after digesting some content.
Cheers,
Florian
We've just got this as part of the move to branded templates. So far it's looking good, however our users are finding that the page 'skips / jumps' when the bar shows up when scrolling. This is rather annoying.
Personally, I'm looking for a good way to set up my google to be able to easily action the feedback. Anyone have any awesome layouts? :)
Cheers,
Ditte
Thanks for the feedback. The 'jumping' is one of the UI flaws that's not easily changed. We deliberately changed the behaviour of the bar so that it only appears when a users scrolls back to the top (previously it was always visible). We did this because scrolling back to the top is an indicator that somebody stopped reading, this is the right moment to ask for feedback. The consequence is that when a users scrolls to the top this additional bar is loaded in the template causing the slight jump.