Guest User

February 22, 2021

Student Recruitment Campaigns by Student CRM

Guest User

February 22, 2021

Student Recruitment Campaigns by Student CRM

Only Student CRM delivers the richness of student data, combined with the best looking CRM you have ever used - to allow your recruitment officers to create unlimited, targeted, effective recruitment campaigns that increase your recruitment performance like never before. See what Campaign Manager can do for you.

Student CRM is the leading-edge CRM software for HE providers.

Transcript:

Hi, I'm Dom Yeadon, founder of Student CRM, and we're going to look at how easy it is to create your student recruitment campaigns from within Student CRM.

So who is this for? It's for:

universities that want to improve their students' recruitment results,
universities that want it to be easier and more effective to recruit students each year,
universities you want to start off by following best practice from day one, and
universities who want to use the best newest cutting edge recruitment tools year after year.

So these are the most effective types of campaigns that our universities send out. They are:

Offer-holder conversion emails
Newsletters
Webinar invites
Audition announcements
UCAS deadline reminders
Open Evening invites
Enquiry follow-ups

To create a list of students you wish to target, you simply add filters, drawing information from everything the students have made enquiries, bookings, applications, looking at certain levels of study faculties, UCAS course codes - the list is almost endless.

And you choose from personalized email and SMS broadcasting, or you can download CSV data or ready to print PDF letters and labels.

To use the built-in Template Builder, you simply select any of your branded email templates and send yourself previews so you can check that it looks great.

Broadcasting - once your student lists and your templates are both ready, you can broadcast immediately or schedule it for later. And for scheduled broadcasts, it double-checks your segment at the time of broadcast to make sure the list is as fresh as possible.

Instant reports show your opens and clicks, your top links, who did what and when, plus you can easily tag recipients for a follow-up campaign in a few clicks.

Students CRM’s Roadmap lists the forthcoming upgrades that give your recruitment campaigns even more power. Now, no other CRM does this because no other CRM is built to perfectly meet the needs of its student recruitment users.

So thank you. If you use student CRM already, we thank you for helping us to make this the world's best university CRM. If you haven't tried it yet. Do get in touch for a demo. And if we can help you, we will.

Guest User

February 18, 2021

Student Database - Tools & Tabs by Student CRM

Guest User

February 18, 2021

Student Database - Tools & Tabs by Student CRM from Dom Yeadon on Vimeo.

The Student Database app (SDB) stores every student along with a record of everything they have ever done.

This data is updated in real-time as the student opens emails, completes web forms, enquires, books onto events, applies, uploads documents, changes their mobile, and so on. Learn more about Student Database.

Student CRM is the leading-edge CRM software for HE providers.

Transcript:

Hi, I'm Dom Yeadon founder of Student CRM, and today we're going to look at the student record card - tools and tabs.

This webinar is going to cover the student record card itself, new keyboard shortcuts, looking at applications, the likelihood ring, tools and tabs. And then, at the end, we're going to look at the future of Student Database (SDB) - where the product is going on the Roadmap.

(DOM CLICKS THROUGH THE DECK)

The student record card is obviously where all the information generated in all of the other apps gets centralised into one location. The student record card typically consists of some engagement bar information at the top of the record - here we have the name, persona, stage etc, and then some more information underneath. You'll see straight away that the information underneath is in tabs.

New keyboard shortcuts. As you know, I am a fan of using fingers rather than mice, if I can. So I've just highlighted the four new shortcuts. When you're in a student card, if you want to edit any of the tabs, you simply click “E” to edit.

On the right-hand side, to jump to any of the tabs, you can use the numeric keys 0 to 9, and that will jump you to the relevant tab. And down the bottom, the rolodex viewing - so when you are viewing a student or a number of students, you can use the arrow keys on your keyboard to tab left and right. And finally, we've got the “plus button” to add. So the plus button will then add a note or a task or an association. It is contextual so it will add an item depending on which tab you are in.

Let's look at the first thing in the top of the engagement card, which is applications. In the engagement bar we have the student's ID and to the right of that, you'll see a number of ticks. Each tick is an application and the different colours represent different things. So if it is a grey color, then the application is from a previous year of entry. If it is a green application, then that student has enrolled. And if it's a black or very dark grey tick, then that is for an application that is still waiting to close - so not yet enrolled in the current season.

