If you're a business thinking about making AI calls in Australia, you're stepping into a regulatory framework that's more complex than most business owners realise.
Multiple laws govern when you can call, who you can contact, what you must disclose, and how you handle data.
Here's What Applies to AI Calls in Australia
AI calling in Australia falls under the Telecommunications Act 1997, Do Not Call Register Act 2006, industry standards for calling hours and identification, plus the Privacy Act 1988. There are also state-level laws governing automated calls within certain jurisdictions, including the Surveillance Act 1997.
Let's break down what each one means for running AI calls in Australia.
The Five Laws You Can't Ignore
1. The Telecommunications Act 1997
This is the foundation. It establishes ACMA (Australian Communications and Media Authority) and sets out general requirements for telecommunications services.
What it means for you:
- ACMA oversees telecommunications compliance
- Enables subsidiary regulations that directly affect AI calling
- Provides the framework for consumer protection
- Creates the enforcement mechanisms
2. The Do Not Call Register Act 2006
This establishes Australia's national Do Not Call Register. Over 11 million numbers are registered (roughly 40% of Australian phone numbers).
What you must do:
- Check your call list against the Register before calling
- Remove any numbers found on the Register
- Re-check at least every 30 days
- Maintain records of this "washing" process
Exemptions exist, but they're narrow:
- Previous purchase within 18 months
- Enquiry within 3 months
- Must be related to that relationship
This article explains exactly how to integrate DNC checking into your AI calling workflow.
3. The Telecommunications (Telemarketing and Research Calls) Industry Standard 2017
Telemarketing and outbound cold calling is legal in Australia and can be a great communication channel for marketing your products when done correctly. However, telemarketing calls need to meet regulatory standards to ensure contacted parties are fully informed and have the ability to opt-out from fielding marketing calls on their personal phone. The Telecommunications (Telemarketing and Research Calls) Industry Standard 2017 sets detailed rules for how and when you can call, including strict guidelines on transparent disclosure.
Calling hours you must follow:
- Weekdays: 9am to 8pm (local time where the number is)
- Saturdays: 9am to 5pm
- Sundays and public holidays: Don't call
The Voxworks Advantage: Our platform automatically schedules outbound calls within permitted windows, ensuring you never accidentally ring a dinner table at 8:30 PM
Caller identification requirements:
- Provide your name and the business name you represent
- Provide a contact number for your business
- The number you display must actually accept incoming calls
The Voxworks Advantage: Our platform lets you set an inbound call script for numbers you use to conduct outbound calls, with instant contact recognition based on phone number lookup, ensuring the conversation can continue as normal when the contact returns a missed call.
Call conduct:
- State the purpose of your call immediately
- End the call right away if requested
- Remove the number from your list if requested
The Voxworks Advantage: Call scripts can be configured to recognise contacts requests to end a call at any point in the conversation.
5. The Privacy Act 1988
This governs how you handle personal information collected during calls.
What you must do:
- Collect information lawfully and fairly
- Only use information for stated purposes
- Allow individuals to access their information
- Store information securely
- Follow additional rules for overseas disclosure
If you're using offshore platforms for running AI calls in Australia, this is where you need to be careful. More on that here Data Sovereignty: Why Your AI Voice Data Should Stay on Australian Servers.
How These Laws Apply to Your AI Calls
You Will Need Some Form of Consent
For outbound marketing calls:
- Express or inferred consent to record is required
- Disclose the call is being recorded early on in the call
- Need to follow calling hours and identification rules
For debt collection:
- Additional regulations under ASIC and ACCC guidelines apply
- Can't harass or coerce
- Must identify yourself and purpose immediately
Do Not Call Register: How It Works
Your AI calling system must:
- Integrate with DNC Register checking
- Automatically exclude registered numbers
- Maintain wash records proving compliance
- Update lists at least every 30 days
Exemptions exist for existing customer relationships, charities, educational institutions, political parties, and government bodies, but they're narrower than most people think.
Disclosure: What You Must Tell People
Your AI should disclose:
- That it's an AI/automated system. Many businesses typically use the terminology 'digital assistant'
- The business name making the call
- The purpose of the call
- How to speak to a human if preferred
- How to opt out of future calls
While not every regulation explicitly requires all of these, disclosure is:
- Required in specific circumstances
- Best practice for maintaining trust
Recording Calls: State-by-State Requirements
Call recording consent in Australia varies by state. In most states you need to tell the other party the call is being required. However, even in states where this requirement is looser, if the call recipient is travelling in another state, a higher standard may apply.
What your AI must do:
- Disclose that recording is occurring
- Store recordings securely
If you're making AI calls in Australia, design call scripts for the strictest standard (all-party consent) rather than a dynamic approach based on the contact location.
The Penalties for Getting This Wrong
Do Not Call Register and Privacy Act violations carry significant penalties. Beyond the fines, there's potential reputational damage to consider. If you require clarification on the regulations that apply to your business, seek advice your relevant legal expert for specific details on potential impacts.
Building a Compliant AI Calling System
Technical Requirements
Consent management:
- Database tracking consent status for every contact
- Integration with registration and opt-out systems
- Audit trail of how you acquired consent
DNC integration:
- Automated Register checking before calls
- Real-time exclusion of registered numbers
- Documentation of your wash process
Calling hour enforcement:
- Timezone-aware scheduling
- Public holiday calendar integration
- Automatic queue management
Recording compliance:
- Configurable by jurisdiction
- Disclosure scripts before recording starts
- Secure storage with access controls
Operational Requirements
Staff training:
- Understanding applicable regulations
- Escalation procedures for complaints
- Documentation requirements
Monitoring and audit:
- Regular compliance reviews
- Call sampling and quality assurance
- Documentation retention
Complaint handling:
- Clear process for receiving complaints
- Timely investigation and response
- Recording and trend analysis
How Voxworks Handles Compliance for AI Calls in Australia
We built Voxworks specifically for Australian requirements:
Do Not Call Register:
- Integrated DNC checking
- Automatic list washing
- Compliance documentation
Calling hours:
- Timezone-aware scheduling
- Public holiday recognition for each Australian state
- Configurable calling windows
Disclosure:
- Customisable disclosure scripts
- AI identification options
- Built-in opt-out mechanisms
Recording:
- Jurisdiction-aware consent collection
- Secure Australian-based storage
- Access controls and audit trails
Consent management:
- Contact status tracking
- Opt-out processing
- Compliance reporting
It's built into the platform because we understand what's required for AI calls in Australia. Notwithstanding our inbuilt safeguards, the obligation is on the caller to understand the rules in particular with regards to outbound calling.
Your AI Calls in Australia Must Meet Australian Standards
AI calls in Australia are subject to a comprehensive regulatory framework covering consent, timing, identification, data handling, and more.
Compliance requires:
- Understanding which regulations apply to your specific use case
- Implementing technical controls to enforce requirements
- Maintaining operational procedures and documentation
- Monitoring for regulatory changes
The penalties for non-compliance are material. But the requirements are completely achievable with proper planning and the right platform.
That's why we built Australian regulatory compliance into the Voxworks platform from day one.
Need AI calling that's compliant with Australian law? Voxworks is built for local requirements. Start your free trial at voxworks.ai.