How to automatically send an E-mail or SMS via an alert.

How to create an alert to automatically send an E-mail or SMS

An alert sends an E-mail or SMS from one of your templates a set number of days before or after a date on a job. That date can be the job date, a deadline, or a stage's target or actual date. Typical uses are reminders to clients, chasers for missing information, and internal nudges to staff. You can find a fuller explanation in What is an alert and when do they send?

Alerts are created with a step-by-step wizard. It checks your choices as you go and warns you about settings that would stop the alert from sending, or would make it behave in a way you might not expect.

Before you start

  • You need to be a superuser to change workflow settings, including alerts.
  • Alerts send a template. If the message you want to send does not exist yet, see How to create a new template for email and SMS messages. You can also create one partway through the wizard.
  • Alerts belong to a single workflow route. If a workflow has several routes, such as Individuals and Partnerships, add the alert to each route that needs it.

Open the alert wizard

  1. Click Config and then Edit Workflow Systems.
  2. Click the pencil icon next to the workflow system you want to add the alert to.
  3. On the Routes tab, choose the route from the Select workflow route dropdown.
  4. Scroll down to the Automated Job Actions panel and click New automated message.

The wizard opens on a new page. The workflow and route you are working on are shown under the title.

The bar across the top shows the seven steps. Completed steps turn green, and you can click any of them to go back and change it. Click Next to move on, or Back to return to the previous step. Cancel returns you to the workflow editor without saving anything.

In the example below we set up a chaser for personal tax clients. It sends 14 days after we asked them for their information, but only if the job is still waiting for that information.

Step 1 – Trigger

This step sets when the alert fires.

What triggers the alert? Choose one of:

  • Job date: the date on the job, for example the year end or tax year end.
  • Actual stage date: the date a stage was actually completed. Stages are listed by their milestone, meaning what has been achieved once the stage is done (for example Information requested). If a job goes through the same stage more than once, only the most recent actual date counts.
  • Target stage date: the target date set for completing a stage. Only the latest target date on each stage counts, so moving a target date resets the alert. This makes a repeating chaser possible: each time you chase the client, push the target date back, and the alert fires again after the next interval. Add a stage order filter in step 2 so it stops once the job moves on.
  • Deadline: one of the deadlines on the route, for example a filing deadline. The alert only sends for jobs that actually have the deadline, so check it has been added to the route and isn't filtered out for the client's type.

If you choose a stage or deadline trigger, a second dropdown appears so you can choose which stage or which deadline.

Offset (days) is how many days before or after that date the alert fires. Use a negative number for before (e.g. -30   for 30 days before a deadline), a positive number for after, or 0   for on the day.

The blue Example box spells out what your settings mean, with an example date, so you can check them at a glance.

Completed jobs: only the Job date trigger can send alerts for completed jobs. Actual stage date, Target stage date and Deadline alerts only send for active jobs.

The wizard also checks your trigger against how jobs are created in this workflow:

  • A red message means the alert could never send, for example because it would fire before the job is created. You can't continue until you change it.
  • An amber message means the alert is allowed but is unlikely to work as you intend, for example a negative offset on an actual date. Actual dates are recorded as things happen, so a date before one has almost always already passed.

Step 2 – Filter

The release filter adds an extra condition that is checked on the day the alert is due. If the condition is not met, no message is generated. This is how you stop a chaser from going out once the client has already replied.

The options depend on the trigger you chose in step 1:

Trigger Release filter options
Job date Always send (active and completed jobs); active jobs only; or active jobs only where the current stage order value equals, is less than, or is more than a value
Deadline Send regardless of whether the deadline is fulfilled; send only if the deadline is not yet fulfilled; or send only where the current stage order value equals, is less than, or is more than a value
Actual or target stage date No additional filtering; or send only where the current stage order value equals, is less than, or is more than a value

How the stage order filters work

The three current stage order value options are the most useful filters, because they make an alert depend on how far the job has got. Choose one of them whenever an alert should only send at a certain point in the workflow.

Every stage has a stage order value. This is a number that sets the stage's position in the workflow: lower numbers come earlier, higher numbers later. You can see and change each stage's value on the Elements tab of the workflow editor, under Job stages (click the pencil icon to edit one). Space the values out in tens and give every stage its own value. That leaves room to slot new stages in later and keeps equals filters unambiguous. A personal tax route might be numbered like this:

Stage Stage order value
To request information 10
Awaiting information 20
Ready to start 30
In progress 40
Awaiting review 80
To send return to client 250
Awaiting client approval 260
To file with HMRC 270
To finalise 280

On the day the alert is due, Glide looks at the stage the job is on at that moment and compares that stage's order value with the number you entered. If they don't match the way you chose, no message is created for that job.

Option Sends when the job's current stage value is… In plain English Example, using the stages above
Equals a value exactly the number you enter "Only while the job is sitting at this stage" Equals 20 sends only while the job is at Awaiting information. This is the classic setting for a chaser.
Less than a value lower than the number you enter. The number itself does not count. "Only if the job hasn't reached this point yet" Less than 30 sends only while the job is at To request information or Awaiting information, so you still don't have the client's records. It is ideal for a reminder before a deadline.
More than a value higher than the number you enter. The number itself does not count. "Only once the job has gone past this point" More than 250 sends only once the return has gone to the client: Awaiting client approval, To file with HMRC or To finalise. It does not send at To send return to client (250) itself.

You don't have to work this out yourself. As soon as you enter a value, the wizard lists exactly which stages it matches on this route. If the list is long, click For a full list, click here.

