Achievements provide Teams with the ability to define and track leading indicators of success with their account. For example:
- New Customer Goals identifies in last year
- Initiatives have been updated in the last 30 days
- New Product Launch kicked off with a Customer
- Plan Reviewed By Manager In last 90 days
- Customer Approved Plan in the last year
Outlining these behaviors as leading indicators of success provides Account Teams with a roadmap to improve and helps Manage gain new insights on what work is driving the right results and manage adoption of best practices.
The Achievements feature is very configurable and might require some 'test and learn' work before full deployment for your organization. We recommend you meeting with your Valkre Customer Success Manager to outline a plan ahead of the 2025 calendar year. Ahead of that discussion, here are some highlights on this new capability:
A new widget is available that summarizes how many Achievements have been assigned to this customer and which ones have been achieved:
Clicking in on the Widget shows a list of the Achievements and their status. The Achievement status is monitoring automatically daily by Valkre. Team Members can click on the Achievement to go to view the underlying information and make updates.
Setting up Achievements requires a few steps.
- Define the Achievements under Settings->Customers->Achievements. This is basically setting the criteria for an Achievement using filter combinations.
- Turn on Achievement Feature and Widget under Customer Type like all other Valkre features.
- Assign Achievements to a Customer Type. Not all Achievements might be right for every customer.
- By default, Achievements is not turned on for any users except ADMINS. This allows Management to test and monitor Achievements before deploying to Account Teams. When ready, activate the Achievements feature for desired Roles.
You can optionally change all of the labels as well. Your Customer Success Manager can walk you through the first Achievement setup
Comments
0 comments
Article is closed for comments.