Upvote an idea on behalf of a customer. This is purely quantitative, just like votes in a public idea website, but incremented internally when we get direct input from the customer.
+1 -> I track the feature requests that I get from customers as ideas in Aha. I would love to be able to count how many times a feature was requested by our customers.
Agreed on this! I am looking at moving my team to UserVoice because they have this functionality.
This my top request for Aha: We collect a lot of similar request from user via the phone. support desk, in interviews and appointments. We would love the ability to up vote an idea on behalf of these users as we have no way of collecting these votes without replicating the idea in the ideas centre. At the moment we have created a custom tag called Voter and we create a tag for every user.
Much needed. I'm not sure aha will work for us without this capability. Trying to "force" our senior partners to vote via aha will only get me fired :) We dont want to lose the great ideas and feedback we get over the phone.
+1 what david says. Customer requests come in from a variety of sources, including user testing and support, and i would love to track how often they come in using the portal.
This would be a valuable feature. As part of it I'd like to be able to add the name and email address of the person I am entering it on behalf of for communication purposes.
blocking our ability to expand aha use to our sales/partners and customers across our entire portfolio
We are also looking at going back to uservoice for ability to submit on-behalf of as well ability to have different portal interface for customer/sales under same product. Suggested Aha workarounds are becoming undue burden to our sales teams and blocking our ability to launch to customers.
Our backlog is only as good as the funnel to collect feedback. This would be a huge help to ensure the top of the funnel is as data-rich as possible.
If using the Salesforce integration, it would be great to vote for the user when linking them to the Idea.
For those following, I found a workaround for this. If you change the creator on the idea, it marks the new person as having voted for the idea while leaving the previous creator as having voted. You can then switch the creator back.
Since you're now evaluating this idea, I wanted to cover the use cases that are important for us.
There... I just made your job easy. You're welcome! :-)
+1 what Mat said (nice job). For me, only #4 and #6 would be required for v1. Thanks.
I really like the Ideas feature but for some of our customers they have a formal user group process at which they vote on ideas by show of hands. We don't want to expose a portal to them as the current process works well and is great for customer engagement. The challenge we have is that we'd like to add the votes received to the idea without the need to create a custom field.
This would be hugely beneficial for us. We have an internal facing portal and ideas are filed by our delivery team on behalf of our customer. Voting on their behalf would be super cool.
may need to append additional info...i.e company to custom field when voting on behalf of
Wow. That is huge for us. Can I please get more info on the planned workflow?
We sometimes have to split Ideas and, as there is no split function that would duplicate the voting from the original Idea, it would reassure our clients that votes were not being lost if we could manually update the votes on the new Idea.
You won't be notified about changes to this idea.