Institutions run on a calendar almost nobody else uses. Application deadlines, offer days, enrolment windows, financial aid cutoffs, housing allocation, and semester starts produce contact spikes that are severe, repeatable, and completely unrelated to the retail year that most capacity models assume. A contact centre plan built on an annual average will be idle in July and overwhelmed in the first week of term.
The good news is that the peaks are known a year ahead, which makes them among the easiest surges to staff for and the least excusable to be caught out by. This article covers how we approach admissions and enrolment call handling for universities and colleges: how the peaks are forecast, who is on the line, what agents may say, and which measures actually tell you whether the operation worked.
Plan against the academic year
Write out the institutional year before talking to any provider. For most institutions it includes the application deadline and the days either side of it, offer release and the acceptance window, the financial aid and scholarship cutoffs, registration and course-change periods, housing and orientation, the first two weeks of each term, and the results and appeals period. Each of these produces a different kind of contact from a different kind of caller, and each has a hard stop after which the question changes or disappears.
Once the calendar exists, the forecasting problem becomes tractable. Last year's contact volumes by week, laid against this year's dates, give a base. Adjust for known changes: a new programme, a change in the application platform, a policy shift that will generate questions. That is enough to plan agent hours by week rather than by year.
A deadline week is not a busy period. It is a different operation. Contact runs longer because callers are anxious, questions are procedural rather than informational, and the cost of a wrong answer is a missed deadline that cannot be undone. The agents handling it need to be trained on the specific process that closes that week, not on the institution in general, and they need the authority to do useful things: confirm a submission was received, explain exactly what is missing, and tell the caller who to speak to if the system itself is failing.
Building the team around the calendar means agent hours ramp in the fortnight before each peak, hold through it, and drop after. Our engagement models allow that scaling; the discovery call is where the hours and agent counts for each window are agreed. A related article on the first ninety days of outsourced support covers how a new team reaches full speed before the first peak rather than during it.
The caller is often not the student
A parent calling about a student's account is the normal case here, not an edge case. So is a school counsellor, a sponsor, or an agent acting for an international applicant. What each may be told is governed by the rules that protect student education records rather than by service preference, and by whatever consent the student has recorded. An agent who improvises that decision creates a records problem rather than a service failure, and the records problem is the one that reaches the registrar.
The practical consequence is that verification cannot be left to judgement. The agent needs to know, at the moment the question is asked, whether this caller is authorised to receive this category of information about this student. That is a data question, and it has to be answered by the workflow.
Build verification into the workflow, not the policy
Rules that live in a policy document get improvised around under volume pressure. Rules that live in the agent's screen at the moment the question arises get followed. During onboarding, we work with you to turn the disclosure policy into a decision path the agent walks through on every call that touches a student record. A workable version covers:
- How the caller's identity is confirmed, and which identifiers are acceptable.
- How the caller's relationship to the student is confirmed, and where recorded consent is checked.
- Which categories of information may be discussed with each caller type, and which may only be confirmed to the student.
- The exact phrasing for declining, so the caller understands it is a rule rather than a refusal to help.
- Where the agent records what was verified and what was disclosed.
Log the decision, not just the call
Those rules are yours to set, with your registrar and counsel; our part is to make them executable and to train agents until following them is automatic. The log is the other half. What was verified, and what was disclosed on the strength of it, needs recording. The log is what makes the decision defensible months later, when a student asks who was told what, and it costs nothing at the time. It also gives quality reviewers something concrete to score. A call can be polite, quick and wrong; the log is how the wrong ones are found.
Systems access follows from this. Agents need read access to the student record system for the fields they are permitted to see, and a place to write the verification note. Access is role-based, limited to what the workflow needs, and set up by the project manager before training starts. Agents should not be working from spreadsheets exported from the student system, because exports do not carry the permissions the system enforces.
Speed is the wrong headline metric
For institutional contact the measure that matters is whether the caller left with the right answer and a correct next step. Programmes optimised purely on handle time degrade faster in this setting than in consumer service, because the questions are procedural and the wrong answer sends someone down a dead end for weeks, sometimes past a deadline. A caller who is told to upload a document to the wrong portal will not find out until the application is marked incomplete.
The measures we recommend agreeing up front for admissions work are first-contact accuracy, checked by quality review against the process; repeat contact from the same applicant within the same window, which usually indicates a wrong or incomplete answer; escalation rate to the admissions office; and, for deadline weeks, the proportion of calls answered live rather than sent to a queue or voicemail. Handle time stays in the report as context, not as a target.
The right answer delivered in six minutes beats the wrong answer delivered in two.
Multilingual coverage is an access question
Families whose first language is not English are frequently the ones going through the process for the first time and with the least institutional knowledge to fall back on. Routing them to a callback rather than a live agent affects whether they complete, which makes it an enrolment issue rather than an inclusion gesture. The languages needed are usually known from the applicant pool, and the peak periods for those callers track the same calendar.
Our multilingual support and bilingual call centre coverage is built so that the same queue serves multiple languages with the same verification rules and the same logging, rather than a separate line with different standards.
Knowledge transfer with an institution
Institutions hold their process knowledge in many places: the admissions office, the registrar, financial aid, the international office, the housing team, and a set of web pages that are not always current. Agents need one consolidated answer set, and building it is the main onboarding task. Our project manager maps the process with each office, resolves the contradictions between them, and turns the result into the material agents are trained on.
Three things make this go faster. A named contact in each office who can settle which version is correct within a day. A single change log so that when a deadline moves, every agent knows the same day. And a decision on what the agent does when the answer is genuinely not known: which office they transfer to, or which promise to call back they may make. The education page sets out how the coverage is structured across these offices.
When to keep it in-house
Some contact should stay with your own staff: appeals, complaints about decisions, anything involving a safeguarding concern, and conversations where an academic judgement is being explained. These are low volume and high consequence, and the right person is a member of the institution. The outsourced team's job is to recognise them quickly and hand them over cleanly with the context attached.
Outsourcing is also the wrong move if the institution cannot yet say what its disclosure rules are, or cannot give a provider access to the student system on any terms. Both need settling first. Until they are, an external team can only take messages, which adds delay to exactly the calls that cannot afford it.
Choosing a partner for institutional contact
Ask a provider how they plan around the academic calendar and whether agent hours can move with it. Ask to see how verification is built into the agent workflow, not just whether they say they understand education records. Ask what is logged on each call and how you can audit it. Ask how multilingual callers are handled in the same queue. Ask how the answer set is kept current when a deadline moves. And ask for the reporting rhythm in writing before launch, so you are measuring accuracy and completion rather than only speed. Those answers separate a partner who has staffed a deadline week from one who has not.