Skip to content

Compliance and data

Every call recorded, scored and ready for audit.

Education providers answer to regulators, and so does every conversation our agent has on your behalf. This page sets out what happens on every call, the Australian rules we build campaigns around, and how we handle your data.

For UK and New Zealand providers we build to the local equivalents and confirm them with you at kickoff.

On every call

What happens in every conversation

  • AI and recording disclosure

    At the start of every call the agent says it is an AI agent and that the call is recorded. We apply this on every call so it meets the strictest all-party consent rules in any state.

  • Recorded, transcribed and scored

    Every call is recorded, transcribed and scored against the compliance rules for your market. You get a full audit trail.

  • Vulnerability escalation

    The agent is tested against vulnerability, domestic violence, mental health and aggressive caller scenarios, with escalation to a person built in.

  • Opt-outs the same day

    Do Not Call and Do Not Email requests made during any conversation are processed the same day and written back to your CRM and suppression list.

  • Unqualified leads removed

    Leads that are not a fit get tagged with a reason and taken out of the campaign, so nobody is called again without cause.

  • Your approved course information

    The agent answers from the course information you approve. Questions it cannot answer go to your team.

Australian rules

The rules we build each campaign around

This is a plain summary, not legal advice. Your own compliance team stays responsible for your obligations, and we set campaigns up to match them.

Standards for RTOs (ASQA)

What it covers

Marketing and pre-enrolment information must be accurate, and RTOs must not guarantee outcomes they do not control, such as completion or employment.

How campaigns handle it

The agent answers from your approved course information and every call is scored against your marketing and information rules.

ESOS Act and National Code

What it covers

Providers recruiting international students must give accurate information and must not make misleading claims about courses or outcomes.

How campaigns handle it

For international student campaigns, the agent’s scripts and call scoring include your National Code obligations.

Privacy Act 1988 and the APPs

What it covers

Collection, use, storage and disclosure of personal information about prospective students.

How campaigns handle it

You stay the data controller. We act as your processor, encrypt data in transit and at rest, and keep recordings for the period your agreement sets.

Automated decisions (from 10 December 2026)

What it covers

Privacy policies must describe where a computer program uses personal information to make, or do something substantially and directly related to making, decisions that could significantly affect an individual’s rights or interests.

How campaigns handle it

The agent qualifies and routes enquiries. Enrolment decisions stay with your team. We document exactly what the agent does so your privacy officer can assess your disclosure.

Spam Act 2003

What it covers

Commercial SMS needs consent, must identify the sender and must carry a working unsubscribe.

How campaigns handle it

SMS runs only to leads who enquired with you, and opt-outs by text or voice apply across every channel the same day.

Do Not Call Register Act 2006 and the Telemarketing Industry Standard

What it covers

Telemarketing calls are limited to 9am to 8pm on weekdays and 9am to 5pm on Saturdays, with no calls on Sundays or national public holidays such as Christmas Day, Good Friday and Anzac Day. The hours apply whether or not a number is on the Do Not Call Register.

How campaigns handle it

Calling windows for each campaign are set to these hours in the recipient’s local time zone.

Your data

You control it. We process it.

You are the data controller for lead and call data. We process it only for the purposes you instruct and the services agreement allows. We never use one client’s data to train models we sell to another client.

Infrastructure
Amazon Web Services and Google Cloud
Regions
Australia, the US or the EU, set per client
Encryption
In transit and at rest, with least-privilege access
Retention
Set in your agreement, matched to your audit window
Sub-processors
A full list naming each provider and region is available on request. Read the privacy policy for the detail.

FAQ

Compliance questions

Does the agent tell people it is an AI?

Yes. At the start of every call it identifies itself as an AI agent and says the call is recorded.

Who owns the call recordings and lead data?

You do. You are the data controller and we process the data on your instructions under the services agreement. At the end of an engagement we return or delete it as you direct.

Where is the data stored?

On Amazon Web Services and Google Cloud, in Australia, the United States or the European Union depending on the client and workload. A sub-processor list naming each provider and region is available on request.

How long are recordings kept?

For the period set in your services agreement, usually matched to your own audit obligations. ASQA and TEQSA audit windows can run to seven years.

Can we review individual calls?

Yes. Every call has a recording, a transcript and a compliance score, so you can audit any conversation.

Does the agent make enrolment decisions?

No. It qualifies and routes enquiries. Your team decides who enrols.

Bring your compliance team to the demo.

We build the demo on your courses and your rules, and walk your team through how calls are scored.

Get a demo trained on your data