Manage routing rules in a table view with spreadsheet/CSV bulk upload
in progress (now)
Taylor Jennings
Routing rules must be created and edited one at a time through the UI, with no way to view, edit, or upload rules in a tabular format. This breaks down for large or complex rule sets, like territory structures where dozens or hundreds of region-to-rep or region-to-round-robin-pool mappings need to be configured and kept current.
Admins should be able to manage routing logic in a table-based view where mappings are visible and editable in a single place, and upload or update rules in bulk via spreadsheet or CSV. This should cover routing rules broadly, with territory-to-rep and territory-to-pool assignment as a primary use case.
Manual one-at-a-time entry doesn't scale, introduces errors, and makes audits, migrations, and rebuilds slow and painful, especially when territories change, new reps join, or routing is rebuilt from scratch. A table-based model with bulk import makes large rule sets practical to build and maintain.
Taylor Jennings
Merged in a post:
Manage routing rules using a data table or spreadsheet format
Taylor Jennings
The customer requests the ability to use data tables for managing routing rules. This feature would allow them to upload and manage rules in a sheet format, simplifying the process of handling multiple lines and rules. This request is currently being worked on by the distro team.
Taylor Jennings
marked this post as
in progress (now)
Work to start this week
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.
Taylor Jennings
Merged in a post:
Manage routing rules using a data table or spreadsheet format
A
Anne-Charlotte Chauvet
Complex routing rules with many conditions must be managed through the UI one at a time. There is no way to view, edit, or upload routing rules in a tabular or spreadsheet format. Admins should be able to manage routing rules in a data table format, including uploading rules via a spreadsheet, so large rule sets can be edited and maintained more efficiently. The current UI doesn't scale for rule sets with dozens or hundreds of conditions. A tabular view dramatically reduces the time required to audit, update, or migrate routing logic.