Development build — sample configuration

Build an automation with a trigger, conditions and actions

Set up a rule that reacts to an issued invoice, an overdue balance or a scheduled date, test it on a real record, and turn it on only once the result looks right.

Updated on

An automation ties together an event, optional conditions and a sequence of actions, such as sending a reminder or opening a collection case, with no manual work. The Owner, Administrator, Finance and Operations roles can create and change automations; Customer service and Analyst can only view them.

Before you start#

  • Each action needs its own permission: sending notifications, writing collections, invoices, work orders or support requests. If your role lacks one, that action is missing from the list.
  • To filter by area, the areas must exist under Settings, in the Service areas section.
  • To test the rule before turning it on, you need at least one record of the kind the event watches, such as an invoice or a support request.

Step 1: Start the rule#

  1. Open Settings and, in the System group, choose Automations.
  2. Click New automation.
  3. Under Start from a template, pick a template or leave it Blank.
  4. Fill in Name and, optionally, Description.

Step 2: Set when it runs and under which conditions#

  1. Under When, choose the Event, for example An invoice is issued or An invoice becomes overdue. For the second, enter the Days overdue.
  2. To run at fixed times, choose On a scheduled date and set the frequency and time.
  3. Under If, click Add condition to narrow the rule, for example by Amount, Days overdue, Customer category or Service area.

Step 3: Choose the actions#

  1. Under Then, click Add action and choose the Action, for example Send notification or Open collection case.
  2. For Send notification, choose the Notice (for example Invoice issued) and the Recipient (Customer or Team). Tick Text message or E-mail under Also send directly by if you want to write the Message yourself.
  3. Use Wait before running and Wait after the previous step to space the steps out.
  4. Click Save.

Step 4: Test and turn it on#

  1. New rules start turned off. On the automation's page, under Test on a real record, pick a record and click Test. No action runs; you see whether the conditions pass and What it would do.
  2. Open More actions and choose Turn on. If some records already match the rule, decide whether to apply it to them as well.

What happens next#

  • The status changes from Disabled to Enabled and the message Automation turned on appears.
  • Every time a record triggers the rule, a line appears under Runs, with the status Pending, Running, Waiting, Succeeded or Failed. The automations list shows the Last run and how many runs Succeeded.
  • Notifications that go out are listed in the Notifications log.

Common problems#

  • The Save button is greyed out: next to it, the form says what is missing, such as Give the automation a name. or Add at least one action.
  • Next to Save you read "Action 1: this action needs a record and a schedule has none.": actions such as opening a collection case, issuing a disconnection notice or applying a late fee need an account. Use an event instead of On a scheduled date, or remove that action.
  • The automation's page shows Your roles do not allow every action in this automation, so you cannot change it.: only a user who holds the permission for every action can edit or turn it on. Ask them to make the change.
  • Next to Save you read "Action 2: the wait cannot be negative.": set that step's wait to zero or more.

Start today. Set up your utility in minutes.