Why are admissions enquiries a good fit?
Admissions enquiries are a good fit for a Digital FTE because the majority are routine questions with a documented answer, they arrive in seasonal peaks that are hard to staff, and they come from people who deserve a fast, accurate reply. A prospective student asking about entry requirements at 11pm should not wait until Monday.
The minority that are about a specific person, such as an applicant's status or circumstances, need a trained human, and the design keeps them there.
How does it answer routine enquiries?
The Digital FTE answers from the documents you approve: the prospectus, programme pages, entry requirements, fee schedules, deadlines, and application guidance. Each reply cites the document and section it used, so the enquirer can read further and the admissions team can verify quickly.
Replies start as drafts for approval. Once a category such as application deadlines shows a long run of unchanged drafts, it can be promoted to auto-send. Categories are promoted individually, and any can be stepped back.
What always goes to the admissions team?
Anything about an individual applicant goes to the admissions team: application status, decisions and appeals, disability or learning support needs, safeguarding concerns, financial hardship, visa or immigration circumstances, and any enquiry from or about a minor that goes beyond public information.
The escalation arrives with the enquiry, any relevant policy the FTE found, and a suggested next step, so the team member starts informed. The list is fixed and does not shrink as the FTE earns autonomy elsewhere.
- Application status, decisions, and appeals
- Support needs and reasonable adjustments
- Safeguarding and welfare
- Financial hardship, visa, and immigration questions
What happens when documents conflict?
Institutions often have a prospectus, a programme page, and a policy document that disagree on a detail such as a deadline or a fee. The Digital FTE flags the conflict rather than choosing between them, and escalates the enquiry with both passages quoted so the admissions team can resolve it and correct the source.
Over a cycle, these flags become a list of document corrections, which is a useful by-product: the institution's public information gets more consistent because every inconsistency that confused an enquirer was surfaced.
How does the FAQ improve?
When the same question escalates repeatedly because no document covers it, the Digital FTE proposes an FAQ addition drafted from how the team answered, for approval. Next cycle, that question resolves at first line with a citation.
Measure with first-line resolution rate, median response time including out of hours, and the volume reaching the team during peak weeks. Record the baseline from the previous cycle, and review the escalation reasons weekly during the first peak to tune the remit.
What does a cited enquiry answer look like?
A cited enquiry answer is short, specific, and points at the document it came from. As a labelled example, a question about the entry requirements for a programme is answered with the requirements as stated on the programme page, a link to that page, the application deadline from the current calendar with its date, and one sentence on how to apply, with the guidance page linked. If the prospectus and the programme page disagree on a detail, the answer is not sent; the conflict is flagged with both passages and the enquiry escalates.
The admissions reviewer checks the answer against the cited page in seconds, checks the tone, and approves; a send-back with a reason is logged and repeated reasons become a rule. Anything about the enquirer's own circumstances, an application's status, or a support need is not answered by the FTE at all; it reaches a person with the enquiry and any relevant policy attached. During peak weeks the manager sees, in the morning brief, the volume handled at first line, the categories escalating most, and the proposed FAQ additions waiting for approval.
Record the baseline from the previous cycle before the first reply: enquiries received, first-line answers given by the team, response times including out of hours, and the questions that came up most. Those numbers are what the second cycle's comparison is read against, and they usually reveal which document corrections would have prevented the most enquiries.