Routing & Orchestration

Routing logic can only evaluate individual form field values directly. There's no way to perform calculations on multiple form fields, such as multiplying enrollment by tuition or summing numeric inputs, before routing decisions are made. Request: Support calculated values based on form field inputs, evaluated at submission time and available as inputs for routing conditions. This would allow routing decisions to factor in derived metrics rather than just raw field values. Impact: Many routing decisions depend on compound metrics that require calculation. Customers managing tiered routing based on deal size, total opportunity value, or calculated scoring need to derive those values from multiple form inputs before routing can be applied accurately.

Routing rules in Chili Piper can reference lead, contact, and account fields but not fields on the Salesforce User Object. Teams that track rep-level performance metrics in Salesforce, such as pipeline attainment percentage, close rate, or no-show rate, have no way to incorporate those values into routing logic. Chili Piper should support reading Salesforce User Object fields and making them available as conditions when building routing rules, so admins can factor rep performance data into how leads are assigned. Rep performance metrics stored on the User Object represent meaningful signals for smarter distribution. Routing high-intent leads to reps with stronger close rates, or managing load for reps with high no-show rates, requires access to data that already exists in Salesforce but cannot currently reach Chili Piper's routing layer.

Integrate with and “read” Salesforce’s Enterprise Territory Management (ETM) object when routing, distinct from Account or Opportunity team assignments. This enables routing logic for enterprise customers using ETM for sales alignment and expands support for complex enterprise orgs.