Once you've assigned your users' licenses, you'll next want to verify the PowerStandings system KPIs (Key Performance Indicators). By default we include approximately two dozen default KPIs. Head back to your InsideSales tab, and click the Key Performance Indicators link under the PowerStandings >> Settings heading.
Ultimately there's two things you need to determine: 1) the PowerStandings "Points" value for each KPI, and 2) the action your reps take in Salesforce that trigger the PowerStandings data "push."
"Points" are a way of creating a weighted value for different KPIs in calculating effectiveness. For example, in many organizations setting an appointment with a prospect would be seen as more valuable than simply making a lot of phone calls. In this case you might want to weight the value of a set appointment as 25 times more important than a single phone call.
Point values for each KPI are set individually in the KPI settings.
Note that KPI points are tracked independently of the KPI tally. Meaning, we always give you the option of tracking the points values for work your agents do, or tracking the raw KPI numbers.
For example, Janet has accumulated 175 points today, by setting 4 appointments (worth 25 points each) and making 75 calls (worth 1 point each). In your PowerStandings reports, leaderboards, and dashboards you can choose to track the total points, or the actual tallied KPI.
PowerStandings performs its database activity in a third-party system. To get the data from Salesforce into the PowerStandings engine, you'll need to set up Salesforce Workflow Rules that correlate to the appropriate KPI(s).
Notice in the KPI settings the Post URL setting. This is the location where you'll instruct a workflow rule to send a notification when the rule triggers.
Head to your Salesforce system setup page, then use the Workflow Rules link. What we're going to do is setup rules that match an agent's activity to a PowerStandings KPI. Any time an agent performs that action, the workflow rule will "ping" the PowerStandings URL, and increment a data tally based on the event.