Notifications configuration
Notifications are messages (email or SMS) sent to users based on a trigger.
There are some notifications that have already been set up for you in your account. These can be changed or deleted, and additional new notifications created.
Notification triggers include:
- Application moderated
Triggered when an application is moderated (Approved, Rejected or Undecided) See Moderation - Application submitted
Triggered when an application is successfully submitted (whether by the applicant or grant manager) - Application resubmitted
Triggered when an application is resubmitted (whether by the applicant or a grant manager) See Resubmission - Application tagged
Triggered when an application is tagged - User registered
Triggered when a user registers successfully - User invited
Triggered when a user is invited to the platform - Payment pending
Triggered on application submission when the invoice option is selected by the applicant - Payment success
Triggered on application submission when a payment succeeds via your payment gateway - Role granted
Triggered when role is assigned to a user - Action stage started
Triggered when an action stage is started. The notification needs to be selected on the action stage before being triggered - Action stage completed
Triggered when an action stage is completed (i.e when a Proceed or Stop decision is made)
Note: the notification must be selected on the review stage before being triggered. - Application eligible
Triggered when an application is found to be eligible when using the eligibility check feature. - Application ineligible
Triggered when an application is found to be ineligible when using the eligibility check feature.
Creating a notification
- Go to Settings > General > Notifications
- Click New notification
- Select the trigger for the notification
- 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:
a. User: The person the event relates to
b. Email addresses and/or phone numbers: One or more specified addresses
c. Address specified in a field: allows an email or phone number field from the application process to be selected; this step allows for someone an application relates to, to receive a notification - A sender name and reply-to email address may optionally be set
Note: we strongly recommend including a reply-to address so your users can contact you via return email. To improve email deliverability, the sending address cannot be updated. - Write an email subject, email body message and SMS body message
- If both an email and SMS are defined, what is sent depends on the recipient; i.e. the recipient has both addresses defined, only the email is sent
- SMS body is required and should be kept as short as possible
- Email body is optional—if not defined, the notification does not get sent to email recipients
- Content related to the triggering user or application 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.
Merge fields
Depending on the trigger selected, there are different merge fields available. See below the complete list of merge fields available for notifications. (Note: some merge fields may not be available on the Intro plan, such as those related to action flow)
|
{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 application was submitted under |
|
{chapter} |
Chapter the application 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 |
|
{application_field:aAbBcCdD} |
Any application field for the season. The identifier after the colon is the eight character 'slug' for 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 |
|
{application_local_id} |
Each application has an entry ID number. You can find the entry ID next to the entry name under Applications > Manage applications (by default the application ID is not shown to entrants, you can turn it on under Settings > Applications > General) |
|
{application_name} |
Title of the application |
|
{application_slug} |
Each application has a unique 8 character identifier. You can find the slug by going to the application and looking for the eight-character identifier in the URL |
|
{first_name} |
First name of the applicant |
|
{invoice_url} |
For paid application, the URL of the invoice |
|
{last_name} |
Last name of the applicant |
|
{order_id} |
For paid entries, the order ID |
|
{payment_amount} |
For paid applications, the amount paid for applications |
|
{review_url} |
For action 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' for 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 |
