Skip to main content
Decision Announcement Pack

Use this Pack to automatically alert applicants when admissions decisions are made.

Ardis Kadiu avatar
Written by Ardis Kadiu
Updated over 4 months ago

Overview

The Decision Announcement Pack contains pre-written emails and an automated workflow that automatically emails an applicant when a decision status has been changed and released in Decision451.

This Pack is useful for for institutions who wish to automatically contact applicants with email notifications when an admission decision has been made. It offers pre-written emails in a variety of tones and design styles to give users the flexibility to choose a message that fits their institution's needs.


This Pack is for any institution using App451 and Decision451. This Pack sends out email notifications to applicants when decisions have been released. Each notification is installed as a separate Pack. For example, if an institution wants to alert applicants when "admitted" decisions have been released and when "conditionally admitted" decisions have been released, they should install both an "admitted students" pack and a "conditionally admitted students" pack.

This separation of workflows is purposeful, so institutions only install and configure one workflow and accompanying automated message at a time, given the need to be deliberate with these types of communications.

Video Guide

Customizations

This Pack offers several places to customize the message and workflow. You can select your application and term to associate with this workflow and specify a custom link in the email call-to-action button. Additionally, you can set the delay between a decision status being released and the email message going out to the applicant.

Brand assets such as your logos, fonts, and colors are automatically built into emails generated in this Pack from your Packs tokens. You can also choose from pre-written email styles and select a custom background animation.

Like all Pack components, we strongly recommend reviewing any installed components before activating a workflow. To use any Pack in the Library, you must first set up your Packs Tokens. Click here to learn more about Packs Tokens.To use any Pack in the Library, you must first set up your Packs Tokens. Click here to learn more about Packs Tokens.To use any Pack in the Library, you must first set up your Packs Tokens. Click here to learn more about Packs Tokens.

To use any Pack in the Library, you must first set up your Packs Tokens. Click here to learn more about Packs Tokens.

Pack Install Options

When installing the Pack, you'll need to configure the following options.

  • Application Type and Application Term: You can install this Pack multiple times to connect to as many applications as you wish. However, each Pack install only connects to one single application. Select the application you wish to use with this Pack in the drop-down menu.

  • Optional CTA link: The default link in each email's call-to-action button is the associated application portal. You can change this with a custom link. For example, if you want to send admitted students to a specific landing page rather than the application portal.

  • Message Delay: This is the delay between a decision status being released and the message being sent. By default, it is set to 24 hours, but you can choose any other value.

  • Decision Status: Choose from admitted, conditionally admitted, waitlisted, or denied. Subsequent email choices are displayed based on the decision status selected.

  • Configure Communications

    • Sender email address and name: configures the reply-to email address and name of the sender in messages that are sent.

    • Contact info: Populates the footer fields in the associated emails


Reviewing the Workflow and Email/SMS Messages

Before activating the campaign, you should review all the included components in this Pack. After installing the pack, you can see a list of these.

Email Components

You can access your email under Engagement > Campaigns > Ongoing Communications.

Content is pre-written but we strongly recommend reviewing before setting your campaign to active. There is additional space with highlighted instructive copy for the institution to include any additional information or context for the user.
​

These emails use the following tokens:

  • [user:first_name, fallback="there"]

    • Displays the user's first name with a fallback option in the event it isn't in the system (unlikely).

  • [client:name]

    • Displays your institution's name as specified in your Pack tokens.

  • [user_application:term]

    • Displays the application term to the user as specified in the Pack install options. For example, "Fall 2023."

Customizing Emails

Each installed email is pre-configured in the Pack install options for the decision type, style, and background image.

Download previews of all email types and styles by clicking the links below:

Video Guide: Email Customizations

Workflow Components

The installed workflow is available under Data + Automations > Workflows > All Workflows.

Video Guide

This workflow automates the sending of the email message. The workflow is triggered by the following criteria:

  • Decision {Released}

    • {Status} is {admitted, conditional, waitlist, or denied}

    • {Application} is {your application}
      ​

Messages are sent after a delay if they meet the following criteria:

  • Application (all properties)

    • {Status - Decision} is {admitted, conditional, waitlist, or denied}

    • {Stage} is {Release}

    • This looks to see if a decision has been released for a specific application. If the decision has been released, the message will be sent.
      ​

Before activating the campaign, check the delay between the initial campaign trigger and the "send communication" stage. By default, this is set to 24 hours to provide a buffer in case a decision is accidentally released.


Activating the Campaign

After you have reviewed your email message and your workflow configuration, set your workflow status to active to begin running the campaign.

Did this answer your question?