Overview

Automation Rules in SmartMoving are evaluated in order from top to bottom whenever a trigger event occurs (such as Lead Created, Booked, or Estimate Sent).

By default, when a rule runs, SmartMoving stops evaluating additional rules that use the same trigger.

However, SmartMoving now allows you to control this behavior using a rule-level toggle. This gives you the flexibility to run multiple workflows from the same trigger, when appropriate.

This article explains how the setting works and how to configure it correctly.

How Rule Evaluation Works

When a trigger event occurs:

SmartMoving scans your Automation Rules list from top to bottom.
It looks for the first enabled rule whose trigger and conditions match.
That rule runs.
Depending on your rule’s toggle setting, SmartMoving may or may not continue checking additional rules with the same trigger.

Rule order matters. You can drag and drop rules to change their priority.

The Toggle: Stop or Continue Processing Rules

Each Automation Rule includes the following setting:

If this rule runs, don’t process subsequent rules

This toggle determines whether SmartMoving should stop or continue evaluating additional rules that share the same trigger event.

Toggle ON (Default Behavior)

If this toggle is enabled:

When the rule runs, SmartMoving will not evaluate any additional rules that use the same trigger.
Only the first matching rule in the list will execute.
Any rules below it with the same trigger will be ignored.

This is ideal when:

You want one workflow to take priority.
You want mutually exclusive automation logic.
You want to prevent duplicate tasks, assignments, or follow-ups.
You are building fallback logic (for example, a general rule at the bottom of the list).

Because rules are evaluated top to bottom, the highest rule in the list takes precedence when this toggle is enabled.

Toggle OFF (Allow Multiple Rules to Run)

If this toggle is turned OFF:

SmartMoving will continue evaluating additional rules with the same trigger.
Any subsequent rules whose conditions are met will also run.

To allow multiple rules to execute from the same trigger event, you must turn this toggle OFF on each rule that shares that trigger.

If any matching rule above has the toggle enabled, SmartMoving will stop processing and rules below it will not run.

Example Scenarios

Example 1: Booked Trigger

You have three rules that all use the trigger:

When Opportunity Is Booked

Rule #1 – Create tasks for Portable Storage jobs
Rule #2 – Create tasks for Carton Delivery jobs
Rule #3 – Schedule labor for Interstate moves

If each rule has clearly defined conditions and the toggle is OFF, SmartMoving will evaluate and run each applicable rule when a job is booked.

If Rule #1 has the toggle ON and matches first, Rules #2 and #3 will not run, even if their conditions are met.

Example 2: Lead Created Trigger

You may have:

Rule #1 – Assign Interstate leads to the Interstate Sales Team
Rule #2 – Assign Local leads to the Local Sales Team
Rule #3 – Create follow-ups for website leads

If the toggle is OFF on each rule, multiple workflows can run from the same lead creation event, allowing routing and follow-up logic to operate together.

Best Practices

To design scalable automation:

Keep related rules grouped together.
Use clear, descriptive rule names (e.g., “Booked – Interstate Tasks”).
Carefully structure conditions to prevent unintended overlap.
Review rule order whenever adding or modifying rules.
Test with sample opportunities to confirm expected behavior.

If your workflows are intended to be mutually exclusive, leave the toggle enabled.

If your workflows should run independently from the same trigger, disable the toggle on all relevant rules.

When Should You Use This Feature?

Allow multiple rules to run when:

Different service types require different task sets.
You want routing and follow-ups to run together.
You need separate workflows for Local vs. Interstate vs. Packing jobs.
You want to avoid workaround triggers (such as using Deposit Completed instead of Booked).

Keep the toggle enabled when:

You want one rule to take priority.
You are building tiered or fallback logic.
You want to prevent duplicate automation from running.

Conclusion

The “If this rule runs, don’t process subsequent rules” setting gives you full control over how Automation Rules behave when they share the same trigger.

Fire Multiple Automation Rules with the Same Trigger