ChatGPT
Claude
Perplexity
Gemini
GrokStart from the job, not the product category
An AI admissions agent converses with a prospective student and answers in real time. A basic chatbot returns prepared answers to expected questions. CRM automation runs rules and sequences on records you already hold. They solve different problems, so compare them job by job.
Australian admissions teams serve two audiences with different rhythms: school leavers, whose questions cluster around ATAR release and offer rounds, and international students, who write from other time zones at any hour. An agent answers the question that arrives at 2am Sydney time. Automation handles the structured follow-up once the enquiry is a record.
This guide sets out a decision matrix, suggests who owns each tool and covers the Australian privacy and messaging rules. It extends our pieces on AI agents from first contact to CRM and the CRM comparison for higher education.
Definitions
- FAQ chatbot. Follows a script or matches canned answers. Predictable, brittle when a question is phrased in an unexpected way.
- AI admissions agent. Understands free-text questions, answers from content the institution has published, asks qualifying questions, offers a call or open day and hands over to a staff member. See the glossary of admissions AI agents.
- CRM automation. Triggers actions from CRM data: a status change sends a message, creates a task or assigns an adviser. It acts on what is known and does not converse.
The agent works at the moment of the question, automation on the record afterwards.
The decision matrix
| Job to be done | FAQ chatbot | AI admissions agent | CRM automation |
|---|---|---|---|
| Answer an entry-requirements question after hours | Only if anticipated | Yes, from published pages | No |
| Qualify an enquiry (course, intake, domestic or international) | Fixed questions | Conversational, adapts | Only from captured data |
| Book an open day or adviser call | Link to a form | Can offer times in the chat | Confirmations and reminders |
| Follow up after an open day | No | Not its role | Yes, its strength |
| Keep records consistent and deduplicated | No | Passes data to the CRM | Yes, with matching rules |
| Route an enquiry to the right adviser | Basic | Can summarise context | Yes, rules and queues |
| Handle a sensitive or complex case | No | Hands over to a person | Creates a task |
The agent is strongest before a record exists, automation after it does.
Who owns what
| Component | Natural owner | What they decide |
|---|---|---|
| Published answers the agent relies on | Admissions with marketing | Which pages and policies are the source of truth |
| Escalation rules to staff | Admissions manager | What triggers a handover, and the response time |
| CRM fields, statuses, sequences | Marketing or enrolment operations | Data model, triggers, sending rules |
| Consent and suppression | Privacy officer | Consent by channel, retention |
| Review of conversations | Admissions with the supplier | Gaps to fix, wrong answers to correct |
Without clear owners, the tools contradict each other: the agent promises a call no sequence schedules, or automation emails someone who just opted out in the chat.
When to choose one, and when to combine
- Repeat questions go unanswered after hours. Start with an agent on your website, grounded in published pages.
- Enquiries arrive but follow-up is slow. Start with CRM automation.
- Records are duplicated. Fix the data first, because both tools amplify it. See our guide to deduplicating student records across channels.
- Both gaps exist. Combine, with the agent capturing a qualified enquiry and the CRM owning what follows.
Write the boundary down. The agent collects, qualifies and books, then passes a summary and the consent record to the CRM. If both tools message the same applicant, you have built a collision.
Privacy and messaging: the Privacy Act and the Spam Act
Privacy Act 1988. The Office of the Australian Information Commissioner publishes guidance on the Privacy Act and the Australian Privacy Principles. Public universities are generally covered, and private providers may be depending on their circumstances, so confirm your status. The principles that matter here are collection limited to what is needed, notice about how data is used and rules on disclosing personal information overseas. That last point matters if an AI agent or CRM is hosted outside Australia.
Spam Act 2003. Commercial electronic messages, including email and SMS, require consent, identification of the sender and a working unsubscribe. The Australian Communications and Media Authority explains this on its website. Automation sequences are where this bites: consent should be recorded per channel, with date and source.
Do Not Call Register. Telemarketing calls are subject to separate rules; check how they apply to outbound calls from your team.
For both tools. Tell people they are speaking with AI, set a transcript retention period and make suppression work across systems. The agent routes and informs; admission decisions stay with staff and published criteria, which for many courses involve TEQSA-regulated standards and, for school leavers, state tertiary admissions centres.
Australian context: ATAR, offer rounds and international students
School-leaver traffic spikes around ATAR release and offer rounds, when families compare courses across institutions. An agent can absorb those peaks. For international students, the agent also covers time-zone gaps. Questions about visas should point to official Department of Home Affairs sources; the agent must not promise outcomes. Note that agents and education agents are different things: an AI agent answers enquiries, while an education agent is a person or company that recruits students and carries its own obligations.
What to ask a supplier
- Which sources does the agent answer from, and what happens when it has none?
- How does it hand over to a person, and what does the adviser see?
- Where is data hosted, and is it used to train models?
- Which CRM objects does it read or write? Ask for it in writing.
- How do consent and unsubscribes pass between the agent and the CRM?
- Who reviews transcripts, and how often?
Measure your own baseline first: after-hours response time, follow-up speed, duplicate records. No public source provides a dependable benchmark for your institution.
Where Skolbot fits
Skolbot Chat is an AI agent installed on the institution's website. It answers from published content, qualifies the enquiry, offers an appointment or open day and passes the conversation to your team and CRM. It supports advisers rather than replacing them. Sequences and reporting stay in your CRM; how the connector works with a specific CRM is confirmed during scoping. For the wider picture, read our guide to recruiting more students.
