How Many Hours Your Admissions Team Loses to Repetitive Questions

How many hours is your admissions team really losing? Here is the formula

Most admissions directors guess somewhere between "a lot" and "I don't want to know." The honest answer is calculable in under five minutes with a number your own team already has: monthly enquiry volume.

The formula is simple: hours lost per month ≈ (monthly prospect enquiries) × 72% × (average minutes to answer one repetitive enquiry) ÷ 60. The 72% comes from Skolbot's classification of 12,000 real chatbot conversations: 72% were simple FAQ-type questions answerable without any school-specific context, 21% needed some institutional context, and only 7% genuinely required a human adviser (Source: Skolbot, 12,000 conversations, 2025). In other words, roughly three out of every four prospect questions your team fields are variations on the same handful of topics — tuition fees, career outcomes, work placements — asked by a different person each time.

That 72% is not a guess about your school specifically. It is a measured share of question type, and it holds remarkably steady across business schools, specialist colleges and university faculties because the underlying anxieties (cost, career outcome, accommodation) don't change much by sector. What varies is your enquiry volume and your average handling time — both of which you can plug in yourself, which is exactly what the worked example below does.

Why the same handful of questions dominate every enquiry inbox

The repetitive 72% is not randomly distributed across topics. A small cluster of questions recurs so consistently that Skolbot's analysis of 12,000 chatbot conversations (September 2025–February 2026) can rank them by frequency.

Tuition fees top the list at 89% of conversations, followed by career outcomes after graduation at 84%, work-study or sandwich options at 78%, and student accommodation at 71% (Source: Skolbot, 12,000 conversations, Sept 2025–Feb 2026). International exchange options, entry requirements, internship duration, degree accreditation, campus life and financial aid round out the top ten. None of these questions are unpredictable — a prospective student researching a business school or specialist college asks about money and career return before anything else, then works down to logistics.

The reason this matters operationally is that these are precisely the questions your prospectus, programme pages and FAQ already answer somewhere. Prospects ask anyway because the answer is buried three clicks deep, split across a PDF and a webpage, or simply hard to find at 9pm on a Sunday when they're actually doing the research. Your team ends up re-typing the same fee breakdown and placement statistics dozens of times a month, not because the information doesn't exist, but because it isn't surfaced at the moment the question is asked.

The hidden cost isn't just hours — it's the prospects who stop waiting

Hours lost to repetitive questions are only half the problem. The other half is that prospects don't sit patiently in your queue while your team gets to their email — most simply move to the next institution on their shortlist.

Skolbot's 2025 mystery-shopping audit tested 80 institutions across five enquiry channels and timed every reply from submission to first substantive response.

(Source: Skolbot mystery-shopping audit, 80 institutions, 2025.)

The phone line, often assumed to be the fastest route, is answered barely one time in three. A prospect who cannot get through by phone and does not want to wait 47 hours for an email reply has one obvious next step: opening a tab for the next school on their UCAS shortlist. This is the pairing worth internalising — hours lost to repetitive questions (this article) and the response-time gap that pushes prospects toward competitors (covered in full in our UK school response time benchmark) are two sides of the same operational problem.

What schools recover by automating the repetitive 72%

Automating the repetitive share of enquiries does not just save admissions staff time — it changes what the funnel produces, though never in isolation from everything else a school is doing.

Across an 18-school panel that deployed an AI chatbot alongside other funnel work in 2024-2025, Skolbot recorded median qualified prospects rising from 120 to 195 per month (+62%), cost per qualified prospect falling from €42 to €26 (-38%), and open-day registration rate climbing from 6.2% to 18.4%. Median payback on the chatbot investment was around 5 months, with 12-month ROI at 280% (Source: Skolbot cross-market panel, 18 schools, 2024-2025). These are euro figures from Skolbot's pan-European panel, presented here as illustrative of the scale of gain, not as a UK-specific guarantee.

Read that median result with its caveat attached. It reflects the combined effect of the chatbot and the funnel optimisations schools typically run alongside it — new landing pages, revised nurture sequences, adjusted open-day formats. The chatbot alone does not explain 100% of the gain; it is one lever among several, and its cleanest, most attributable contribution is the time freed up when 72% of enquiries stop needing a human first draft. For the full breakdown of how these ROI figures are built and how to model them against your own numbers, see our detailed chatbot ROI calculation guide.

