Application Submit Push

Nudge applicants to submit completed app and offer to auto-submit it for them using this Pack.

Ardis Kadiu avatar
Written by Ardis Kadiu
Updated over a week ago

On This Page:

Overview

The Application Submit Push Pack is a communications campaign and action that offers to auto-submit an application that is complete, but not yet submitted.

Who this Pack is for
This Pack is for any institution using App451 to manage applications.
​
​What you can customize
You must choose an application to associate with this Pack.
​
You can also set the delay from the applicant's last login to auto-submit the application (default is 48 hours).


Once the Pack is installed you can also customize the emails as you see fit. Your brand assets such as logos, fonts, colors, as well as pre-written messaging, are included in the installed components. Like all Pack components, we strongly recommend reviewing any materials before activating a workflow.

Packs to Support Application Completion, Submission, and Admitted Yield

This Pack can be used with other Packs in our library to support the full application journey from submission to deposit.

See how you can use these Packs together in the overview video below.
​

Packs Tokens

To use any Pack in the Library, you must first set up your Packs Tokens (usually done during implementation). Learn more about installing Packs Tokens.
​
​

Pack Install Options

  • Application Type: 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 you use with this Pack in the drop down menu.

  • Hours Until Automatic Submission

    • Sets the delay between the last applicant login and the auto-submit action.

  • Configure Communications

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

    • SMS phone number and sender name: similarly configures the phone number and name referenced in text messages that go out. (e.g., "This is Chris from Element University...")

    • 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. You can see a list of these after installing the Pack.
​

Email Components

The reminder emails ask applicants to return to their portal to submit their completed application and offer to auto-submit on their behalf after a delay.

This also includes 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.

Feel free to edit the messages as you see fit or add any additional information or context for the recipient about the next steps in this process.

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

Workflow Components

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

Users are entered into the workflow if they have completed (but not submitted) an application specified in the Pack install options. One email reminder will be sent encouraging the user to submit their application.

If they do not do so, a follow-up message will go out offering to auto-submit on their behalf if they do not log in to the application portal within the window specified in the Pack install options.

  • If the user does not log in, the application will autosubmit.

  • If the user does log in, but does not submit their application, the communications sequence will restart.

Before activating the campaign, check the delay in between steps to confirm the campaign will run at your desired message frequency.


​

Activating the Campaign

After you have reviewed your email/SMS messages and your workflow, set your workflow status to active to begin running the campaign.

See Also

Did this answer your question?