The likelihood ring is a ring that closes around the inside of your avatar. So Rob Andrew Sanderson has an avatar, a purple avatar because he has the persona of “wise owl”, so that's what colours it. And around the inside of that ring, you can see his likelihood score at 30%. Because again, that's driven from the “stage 3 - Intends to apply”. We know this gives Rob a 30% likelihood of actually enrolling and that now creates a ring around the inside. As the likelihood creeps up, the rings go round and round until they close up with an enrollment.

In tools on the right-hand side, you've got the “more options button”. And in here we can send an email, we can send an SMS, we can add a note or a task. We can even add a course of interest. And again, as before we can send the privacy center login links, or we can reset a password. We can also add a new student, merge this student or even delete this student.

Looking across the bottom, we first have the “Personal” tab. Here we can see all the standard personal information.

The ”Courses” tab - here you can see the most recently interested course on the left and then all the history on the right-hand side.

In the “Apps” tab is all the information the student has given through the various apps that they have interacted with.

“Data” tab contains the codes, legacy codes, MIS codes, any data stuff in the left-hand panel. And then on the right we control the GDPR consents, channels and topics.

Number five, “Tasks” - tasks is one tab totally related to tasks for this record only. And you can see other officers' tasks in here, so you can see who else is working on tasks for this one student.

“Notes” are searchable. Any notes you put in are displayed here. On the right-hand side you'll see a plus icon to add a new note. And again they're searchable.

“Docs” - this lists all the docs that the student or an officer has uploaded either in Enquiries or in Applications. And you can see the source of those and jump through to look at the Application or the Enquiry.

“Associations” allows you to associate a student with another entity. So it can either be another student or an organisation in Contract Manager or an agency in Agent Manager or teachers or agents or different students. There are lots of ways you can create an association. They all get listed here.

“Logs” - this is where everything is stored. So whatever is done to the student is stored here in different log types and the filters across the top allow you to search by logs and filter by log types and even the apps that they were generated in.

“Sensitive Data”, requires a permission in your user card to view this tab. You can get permission very easily by asking your user admin, and anyone who lands on this page can click that link at the bottom and they can read how to request access to sensitive data.

This is what's in the sensitive data at the moment. It's just gender, ethnicity, disability code and death/fraud.

And in order to get access to sensitive data, you need to check that this is checked in your platform access profile. If it isn't, then simply contact one of the user admins on the right-hand side.

And of course the last tab is the All-in-one tab. Everyone should be familiar with this. It’s the classic All-in-one tab, that is still there for anyone who wishes to use the old layout.

We'll follow up at the end with the Roadmap. So the Roadmap which you can access inside from your jump menu, I've simply filtered by Student Database to have a look at all of the items to do with Student Database that we are shipping.

So some are at a hundred percent progress and some are still being shipped. That one at the bottom, of course, will move up to a hundred percent as it was shipped yesterday.

Okay, thank you. I'm now going to go into the app itself and let's have a look.

(DOM LOGS INTO STUDENT CRM TO DEMO)

We're starting on the homepage. And of course, what I'm going to do is I'm going to look at my student record called Sanderson. So I'm going to shortcut F for “Find” and I'm going to find all the Sandersons.

So again, what this does, you can see there we had some saved searches from the ones I've done before. And if I go into here, I obviously want to sort by score, find the most engaged, which is Rob Sanderson. Fantastic. I am going to click into Rob and look at his record card live.

