Table-Based Routing with CSV Import for Territories and Rep Assignments
Taylor Jennings
Routing rules in Chili Piper must be created one at a time through the UI. Organizations with large or complex territory structures, where dozens or hundreds of region-to-rep mappings need to be configured and maintained, have no way to manage this at scale.
Admins should be able to manage routing logic through a table-based interface, similar to what LeanData offers, where territory-to-rep or territory-to-round-robin-pool mappings are visible and editable in a single view. Admins should also be able to upload or update these mappings via CSV, so configurations can be built, migrated, or updated in bulk without manually touching individual rules.
This is especially painful when territory structures change, new reps join, or routing needs to be rebuilt from scratch. Manual rule entry creates errors and doesn't scale. A table-based model makes territory management practical for growing organizations and reduces the ongoing admin burden of keeping routing logic current.
Taylor Jennings
Merged in a post:
Independent lead segmentation management
Taylor Jennings
Segmentation logic is embedded directly in routing rules, making it hard to maintain and scale. Changes to segmentation require touching multiple routing rules, and there is no centralized place to manage it.
Admins should be able to define and manage lead segmentation as a standalone configuration layer that routing rules can reference, rather than embedding segmentation logic inside each rule.
Maintaining segmentation inside routing rules creates duplication and makes changes error-prone at scale. A dedicated segmentation layer improves maintainability and reduces the risk of missing a rule when segment criteria change.
Taylor Jennings
Merged in a post:
Upload routing rules in bulk via CSV
Taylor Jennings
Routing rules must be entered one at a time through the UI. Organizations with large rule sets or complex territory configurations have no way to import them in bulk.
Admins should be able to upload routing rules in bulk using a CSV file, rather than configuring each rule individually through the interface.
Manual rule entry doesn't scale for large datasets. Bulk upload dramatically reduces configuration time and makes it practical to migrate or rebuild routing logic from an external source.