vylan

Job and task automations

A rule on a job or a task watches a status or a date, and does one thing when it comes true.

Adding and changing one

Rules live on a job's Automations tab, in a task's panel, and on job templates.

  1. Press Add automation.
  2. Pick what to watch under Select condition, and what happens under Select action.
  3. Check the sentence, then press Add automation.
  • One rule, one action.
  • Edit changes a rule and Remove deletes it. Both need Edit automations in your permission set.

Examples

  • Hand the work on
    1. WhenWhen the previous task, document request or form request has a status of Done
    2. Thenthen put someone on it: the reviewer
  • Chase the client
    1. WhenWhen the job is past a date: 2 days past the Due
    2. Thenthen send a client email: your Missing slips email

A rule that sets a done status finishes the job like your own click: reminders stop, the next repeat is released, and an invoice billed on completion is created.

What a rule can watch

ConditionWatches
When the job has a status of, When the task has a status ofThe job, or the task.
Another row's statusA named row, the row above, everything above, or the whole list.
When the job is createdThe moment the job is made.
When the job is approaching a date, When the job reaches a date, When the job is past a dateOne of the job's dates.
When the task is approaching a date, When the task reaches a date, When the task is past a dateOne of the task's dates.

What a rule can do

ActionWhat it does
then put someone on itA person, a team or a client role.
then send team member notificationA person, a team, a role, or everyone on the job, task or client.
then record the dateToday, on one of your dates.
then create a jobA new job from a template.
then send the form request / then send the document requestOnly on a request's own rules: see request automations.
then send a client emailOne of your automation emails.
then set the job statusOn a job's rules.
then set the task statusOn a task's rules.

Emailing your client

then send a client email sends one of your emails from Templates ▸ Emails ▸ Automations, each in English and French. It goes out in the client's language, with the client's name, their contact's, your firm's, the job's name and the job's due date filled in.

  • It emails your client. Send to picks who on the client gets it.
  • Replies go where Firm settings ▸ Emails says for Automation emails.
  • It works on every question: a status, a date or When the job is created.
  • It sends at most once a day for each rule on the same job or task, and a date rule never emails about finished work. It can send again, so its card is never crossed out.
  • Only people whose permission set can add tasks can add one. If its author loses that permission, it stops sending.

Rules cannot message a client: there is no message thread. What a rule sends a client is an email, or, on a request's own rules, the request itself.

When they fire

  • A status rule runs when what it watches moves, and only then. No rule reopens finished work.
  • Nothing fires on a job still waiting for its client to accept the proposal.
  • A date rule fires once for each date.
  • A task has its Start, its Due and your firm's own dates, like a job.
  • Recording the Start or the due date changes the real date.
  • A date rule acts in its author's name, and stops if they leave your firm.
  • On finished work, a date rule that would notify someone, email the client or put someone on it stands down.

What a rule has done

Once a rule has run, its card shows Last ran on and the date. Only the date: the card never says who the rule acted for.

No line means it has not run, or that its history could not be loaded: it is not a promise that the rule never ran.

A one-time rule is crossed out once done: then send the form request or then send the document request once the request has gone, by that rule or any other way, and then create a job once it has made its job. Every other rule can act again, so it is never crossed out.

The whole story is in your firm's audit log, in your settings, for the owner and Administrators. Names are kept there, not on the job or the task.

  • Every time a rule runs, it records what the rule did, on which job or task, and in whose name.
  • Every time a rule could not act, it records that too, with the reason.
  • A rule refused again and again is recorded at most once a day.

Copies and repeats

  • Copying a job copies its rules, pointed at the new job.
  • A repeat's next jobs start with the rules in Repeat this job. A rule you add on one job of the series stays on that job.
Still stuck?

If you can't find it here, write to us. A real person reads it.