Our team has multiple statuses for ideas. We would like the ability to send a customized email message based on that specific status. Currently Aha only has a "general" status notification email. We would like to extend this as our portal is setup to have multiple types of accepted or rejected status updates. For example:
Rejected - already built.
Rejected - already in roadmap
We'd like a separate email message sent depending on which status was selected.
This would be useful for our team as well. It's all about the user experience. The bulk of a user's experience with the idea portal as I see it is, frankly, getting updates on something they've submitted. (Tell me I'm wrong?) Right now I have a choice between sending a stale and impersonal "your idea status has changed" or sending an email with way more information than the user actually needs at that point in time. It's a clumsy experience. It doesn't create the feelings of trust, confidence, and personalization I want users to associate with our brand.
Our team is also interested in this for specific status updates to be sent out.
It would be nice to tailor the Idea status change email response to indicate what Release the Feature was added to. Customer running older Releases would be notified and now immediately that the Feature is or is not provided in the Release that they are using.
This is a very specific use case: If the status changes to shipped, insert the Release name into the email.
This is our exact use case as well. We'd love to send a message that includes how to sign up for our Beta program when something moves to be available for Beta. Currently we have to embed all of this information in a generic email that may never be pertinent.
This would be very beneficial to communicate back to our requestors with more details relative to the idea status:
Prioritized - item is prioritized and will be communicated through the roadmap
"Released" - Thank you for the idea, it is now released to production. Add link to release note library
Yes, this would be AWESOME! For us, here are a couple of examples of how we could use this:
Bulk administering ideas can be a challenge, templates will minimise this and keep contributors up-to-date with the stasis of their ideas.