To build the NPS Bucket calculated field, we'll go to admin calculated fields and we'll create a new calculated field based on the candidate experience object.
00:13
Next we'll click new and we'll title this.
00:16
NPS Bucket.
00:21
Next we'll add our first bucket.
00:22
In this case we'll call it Promoters and we'll give some context that these will only be submissions that are 9 through 10.
00:34
Next we'll add our fields to match and in this case we're looking for the candidate submitted nps.
00:40
Let's go ahead and do a search for it.
00:46
Next, we want this to be is greater than or equal to nine, which means any nine or ten responses will be included.
00:55
Let's add a new bucket in this case for passives that submit in a 7 through 8 range.
01:04
This case we want this to be is greater than or equal to seven.
01:09
We don't need to put in eight because Ashby is going to evaluate each survey response.
01:14
In other words, first it'll check for promoters.
01:17
Is the response greater to or equal to 9?
01:20
If not, let's move on to, the next criteria.
01:22
Is the survey response greater than or equal to 7 If the response is not a 7 or an 8, Ashby will move on to the next evaluation.
01:31
In this case, we'll call this Detractors for anyone that submits between a zero or a six.
01:42
And lastly, we can rename our other bucket into no survey response since they'll have no score associated if they didn't submit a response.
01:51
There we have it.
01:52
We've completed our NPS bucket.
01:53
Since we have the behavior set to take the first that matches, Ashby will first take a look at the server response.
01:59
If it's nine or greater, it will bucket the candidate and promoters.
02:02
If not, it will move on to passives and check to see if the response is a 7 or an 8.
02:07
If it's neither of those, it will move on to detractors, so on and so forth.