Communication Event (archived)
Overview
This page outlines the detailed instructions to assist in walking you through how to send bulk communication emails with and without personalised attachments such as final grades, CANs and invoices.
Complexity: MEDIUM
Page Contents
Be Advised
The communication event module uses the email delivery provider SendGrid to deliver emails on behalf of the users. To avoid being classified as SPAM, it is important that our SendGrid email server IP address (168.245.65.115) is white-listed to ensure that Paradigm is able to send emails on behalf of your existing company email server. It may also be nescessary to configure a DKIM or SPF DNS record to ensure that Paradigm is permitted to send emails on behalf of a provider email domain.
For further details please contact the Silverband support team.
Key terms and concepts
The letter templates are designed to be a cover letter (in email format) for attaching invoices, CANs, enrolment letters, etc to be emailed to the students and stored as proof of communication. Copies of both the letter and attachments are then saved to the student's record within the communication event section. These can then be interrogated for delivery, bouncing, and opening. The letter can be formatted within the provider section for ease of use and minimal updating when used.
Contained within each email sent with the communication module is a one-pixel tracker. This is one 1x1 pixel that is hidden within the body of the email that allows the email client to track the email. It can determine if the email has bounced, been delivered, has been opened and read and if any attachments have been clicked into. This can be particularly useful when students are questioning if an important email/communication was sent to them and if they received it.
Below is a list of required fields to build a bulk student report for Communication events. This report can be built in the report builder and saved for future use. The fields below are required for such a report (i.e. Bulk student report) but additional ones can be added.
Table 1. All field Overview
Field Name | Brief overview |
---|---|
From Communication Request Sender | It will be sent from the email address that is recorded against the users profile. Provider record is linked with the student’s course enrolment. Make sure you load the student’s course enrolment first, then you will see Provider option in the drop-down. If you want a Provider Name/Home Institution to be in one of the options under the From field, you have to add a role to that Provider record as a “Communication Sender“, see https://silverband.atlassian.net/wiki/spaces/PKB/pages/984771 for more details. |
To Communication Request Recipient | Who the email is going to |
Communication name / Email Subject | The subject name / line of the email |
Communication Date | Date sent. This date is recorded within the communication event as the sent date. |
Communication Type | For Communication Events this is normally set to Email |
Communication Status | This will tell you the status of the communication event:
|
Course Enrolment | The Course of Study the student is enrolled in |
Communication Template Message | This option will allow the user to select from pre-written email templates. These can be added to or updated once loaded into the HTML writer. |
Communication Description / Email Body | This is where the template will be displayed once loaded. Alternatively this is where the user can write the body of the email to be sent. |
Table 2. Merge Fields in Communication
Merge Fields Within Communication Templates | Brief Overview |
---|---|
{email_from} | This is the email address of the sender |
{email_from_first_name} | This is the first name of sender (blank if the sender is a provider) |
{email_from_last_name} | This is the last name of sender (blank if the sender is a provider) |
{url_read_tracker} | This is a 1 pixel image that, when added to an email, will upon opening of the email by the receiver will mark the email as open within the system |
{email_first_name} | Student / Receiver's first name |
{email_last_name} | Student / Receiver's last name |
{student_number} | Student’s number issued by provider |
{email_subject} | The communication event/email subject |
Implications
Please note: The Example below for sending bulk communication events with an attachment assumes that a default has been set up in the report builder and uses the CANs notice. It includes instructions for checking the census date for it. If you are sending other attachments ensure that the dates required for that type of attachments are correct e.g. Final grades, invoices etc.
Workflow
Video Tutorial
Related Pages