In addition to the existing Smart Score Logic of "If" "Then" could an "And" be added? Specifically, to calculate something using the Excavator Incidence Rate as the "if" but adding an "and" such as has requested at least 500 tickets before applying the "then"/score. I believe adding additional, optional, logic would allow for further targeting and utilization of tickets where action(s) could be applied.
1 Votes
1 Comments
Jordan Marciniakposted
30 days ago
Admin
SmartScore rules can currently be configured for "AND" conditions only. This causes numerous rules to be created around items like excavator, when the "Add score" would be identical based on this field.
Instead, allowing a rule to have a toggle that operates similar to the "match on" geocoding logic of auto-responses, where "ANY" criteria in the rule that is met would add the score associated with the rule.
The customization capabilities would make for swifter SmartScore rule creation, and would allow for different actions based within the same score rather than requiring multiple SmartScores, causing ticket histories to appear very busy.
In addition to the existing Smart Score Logic of "If" "Then" could an "And" be added? Specifically, to calculate something using the Excavator Incidence Rate as the "if" but adding an "and" such as has requested at least 500 tickets before applying the "then"/score. I believe adding additional, optional, logic would allow for further targeting and utilization of tickets where action(s) could be applied.
1 Votes
1 Comments
Jordan Marciniak posted 30 days ago Admin
SmartScore rules can currently be configured for "AND" conditions only. This causes numerous rules to be created around items like excavator, when the "Add score" would be identical based on this field.
Instead, allowing a rule to have a toggle that operates similar to the "match on" geocoding logic of auto-responses, where "ANY" criteria in the rule that is met would add the score associated with the rule.
The customization capabilities would make for swifter SmartScore rule creation, and would allow for different actions based within the same score rather than requiring multiple SmartScores, causing ticket histories to appear very busy.
0 Votes
Login or Sign up to post a comment