When distributing a record, Chili Piper cannot take the candidate rep's own Salesforce User fields into account. Teams that track rep-level performance in Salesforce, such as pipeline attainment percentage, close rate, or no-show rate, have no way to factor those values into who receives the record.

Chili Piper should be able to read a rep's Salesforce User fields and use them when deciding which rep in a pool gets the record, so admins can send high-intent leads to reps with stronger close rates, or manage load for reps with high no-show rates.