Student Portal Onboarding Friction at a University
A university’s IT service supports 28,000 students. At semester start, the student portal receives three times normal demand. Forty percent of service desk tickets are password resets. New students report confusion about multi-factor authentication (MFA) setup, and the service desk uses a single phone queue with an average wait of 25 minutes. Student satisfaction with onboarding is 3.1 out of 5, and 18% of new students fail to complete online enrollment by the deadline. The portal is the only channel for enrollment, and there are no self-service options. There is no journey map; SLAs focus on ticket resolution time rather than student outcomes. Marketing, academic registry, and IT each send separate onboarding communications. The CIO wants to improve the student journey without increasing the service desk budget and has asked for a plan that shapes demand rather than only adding capacity.
1. Map the student onboarding journey from offer acceptance to the first week of classes. Identify at least three moments of truth and explain how the current service design affects each.
Read the worked answer
Journey stages: offer acceptance → account creation → MFA setup → first portal login → online enrollment → orientation → first week of classes.
Moments of truth:
- Account creation and first login: students receive credentials but no guided MFA setup. This is a high-emotion moment; failure here blocks everything. Current design pushes students to a phone queue, so a simple setup problem becomes a 25-minute wait and a poor first impression.
- Online enrollment deadline: the portal is the only channel and there is no self-service. When students are confused, they cannot self-correct; 18% miss the deadline. The service design treats this as a ticket-resolution problem, not a student-outcome problem.
- First week of classes: separate communications from marketing, registry, and IT create conflicting instructions. Students lose trust and call the desk for clarification, adding demand.
Reasoning: The journey map would show a rising emotional dip at MFA setup and enrollment. The current SLAs measure how fast tickets close, not whether students complete enrollment. Mapping the journey exposes that the biggest pain points are avoidable demand, not desk capacity.
2. Recommend engagement and demand-shaping actions to reduce password resets and improve enrollment completion. Explain how each action affects demand or the customer journey.
Read the worked answer
Self-service password reset and MFA pre-registration: allow students to reset passwords and register MFA before the semester peak. This shifts demand from the phone queue to self-service and removes the most common ticket type (40%). Measure adoption, not just ticket reduction.
Proactive, sequenced communications: replace separate marketing/registry/IT messages with a single onboarding campaign that tells students exactly when to set up MFA and enroll. This reduces confusion-driven demand and improves the journey at the moment of truth.
Staggered onboarding windows: give different student cohorts enrollment windows and reminders. This shapes peak demand away from a single week, reducing wait times without adding staff.
Guided chatbot or virtual assistant: provide step-by-step MFA and enrollment help with escalation to a human. This shapes demand by deflecting simple queries and improves first-contact resolution.
Engagement with academic registry: agree joint success measures (enrollment completion, time to first login) and share journey data. This aligns service relationships around student outcomes rather than internal SLAs.
3. How should the university change its SLAs and service relationship measures to reflect the student journey rather than ticket resolution?
Read the worked answer
Shift from ticket SLAs to journey SLAs: define measures such as percentage of new students who complete MFA setup within 24 hours of account creation, percentage who complete enrollment before the deadline, and time from first login to enrollment completion. Keep a resolution-time measure for incidents, but do not let it dominate.
Add experience measures: onboarding satisfaction, journey NPS, and effort score at MFA setup and enrollment. These show whether the service is easy, not just fast.
Create joint service relationships: agree targets with academic registry and marketing for communication timing, data quality, and enrollment outcomes. Hold a monthly journey review using a shared dashboard. This reflects DSV’s emphasis on service relationships and customer outcomes.
Use demand-shaping targets: self-service adoption rate, phone queue wait time during peak, and percentage of password resets handled without a ticket. These measures show whether demand is being shaped rather than merely absorbed.