If the value matches no stage on the route, the wizard shows a red message, because the alert could never send. You can't continue until you change the value.

Important points about stage order filters

  • The job's stage on the day the alert is due is what counts. The stage the job was on when the trigger date passed doesn't matter. For an actual stage date trigger, the job will already have left the trigger stage by then. The wizard warns you if your filter rules out the stages the job can be on.
  • "Less than" and "more than" leave out the number you enter. To include a stage, use a number just beyond it. For example, use more than 249 to include To send return to client (250).
  • Stage order filters only ever send for active jobs. Completed jobs are skipped, even with a Job date trigger. To reach completed jobs, use the Job date trigger with Always send (active and completed jobs).
  • On a Deadline trigger, the stage order options also stop sending once the deadline is fulfilled. To send whether or not the deadline is fulfilled, choose Send regardless of whether the deadline is fulfilled instead. That option can't be combined with a stage order filter.
  • The filter stores a number, not a stage name. If you later add stages or change their order values, an existing alert may start or stop matching them. After reorganising a workflow, check its alerts: open each one with the pencil icon and look at step 2, where the wizard shows what the value now matches.

Tip: for a chaser, use equals with the order value of the stage where the job sits while you wait. In our example, 20 is Awaiting information. Once the client's information arrives and the job moves on, the chaser stops automatically.

Step 3 – Method

Choose whether the alert is sent by Email or SMS. SMS suits short reminders. Use E-mail for anything with detailed instructions or links.

Step 4 – Template

Choose the template to send. The list shows templates that belong to this workflow, plus any shared across all workflows.

If the template you need does not exist yet, click Create a new template. The template editor opens in a new browser tab. Once you have saved the template, come back to the wizard and click the refresh icon next to the dropdown so the new template appears.

Once you have chosen a template:

  • Click the eye icon to preview it.
  • A label under the dropdown shows whether messages from this template will Send straight away or Queue for you to review first. It also shows whether that comes from the template itself or from your system default. To change it, see How to control whether an E-mail or SMS template is sent immediately or is queued.
  • For SMS, the wizard counts the characters. Over 160 characters it warns you that the message will be split into several parts. Over 459 it is too long to send, and you need to shorten the template.

Step 5 – Recipient

Choose who receives the alert:

  • External – the client's E-mail / Mobile: one message to the E-mail or mobile number on the client's own record. The wizard tells you which client field your system uses for this.
  • External – contacts linked to the client with a chosen tag: a message to each contact linked to the client where the tag you choose is on the link. Use this to reach several people, or as a filter. See How to set the recipient(s) of an automated email or SMS message.
  • Internal – a specific Glide user: always goes to the user you choose.
  • Internal – the Glide user in a chosen job position: goes to whoever holds that position on the job (e.g. the manager or preparer) when the alert fires.

First name merge fields: if your template uses a recipient first name merge field, the wizard warns you that it only works when the recipient is an individual. Organisation clients, including sole traders, don't have a first name. A custom field such as 'Salutation' does the same job and works for every client.

Step 6 – Progression (optional)

An alert can also move the job on in the workflow when it sends, exactly as if someone had clicked the step's progress button. In our example, sending the chaser also takes the Information chased step, so the job records that the client has been chased.

To set this up, switch on Progress the job automatically when this alert is sent and choose the step to take. Leave the switch off if you only want to send the message.

Things to know:

  • A step can only be taken when the job is on the step's starting stage. If the job is somewhere else when the alert fires, the message still sends but the job stays where it is.
  • With a stage order filter in step 2, only the steps that can actually be taken are listed. Without one, the wizard explains which stage the job must be on and offers an Add this filter button. That button sets the step 2 filter so the alert only fires when the job can progress.
  • If the step you pick also sends a message, the wizard lists it. It stops you if the step would send exactly the same message as the alert, and warns you if it sends the same template another way.
  • The job moves on as soon as the alert generates at least one message for it. If the template queues its messages, the job moves immediately, so remember to send the messages from the queue.

Step 7 – Review

The last step describes the alert in a plain-English sentence, followed by a summary of every setting. The summary includes whether messages send or queue, and the From name, From address and signature that E-mails will use. Check it carefully, then click Create Alert.

If any step still needs attention, it is marked in red in the step bar. A list of the problems appears above the button, with a link to each step. Fix them and come back to the review.

After saving

You return to the workflow editor, and your new alert is listed in the Automated Job Actions panel. Each row shows:

  • the trigger and offset
  • the release filter
  • the template, with an eye icon to preview it
  • the delivery method, with a Send or Queue badge
  • the recipient
  • under Then, any step the job will be moved on by

Click the pencil icon to change the alert later; this opens the same wizard with your settings filled in. Click the bin icon to delete it.

When will it send? The alert is live as soon as you save it, and it applies to existing jobs as well as new ones. Alerts are processed once a day, at 09:30 UK time, all year round (in both GMT and British Summer Time). If an existing job already matches your trigger and filter on that day, it receives the message. If you aren't sure, see How to test an external email automation before adding an alert to a busy route.

Editing older alerts

Alerts created before the wizard open in the same wizard. If an older alert has a setting that is no longer valid, perhaps because the workflow has changed since it was saved, a red message appears at the top and the affected steps are marked in red. Fix those steps and save again.

Did this answer your question? Thanks for the feedback There was a problem submitting your feedback. Please try again later.

Still need help? Contact Us Contact Us