For now, this is not functionality we will be implementing.
There are two primary reasons for this:
When someone provides feedback, it’s in the best interest of the company to whom they provided it to follow up, either with status information or to ask for further detail about the problem to be solved or implementation specifics. Without knowing who to contact, product teams are left making assumptions about intent and solution, and often this can lead to a misfire.
Perhaps more importantly, without knowing who provided the feedback, product teams are left without context – is the feedback coming from a current customer? A prospect? What role do they fill and what are the jobs they’re trying to complete?
I do want to acknowledge that there is some value in feedback no matter whether it’s got attribution or not, so this is a decision we may re-visit in the future. However, for the moment, we’re focused on getting the most valuable feedback in front of product teams, and encouraging product teams to interact with those people who generously took their time to provide feedback.
For now, this is not functionality we will be implementing.
There are two primary reasons for this:
When someone provides feedback, it’s in the best interest of the company to whom they provided it to follow up, either with status information or to ask for further detail about the problem to be solved or implementation specifics. Without knowing who to contact, product teams are left making assumptions about intent and solution, and often this can lead to a misfire.
Perhaps more importantly, without knowing who provided the feedback, product teams are left without context – is the feedback coming from a current customer? A prospect? What role do they fill and what are the jobs they’re trying to complete?
I do want to acknowledge that there is some value in feedback no matter whether it’s got attribution or not, so this is a decision we may re-visit in the future.…
Ability to make e-mail optional for feedback submission.