Allows users to simplify their process by adding multiple updates in a single node.

This improves the experience when viewing or editing rules. Users can see more options rather than always having to view more.

Previously when you had two items or more the rules would look like this:

Now it is updated to show more options like this:

We now have a custom field that will let you know that Distro converted your lead into a contact.

More details ➡️

Option to set a specific date or set up a relative date time frame.

Add a lead or a contact to a Salesforce Campaign. More details on Salesforce Campaigns. Again taking out additional steps that need to be built elsewhere and giving admins the ability to add routes to a campaign directly in Distro. You can select the campaign and update the status.

Add the minus one in both places. Easier to see the -1 in both places and understand.

A new option has been added within the "Meeting Queues" → "Algorithm" settings to make Ownership Queues, when booking a meeting into a Queue thru the Chrome Extension, "Strict".

This update prevents a Booker from hand-picking an Assignee in an ownership queue and are restricted just to the "matched" owner. ie Existing Account/Contact/Lead Owner.

Within the "Workspace Settings" tab in a "Handoff" workspace, a new setting has been added to Allow/Prevent users from booking a meeting into a non-matching queue.

By default, the setting is Checked, which aligns with the previous behavior. In this case, a Booker is able to choose which to Queue to book into, even if that Queue does not match queue rules.

If the new setting is Unchecked, then the Non-matching queues are hidden from the Handoff Router.

Note: Both features mentioned above can be used together to enforce desired rep behavior when Booking meetings.

Automatically convert a lead in Distro. This node only appears when you have the trigger on the lead object. For some companies at the point of being routed, they would also like the lead to be converted to a contact and attached to an account and or create an opportunity. Explanation included in the settings!

Customers that are on an annual subscription and over $15k ARR threshold can move to pay by invoice as opposed to only paying by credit card

Previously if you would like the same routing logic for a trigger where a record was created and updated you would need to create two routers with the same logic. Now you can use the newly created and updated trigger within one router!

Now you start with selecting the object of the trigger, then the action

Test your router is set up and working as you expect it to all within the router preview! Go to preview flow → enter an SFDC ID (works with 15 or 18 ID) → then you can click preview and you can go into the routing rules to see which one matches.

Previously you could only re-order your paths, now you can duplicate or delete them. This makes reusing or getting rid of routes much easier!

🚀 Routing Rule View in Router

Instead of going to change and finding the rule to review it or going into your rules section, you can now view the details of the router rule easily from the view button.

You can now add a node that allows you to convert a lead into a contact, account, or opportunity. Previously customers would do this in salesforce flow now they can do everything in DIstro. This allows Distro to handle more of our customer's workflows. 

The previous message was less descriptive of the issue. A typical use case is when a Chili Piper User receives a Distro License but this user does not have a Salesforce License.

New Message:

"Could not assign record {{recordID in SF}} to {{Email of the User}}, a Salesforce ID was not found for this user.

Please have them reconnect to Salesforce within Chili Piper"

Anytime you have a path with the assignment you can allow for multiple updates. For example, you can update the contact owner with the team member assigned and update the account owner.

First Name → Nome

Last name → Cognome

Full name → Nome Completo

The distro router is now being visually represented in a brand new way! Includes all you know and love with Distro and more with a new top-down approach to building a router.

You can catch up or hold down users with calibration, see the position, record routed, and adjust the weight. It will also not let you leave unless you publish! You can find this Distribution algorithm > fairness

In the SLA, you can select from working hours or instant hours. Working hours will only route during the working hours of the assignee and instant will route instantly

When a field is removed in Salesforce admins will be notified! This is important information to be alerted on especially if that field is being used in your router, preventing unknown errors 😍

Everything on the booking confirmation screen will now appear in the proper language based on the user's IP

Admins can now add licenses, see invoices, and manage their billing in Chili Piper! You can find the new Billing Center in the Chili Piper Admin Center, under Integrations!

1. In the Overview, you can see Billing Frequency, Renewal Date, Payment Method, Bill amount, and purchase new licenses!

2. Invoice History includes a history of invoices that can be searched and downloaded

3. Payment Method allows you to add or manage payment methods

4. In Billing Details you can add and manage billing contacts, send billing information to additional team members, and edit your company billing details

If a field has been deleted in Salesforce, and that field has been used in 1 or multiple routers, previously the router would fail. This update provides a solution of - If Distro detects that a field has been deleted in Salesforce and that field is used in Rules X and Router Y - we will now send an Email notification to the Admin. In the Email, we will specify which rule and which router reference the Field X.

This is an Important update to reduce admin errors! Previously when using the feature: “update Ownership”, you would get access to all fields on the object. This could result in some invalid operations.

In the router, you can have multiple updates on the same object type. For example, you can now update the lead owner, update a field on the lead, and do as many other actions as you desire.

Making it simpler to search for the field you are looking for

1. Automatically start in the search bar

2. If only one result is shown allow the user to use ‘Enter’ button to select the value

3. If more than one result is shown - allow 'Tab' to go down the list to select a value

4. If something is selected menu should close

Removed any invalid operations and restricted certain field types that cannot be used together

Now supporting the parameters: caseId and opportunityId (the same that we use in queues today) and it will work as follows:

Admins can set this action directly in their distro route. This could be used to update an additional custom field such as lead status or router name. It is a very useful additional reporting tool!

Have a 3rd option that says ‘No distribution' which only shows those that have not been distributed. If NO option is selected in the filter (clear all selections), then no data will show. In the current state we default to select all this excludes records that have not been distributed.

Only the last 3 months are shown - change sorting from "this Year" to "Last 3 Months"

Replace "Untitled" with an error that will show “the name is missing” if the asset is published. This prevents more untitled assets from remaining in your workspace.

Sorting fields are now in Alphabetical Order

We have modified the Order in this picklist to follow the typical Sales Process of any company