Give each channel a job
A student can receive plenty of messages and still be unsure what to do next. O.R.E. Report 003 asks enrollment teams to examine the purpose, timing and usefulness of those messages together. The practical starting point is a channel map: what does this person need, and which route makes that need easiest to meet?
Use email for instructions and context that someone may need to revisit. Keep an opted-in text focused on a timely action or a short exchange, with a clear way to stop receiving texts. A physical piece can support a milestone or shared household reference. Offer a live conversation when the question needs dialogue, while respecting the person's contact preference. The channels should support the same next step without each repeating the whole explanation.
In the recording · 11:17 ↗Read preferences with the research population in view
The linked EAB article reports on its 2025 Student Communication Preferences Survey, which EAB says reached about 20,000 prospective students. Participants could choose multiple channels, and preferences varied with their search stage. A strong email preference therefore leaves room for a useful text or mailed piece; it does not establish one channel for every situation.
SchoolFinder Group's 2025 report draws on more than 1,500 students who requested information through its platform between 2023 and 2025. Respondents were mostly based in Canada, with undergraduate, international and graduate-study perspectives represented. Use those findings to question local practice, then check the needs of your own audience. Stated preferences and impressions are different measures from completed applications or enrollment.
In the recording · 06:06 ↗Measure the answer, not just the acknowledgement
The episode recommends a clear response standard and a handoff from automated confirmation to human help. Define when that clock starts, which hours the team covers and what counts as a useful response. A receipt confirms that a question arrived; a student asking about a missing requirement still needs an answer.
Give each unanswered inquiry an owner, a next action and an escalation route. Track first acknowledgement and first substantive response separately. Look at the median alongside the oldest unanswered items, because a reassuring average can conceal a few people waiting for days. Explain out-of-hours coverage plainly and choose a standard the team can staff. If another office must answer, keep responsibility for following the question through.
In the recording · 12:22 ↗Review the sequence from the student's side
The report shifts attention from a weekly send count to the sequence a student experiences. Its proposed audit maps thirty days of contact across channels. Add the purpose, relevant stage and expected action for each touch, then look for duplicated reminders, unexplained gaps and requests that no longer apply.
A confirmation, a useful follow-up and a later reminder can form a coherent sequence when each has a reason to arrive. Check current status before every send. Stop an application reminder when the application is complete, and honor opt-outs across the systems involved. Keep family communications in a separately permissioned stream rather than assuming the student's preferences or information can simply be copied.
In the recording · 13:02 ↗Make the next step visible on a phone
Preview the subject, preview text and first screen together. Can someone identify the purpose, find the relevant date and understand the main action without opening several links? Put supporting detail below that first answer, using short paragraphs, descriptive links and a layout that remains readable on a small screen.
Make relevance concrete. An interest the student supplied can lead to a useful program resource; an application stage can determine which instructions belong next. Let people update those choices. Avoid turning uncertain tracking into a confident statement about their intentions, or using intimate-sounding language to demonstrate how much the system observed.
In the recording · 13:50 ↗Test one change with a defined outcome
Choose a manageable segment and a specific question: does a shorter sequence help people finish the next step, or does a staffed reply queue reduce unanswered inquiries? Record the starting measure, comparison group or period, and the change being tested.
Review replies, task completion, unresolved questions and opt-outs alongside clicks. Keep required information and support available to everyone in the test. A rise after a change is a reason to investigate, especially if timing or audience also changed. Use the result to revise the sequence and staffing plan rather than declaring a universal winning channel.
In the recording · 16:28 ↗