Product Updates - Distro (April to September 2026)

Here's what's new in Distro from April through September 2026: routing from a territory table, routing on your schedule, enrichment before routing, and spam blocking.

🚀 Assignment Tables

Keep your territory map, segment thresholds, and who owns what in a single table, then point your routing at it instead of building a path for every combination. Fifty territories used to mean fifty paths. Now they're fifty rows, and one Assignment Rule points at the whole table.

What you can do:

• Route by country, state, or postal code without a path per territory
• Segment by company size, industry, or any picklist, with several values in one cell
• Assign each row to a named user or to a Distribution
• Download the table, edit it in a spreadsheet, and upload it back, so a reorg becomes a CSV edit
• See in the logs which row matched and who it assigned

How it works:

1. Build the table under Rules, then Assignment Tables
2. Create an Assignment Rule that points to the table and defines how record fields compare to its columns
3. Select that rule in a Routing Rule node in your Distro flow

Things to note:

• Rows are checked top-down, and the first match wins, so put specific rows above catch-alls
• A CSV upload replaces every row rather than merging
• An empty cell means the field must be empty, unless you turn on Treat empty cells as a match
• Assignment Tables work in Distro flows today

How do I use Assignment Tables?

🚀 Scheduled Triggers

Distro routers can run on a recurring schedule, on a specific date, or on demand. A Records for Processing node fetches the records to route, using a visual query builder or raw SOQL, with no cap on the number of records.

Trigger types:

• Recurring: every hour, day, week, or month
• Custom (Cron): any Quartz cron expression, like weekdays only at 8 AM, or 9 AM and 5 PM
• Specific date: a one-off run
• On demand: start a run whenever you like, including from the API, MCP, or an automation tool

Things to note: for large jobs, split into narrower queries and schedule outside business hours to avoid slowing live routing.

How do I set up a Scheduled Trigger Flow in Distro?

🚀 Enrichment Before Routing

An Enrich node enriches Salesforce fields inside a Distro flow, before the first routing rule, using the same providers and waterfalls as Concierge and Chat. Routing rules then evaluate the updated values.

Use cases:

• Enrich trial sign-ups, eBook downloads, and webinar leads that don't come through Concierge
• Enrich post-event lead lists before deduplication and routing
• Refresh routing criteria on existing records with a Scheduled Trigger

How it works: pick the field and waterfall in the node. With Overwrite off, we only fill empty fields. With it on, we always replace the existing value. Each enrichment shows in the log with the before and after values.

Things to note: this works on Lead and Contact routers.

How do I set up Enrichment in Distro?

🚀 Spam Checker in Distro

Add the Spam Checker node after your Entry Rule and before any routing. Clean records continue as normal, and spam records are blocked and stay unassigned. It uses the same checks and threshold as Concierge and Chat, set once under Chili Agents.

What you can do:

• Write the spam score, and any other fields you choose, back to Salesforce
• See blocked records in Distro Logs with a Blocked as Spam banner and the full score breakdown

How do I use the Spam Checker in Distro?