Skip to main content
All CollectionsPeopleRelationships
Sending Campaigns to Parents/Guardians
Sending Campaigns to Parents/Guardians

Discover how to effectively send Campaigns to parents or guardians.

Michael Stephenson avatar
Written by Michael Stephenson
Updated over a month ago

Overview

Communicating effectively with parents or guardians is pivotal in nurturing a successful enrollment funnel. This article covers the process of sending Campaigns to parents or guardians and important things you should know, especially if you don't have separate parent records/profiles. We recommend reviewing the Family Members and Relationships article as a prerequisite to this article.

The push notification channel in Campaigns is intended for student communication only, as parents/guardians do not have access to StudentHub.


Email Campaigns

Tokens for Parent/Guardian Emails

There are two different tokens you can use to send email Campaigns to parents/guardians:

  1. Guardian Emails [user:guardian_emails]

    • This token targets family members with the internal type “guardian” (when family/guardian data was collected using the "Parent / Legal Guardian” field grouping (user-family-root) or imported using user-family-guardian mappings).

  2. Relationship Emails [user_related:emails]

    • This token targets separate family records with a relationship to the student record with a specified relationship type (when you store parent/guardian data as separate contact records).

    • When using this token, you will have the option to configure the token properties, which will allow you to target specific relations (parent-child, guardian-dependent, grandparent-grandchild, etc.).

Using Tokens in Campaigns

Option 1: Email from a Token (Guardian Emails)

If you collect family/guardian data using the field grouping or import and do not store the data on separate contact records via a relationship, you can use the Guardian Emails token in the "Send To" field.

It is important to note the Send To field supports only a single email address. As a result, if the contact has multiple family members with email addresses on their record, only one family member will receive the Campaign. This approach is straightforward but might not be able to meet your comprehensive outreach needs.

Tokens used to personalize the email, like [user:first_name], will be replaced with data from the student's record.

When using this method, email activity (received, opened, clicked) is tracked on the student profile, but you can see the email address to which the message was sent by viewing the activity details.

Option 2: CC'ing Guardian and Relationship Emails

A more inclusive alternative is to utilize the student's email in the "Send To" field and place one of the two email tokens in the CC (or BCC) field. Unlike the "Send To" field, the CC and BCC fields can accommodate multiple email addresses, ensuring all listed family members receive the Campaign.

While this method ensures a broader reach, the student is the primary recipient, and therefore, any tokens used to personalize the email, like [user:first_name], will be replaced with data from the student's record.

To determine which token to use depends on how you store the family/guardian data:

  • If separate records exist for parents/guardians, you can use either token. It depends on your needs and if you wish to target specific relationships.

  • If separate records do not exist, you can only use the Guardian Emails token.

Option 3: Create Separate Family Records

For a more direct and inclusive approach, consider using a Rule to generate separate records for each family member with data stored on the student's record. This option works best when your message targets only parents or guardians—perhaps starting with "Dear [Parent's Name]" or sharing specifics exclusively relevant to them.

This method guarantees that if a student has more than one parent with independent records, they will each receive the personalized Campaign.

Once a parent/guardian has a separate record, the process mirrors sending Campaigns to student records:

  • Create a parent/guardian Segment using the filters of your choice, but you must use the Profile Type to exclude student and other record types.

  • Use that Segment as your audience in your Campaign (one-time) or Workflow (ongoing).

  • Configure your Campaign 'Send To' setting to the Primary Email of the family record.


SMS Campaigns

To send text message Campaigns to parents or guardians, you need to create separate records for them. You can follow the same steps as outlined in Option 3 for sending an email Campaign. Once you have separate records created, you can then create/select a segment of family records as your SMS audience. For the steps to create a parent segment, see the next section below.


Create a Segment for Parent Communication

📙 Note: Before creating a parent Segment, you should have a basic understanding of Segments, Campaigns, and Workflows.

  1. Navigate to Contacts > People

  2. Click Add Filter

  3. From the Type dropdown, select Relationships

  4. A new window will open, where you will configure your Segment.

  5. Click the Relationship is dropdown to select your relationship type. For this case, we will want to choose the Parent-Child.

  6. Additional configurations will appear. Since we are segmenting parent records, we will keep the default selection of Parent.

  7. Click Add Filters and choose the related student filter(s). Even though you're targeting parent records, select filters related to student data. For example, to target parents of students interested in a specific major, you could use the filter intended major = accounting.

  8. Once you're finished adding filters, click Submit. You will be returned to the People list, where your new Relationship filter should be visible.

  9. Click Apply to apply your Relationship filter.

  10. You should now see your segmented parent records associated with students who match the specified filter (e.g., students with an intended major in accounting).

  11. You can then click Save As New Segment to retain your Segment for future use and the ability to load it into a Workflow. If you want the Segment to automatically update as data changes on records, be sure to convert it to a calculated segment.

Did this answer your question?