Business case and benefits
- Director of admissions
- A · Accountable
- Product owner
- R · Responsible
- Solutions architect
- C · Consulted
- Technical PM
- C · Consulted
- Engineers
- I · Informed
- Legal, compliance & DPO
- C · Consulted
- Security
- I · Informed
Prospective students get accurate answers at any hour, drawn only from the university's approved information, with open-day visits booked and enquiries logged. Admissions staff handle offers, visas and anything personal.
At a glance
An illustrative scenario. The numbers are typical examples, not a client case study. The cloud services and UK rules were checked on 9 November 2026.
Prospective students ask the same questions thousands of times a year. Does this course need A level maths? What are the fees for international students, and what else will I pay for? Is accommodation guaranteed? What English test do you accept? Can I work while I study? The answers are on the website, somewhere, spread across course pages, fee tables, PDFs and policy pages that different teams maintain.
The enquiries team answers by email, chat and phone. Replies take days in busy weeks, and two staff can give two different answers. International applicants write at night UK time and wait until morning. In Clearing, every phone line is full. Meanwhile some questions need a person, such as whether a particular qualification will be accepted or what someone's visa options are, and they sit in the same queue as questions about parking.
Accuracy is not just good service. Prospective students are consumers. The CMA's advice to higher education providers says information about courses, costs and terms must be clear, accurate and timely, without leaving out anything material, and since 6 April 2025 the CMA can fine a provider directly for misleading practices. The CMA's 2026 guidance on AI agents says a business is responsible for what its agent says, just as it is for an employee. Visa questions add a second line: giving immigration advice is regulated, and a chatbot is not an adviser.
Agree these, and measure the baseline, before anything is built. Example targets are typical, not promises.
A weekly audited sample checked against the source page. Material errors on fees, entry requirements or visas are counted separately.
ExampleAbove 98%, and no material errors left unfixed
Share of routine enquiries resolved without a person, with no repeat contact on the same question within a week.
Example60–70% of routine enquiries
How long a handed-off enquiry waits for a member of staff.
ExampleUnder one working day; same day in Clearing
A fixed test set of offer, grade-prediction and personal visa questions, run before every change. Every one must be handed off, never answered.
Example100%, every release
Share of source pages within their review date and matching the course catalogue.
Example100% for the current cycle
Open-day bookings and applications from people who used the assistant, compared with last cycle.
ExampleMeasured against last cycle
Cross-sector rules are on the UK regulation map.
C1 requires providers to show they have given due regard to guidance on consumer protection law in their policies, procedures and terms, which covers prospective students. The OfS consulted from 16 April to 9 July 2026 on a new condition C6, replacing C1 and C3, which would require clear, accurate and comprehensive information for prospective students. The assistant answers only from approved, current content, and its answers are logged so the university can show what each person was told.
Misleading information and the omission of material information, such as additional course costs, are unfair commercial practices. Since 6 April 2025 the CMA can enforce directly, with fines of up to 10% of global turnover. Fees and costs come from the fee tables through a tool and are quoted exactly, with any additional costs the page lists.
The university is responsible for its assistant as it would be for a member of staff, including errors. People are told they are talking to an AI, it doesn't overstate what it can do, and a person is one click away. Monitoring and escalation are part of the design, not an afterthought.
Giving immigration advice is regulated. Universities can advise their own students and prospective students under an exemption for educational institutions, through trained advisers following the IAA's Code of Standards. The assistant isn't one of them. It gives general published information, links to GOV.UK, and hands anything about a person's own circumstances to the university's international student advisers.
Sponsors must keep visa refusal rates below 5% and enrolment at 95% or more, and those using recruitment agents must commit to the Agent Quality Framework and record agent details on the CAS. The assistant never assesses visa eligibility or promises a CAS, gives every applicant the same published pre-arrival information, and records in the CRM when an enquirer says an agent is helping them.
For signatories, admissions must be fair, transparent and consistent. The assistant describes entry requirements and contextual offers only as published, never says what grades will be accepted for an individual, and refers qualification questions to admissions staff.
Many applicants are 17, so treat the chat as a service children will use: collect only what's needed, no profiling by default, and clear privacy information. Marketing emails after an enquiry need consent, recorded in the CRM. Chat logs get a retention period, and the contract stops providers training models on them.
Showing AWSAzuresovereign / on-prem services. Switch with the toggle; every diagram and table on this page follows it.
01Channels
02Intake
03Intelligence
04Orchestration
05Systems of record
06People
| Layer | AWS | Azure | Sovereign / on-prem |
|---|---|---|---|
| Intake: chat, email, portalOne assistant behind every channel, so every channel gives the same answer. | API Gateway, Amazon SES | API Management, Logic Apps connectors | Kong or your existing API gateway; your mail server |
| Reasoning and answersBoth clouds offer a choice of models, including Claude. On-prem and sovereign options run open-weight models. | Amazon Bedrock | Microsoft Foundry | Open-weight models served with vLLM on your own GPUs, or IONOS AI Model Hub |
| Approved content (retrieval)Only approved pages for the current cycle, each with an owner, an academic year and a review date. Old prospectuses and last year's pages stay out. | Bedrock Knowledge Bases | Foundry IQ, built on Azure AI Search | OpenSearch, or PostgreSQL with pgvector |
| Course facts and feesFacts that matter legally come from structured data and are quoted exactly, with the link. | Lambda tools calling the course catalogue API | Azure Functions tools calling the course catalogue API | Tools on Kubernetes calling the course catalogue API |
| Agent runtimeThe original Bedrock Agents closed to new customers on 30 July 2026; new builds use AgentCore. | Amazon Bedrock AgentCore | Foundry Agent Service | An open-source agent framework (e.g. LangGraph) on Kubernetes |
| Agent permissionsThe assistant's tools can book and log. They have no route to offers, applications or student records. | Amazon Verified Permissions, IAM | Entra ID app roles and API Management policies | Open Policy Agent, or Keycloak authorisation services |
| Translation (optional)Translated answers say the English page is the authoritative version and link to it. | Amazon Translate | Azure Translator in Foundry Tools | An open-weight model served with vLLM |
| WorkflowHandoffs, bookings and confirmations, with retries that never double-book. | AWS Step Functions | Logic Apps or Durable Functions | Temporal, or n8n |
| Events and messagingAmazon Pinpoint reached end of support on 30 October 2026; use AWS End User Messaging. | Amazon EventBridge, SQS; AWS End User Messaging for SMS | Event Grid, Service Bus; Azure Communication Services | Apache Kafka or RabbitMQ; your SMS provider |
| Link to the CRM and booking systemReuse the integration layer you have. Don't buy a new one for this. | API Gateway, plus your existing integration platform if you have one | API Management, plus your existing integration platform if you have one | Kong or your existing API gateway, plus your existing integration platform if you have one |
| Human handoffStaff pick up handoffs where they already work, with the conversation attached. | In the admissions team's existing CRM queue | In the admissions team's existing CRM queue | In the admissions team's existing CRM queue |
| GuardrailsDenied topics for offers, grade predictions and personal immigration advice, backed by the handoff rules in the workflow. | Bedrock Guardrails | Foundry guardrails (Azure AI Content Safety) | Open-source guardrails (e.g. NeMo Guardrails, Llama Guard) |
| Identity, keys, data protection | IAM Identity Center, KMS, Macie | Entra ID, Key Vault, Purview | Keycloak or your existing Active Directory; OpenBao or HashiCorp Vault; an HSM |
| Monitoring and auditLog every answer with the sources it used, so you can show what someone was told. | CloudWatch, CloudTrail | Azure Monitor, Log Analytics | Prometheus, Grafana, OpenTelemetry |
| UK data residencyIONOS AI Model Hub runs in German data centres: EU, not UK, residency. | eu-west-2 (London) | UK South / UK West | Your own UK data centre, or a UK or EU provider |
On a phone, the table shows the platform you pick. Sovereign / on-prem means open, portable components you can run in your own data centre or with a UK or European provider; IONOS is shown as one example, and others exist. What sovereign cloud means →
Many organisations keep core systems and sensitive data on their own servers. This is how the same design works across both.
Stays on-prem
The student records and admissions system and the course catalogue database often run on the university's own servers, and they stay there. The student CRM and the events system stay wherever they run today.
Uses cloud AI
The approved content index, the assistant and the guardrails run in a UK cloud region, or on the university's own GPUs with open-weight models. Only published content is indexed, so the index itself holds nothing confidential.
How they connect
Through the API layer, over a private link such as AWS Direct Connect or Azure ExpressRoute. The assistant reads the catalogue and writes enquiries and bookings; it has no connection to the admissions system at all.
If the link drops
The chat says it can't answer right now and offers the enquiry form and the relevant published pages. Enquiries queue and reach staff as they did before the assistant. Nothing is answered from a stale copy.
What each agent may do through its tools, what it may not, and where a person signs off. The limits are enforced by the platform, not the prompt.
Enquiries assistant
Where a person signs offAdmissions staff make every decision about an applicant, and only the university's trained advisers give immigration advice. The assistant's tools and data access are enforced by the platform's identity and policy controls, not by instructions in a prompt.
Content check
Where a person signs offA named content owner approves every page before it enters the index, and the web team publishes changes through the usual process.
The course catalogue is the single source of truth for course facts and fees. The assistant reads it through the API layer; web pages, the prospectus and the assistant all draw from the same data, so they can't drift apart.
Bookings and enquiries are events. If the CRM or the events system is slow or down, they wait safely on the queue. Every message carries an ID, so a retry never creates a duplicate enquiry or a double booking.
The assistant has no connection to the admissions system. That's a design choice, not a limitation: it can't reveal or imply an application outcome because it can't see one.
Inventory the content and its owners, measure enquiry volumes and repeat questions, agree the always-to-a-person topics, and check the catalogue API.
Gate · must be true to passContent owners named, handoff topics agreed with legal and the international advisers, DPIA started, baseline measured.
Staff-assist first: the assistant drafts email replies that staff check and send. Then public chat for postgraduate taught courses only, outside any peak period.
Gate · must be true to passAccuracy above the agreed level, every out-of-scope test handed off, and admissions and compliance sign-off.
Public chat for undergraduate and postgraduate enquiries, with booking and CRM logging, monitoring, support and a rollback plan.
Gate · must be true to passMonitoring, handoff cover, rollback plan and staff training in place, and not launched in Clearing.
Add languages for priority international markets, then support during Clearing with clear routes to a person.
Gate · must be true to passEach new language or season passes the same accuracy and out-of-scope tests.
| Activity | Director of admissions | Product owner | Solutions architectI can fill this | Technical PMI can fill this | EngineersI can fill this | Legal, compliance & DPO | SecurityI can fill this |
|---|---|---|---|---|---|---|---|
| Business case and benefits | Accountable | Responsible | Consulted | Consulted | Informed | Consulted | Informed |
| Handoff topics and scope | Accountable | Responsible | Consulted | Informed | Informed | Responsible | Informed |
| Target architecture | Informed | Consulted | Accountable and Responsible | Consulted | Consulted | Consulted | Consulted |
| DPIA and consumer law review | Consulted | Consulted | Consulted | Informed | Informed | Accountable and Responsible | Consulted |
| Build and integration | Informed | Consulted | Accountable | Responsible | Responsible | Informed | Consulted |
| Accuracy and out-of-scope testing | Consulted | Accountable | Responsible | Consulted | Responsible | Consulted | Informed |
| Go-live decision | Accountable | Responsible | Consulted | Responsible | Informed | Consulted | Consulted |
| Run, monitor and improve | Informed | Accountable | Consulted | Consulted | Responsible | Consulted | Consulted |
R ResponsibleA AccountableC ConsultedI Informed· not involved
Option A
If there's no architect on the programme, I'd own the design end to end: the approved content index, the catalogue and CRM integrations, the assistant's permissions, and the gates. I'd report to your programme board, and I'd make sure the line on offers and immigration advice is enforced by the platform, not left to a prompt.
Option B
If your partner or your own team already has an architect, I'd take on the retrieval, the agent tools and the CRM and booking integration under their lead, and give them a second senior opinion on the rest, especially security and data protection.
Goes wrong
Everything on the website goes into the index, including last year's fees and an old prospectus PDF.
How the design avoids it
Only approved pages for the current cycle, each with an owner and a review date. Anything out of date leaves the index automatically.
Goes wrong
Someone asks 'will I get in with BBC?' and the assistant gives a hopeful answer.
How the design avoids it
Offer and grade questions are denied topics, backed by handoff rules in the workflow and tested before every release.
Goes wrong
A visa answer is confident, specific and wrong for that person.
How the design avoids it
General published information and GOV.UK links only. Anything about someone's own circumstances goes to a trained adviser.
Goes wrong
The model paraphrases a fee and changes its meaning.
How the design avoids it
Fees and entry requirements come from the catalogue through a tool and are quoted exactly, with the link.
Goes wrong
It launches in Clearing week, with nobody free to take handoffs.
How the design avoids it
Launch outside peak periods, plan handoff cover first, and keep Clearing offers with people on the phone.
Changes already announced or under way that affect this design. More in the UK horizon scan.
Keep the logs of what the assistant told each person, and make the content owners' review process something you could show the OfS.
Give visa content effective dates, so the assistant gives today's applicants the rule that will apply when they graduate, and review it with the international advisers.
Keep pre-arrival information consistent and logged, so applicants arrive with the right expectations.
If fees change, change them once in the catalogue. Nothing about fees should live in a prompt.
Keep the answer logs, the handoff records and the scope decisions in a form you could show the ICO.
Good answers are specific. Vague answers to any of these are worth following up.
Whether you need someone to lead the design or to support the architect you already have, let's talk it through.