The short answer: grade vendors on eight criteria, then pilot two
Choosing an AI agent for student recruitment in Canada comes down to a fixed grid of eight criteria, scored the same way for every vendor, followed by a thirty-day pilot of the two best on your own content. Canadian institutions add two constraints that a generic checklist misses: privacy obligations that differ by province, and a bilingual applicant base in many regions.
This guide is for recruitment, admissions and communications teams at Canadian universities, colleges and private career institutions. It sets out the grid, a weighted scoring table, red flags, a pilot protocol with test questions and the privacy context. For background on what these agents do, read the guide to AI chatbots for student recruitment. For a longer list of questions to put in writing, use the chatbot RFP checklist for higher education.
Why Canada changes the weighting
Admissions in Canada is not one system. Ontario universities receive many undergraduate applications through OUAC, while other provinces use their own application services or apply directly to the institution. Colleges, polytechnics and private career schools have separate routes again. An agent that assumes a single national process will mislead someone.
Two consequences follow. First, grounding matters more than usual: the agent must answer from your published requirements, by province of study and by applicant type, and say so when a question falls outside them. Second, the distinction between domestic, out-of-province and international applicants affects deadlines and fees, so the agent should ask early which one applies and route accordingly.
Criterion one and two: grounded answers, and a clean path to a person
Grounding. The agent should answer only from content you approve, show the source page and decline to guess. Ask each vendor to run on your site, not a sample. Try one question your pages answer, one they do not and one that invites a promise, such as "Will I get an entrance scholarship with a 90 average?" A graceful refusal is a feature.
Qualification and handoff. The agent asks a few natural questions, such as program, level, domestic or international status and start term, then routes the person to the right team with a summary. Decide the triggers beforehand: a request for a person, a complaint, an accessibility need, a financial concern, a welfare disclosure. Then ask what happens outside office hours, when nobody can take over.
Criterion three: integrations, shown live
Ask each vendor to demonstrate how a conversation reaches your CRM and how a campus visit, information session or advising appointment is booked on a real calendar. Do not accept descriptions. Give every vendor the same brief: your CRM, your booking tool and your consent practices. Ask which fields are written, how duplicates are handled and who is alerted if a write fails.
Criteria four to eight in practice
Privacy and hosting. Ask where personal information is stored and processed, who the sub-processors are, whether your content and conversations are used to train models and what the retention settings are. Many Canadian institutions prefer, or are required by policy, to know whether data leaves Canada. Ask for the answer in writing rather than assuming.
Bilingual and after-hours. If you recruit in French and English, test both with real questions, including ones with regional vocabulary. Check that the French is natural, not literal. For international recruitment, test the languages of your priority markets and the time zones that follow.
Review and analytics. Staff should read transcripts, see unanswered questions and find content gaps.
Channels. Begin on the website. Treat messaging apps as a separate decision with their own consent review.
Pilot, cost, exit. Ask for a time-boxed pilot, an itemized view of what the total cost includes and a written answer on exporting data.
The scoring table
Score each criterion from 0 to 5 and multiply by the weight. These weights are a starting suggestion and shift the privacy and bilingual criteria upward compared with a generic grid.
| Criterion | Suggested weight | What a top score looks like |
|---|---|---|
| Grounding, sources, refusal | 20% | Cited answers by applicant type and province, graceful gaps |
| Qualification and handoff | 12% | Clear triggers, summary to the team, after-hours rule |
| CRM and calendar integration | 13% | Demonstrated on your systems |
| Privacy, hosting, no training on your data | 18% | Hosting location in writing, sub-processors listed |
| Bilingual and multilingual | 10% | Natural French and English, tested on real questions |
| Review and analytics | 10% | Transcripts, unanswered questions, content gaps |
| Pilot and cost transparency | 10% | Written pilot plan, itemized total cost |
| Portability and exit | 7% | Export of conversations and configuration |
Score with at least three people from different teams. Treat a failure on privacy as disqualifying, whatever the total.
Red flags
Stop the process, or require a fix in writing, when:
- the vendor will not run the agent on your content before you commit;
- answers show no source and the agent never says it does not know;
- it predicts admission, scholarship or visa outcomes;
- integrations are described but never demonstrated;
- hosting location and sub-processors cannot be stated;
- your content or conversations may train models;
- the French output is clearly machine-literal when you need a bilingual service;
- there is no pilot, no export right and no exit clause.
Privacy context: PIPEDA, Quebec and provincial rules
Federal privacy law for the private sector is PIPEDA, but it is not the whole picture. Public universities are often covered by provincial public-sector or freedom-of-information and privacy statutes instead, and some provinces have private-sector laws of their own. Quebec's Law 25 modernized its regime, and the Commission d'accès à l'information is the regulator to know if you recruit there. Your privacy office or counsel should confirm which regime applies to your institution and what it requires for a vendor, including any assessment before deployment.
On the sector side, Universities Canada is a useful reference point for how institutions describe themselves, but provincial authorities, not a national body, oversee quality and program approval. Whatever the agent says about programs, fees and outcomes must match your published information.
Tell applicants, at the start, that they are speaking with an automated assistant.
A thirty-day pilot with test questions
Pick one faculty or program family. Write down what success means first, for example fewer unanswered overnight inquiries or cleaner records in your CRM.
- Week one. Load approved content, set handoff triggers and connect CRM and calendar.
- Week two. Staff test with the questions below and fix gaps.
- Weeks three and four. Go live on selected pages, read transcripts weekly, log handoffs, bookings and unanswered questions.
Questions to include, in English and French where relevant:
- "What are the admission requirements for an Ontario high school student?" (answer from content)
- "I studied in another province. How is my transcript assessed?" (answer or hand off)
- "Is there a co-op option, and does it affect tuition?" (must match your pages)
- "Can I book a virtual information session this week?" (booking flow)
- "Can you guarantee a spot?" (must refuse)
- "Where is my data stored?" (a clear, accurate answer)
- A question asked at midnight from another time zone.
Finish by scoring the pilot on the same grid. The comparison of AI chatbots for higher education and the comparison of AI agents for student recruitment can help you assemble the 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. Score it as you would any other vendor.


