System emails are transactional and trigger based on a specific action in Slate.

What are system emails?

System emails are configured when your Slate database was initially provisioned. Find them in Deliver → Folders → System.

You can customize most system emails. You can also create and customize your own system emails.

This article lists each default system email, its purpose, and whether it has default content or requires configuration before it will be delivered.

Some system emails won’t send until they are configured

Some system emails do not have default content, and they do not send until they are specifically configured. These include:

• Application Creation

• Application Submission

• Decision Notification

• Reader Queue Notification (Daily)

• Reader Queue Notification (Weekly)

📝 Administrative creation and submission of a Slate-hosted application does not cause application-related system emails to be sent to applicants.

Account Creation

Sent when an account is set up in Slate before an applicant starts a Slate application.

Subject: {{Name of Slate School}} Online Registration

Thank you for registering online with {{Name of Slate School}}.

To activate your account, please use the link below:

Activate Account

When requested for a password, enter the following temporary PIN:
##########

{{Name of Default Message Group}}

Account Email Migration

Sent when an applicant requests a change to their email address.

Subject: {{Name of Slate School}} Change Email

It was requested that the email address for this account be changed.

To complete the requested changed, please use the link below:

Complete Requested Change {{Link}}

Upon logging in with your current credentials, the change will be completed.

Account Password Reset

Sent when an administrator resets a password or an applicant has forgotten their password and submits a request to change their password from the /apply page.

Subject: {{Name of Slate School}} Password Reset

It was requested that the password for this account be reset.

To access your account, please use the link below:

Access Account {{link}}

When requested for a password, enter the following temporary, randomly-generated PIN:
###########

You will have an opportunity to change your password after authenticating.

{{Name of Slate School}}

Application Creation

Sent when an applicant creates a Slate application.

📝 This system email does not have default content is not sent until it is configured.

Application Submission

Sent when an applicant submits a Slate application.

📝 This system email does not have default content is not sent until it is configured.

Decision Notification

Sent to the applicant when a decision is confirmed and released with a decision letter assigned.

📖 Further reading: Decision Notification Status Update Email

📝 This system email does not have default content is not sent until it is configured.

Recommendation Request (To Recommender)

Sent to a recommender when an applicant requests one through the Slate application.

Subject: Recommendation Request from {{Name of Student}} for{{Name of Slate School}}

Dear {{Name of Recommender}}:

{{Name of Student}} has requested that you write a letter of recommendation to {{Name of Slate School}}
on their behalf. In an effort to make this process as easy as possible for you, we offer the ability to complete
your recommendation online through our secure website. To submit your recommendation, please use the link below.
This link is unique to this recommendation and should not be shared or forwarded.

Submit Recommendation (link)

Thank you for your time and consideration.

{{Name of Slate School}}

Recommendation Submission (To Applicant)

Sent to the applicant when the recommendation is received and stored in Slate.

Subject: {{Name of Slate School}}

Dear {{Name of Student}}:

We have successfully received your letter of recommendation from {{Name of Recommender}}
to {{Name of Slate School}}.

{{Name of Slate School}}

Recommendation Submission (To Recommender)

Sent to the recommender when the recommendation is received and stored in Slate.

Subject: {{Name of Slate School}}

Dear {{Name of Recommender}}:

We have successfully received your letter of recommendation for {{Name of Student}}
to {{Name of Slate School}}.

Thank you for your time and consideration.
{{Name of Slate School}}

School Report Request (To School Official)

Sent to the school official when the applicant submits a School Report request.

Subject: School Report Request from {{Name of Student}} for {{Name of Slate School}}

Dear {{Name of School Official}}:

{{Name of Student}} has requested that you submit a school report to {{Name of Slate School}} on their behalf.

In an effort to make this process as easy as possible for you, we offer the ability to complete your school report
online through our secure website. To submit your school report, please use the link below:

Submit School Report (link)

Thank you for your time and consideration.

{{Name of Slate School}}

School Report Submission (To School Official)

Sent to school official when a School Report is received and stored in Slate.

Subject: {{Name of Slate School}}

Dear {{Name of School Official}}:

We have successfully received your school report for {{Name of Student}} to {{Name of Slate School}}.

Thank you for your time and consideration.

{{Name of Slate School}}

School Report Submission (To Applicant)

Sent to applicant when a School Report is received and stored in Slate.

Subject: {{Name of Slate School}}

Dear {{Name of Student}}:

We have successfully received your school report from {{Name of School Official}} to {{Name of Slate School}}.

{{Name of Slate School}}

Reader Queue Notification (Daily)

Sends messages to users where:

• That user has applications in their queue

• Those applications are:

  • In an active Period

  • In a bin that has the Queue Notifications set to "Active"

Reader Queue Notification emails will only send if there is at least one application in the reader's queue where the bin setting for Queue Notifications is set to Active. The merge field "count" will send a total count of all applications in the reader's queue that are in an active period. The merge field "count_notification" will send a count of applications in the reader's queue in a bin where the Queue Notification setting is Active. (This number will be the same or less than the "count" number since this will only include the number of applications in the queue in the bins configured for Queue Notification).

📝 This system email does not have default content is not sent until it is configured.

Reader Queue Notification (Weekly)

Sends messages to users where:

• That user has applications in their queue

• Those applications are:

  • In an active Period

  • In a bin that has the Queue Notifications set to "Active"

Reader Queue Notification emails will only send if there is at least one application in the reader's queue where the bin setting for Queue Notifications is set to Active. The merge field "count" will send a total count of all applications in the reader's queue that are in an active period. The merge field "count_notification" will send a count of applications in the reader's queue in a bin where the Queue Notification setting is Active. (This number will be the same or less than the "count" number since this will only include the number of applications in the queue in the bins configured for Queue Notification).

📝 This system email does not have default content is not sent until it is configured.

When does the weekly email send?

The weekly Reader Queue Notification email sends on Monday mornings at approximately 6 AM EST.

Reader Queue Notification System Emails will not send for workflows. Please review Workflow Queue Internal Notifications with Deliver to configure workflow notification emails.

System Emails for Slate Payments

Details on automatic emails related to Slate Payments, their message content, and how they can be customized are found in the System Emails for Slate Payments Slate Scholar article.