Two updates to Distro are live for all customers:
- Spam records get blocked before they're ever routed
- Scheduled Triggers can now run on any schedule you can write as a cron expression
1. Spam Checker Now Runs in Distro Flows
The same checks that filter spam form submissions in Concierge and spam conversations in Chat now runs inside Distro. Checks, weights, and the threshold are set in Spam Checker settings under 'Chili Agents' and are shared across all three, so a single configuration covers Concierge, Chat, and Distro.
How It Works
Add the Spam Checker node after your Entry Rule and Delay (those two can be in either order) and before any Routing Rule or CRM Matching nodes. Clean records continue through the Flow as normal; spam records are blocked, routing stops, and the record remains unassigned.
What's Possible
- When a record is marked as spam, write the score to a Spam Score field in Salesforce and update any other Salesforce fields you pick, for example setting Description to "This is spam", all in one Salesforce update
- See blocked records in Distro Logs with a "Blocked as Spam" banner, counted in the log summary totals
- Read the full breakdown on any blocked record: the score against your threshold, and which checks passed or failed
Learn more in our Support Article.
2. Run Routing Only When Your Team Is Working
A recurring Scheduled Trigger could only run every hour, day, week, or month. That covered most cases, but not "weekdays only" or "twice a day, 9 AM and 5 PM", so teams who didn't want routing firing at midnight or over the weekend were stuck running a single daily job.
What's New
"Flow starts every" now has a fifth option: Custom (Cron). Enter a Quartz cron expression and the Flow runs on every occurrence it matches.
[Second] [Minute] [Hour] [Day of Month] [Month] [Day of Week]
For example:
- 0 0 8 ? * MON-FRI- 8 AM, weekdays only
- 0 0 9,17 * * ?- twice a day, 9 AM and 5 PM
- 0 0 8 ? * FRI#3- the third Friday of each month
- 0 0 8 L * ?- the last day of each month
The Timezone you select on the Flow is the timezone in which the schedule is evaluated.
Things to note
- One of Day of Month and Day of Week must be ?. Quartz can't honor both at once, so setting both, or neither, is rejected. A five-field Unix expression is rejected too, since seconds are required
- Start Date and Start Time bound when the expression starts firing; they don't add a run of their own. Picking Custom (Cron) sets them to the next whole hour, and you can override it to run sooner
- Expressions are checked as you type and again on publish, so a broken schedule can't go live
Learn more in the 'Use a cron expression' section of our Support Article.