What the time savings mean in practice: your team stops re-answering the same fee question for the fortieth time this month and instead spends that time on the 7% of enquiries that genuinely need a human — a bursary appeal, an unusual transfer case, a nervous parent who wants a real conversation. Automation here complements the admissions team rather than replacing it; it frees up capacity for judgement calls that a chatbot correctly escalates rather than attempts to resolve.

How to calculate this for your own school, in Excel, this afternoon

You can build this calculation in a single spreadsheet with three inputs you already have or can gather in a few days. No specialist tools required.

Step 1 — Pull your monthly enquiry volume. Count every question that comes in through email, contact form, phone and live chat combined over a typical month. Most CRMs (HubSpot, Salesforce Education Cloud, Dynamics) can export this in a few clicks; if not, a rough count from your shared inbox and call log is good enough to start.

Step 2 — Apply the 72% repetitive-question share. Multiply your monthly enquiry volume by 0.72. This is Skolbot's measured share from 12,000 real conversations, not a school-specific estimate, so it's the one input you don't need to guess (Source: Skolbot, 2025).

Step 3 — Track your own average handling time. This is the one variable that is genuinely yours to measure, and it is not a published Skolbot benchmark — don't borrow someone else's number. For two weeks, have your team log how long it actually takes to draft and send a reply to a typical fees, outcomes, or placement question. Most teams land somewhere between 3 and 5 minutes per reply once you include reading the enquiry, checking a detail, and writing the response, but yours could be different — measure it.

Step 4 — Do the maths. Hours lost per month = (monthly enquiries × 0.72 × average minutes per reply) ÷ 60.

Worked example (illustrative volume, not a benchmark): a school receiving 500 prospect enquiries a month, with a team spending 4 minutes on average per repetitive reply:

500 × 0.72 = 360 repetitive enquiries per month 360 × 4 minutes = 1,440 minutes 1,440 ÷ 60 = 24 hours a month — roughly three full working days spent answering questions your prospectus already answers.

Run your own numbers with your real enquiry volume and your measured handling time, and you'll have a defensible figure to bring to your next budget conversation — one grounded in your own data rather than an industry rule of thumb. If you're evaluating vendors to act on that figure, our chatbot RFP checklist for higher education sets out what to ask before you sign.

FAQ

Is the 72% repetitive-question figure specific to UK institutions?

No — it's a global classification of question type across 12,000 Skolbot chatbot conversations, not a UK-only sample, but the underlying topics (fees, outcomes, placements, accommodation) map directly onto what UK admissions teams field daily from UCAS applicants and direct enquirers alike (Source: Skolbot, 2025). The share tends to hold steady because prospect anxieties around cost and career outcome are not sector- or country-specific.

Does automating repetitive questions replace admissions staff?

No — it reassigns their time. The aim is to let a chatbot handle the 72% of questions that don't need school-specific judgement so your team can focus on the 7% that genuinely require a human adviser, plus the relationship-building work a spreadsheet can't do (Source: Skolbot question-complexity classification, 2025).

How do I know if my handling-time assumption is realistic?

Track it directly rather than guessing. Ask two or three team members to log actual time spent on ten typical repetitive replies over a week; most UK admissions teams find the true figure sits between 3 and 5 minutes once reading, checking and writing are all included, but this is your number to measure, not one Skolbot publishes as a benchmark.

Will the ROI figures from the 18-school panel apply directly to my school?

Treat them as illustrative of scale, not a guarantee. They are median results from a pan-European panel of 18 schools where the chatbot was deployed alongside other funnel changes, so the +62% qualified-prospect increase and 280% 12-month ROI reflect a combined effect, not the chatbot in isolation (Source: Skolbot, 18 schools, 2024-2025). Your own payback period depends on your enquiry volume, current handling time, and what else you change at the same time.

What should I do with the hours figure once I've calculated it?

Use it to size the opportunity, then decide what "recovered" time is worth to your team — earlier follow-up on applications in progress, more open-day outreach, or simply fewer evenings and weekends spent clearing a backlog. For deeper analysis of how UK institutions specifically compare on response speed, see the UK school response time benchmark, and for the broader picture of chatbot deployment start with our complete guide to AI chatbots for schools.

External sources worth reading alongside this piece: McKinsey's work on generative AI in education examines where automation genuinely frees up staff capacity versus where it doesn't; EDUCAUSE's research on AI in higher education covers adoption patterns across admissions and student services; and JISC's guidance on AI in education is a useful UK-specific reference point for institutions weighing where to start.