While you can upvote features from inside your Savio Vault, we heard from customers that you'd like more ofa B2C experience for your customer-facing teams to upvote features.
Today, we've launched the ability for your teams to do just that. When they're logged into Savio and on your voting board, they'll see two options when they click the Vote button:
Clicking Upvote on Behalf of Someone Else will let you do just that:
Here's the feature in action:
Before, Feature Request States were fixed:
Now, you can edit, reorder, and add and remove states to match your workflow:
In our own Savio Vault we customized statuses to keep track of whether a feature needs to be added to the marketing site, whether it's been added to this changelog, and whether it needs a knowledgebase article.
Customizing Feature Request Statuses is available on all paid plans.
You can customize statuses by going to Settings => Feedback and Feature Request Attributes => Status.
Want to decide what shows up on your Feature Request List? Good news - we got you covered.
Just go to Settings => Manage Feature Request List Columns.
From there, you can pick any Custom Attributes or other Feature Request fields and show (or hide) them.
Here's what it looks like in action:
Customizing Feature Request Columns is available on all paid plans.
Do you want to add and edit People or Companies attributes that can't be imported into Savio?
Now you can. Here's how:
First, visit Settings => People and Company attributes.
Then click New Attribute:
Fill in the relevant details (you can refer to our Knowledgebase article on Custom Attributes for more on each field).
Be sure to check "Show With User Info" so the attribute shows up in Savio.
Your attribute will appear in your Attributes list. The Savio logo indicates it's a manual attribute:
When you've checked "Show With User Info", the attribute will appear alongside a Person. It can be edited from there by clicking the pencil icon:
One scenario we've heard is manual attributes are useful for tracking approximate deal size for leads who never make it into the CRM because you're missing a must-have feature.
To track that your sales team would send in feedback via the Chrome Extension and include the estimated deal size (you can use Feedback Templates to prompt them to include the fields you care about:
Then during Triage you'd add the lost deal revenue to the Person by clicking on the attribute:
Then entering and saving the attribute info:
Customize your Feature Request columns to show how much deal revenue you've lost out on because you were missing a feature request:
Do you have Feature Requests that are large in scope?
We do.
And when we build part of the feature that helps SOME of the requesters, bit not all of them, it was a pain to move feedback from the old completed feature to the new one that you'd work on later.
For example, imagine you have a Feature Request called "Mobile App" that has 10 pieces of feedback - five asking for an iOS app and the others for an Android app.
When you build the iOS app you can close the feature request. But you'd probably want to move the five Android requests to a new feature request.
Yesterday, that was a pain in Savio. But today, it's easy.
Just watch:
Batch moving feedback is available on all paid plans.
Fixed a bug where Zendesk was only returning the first 100 tags when you turned on the integration in Savio. Now Zendesk returns all the tags in your account.
Previously, you could filter Features with only one status (for example, show me all Planned Feature Requests).
But we found that limiting, especially when planning.
So today, you can see Feature Requests with any status that you choose on one page. For example, you can now see Feature Requests that are either Under Consideration OR Planned
Related to that - we've changed the Planned canned filter on the Feature Request List to be called Up Next. It filters your list to show Feature Requests that are either Under Consideration or Planned:
We think this model makes more sense for planning. When you're considering what to build next, one slice of your list is to look at Feature Requests that you've decided you're definitely going to build (Planned) along with ones that you may build (Under Consideration).
Once we ship a feature and close the loop with them, we don't have much use for the feature any longer.
And we certainly aren't assigning more feedback to it.
So we've removed them from the Feature Request pickers on the Triage page and the Create/Edit Feedback pages.
In other words, this dropdown no longer includes Customer Notified feature requests:
Two improvements to make triage faster:
You can now edit Status, Priority, and Effort inline on the Feature Request list.
