A grid first, a pilot second, and data protection as a hard gate
To choose an AI agent for student recruitment in Ireland, score every vendor on the same eight criteria, treat GDPR compliance as a pass-or-fail gate rather than a weighted line, and then pilot the top two on your own content for thirty days. Irish institutions work inside EU law, so questions about hosting, sub-processors and transparency are not optional extras.
This guide is for admissions, marketing and data protection staff at universities, technological universities, institutes and private colleges in Ireland. It covers the grid, a scoring table, red flags, a pilot and the regulatory context. If you want the fundamentals first, read the guide to AI chatbots for student recruitment. To turn the grid into written questions for suppliers, use the chatbot RFP checklist for higher education.
Gate one: data protection, before any scoring
Before you weigh features, ask each vendor for written answers on five points: where data is hosted, whether it stays within the EU or EEA, who the sub-processors are, whether your content and conversations are used to train any model and what retention settings you control. Ask for the data processing agreement at this stage, not at signature.
If a vendor cannot answer in writing, it does not proceed. This is not about preference. As a controller you carry the responsibility under the GDPR, including for what your supplier does on your behalf. Ask too how the agent tells applicants they are talking to an automated assistant, which is good practice now and is in line with the transparency direction of EU rules on AI.
Then score the other seven criteria
Grounded answers. The agent should answer from content you approve, show its source and admit when it does not know. Ask for a live test on your own site. Try a question your pages answer, one they do not and one that invites a promise: "Is 500 points enough for this course?" The correct behaviour is to point to published CAO points and entry requirements, which change from year to year, without predicting an offer.
Qualification and handoff. A few natural questions on level, course interest, school leaver, mature or international status, then a handoff with a summary. Agree triggers beforehand: a request for a person, a complaint, a disability or access need, a welfare disclosure. Ask what happens at night or on weekends.
Integrations. Ask the vendor to demonstrate, on a call, how a conversation reaches your CRM and how an open day or appointment reaches your calendar. Provide the same brief to everyone, and ask which fields are written and how failures are reported.
Languages and hours. Irish-language content and international languages both matter in some institutions. Test the ones you need, plus a late-night question.
Review and analytics. Staff must be able to read transcripts, see unanswered questions and fix content gaps.
Channels. Start with the website. Treat WhatsApp as a separate decision with its own consent and privacy review.
Pilot, cost and exit. Ask for a time-boxed pilot, an itemised total cost and a written export and exit route.
The scoring table
Because data protection is a gate, the remaining weights add up to 100 across seven criteria. They are a suggestion; agree yours before demos.
| Criterion | Suggested weight | What a top score looks like |
|---|---|---|
| Grounded answers, sources, refusal | 25% | Live test on your site, visible sources, clean refusals |
| Qualification and handoff | 15% | Defined triggers, summary delivered, out-of-hours rule |
| CRM and calendar integration | 15% | Demonstrated on your systems |
| Languages and after-hours | 10% | Tested in the languages you need |
| Review and analytics | 15% | Transcripts, unanswered questions, content gaps |
| Pilot and cost transparency | 12% | Written pilot plan, itemised total cost |
| Portability and exit | 8% | Export of conversations and configuration |
| Gate: data protection and transparency | Pass or fail | EU hosting stated, DPA supplied, no training on your data |
Have scorers from admissions, IT and your data protection office work separately, then compare. Large gaps show where to ask again.
Red flags
Step back if you see any of the following:
- the vendor will not run the agent on your content before you sign;
- answers look confident but never show a source or an "I don't know";
- the agent tells applicants whether they will get an offer;
- integrations are described but not demonstrated;
- the hosting location or sub-processors cannot be stated in writing;
- your content or conversations may train models;
- no pilot, no export right and no exit clause;
- a price linked to a measure nobody can explain.
Ireland's regulatory context
The Data Protection Commission is the supervisory authority for the GDPR and the Data Protection Act 2018. For an agent, that means a lawful basis for processing, a privacy notice reachable from the chat, a processing agreement with the supplier, clear retention rules and a route for applicants to exercise their rights. If conversations might include data about health or disability, take specific advice.
On the education side, QQI oversees quality assurance and the qualifications framework, and the HEA funds and oversees the public higher education sector. What the agent says about programmes, awards and outcomes must match your published information. Most school leavers apply through the CAO, so the agent supports the stages before and after that application: course questions, open days, points explanations and next steps. It does not take part in CAO decisions.
Keep one calendar point in mind. Enquiries peak around open days and the CAO deadlines, and again once results are released. Ask vendors how quickly you can update content when the information changes, such as a revised points figure.
A thirty-day pilot with test questions
Choose one school or faculty. State the measure of success first, for example fewer overnight enquiries left unanswered and tidier CRM records.
- Week one. Load approved content, set handoff triggers and connect CRM and calendar.
- Week two. Advisers test with the questions below. Fix the gaps they find.
- Weeks three and four. Go live on selected pages. Read transcripts weekly and log handoffs, bookings and unanswered questions.
Test questions:
- "What were the points for this course last year, and will they be the same?" (state the published figure, no prediction)
- "I'm a mature student without the Leaving Cert. What are my options?" (answer or hand off)
- "I did a PLC course. Can I progress to this degree?" (answer from content)
- "Can I bring my parents to the open day?" (booking flow)
- "Can you guarantee me a place?" (must refuse)
- "Where is my data stored, and is it used to train AI?" (a precise, accurate answer)
- A question in a priority international language, sent on Sunday at midnight.
Score the pilot with the same grid. The comparison of AI chatbots for higher education and the comparison of AI agents for student recruitment can help build your shortlist.
For reference, Skolbot Chat is a website agent that answers from your institution's own content, qualifies applicants, books open days and appointments and pushes the record to your CRM. WhatsApp is an optional module. Put it through the same gate and grid as any supplier.


