Notification configuration

 

Notifications are messages (email or SMS) that are sent to users based on a trigger— an event that happens related to the user.

There are some notifications that have been set up for you in your account. These can be changed or deleted, and additional new notifications created.

Notification triggers include:

  • Entry moderated
    Triggered when an entry is moderated (Approved, Rejected or Undecided). See Moderation
  • Entry submitted
    Triggered when an entry is successfully submitted (whether by the entrant or manager).
  • Entry tagged
    Triggered when an entry is tagged
  • User registered
    Triggered when a user registers successfully.
  • Payment pending
    Triggered on entry submission when the invoice option is selected by the entrant.
  • Payment success
    Triggered on entry submission when a payment succeeds via your payment gateway.
  • Role granted
    Triggered when role is assigned to a user
  • Review stage started
    Triggered when a review stage is started. The notification needs to be selected on the review stage before being triggered
  • Review stage completed
    Triggered when a review stage is completed (i.e when a Proceed or Stop decision is made). The notification needs to be selected on the review stage before being triggered

Creating a notification

  1. Go to Settings > Notifications.
  2. Click New notification.
  3. Select the trigger for the notification.
  4. Set the recipient(s) for the notification, from the following options. Note that you may create multiple notifications with the same trigger, so the event sends different notifications to different people:
    1. User: The person the event relates to.
    2. Email addresses and/or phone numbers: One or more specified addresses.
    3. Address specified in a field: allows an email or phone number field from the entry process to be selected. This allows for someone an entry relates to, to receive a notification.
  5. A sender name and email address may optionally be set. If these are not set, system defaults (a 'no-reply' email address) will be used.
  6. Write an email subject, email body message and SMS body message.
  7. If both an email and SMS are defined, what is sent depends on the recipient. If the recipient has both addresses define, only the email is sent.
  8. SMS body is optional and should be kept as short as possible. If an SMS body is not defined, the notification does not get sent to phone number recipients.
  9. Email body is optional. If not defined, the notification does not get sent to email recipients.
  10. Content related to the triggering user or entry may be included in the email subject, email body and SMS body with the use of merge tags. Different trigger events have different content merge tags available, noted on the notification configuration view.

Depending on the trigger selected, there are different merge tags available. The table below shows the complete list of merge tags available for notifications.

{account_name}

Name of the program as seen in the app header at the top left of the screen

{account_url}

URL of the program (e.g yourprogram.awardsplatform.com)

{category}

Category that the entry was submitted under

{chapter}

Chapter the entry was submitted under

{confirmation_code}

When a user registers with their mobile number, they need to confirm their mobile number by entering the confirmation code

{confirmation_url}

When a user registers with their email address, they need to confirm their email address by clicking the confirmation URL

{entry_field:aAbBcCdD}

Any entry field for the season. The identifier after the colon is the eight character ‘slug’ of the field you want to display. You can find the slug by going to the field configuration and looking for the eight character identifier in the URL

{entry_local_id}

Each entry has an entry ID number. You can find the entry ID next to the entry name under Entries > Manage entries (by default the entry ID is not shown to entrants, you can turn it on under Settings > General > Entries)

{entry_name}

Title of the entry

{entry_slug}

Each entry has a unique 8 character identifier. You can find the slug by going to the entry and looking for the eight character identifier in the URL

{first_name}

First name of the entrant

{invoice_url}

For paid entries, the URL of the invoice

{last_name}

Last name of the entrant

{order_id}

For paid entries, the order ID

{payment_amount}

For paid entries, the amount paid for entries

{review_url}

For review flow, the URL to the review page for approval/rejection

{user_field:aAbBcCdD}

Any user field for the season. The identifier after the colon is the eight character ‘slug’ of the field you want to display. You can find the slug by going to the field configuration and looking for the eight character identifier in the URL