Skip to main content

Creating Automations From Templates

A quick overview with a video showing how to create an automation using a temaplate



When to Use a Template

Templates are ideal if:

  • You want a quick setup

  • Your workflow matches common industry use cases

  • You don’t want to build conditions from scratch

  • You’re new to Automations

Templates are built based on feedback from moving companies and represent the most requested workflows.


Step 1: Create a New Automation

  1. Go to Settings

  2. Navigate to Automations

  3. Click Create Automation

  4. Select From Template

You’ll see a list of available templates displayed in tile format.


Example Use Case

We’ll walk through this template:

Follow up with customers who sign an estimate but don’t pay a deposit within two hours

Step 2: Name Your Automation

After selecting the template, you’ll land on the first tab.

Automation Name

Choose a clear name that helps you quickly understand its purpose.

Example:

Follow Up – Signed Estimate, No Deposit (2 Hours)

Description (Optional)

You can add additional details here. Descriptions allow for more detail than the title and are helpful for larger teams.

Step 3: Set Enrollment Trigger

You’ll now choose When should this automation enroll?

This determines when the system begins monitoring a job.

For this example:

  • We have selected Estimate Signed

This tells the system:

When an estimate is signed, start tracking whether or not the chosen action should execute. In this example we are telling it to start monitoring the job when the estimate is signed

Also within this screen you can configure the automation to restart when the trigger happens again.

In this case, if a new estimate is sent replacing the old one, you still want to know if they've paid within 2 hours so you would set the restart trigger to once again be estimate signed. This will allow the automation to restart and re-check the two-hour window.

This ensures repeat signing events are monitored properly.

Step 4: Configure Conditions

Conditions determine whether the action should happen.

For this example, we need two conditions:

Condition 1:

Time Since Estimate Signed

  • Set to More than 2 hours

  • You can adjust this to minutes, hours, or days if needed

Condition 2:

Deposit Not Paid

  • Set evaluation to True

The system logic works like this:

  1. Has it been more than 2 hours since the estimate was signed?

  2. Is the deposit still unpaid?

If both conditions are true → the automation proceeds to the action step.

Step 5: Choose the Action

Next, choose what should happen if conditions are met.

For this example you can, send an email, send an SMS, or send both; however we if you hit the pencil icon you can see we have a number of different actions that the automations platform can take.

If you’ve already created message templates, they will appear in the dropdown list.

Email and SMS templates are separated in the system.

You may:

  • Select existing templates

  • Create new ones

  • Customize content as needed

Quiet Hours Option

You'll also see on this screen an option to Respect Quiet Hours.

This prevents emails or texts from being sent during off-hours (such as late at night).

Quiet hours can be configured within the Automations settings.

Step 6: Save Your Automation

Click Save.

Important:
Saving does not activate the automation.

After saving, it will appear in the Automations list as:

Draft

While in Draft mode:

  • No jobs are enrolled

  • No messages are sent

  • No actions are taken

Step 7: Publish the Automation

To activate it:

  1. Return to the Automations list

  2. Open your draft automation

  3. Click Publish

If you make changes after saving:

  • Click Save again

  • Then click Publish

Once published, the automation is live.


Available Templates

There are multiple templates available based on common moving company workflows.

If you have ideas for additional templates that would benefit your team or others, we welcome feedback.


Best Practices

  • Use clear naming conventions

  • Double-check conditions before publishing

  • Confirm message templates are correct

  • Test automations internally before rolling out broadly

  • Monitor performance from the Automations dashboard


Did this answer your question?