Skip to main content

Creating a Distro Router

Henrique Girardi
  • Updated

Who can use this feature?

Available on Distro
Available to Admins Workspace Managers
Billing Center Get a Demo

Distro's Router was created to enhance the overall experience of building and maintaining your router with an all-new visual layout that’s not only easier to use but also much clearer on exactly how your flow will work.

Find out more about it in the video below:

Table of Contents

1. Create the Router

The Routers can be created in the Router tab inside your Distro workspace. To edit or create a net new router, expand the Distro tab in the left-side menu and click the Router option.
mceclip0.png

It will show a screen with all existing routers if there are any. You will then be able to find the button "Create CRM Router" at the top-right of the page.

2. Add a Trigger

A trigger is a mechanism that initiates an action when a specific event occurs. For example, if the prospect matches certain criteria, the trigger mechanism will start the flow for this prospect.

Formula Fields cannot be used as a Trigger, however, you can have something like an automated workflow that updates a specific field, and this field can then be used as a Trigger; with this approach, the workflow would do the same thing a Formula Field would do.

 

Click on the Trigger to start the creation: 

Next, select the desired Object. Here, you can use any Salesforce object (Standard or Custom) after activating them. Click here to learn how!



Select the record type after clicking Add Trigger:

  • Record is created - Salesforce will notify Chili Piper informing us of a new record being created of the object selected in this step.


  • Record is updated - Salesforce will notify Chili Piper of an update on the field selected in this step.

    When using this option, you can select multiple fields to be taken into consideration in your Trigger.
    Be mindful to correctly use the AND/OR operators for such cases. In the example below, while using the OR operator, the Trigger will be activated if the Active in Cadence or Annual Revenue fields - just one of them is enough - is updated.

    For the example below, the Trigger will be activated if the Active in Cadence and Annual Revenue fields are updated, meaning that it won't trigger if just one of these fields are updated.


  • Record is created or updated - Salesforce will notify Chili Piper if a new record was created or an update was made in a specific field.

3. Add a delay to the Trigger (Optional)

The delay optionally adds a certain amount of time that Distro needs to wait before taking any action on the record.

For example, you might be using a data enrichment tool, and you want the router to wait while the tool gathers more information about the Lead before continuing the route.

Click on the "+" button to expand the options and add a delay to the route if you would like to:



Set the time of the Delay: 

4. Add an Entry rule to the Trigger (Optional)

The entry rule optionally sets which conditions must be true on the record to trigger the Router. For example, you set a rule to have only Leads with their Country equal to the United States to proceed further.

Click on the "+" sign to expand the options and add a new entry rule if you would like to:



Select and add the entry rule that will be used:

5. Get familiar with our Matching-related features

Chili Piper and Distro have some Matching-related features that can help you building an even more advanced use case, like matching Leads and Contacts to Opportunities, Duplicate Matching, and more.

Check the articles below before building your Rules and Paths, as they may make sense to you:

6. Add your Routing Rules and start creating Paths

In this step, you will add routing rules to qualify objects based on Ownership or Non-Ownership-based rules or set a Catch-all to qualify the ones that don't match any specific rule(s). Learn more about how to create rules here

After adding your first rule, click the "+" button to configure a New Node to execute an action:


Assign & Update Ownership

Assignee

The first step in this node will be adding or creating a Distribution. Click here to learn more about Distributions.



The Owner option will be enabled only if your Routing Rule is Ownership-based. If your Routing Rule is Round-Robin or Catch-all, the available option will be Team via Round Robin only.

 

Working Hours

Here, you can define if records will be assigned only during the Team members' working hours defined in Chili Piper. If enabled, no records will be assigned outside each Team member working hours.

Check this article to understand better how to define working hours within Chili Piper.

 

Update Ownership

The next step would be selecting the objects and fields to be updated, where you can use the same object previously selected in the Trigger (step #2), or use objects with are natively associated in Salesforce (Contact <-> Account, for example). The fields available to be used are Salesforce's user lookup ones created under the available objects.

Multiple objects and fields can be used in the same node to perform different actions, like for example updating the Contact's and the Account's ownerID:

Fallback Options

Last but not least, you can define the Fallback Option and what should be done if the Capping Limit is reached:

We recommend checking this article for more details about Fallback and Capping.

 

Field Update

A specific field can also be selected to be updated with a pre-defined value. For example, you can set Distro to write "Active" in the Contact's "Account Status" field. 

Opportunity Creation

You can also create an Opportunity within your Router's flow in Distro. After selecting the "Create Opportunity" node, set the Opportunity Name, its Close Date, Stage and Type in the right-hand side menu that will be enabled:

 

Lead Conversion

This node has some additional details, so we created a different article for it here.

 

Task Creation

Distro can also create Tasks within your flow. Click here for more details.

7. Add a Service Level Agreement (Optional)

A "Service Level Agreement" (SLA) is a commitment within your Team to establish how quickly your sales Team will engage with a prospect.

Enabling an SLA trigger within our Distro router will ensure these commitments are met, and the prospect is not left hanging. If you would like more details about SLAs, please check here.



Select the time interval to kick off the SLA after a record is assigned. You can set it as instant or working:

  • Instant: Do not respect the working hours of the assignee.
  • Working: Respect the working hours of the assignee.

 

Select the Rule to be applied to your SLA. The Rule is the condition that must be true on the record within a set time interval, otherwise, the selected actions will occur.



Select the action to be taken if the conditions are not met:

 
Possible Actions to be selected:

  • Send Slack notification to assignee - This notifies the initial assignee to provide a reminder that something needs attention.

  • Send email reminder to assignee - Same as above but with email.

  • Reassign record - Reassign to the same route/Team to which the Router is attributed.

  • Update field on record - Useful for making changes to status, internal SLA fields, ownership, or validation checks in Salesforce.

8. Test your Router using the Preview Flow feature

The Preview Flow helps execute any flows without making any updates in Salesforce. This way, you can ensure that your Router is running as it should or perform any updates before going live.

This feature can be found in the header, and you would need a Lead or Contact ID (depending on your Trigger and use case) to start it. 

We recommend checking this article if you need more context about this!

9. Make sure to Publish Changes!

10. Use the Version History feature to check updates and restore previous versions of your Routers (Optional)

If you need to track the updates made to a Distro Router and rollback any changes that possibly caused any issues to your flow, the Version History is your place to go!

On your Router's header, click More, and then Version History:

The UI will display the Router's current version in View Only mode, meaning you can't edit in this screen, alongside the Version History in the right-hand menu:

If you want to restore to a previous version, click on it, and then Restore Version.

Next, you will be displayed a confirmation screen to confirm or cancel the rollback. If you proceed, note the version you restored will be displayed in Draft mode, meaning you need to Publish it to make it active.

 

Related articles