On this record card, we've again, got the engagement bar at the top with each of those applications, which mouse over. And if I were to click those, I’d jumped to the actual application themselves. We've also got the rolodex. So you will remember that I found three Sandersons I can tab through and look at the other Sandersons. We've got a Dominic Sanderson and a Jane Sanderson. And of course, I'm going to work in Rob Andrew Sanderson. (The data that we're sharing with you, of course, is sample data from a sample university - it’s not client data.)

If we look at the likelihood ring here, we can see that it's up to 75% that's affected by the stage. I think in the demo, it was showing at “4 - Applied”, which is at 50%. “Intends to apply” is 30%. And then it goes up through the stages to the top. What we want to do is, we want to get this student up to enrolled and, of course, these can be automatically updated upon actions using Automations. So I'm moving it manually just to show you that. Of course, this is driven by processes inside Student CRM.

Now we can do quite a few things in here. This is the more options. I'm going to quickly walk you through a couple. So I can send an email. This is a one-to-one email. Okay. And this is, Hi, It’s Dom from NFU and I'm going to just start to type Hi, Rob. And then I don't really want to use an original response. So I'm going to get a saved response. This works exactly the same way as Enquiries. I know that number three is the one I want. So I just bring that saved response in and there it is. Off we go; that is now sent and logged. And we'll find that later when we look down the logs.

The next thing I'm going to do from here is I'm going to add a task. So let's add a task. And what I want to do is I want to add a task - I'm going to assign it to Laura. And I spoke with Rob and there's something we need to follow up on. So, after the weekend, which will be Monday, let's get it done by three o'clock in the afternoon.

I spoke with Rob about the status of his architectural technology application. This one up here, actually, and said we’d check and reply. Laura, could you please do that? So there I've just created a task for another user.

And finally, I'm going to add a note to the student record. So let's add a note and this is going to be a telephone call because I spoke to Robert earlier. And there's the information - he called us and wondered if we can get back to him with the information. Using the more options on the side, there's plenty of things you can now do all by staying on this card.

Let's go to tab two. And I'm just going to remind you by typing “K” that in our shortcuts, we can jump across the tabs using the 0-9 student tabs.

So I will type number 2 and we jump across to Courses.

In Courses, we've got a shortcut to add a course. And we can edit the courses. On the right-hand side, all of the pre-existing history is listed, but in this tab, if you want to add a new course of interest, you can simply do so here by following exactly the same academic selectors. I won't do this because I don't want to over-ride the latest one at the moment. But you can add a new course in and that's really useful if you're on an enquiry and the enquiry comes in through IEM and there's no course in there. So you can add a course in that way.

Next we're going to look at number three, tab three is the Apps, and this is every app that Rob Sanderson has interacted with. So he's made some bookings in Pre Applicant Open Day, and because he's our test student, he has a significant history in this particular tab. There's a lot of information there.

Tab four (Data) is where we can edit the channels; as can the student in their data privacy center. Now, again, one of the shortcuts in here is the “E” for edit. So wherever you see a pencil, you can either click on the pencil to edit the student, or you can type the shortcut “E”. By typing the shortcut, E, it turns into this mode and I'm going to turn off “Phone” because Rob asked me too; on the phone, strangely enough! Okay.

Tab five is Tasks. Task is a listing. And here you can see the tasks that we put in today. So you can search whoever created the task, who it was assigned to and the statuses of them. So you can now cancel a task as well. Statuses are quite useful. That's a new status - the cancelled one.

Number six, the Notes tab. Notes is where you can filter by any note. And again, the notes are by different types. So there's the note I've just put in just now (Rob called us). And again, you can search in Notes for anything you like.

Docs. These are the applications. I can download these straight to my desk here, or I can jump over to the application or the inquiry that they were saved in. Obviously in Applications, these are documents that the student or the agent (if using international agent portal), or the officer themselves uploads against the application.

And these are often files that are sent in as attachments uploaded in the form, so during an inquiry form, these will appear here. There's no, “Plus” here - you cannot add a document here. They have to originate elsewhere.

Tab 8 - Associations. Again, you can connect any student with any other entity in Associations. And in this case, it says here the student was introduced by Bournemouth Collegiate College. Let's jump across to Bournemouth Collegiate College. We leave the Student Database and go into Contact Manager. Here is the college and there is the relationship. So this organisation introduced the student. And again, you can jump back. So Associations allows you to add an association if you want, or to go and look at the other associations you've got.

When I look at the Logs tab, then, again, filterable by the search bar at the top. Out of 1,109 log events, I just want to find all the campaigns that this student has been involved in. This student has been involved in 60 different campaigns. And there's the record of every single one. That's quite useful to see.

In the Sensitive tab, I have been granted permission by my user admin, so I can see these. I can even edit these if I want to.

And then at the end we have the All-in-one tab and this tab contains everything stacked rather deeply and tabs at the bottom. So for those who wish to remain using the All-in-one tab, please do.

For the rest of us, I think these new tabs are fast and easy. If I want to edit this, I can edit just one particular field and save very quickly. So it's much faster to edit specific pieces of information on the student record card now.

(DOM BROWSES TO THE PRODUCT ROADMAP)

Over to the Roadmap. The Roadmap is where we publish where the product is going. So we can see here, I filtered by Student Database and these are the four things that have been shipped and there's more things coming up. As Student Database evolves, the Roadmap can be planned and seen here.

Okay, we're going to go back now to the homepage and these are all the apps we're using.

And just one final slide. This is about Student Database and it's one of the 26 apps inside Students CRM. And if you're seeing this for the first time, please do get in touch and you can request a demo. Thanks very much. Okay. This is Dom Yeadon founder of Student CRM signing off. Thanks very much.

(END)

Guest User

February 17, 2021

Automations Manager by Student CRM

Guest User

February 17, 2021

Automations Manager lets your university student recruitment officers build automations that routinely carry out complex actions.

Saves you time: never carry out manual tasks again.
Extends your powers: get inside your processes like never before.
Optimises how you work: create rules that work for you.
Easy to use: just set it and forget it.

Student CRM is the leading-edge CRM software for HE providers.

Find out more

Transcript:

Hi, it's Dom, the Founder of Student CRM, and we're going to look at Automations Manager. So, a quick webinar just to go through what this app does. In this minute webinar, which is going to run for 12 minutes, we're going to look at how Automations Manager works and how this makes your student recruitment life better.

(DOM CLICKS THROUGH THE DECK)

The apps you can automate in are Enquiries (ENQ), Mobile Event Capture (MEC), Prospectus Requests (PRQ) and Rapid Response (RAP) - there are slight differences between each of those. And we're then going to look at how you can monitor the performance of the automations you've set up. And then the practical part - we'll build three automations, and then we'll look at the future of Automations Manager as well.

So the first part, how does Automations Manager work?

Well, the idea behind Automations Manager is that your recruitment teams use it to configure and then manage any automations. Those automations routinely carry out specified actions when certain processes run.

(DOM EXPLAINS THE 3 BASIC STEPS ON SCREEN)

So on the right-hand side, we can see that every time a PROCESS occurs. And in this case, it's listening out for the process “If an inbound email (IEM) creates a record in your Enquiries app”. OK, Step 1, that's the process that it listens out for.

The second Step is that it sees if the condition is met. So you could say that you only want certain IEMs to be run in this automation. So in this case, it's saying “if it's been forwarded from your Admissions team inbox (admissions@uni.ac.uk) into Enquiries, then it'll meet the CONDITION”. So if the conditions are met in this second step, then it will carry out the action.

And in this case the ACTION is that it's going to replace the existing content in the field ‘category’ with “admissions”. I'll explain later why that is a good thing to do for IEMs.

(DOM EXPLAINS THE 4 BENEFITS)

So how does this make your life better? Well, firstly, it'll save you time, so you never have to carry out manual tasks again.

Secondly, it extends your powers. So it allows you to get inside your processes, like never before. I'll cover that a little bit later.

Thirdly, it optimises how you work. So you can now create rules that work for you and do lots of the heavy lifting.

And fourth, it is just so easy to use, like a lot of processes inside Student CRM, you just set it and forget it.

(DOM GOES INTO DETAIL IN EACH APP)

So the apps that you can automate inside today are Enquiries (ENQ), Mobile Event Capture (MEC), Prospectus Requests (PRQ) and Rapid Response (RAP). In this list the greyed out apps are currently on our roadmap because we are also introducing Applications (APS/V), Student Database (SDB), and the three event apps, Event Manager (EVM), Pre-applicant Open Days (POD), and Applicant Open Days (AOD). So those are the apps you can automate in at the moment, and the other ones are coming soon.

So if we look at automating in Enquiries (ENQ), we know that this gets triggered when an Enquiry comes in. So on the left-hand side, we look at the conditions. You can set a condition, ie: “if the category is XXX, if the channel is XXX, if the message contains XXX, etc”.

So those were your conditions. And on the other two-thirds of the screen, we look at the actions. So actions in Enquiries can update the ‘category’, the ‘owner’ and the ‘priority’ of that Enquiry. But more importantly, it can also update fields from the Student Database Record Card as well. So if an email enquiry contains XXX, (maybe it's got a particular phrase in it), then you can update the record card.

And of course the most useful one of those is down the bottom, right. Which is ‘adding a tag’. In Mobile Event Capture (MEC), you've got a few more fields to use when setting conditions because, unlike an enquiry, the Mobile Event Capture (MEC) web form is on your iPad. MEC is not in huge usage at the moment, because of COVID. Conditions in this app allow you to use any of the fields that the student has completed on their form, which tend to be a lot more fields than an Enquiry.

So we've got MEC - any of the mobile event capture fields down there, and then the Student Database fields that are entered on the screen. So you could set up a condition to look for, say, if they type the mobile number in X, then run an action. And the actions on the right hand side, are this time just updating fields on the Student Database Record Card.

It's much the same for Prospectus Requests (PRQ) and Rapid Response (RAP), so I won't go into too much detail on those two, but it's the same principle that applies.

(DOM SHOWS THE PERFORMANCE CHART)

Once you've set up an automation, then it runs and it charts every single time the automation is successful. So it doesn't chart if it looks but does not get triggered to run because the conditions are not met. So in other words, it's running all the time.

If you get twenty enquiries in, and only three of them qualify to be run as an automation, you'd only see three on this chart. Where one of our Universities is currently running automations and they've got twelve separate automations running - you can see they're getting quite a lot of value from the app itself each day.

(DOM LOGS INTO STUDENT CRM TO DEMO)

What we're going to do is to build three separate automations. Now I will go into our demo account ‘New Forest University’ and I will look at three example automations and we'll build them out together.

Okay. So here we are in Automations Manager being the primary app on my home page. When I click into this, I filter to find my 3 examples as I just want to see those that I've prepared in advance - automations one, two, and three. (And of course I can also filter by the different processes that are available in different apps.)

(DOM BUILDS AUTOMATION NUMBER ONE)

I'm going to go into automation number one, and let's look at how we build it. So automation, number one. This automation assigns a team to a student record based upon the Postcode Area. Okay. So let's look at how we set up this process, then the conditions and the actions.

Let's expand this and take a look. So what I do is I choose the PROCESS I'm looking for in Step 1, and I'm looking for “when a web form creates a record”. I then look at a target app - this one is in Rapid Response (RAP). And then I pick one or more occurrences that it runs on because you can have one automation running simultaneously across many occurrences.

The second part is the CONDITIONS in Step 2. And you'll notice that if I run a second condition, then it can either match ‘any of the following conditions’ displaying the operator ‘OR’, or it can match ‘all of the following conditions’ with the operator ‘AND’. So we've said we want to assign teams based on a postcode, so that's quite simple.

We look at the condition: any postcode areas that are in the list ‘BH DT SP and PO’. So when a student types their full postcode in, the postcode area is automatically calculated. Then it'll find and qualify only those postcodes.

And of course it will carry out the action - and the action is to replace the field content in the team, and this demo uni already has two teams, so we're going to choose ‘UK Recruitment’. So once that's done, we simply set it to active and that is now up and running. So in this one, we have added a team based on a postcode.

(DOM BUILDS AUTOMATION NUMBER TWO)

Let's look at automation number two. Automation number two assigns an enquiry to a category if it comes in via IEM - in other words, there was no web form and it is an unstructured email about a student's application. So let's have a look at the Step 1 PROCESS settings for this one, ‘When a Web form creates a record in Domestic Enquiries, then the following conditions apply’.

So I'm going to add a CONDITION here and I'm going to say that if the forward came from your Admissions team inbox (admissions@uni.ac.uk) - in other words if you're forwarding emails sent into your Admissions team inbox into your Enquiries (ENQ), then I want to replace the category with ‘Admissions’. OK, so what I've done here in this one is I've said that if IEM creates a record in a certain occurrence, and it's been forwarded from a particular email it will assign the correct category. So you've got some useful fields in here, ie: - forwarded from a particular address at your university. Then of course it can replace the field content of the current category with ‘Admissions’.

So that's the second one done.

(DOM BUILDS AUTOMATION NUMBER THREE)

The third one we'll look at is automation number three, which updates the student’s stage. So as we know, a stage on a student's record takes them from 1. Enquiry to 6. Enrollment, and we will look at how this one is built. Step 1 PROCESS is ‘if a web form creates a record in Rapid Response (RAP)’, and we're going to choose the occurrence ‘Domestic Enquiries’ to keep it separate from International Enquiries.

Now, we specifically want to target this automation on students who fill out our “if you intend to apply, please complete this” web form, regardless of what details they submit in the form. Step 2 CONDITION is all students who complete that form, so it's a catch-all condition.

If this form is completed, then the STEP 3 ACTION is going to replace the stage for all who intend to apply. So this allows you to collect an intent from a student, completing a form. One quick note, whenever you are using stages and you are automating stages, stages only ratchet up, so you don't downgrade a Stage 5 Applicant to a Stage 2 Enquirer. It will only ever go up and up and up. (It's just a quick side note.)

So those are the three automations we've looked at. Lets just finish off the webinar.

(DOM WRAPS UP)

So that's the future of Automations Manager. Automations Manager Is currently benefiting from quite a lot of investment from our team. So we know the power of this, just from the apps that are using automations already. We're also adding it into Student Database (SDB), and the three event apps, Event Manager (EVM), Pre-applicant Open Days (POD), and Applicant Open Days (AOD).

(DOM BROWSES TO THE PRODUCT ROADMAP)

When you look at our Roadmap, which you can get from your ‘Jump’ menu inside the login, then please have a look at the jobs that are ‘open’, you can then filter here and you can also look at the progress to shipping %. We have included the due date on the right hand side so you can see which month each new Roadmap item ships in.

So I will draw this to a close now and say that JJ is always happy to send you a quote, and to look at your needs in terms of an AMM automation. Thank you.

(END)

Guest User

February 15, 2021

Get the 2021 University Guide to Best Practice in Student Recruitment

Guest User

February 15, 2021

This 2021 Guide to Best Practice in University Student Recruitment contains the top 5 best practice recommendations you can action today.

This guide can help your university to consistently increase enquiry, engagement, application and conversion rates. So you can hit your numbers, and deliver on your strategic plan.

Dominic Yeadon

April 29, 2020

Super segments - fields to filter by

Dominic Yeadon

April 29, 2020

A super segment finds students who have taken part in many activities, such as 'made an enquiry', 'attended an open day', 'applied for 2020 entry', and then 'enrolled'.

Create your own super segment in seconds:

(Image above: this is what a super segment looks like; note that each filter is searching inside a different app.)

Creating a super segment is easier to do when you know which fields to use from each app. This article lists the apps you can filter by and the fields you can use in each app:

AOD - Applicant Open Days

 Bookable . . . . . . . . . . ie: "yes"
 Booked Open Day Date . . . . ie: "3 Jul 2019"
 Booked Open Day ID . . . . . ie: "2544"
 Booked Open Day Name . . . . ie: "New Forest Applicant Day"
 Booking Status . . . . . . . ie: "Attended"
 Course Code  . . . . . . . . ie: "P0980980"
 Course Group Code  . . . . . ie: "ARCH-20"
 Course Name  . . . . . . . . ie: "French History"
 Form . . . . . . . . . . . . ie: "UG web form(ID:7070.01"
 Interview  . . . . . . . . . ie: "yes"
 Level of Study . . . . . . . ie: "Undergraduate"
 Occurrence . . . . . . . . . ie: "Applicant Days 2020 (ID:4585)"
 UCAS Course Code . . . . . . ie: "C878"
 Year of Entry  . . . . . . . ie: "2020"

APS - Applications

 Application Status . . . . . ie: "Declined"
 Course title . . . . . . . . ie: "Computer Sciencee"
 Date Created . . . . . . . . ie: "3 Jul 2019"
 Deferred . . . . . . . . . . ie: "Yes"
 Enrolled . . . . . . . . . . ie: "Yes"
 Entry Source . . . . . . . . ie: "UCAS"
 Form . . . . . . . . . . . . ie: "UG web form(ID:7070.01"
 Intake Month/Year  . . . . . ie: "September 2019"
 Level of Study . . . . . . . ie: "Undergraduate"
 Occurrence . . . . . . . . . ie: "Passive UG Applications (ID:4585)"
 Qty Enrolled   . . . . . . . ie: "1"
 Qty Submitted  . . . . . . . ie: "2"
 Residency Status . . . . . . ie: "Home"
 Year of Entry  . . . . . . . ie: "2020"

ENQ - Enquiries

 Category . . . . . . . . . . ie: "Admissions"
 Channel  . . . . . . . . . . ie: "IEM"
 Enquiry date . . . . . . . . ie: "Sat 03 Jan 2019"
 Form . . . . . . . . . . . . ie: "UG web form(ID:7070.01"
 Feedback . . . . . . . . . . ie: "good"
 Occurrence . . . . . . . . . ie: "Domestic Enquiries (ID:4586)"
 Open/Closed  . . . . . . . . ie: "Closed"
 Owner  . . . . . . . . . . . ie: "Sally Smith"
 Priority . . . . . . . . . . ie: "Yes"
 Status . . . . . . . . . . . ie: "New"
 Updated date . . . . . . . . ie: "Thu 03 Jan 2019"

EVM - Event Manager

 Booked Event Date  . . . . . ie: "3 Jul 2019"
 Booked Event ID  . . . . . . ie: "12345"
 Booked Event Name. . . . . . ie: "New Forest Student Led Tour"
 Booking Status . . . . . . . ie: "Not Attended"
 Course Code  . . . . . . . . ie: "P0980980"
 Course Name  . . . . . . . . ie: "French History"
 Custom field 1 . . . . . . . ie: "custom value 1"
 Custom field 2 . . . . . . . ie: "custom value 2"
 Custom field 3 . . . . . . . ie: "custom value 3"
 Form . . . . . . . . . . . . ie: "UG web form(ID:7070.01"
 Level of Study   . . . . . . ie: "Undergraduate"
 Occurrence . . . . . . . . . ie: "Student Tours (ID:4585)"
 UCAS Course Code . . . . . . ie: "C878"
 Year of Entry  . . . . . . . ie: "2020"

MEC - Mobile Event Capture

 Course Code  . . . . . . . . ie: "P0980980"
 Course Name  . . . . . . . . ie: "French History"
 Created date . . . . . . . . ie: "Sat 03 Jan 2019"
 Enquiry Source . . . . . . . ie: "Register your interest"
 Event Name . . . . . . . . . ie: "Student Fair"
 Form . . . . . . . . . . . . ie: "RAP - UK Enquiries (ID:6703.01)"
 Level of Study . . . . . . . ie: "Undergraduate"
 Location . . . . . . . . . . ie: "O2 Arena London"
 Occurrence . . . . . . . . . ie: "International Events (ID:4586)"
 Subject Name . . . . . . . . ie: "Art and Design"
 UCAS Course Code . . . . . . ie: "C878"
 Year of Entry  . . . . . . . ie: "2020"

POD - Pre-applicant Open Day

 Booked Open Day Date . . . . ie: "3 Jul 2019"
 Booked Open Day ID . . . . . ie: "12345"
 Booked Open Day Name . . . . ie: "New Forest Open Day"
 Booking Status . . . . . . . ie: "Attended"
 Course Code  . . . . . . . . ie: "P0980980"
 Course Group Code  . . . . . ie: "ARCH-20"
 Course of Interest . . . . . ie: "French History"
 Form . . . . . . . . . . . . ie: "UG web form(ID:7070.01"
 Level of Study   . . . . . . ie: "Undergraduate"
 Occurrence . . . . . . . . . ie: "PG Open Days (ID:4585)"
 UCAS Course Code . . . . . . ie: "C878"
 Year of Entry  . . . . . . . ie: "2020"

PRQ - Prospectus Requests

 Course Code  . . . . . . . . ie: "P0980980"
 Course Name  . . . . . . . . ie: "French History"
 Created date . . . . . . . . ie: "Thu 03 Jan 2019"
 Delivery Method  . . . . . . ie: "Post"
 Enquiry Source . . . . . . . ie: "Register your interest"
 Form . . . . . . . . . . . . ie: "Rap - UK Enquiries (ID:6703.01)"
 Level of Study   . . . . . . ie: "Undergraduate"
 Occurrence . . . . . . . . . ie: "PG Open Days (ID:4585)"
 Subject Name . . . . . . . . ie: "Art and Design"
 UCAS Course Code . . . . . . ie: "C878"
 Year of Entry  . . . . . . . ie: "2020"

RAP - Rapid Response

 Course Code  . . . . . . . . ie: "P0980980"
 Course Name  . . . . . . . . ie: "French History"
 Created date . . . . . . . . ie: "Thu 03 Jan 2019"
 Enquiry Source . . . . . . . ie: "Register your interest"
 Form . . . . . . . . . . . . ie: "Rap - UK Enquiries (ID:6703.01)"
 Level of Study   . . . . . . ie: "Undergraduate"
 Occurrence . . . . . . . . . ie: "PG Open Days (ID:4585)"
 Subject Name . . . . . . . . ie: "Art and Design"
 UCAS Course Code . . . . . . ie: "C878"
 Year of Entry  . . . . . . . ie: "2020"

A super segment of course also includes these fields from the Student Record Card in Student Database:

SDB - Student Database

Address 1 . . . . . . . . . . . . . . ie: "-"
Address 2 . . . . . . . . . . . . . . ie: "-"
Age . . . . . . . . . . . . . . . . . ie: "-"
Consent . . . . . . . . . . . . . . . ie: "-"
Country . . . . . . . . . . . . . . . ie: "-"
County  . . . . . . . . . . . . . . . ie: "-"
Course of interest - ever . . . . . . ie: "-"
Course of interest - most recent  . . ie: "-"
Course Tag - ever . . . . . . . . . . ie: "-"
Course Tag - most recent  . . . . . . ie: "-"
CRM ID  . . . . . . . . . . . . . . . ie: "-"
Date Created  . . . . . . . . . . . . ie: "-"
Date Modified . . . . . . . . . . . . ie: "-"
Date of Birth . . . . . . . . . . . . ie: "-"
Death/Fraud . . . . . . . . . . . . . ie: "-"
Disability  . . . . . . . . . . . . . ie: "-"
Email Address . . . . . . . . . . . . ie: "-"
Engagement Score  . . . . . . . . . . ie: "-"
Ethnicity . . . . . . . . . . . . . . ie: "-"
Faculty . . . . . . . . . . . . . . . ie: "-"
First Name  . . . . . . . . . . . . . ie: "-"
Form  . . . . . . . . . . . . . . . . ie: "-"
Gender  . . . . . . . . . . . . . . . ie: "-"
Last contacted  . . . . . . . . . . . ie: "-"
Last Name . . . . . . . . . . . . . . ie: "-"
Level of Study  . . . . . . . . . . . ie: "-"
Likehood  . . . . . . . . . . . . . . ie: "-"
Marketing Unit  . . . . . . . . . . . ie: "-"
MIS ID  . . . . . . . . . . . . . . . ie: "-"
Mobile  . . . . . . . . . . . . . . . ie: "-"
Nationality . . . . . . . . . . . . . ie: "-"
Note Content  . . . . . . . . . . . . ie: "-"
Note Type . . . . . . . . . . . . . . ie: "-"
Occupation  . . . . . . . . . . . . . ie: "-"
Opted in to Email . . . . . . . . . . ie: "-"
Opted in to Phone . . . . . . . . . . ie: "-"
Opted in to Postal  . . . . . . . . . ie: "-"
Opted in to SMS . . . . . . . . . . . ie: "-"
Persona . . . . . . . . . . . . . . . ie: "-"
Postcode  . . . . . . . . . . . . . . ie: "-"
Prospect Status . . . . . . . . . . . ie: "-"
PRV Account Created . . . . . . . . . ie: "-"
Region  . . . . . . . . . . . . . . . ie: "-"
Responsible . . . . . . . . . . . . . ie: "-"
Source  . . . . . . . . . . . . . . . ie: "-"
Source App  . . . . . . . . . . . . . ie: "-"
Stage . . . . . . . . . . . . . . . . ie: "-"
Subject of interest - ever  . . . . . ie: "-"
Subject of interest - most recent . . ie: "-"
Team  . . . . . . . . . . . . . . . . ie: "-"
ULN . . . . . . . . . . . . . . . . . ie: "-"
UTM Campaign  . . . . . . . . . . . . ie: "-"
UTM Content . . . . . . . . . . . . . ie: "-"
UTM Medium  . . . . . . . . . . . . . ie: "-"
UTM Source  . . . . . . . . . . . . . ie: "-"
UTM Term  . . . . . . . . . . . . . . ie: "-"
Year of Entry . . . . . . . . . . . . ie: "-"

Universities are all moving online to host their open days.

Many of our universities use Event Manager (EVM) for their online events. This is how it works:

What’s the difference between on-campus and online (virtual) events?

The only difference is that you and your team welcome your pre-registered and on-the day visitors to your university’s Live Event webpage, instead of your actual campus.

All registrations go directly into Student CRM.
All touchpoints go out from Student CRM before and after the event.
All activity is saved against each student’s record in Student CRM, maintaining an up-to-date record of ongoing activity throughout the Coronavirus impact.
It is absolutely vital that you get no holes in your data because you go online to manage how the Coronavirus impacts your university’s recruitment events.

We have a FREE one-click integration with Unibuddy.

How to run this season’s events online

1. Create the booking form (in Student CRM)

Create an EVM event called ‘Virtual Open Day’, give it a date and start and end times when it will run.
Give it a location of ‘online’ and set the event live.

2. Prepare for the live event (in Unibuddy Live)

In Unibuddy, set up the event to run at the same date and times as in EVM.
Get your team and content ready.

3. Promote (in Student CRM and social media)

Create a segment of all the students you want to invite, and paste the EVM Booking form URL (inc UTMs) into your email and send out the invite emails.
Give the EVM Booking form URL (inc UTMs) to your social media team as a destination URL for all activity promoting the event.

4. Remind with Touchpoints to increase attendance (in Student CRM)

your touchpoints will go out to all students who booked to attend (including details of Unibuddy Live URL), 20 days before, 10 days before, the day before, etc

5. Host it on the day (in Unibuddy)