Keep your territory map, your segment thresholds, and who owns what in a single table, then point your Distro routing at it instead of building a path for every combination.
What's Changed and Why
A lot of routing logic is really just a lookup. "This country plus this company size goes to that team." Previously, when expressed as Rules, 50 territories meant 50 paths to build, 50 paths to maintain, and a reorg meant editing them all.
Now, an Assignment Table holds that same logic as rows, and one Assignment Rule points at the whole table.
What You Can Do Now
When a rep's territory changes, you edit one row instead of hunting through routing paths to find every rule that mentions them.
- Route by territory on country, state, or postal code, without a separate path per territory
- Segment by company size, industry, or any picklist, with several values in one cell instead of one row per value
- Assign each row to a named User or to a Distribution
- Hand the table to whoever owns the territory map. Download it, edit it in a spreadsheet, upload it back. A reorg becomes a CSV edit
- Check your work in the logs, which show the row that matched and the assignee it produced
A table routing US accounts by size looks like this:
How It Works
- Build the table under Rules, then Assignment Tables. Attribute columns are what you match on: single text, number, true/false, or multiple text values. The assignment column is who gets the Record
- Create an Assignment Rule that points to the table and defines how incoming record fields compare to the attribute columns
- In a Distro flow, select that Assignment Rule in the Routing Rule node. The Assign & Update Ownership node automatically locks to it
Rows are evaluated top-down, and the first match wins, so put your most specific rows above your catch-alls.
Things to Note
- Currently only live for Distro / CRM Routing flows
- An empty cell means the field must be empty. Turn on "Treat empty cells as a match" if you want an empty cell to mean any value instead
- A row missing its assignment value is skipped rather than failed, and the next row down assigns the record. An incomplete row quietly changes where things land, so it's worth a scan before you upload
- A CSV upload replaces every row rather than merging. Download, edit, upload
- Attribute columns don't support dates or ranges. For a range, use 2 number columns with greater-than and less-than
- Assignment columns set assignment only - they can't populate field updates or add a record to a campaign
- Fallbacks aren't available on paths that use an Assignment Rule.
Still to Come
- Assignment Tables for Concierge and Web Experiences, for Meetings, Records, and Conversation assignments
- Assignment Tables for Live Chat reading Conversation Assignment columns
Learn more in our Support Article.