I actually didn't like UserVoice (we thought about using them, but the fact that they limit conversations (votes) to 10, was a no go for us) I guess UserVoice is meant strictly for features and bug fix requests...
We was looking for a more... community/conversation type solution (We want to engage with our users, and have them engage with us as much as possible) So we thought having a limit to this would not be a good idea.
However if your aim is to use UserEcho as strictly a Feature/BugFix request, I can see the benefit in that... having quality feedback vs quantity... however I notice that even I was reluctant to post because it "Costed" something...
Also users don't get their currency back till you "Close" the case, and I assume that no other users can comment after a case is closed? Further limiting the conversation...
It's will be optional and admins be able to set limit in the settings, will be disabled by default
I actually didn't like UserVoice (we thought about using them, but the fact that they limit conversations (votes) to 10, was a no go for us) I guess UserVoice is meant strictly for features and bug fix requests...
We was looking for a more... community/conversation type solution (We want to engage with our users, and have them engage with us as much as possible) So we thought having a limit to this would not be a good idea.
However if your aim is to use UserEcho as strictly a Feature/BugFix request, I can see the benefit in that... having quality feedback vs quantity... however I notice that even I was reluctant to post because it "Costed" something...
Also users don't get their currency back till you "Close" the case, and I assume that no other users can comment after a case is closed? Further limiting the conversation...
If you really need it, we can add such feature in our "Power" plan