Industry guides

University Admissions Phone Handling: Deadlines and Peaks

How university and college admissions offices can handle applicant calls, deadline peaks, results days and out-of-hours enquiries without overpromising.

Call editorial team · Published · 5 min read

University admissions offices work to a calendar. For most of the year the phone is steady; then a deadline approaches, results are released or clearing opens, and the volume jumps overnight. Staff who handle complex applications by day are suddenly answering the same fifty questions by phone, and applicants who cannot get through get anxious.

A university admissions adviser on a call at a desk with a laptop
Illustrative image

This guide covers how admissions teams at universities and colleges can structure phone handling: what to answer automatically, what must stay with people, and how to prepare for the peaks. It sits alongside Handling Seasonal Peaks and Phone Handling for Cram Schools, and is written for general use rather than any single country's system.

Who calls admissions, and what they ask

CallerTypical questionWho should answer
Prospective applicantEntry requirements, deadlines, how to applyApproved written answers, then a person for edge cases
Current applicantHas my application arrived? What is the status?Staff with record access
Parent or guardianCosts policy, accommodation, support servicesApproved answers and a person
International applicantVisas, language tests, document formatsSpecialist staff
Teacher or adviserReference requests, school visitsNamed contact
Offer holderAccepting, deferring, changing courseStaff with authority

The first column explains why one generic menu seldom works. Separating applicants who are still deciding from applicants with a live application is the most useful split.

Questions that can be answered from approved text

Admissions information changes every cycle, and an out-of-date answer on the phone causes real harm: an applicant misses a deadline or applies for a course they cannot take. The safest approach is to keep a single approved document of answers, owned by a named person, and update it at the start of each cycle.

What belongs in the approved answers

  • DatesApplication opening and closing, document deadlines, results and response dates.
  • RequirementsTypical entry requirements by course type, language tests, portfolio or interview rules.
  • ProcessHow to apply, what happens after, how decisions are communicated.
  • SupportDisability support, scholarships information, accommodation and campus visits.

Mark each answer with the date it was last reviewed. If your agent or staff cannot find the answer, they should say so and take a message rather than guess.

What an automated agent must not do

The line between information and decision is critical in admissions. An applicant who hears "you will probably get in" on a recorded line will treat it as a promise.

These limits mirror the cautions in What an AI Receptionist Should Not Do and Voice AI Guardrails.

Preparing for deadlines and results days

Peaks are predictable. You know the dates in advance, which is the one advantage you have. Build a plan for each peak a month ahead.

A peak-day plan

  1. Four weeks beforeReview the approved answers and update dates.
  2. Two weeks beforeTest the phone menu, voicemail and callback options end to end.
  3. One week beforeBrief staff and decide who handles escalations and walk-ins.
  4. Peak daysMonitor queue size and waiting time hourly; adjust staffing and messages.
  5. AfterReview the questions asked and fill the gaps in your answers.

A short pre-recorded message at the top of the menu, such as "Results are released on the date shown on our website; we cannot see results by phone", can cut call volume noticeably when it is accurate and updated. Check it daily.

Offer callbacks rather than long waits

An applicant on hold for a long time is likely to hang up and call again, which doubles your volume. A callback option lets them keep their place without staying on the line. See Using Callbacks and Voicemail in Your IVR.

Applicants in other time zones

International applicants call at times that are inconvenient for them and your office closed hours ago. Offer a clear out-of-hours experience: opening hours stated with the time zone, a way to leave a message or request, and a promise about when you will reply that you can keep.

Out-of-hours options

Voicemail onlyRequest with structured details
What the caller doesRecords a message in their own wordsAnswers a few questions: topic, application number, best time
What staff getAudio to listen to, sometimes unclearA short summary with fields to sort and act on
Best forVery small teamsBusy cycles and international enquiries

Handling applicant data on the phone

Applicant records can include grades, identity documents, health information about adjustments and immigration status. Keep calls to the minimum needed, and avoid asking callers to read out sensitive details unless the process requires it. Where calls are recorded, say so at the start, set a retention period, and limit who can listen. Data Retention for Call Recordings and Access Controls in a Contact Center are good places to continue.

Admissions phone readiness

  • Approved answers reviewed this cycle and dated
  • Staff know which calls always go to a person
  • Callback and out-of-hours options are tested
  • Recording notice and retention rules agreed
  • A named owner updates the messages on peak days

Measuring across the cycle

Report by week, not just by month. Track how many calls are answered, how many become callbacks, how long applicants wait, and the topics of the most common unanswered questions. Those topics tell you what to put on the website, which reduces calls the following year. See Call Center KPI List for definitions.

A worked example: results day

Picture a mid-sized admissions office on the morning results are released. Applicants who hoped for good news and those who did not are all calling at once, and staff are also processing decisions. If the phone is not planned, the line is engaged all day and anxious callers redial hundreds of times.

With a plan, the first thing a caller hears is a short, accurate message saying what can and cannot be discussed by phone, followed by a clear option to leave a request or ask for a callback. Staff with the authority to discuss individual cases work through the list in order. Distressed callers are put through to a person immediately. The example is hypothetical, but the principle holds: when volume is predictable, the kindest approach is to decide in advance what the phone will do.

Doing it in Call

In Call, an admissions team can use an IVR to split applicants, offer holders and general enquiries into queues, with business hours and holiday closures deciding what callers hear. Voicemail per queue and callback requests handle overflow and time zones, and the callback list shows who still needs a return call. An AI agent can be given your approved answers and told to hand over anything outside them. Call summaries let staff read the enquiry before calling back, and the CRM keeps applicant contact records. See Callback Requests in Call and Business Hours and Holidays in Call.

Frequently asked questions

Can an AI agent tell applicants whether they will get an offer?

No. It should only share published information and never imply a decision. Offer decisions belong to the admissions team.

How do we keep phone answers up to date each cycle?

Keep one approved document with a named owner and review dates, and update it before applications open and again before major deadlines.

What should happen when results are released?

Expect a surge. Use a short, accurate message at the top of the menu, offer callbacks, and add staff or overflow cover for those days.

How do we support international applicants in other time zones?

State opening hours with the time zone, accept structured requests out of hours, and reply within the time you promise.

Should the phone line confirm an application's status?

Only after staff have verified identity under your policy. An automated agent should take a request rather than disclose personal records.

Do we need to record admissions calls?

It is your decision, subject to local rules. If you record, tell callers at the start, limit access and set a retention period.

Plan callbacks and queues for admissions peaks in Call

In the demo console you can try incoming calls in a simulation.

Related guides