#3: Calling students who booked onto your Open day

#4: Calling students who didn’t attend a booked event

This article provided 5 examples of segments that work well with SDDs created in Campaign Manager. You can use these to base your own segments on. TIP: including which occurrence the activities have taken place in is recommended, otherwise you get activities from all occurrences of that app.

Scenario #1: 📞📞📞 Calling applicants

Your remote team wants to call all new UG applicants each day using data you will send them via an SDD.

You set up the segment’s filters as follows:

You schedule your SDD to run each day Mon to Fri and activate it.

The SDD is now active and each day it finds students in SDB who match the filters in your segment since the last delivery date/time.

However, if a student has already been sent in this SDD, they are not included again, unless there is new activity to add into your selected summary fields.

Reason: you don’t want to call the same applicant again unless they now have a new application.

When it runs:

Monday sends 10 records: 10 x students with new UG applications (and the summary info field tells you they each have 1 application).
Tuesday sends 1 record: it sends only the 1 x student who added a second application (and the summary info field tells you she now has 2 applications).

Scenario #2: 📞📞📞 Calling enquirers

Your remote team wants to call all UG enquiries using data you will send them via an SDD.

You set up the segment’s filters as follows:

You schedule your SDD to run each day Mon to Fri and activate it.

The SDD is now active and each day it finds students in SDB who match the filters in your segment since the last delivery date/time.

However, if a student has already been sent in this SDD, they are not included again, unless there is new activity to add into your selected summary fields.

Reason: you don’t want to call the same enquirer again, unless they now have a new enquiry.

When it runs:

Monday sends 20 records: 20 x UG students who have just enquired (and the summary info field tells you about the enquiry).
Tuesday sends 16 records: 15 x new UG students who have just enquired, plus 1 x student from Monday’s batch who has made another enquiry since yesterday (and the summary info field tells you about both enquiries).

Scenario #3: 📞📞📞 Calling students who booked onto your open day

Your remote team wants to call all new open day bookings using data you will send them via an SDD.

You set up the segment’s filters as follows:

You schedule your SDD to run each week on a Tue for 6 weeks leading up to the open day, and activate it.

The SDD is now active and each week it finds students in SDB who match the filters in your segment since the last delivery date/time.

However, if a student has already been sent in this SDD, they are not included again, unless there is new activity to add into your selected summary fields.

Reason: you don’t want to call the same UG student again, unless they now have another booking.

When it runs:

Week 1 sends 150 records: 150 x students with new UG bookings (and the summary info field tells you they each have 1 application).
Week 2 sends 175 records: another 170 x students with new UG bookings in the last week, plus 5 x students who added a second booking (and the summary info field tells you they now have 2 bookings).

Scenario #4: 📞📞📞 Calling students who didn’t attend a booked event

Your remote team wants to call students who did not attend an event using data you will send them via an SDD.

You set up the segment’s filters as follows:

You schedule your SDD to run once, 2 days after the open day, and activate it.

The SDD is now active and on the scheduled date it finds students in SDB who match the filters in your segment.

This SDD does not run again as you have set the deactivation date to the day afterwards.

When it runs:

2 days after the open day it sends 20 records: 20 x students who did not attend an event they booked onto (and the summary info field tells you about each booking).
De-activates after 1 send - no more data.

Scenario #5: 💌💌💌 Mailing out prospectuses

You want to send new UG prospectus requests to your mailing house for postal fulfilment.

You set up the segment’s filters as follows:

You schedule your SDD to run each day Mon, Wed and Fri and activate it.

The SDD is now active and each day it finds students in SDB who match the filters in your segment since the last delivery date/time.

However, if a student has already been sent in this SDD, they are not included again, unless there is new activity to add into your selected summary fields.

Reason: you don’t want to send out another prospectus again unless they now have a new request.

When it runs:

Monday sends 50 records: 50 x students who requested a UG prospectus (and the summary info field tells you they each have 1 request).
Wednesday sends 60 records: 58 x new students who requested a UG prospectus, plus 2 x students who added a second request (and the summary info field tells you about each request).