Running ai calls in Australia for financial services? You're facing a specific compliance hurdle that most offshore AI voice platforms completely ignore.
ASIC Regulatory Guide 271 (RG 271) sets detailed requirements for how you handle customer complaints and disputes. When your AI answers the phone, it's not just handling queries—it's your first line of compliance. Mess this up, and you're looking at regulatory consequences.
What Is RG 271 and Why Should You Care?
Quick answer: RG 271 establishes standards for internal dispute resolution (IDR) in Australian financial services. If you're making ai calls in Australia to customers about financial products or services, these rules apply to you.
Here's what it covers:
What counts as a complaint:
- Any expression of dissatisfaction
- Related to your products or services
- Where the customer expects a response or resolution
Response timeframes you can't miss:
- Acknowledge within 24 hours (or 1 business day)
- Resolve standard complaints within 30 days
- Superannuation complaints: 45 days
- Some complaints get extended timeframes
What your IDR response must include:
- Clear, plain language (no jargon)
- Address every issue the customer raised
- Explain the reasoning behind your decision
- Information about external dispute resolution options
Why AI Makes This Tricky
Your AI voice agent is often the first point of contact. Think about it:
- Customer calls with an issue
- AI picks up and handles the conversation
- What the AI does next determines whether you're compliant
Common risk areas:
- AI doesn't recognize a complaint when it hears one
- No acknowledgment sent within 24 hours
- Complaint doesn't get escalated properly
- Documentation is incomplete
- Customer never hears about EDR options
Get it wrong, and you've violated RG 271 before a human even knows there's a problem.
How to Make Your AI Compliant
Step 1: Teach Your AI to Recognize Complaints
Your AI needs to pick up on these phrases:
- "I want to make a complaint"
- "I'm not happy with..."
- "This isn't right..."
- "I want to dispute..."
- "Your service was terrible"
Not all negative feedback is a complaint. Here's the difference:
- Customer frustrated during service → May not be a complaint
- Customer explicitly requests response/resolution → Definitely a complaint
What your AI should say:
"I understand you're unhappy with [specific issue]. Would you like me to lodge this as a formal complaint so we can investigate and respond to you properly?"
This confirms intent and creates a clear record.
Step 2: Acknowledge Within 24 Hours
The 24-hour rule is non-negotiable. Here's how AI handles it:
Immediate verbal acknowledgment:
"I've recorded your complaint about [issue]. You'll receive written acknowledgment by email within 24 hours, along with a reference number and information about our complaint process."
What happens behind the scenes:
- AI logs the complaint in your complaints management system
- Automated acknowledgment email triggers
- Customer gets reference number
- Clock starts on resolution timeframe
Step 3: Escalate Appropriately
AI can't resolve complaints. It doesn't have the authority. What it must do:
- Route the complaint to your complaints team
- Provide full context for seamless handoff
- Set clear expectations with the customer
What your AI should say:
"Your complaint has been logged and will be handled by our complaints team. They'll contact you within [timeframe] to discuss this further. Is there anything else you need right now?"
Step 4: Document Everything
RG 271 requires you to capture:
- Date and time of complaint
- Customer details
- Nature of the complaint
- Products/services involved
- Desired outcome (if the customer mentions it)
- Initial response provided
What AI documentation looks like:
- Full call transcript
- Classification tags (complaint type, product, severity)
- Escalation record
- Integration with your complaints register
This creates an audit trail you can actually use.
Step 5: Provide EDR Information
If the complaint isn't resolved to the customer's satisfaction, they need to know about external dispute resolution.
When to mention it:
- At the conclusion of your IDR process
- If the customer asks about their options
What your AI can say:
"If you're not satisfied with how we handle your complaint, you can escalate to the Australian Financial Complaints Authority (AFCA). Would you like their contact details?"
What Your AI Should Never Do
Let's be clear about boundaries:
Don't make determinations:
- AI doesn't decide complaint outcomes
- AI doesn't assess fault
- AI doesn't offer compensation
Don't provide financial advice:
- AI doesn't recommend products
- AI doesn't give financial guidance
- AI doesn't interpret policies
Don't dismiss complaints:
- Every complaint must be logged
- You can't talk customers out of complaining
- AI provides a pathway, not a gatekeeper
If you're using ai calls in Australia for financial services, these limitations aren't optional—they're legal requirements.
When to Hand Off to a Human
Some situations need immediate human intervention:
Transfer right now:
- Customer explicitly requests a human
- High emotional distress
- Legal threats mentioned
- Complex situation beyond AI's scope
Schedule a callback:
- After the complaint is logged
- Within your specified timeframe
- With clear expectations set
This hybrid approach keeps you compliant while maximizing efficiency.
Testing Your AI for Compliance
Before you launch ai calls in Australia, test these scenarios:
Clear complaint expressions:
- "I want to make a complaint about my account"
- Direct, obvious complaints
Subtle complaint expressions:
- "I'm not sure this is right..."
- "Nobody's helped me with this..."
- Indirect complaints that still require action
Non-complaint negative feedback:
- "This is frustrating" (during active service)
- Not every negative comment is a formal complaint
Multiple issues in one call:
- Can your AI capture all of them?
- Does it acknowledge each issue?
Verification checklist:
- ✓ Complaint recognized correctly
- ✓ Acknowledgment provided
- ✓ Escalation happened
- ✓ Documentation complete
Common Mistakes to Avoid
Under-classification
What happens: AI doesn't recognize a complaint Result: No formal process triggered, acknowledgment missed, you've breached RG 271
Over-classification
What happens: General feedback treated as a complaint Result: Unnecessary process burden, customer confusion
Poor handoffs
What happens: AI doesn't provide enough context to the complaints team Result: Customer repeats their story, delays, frustration
How to fix it:
- When in doubt, escalate (conservative approach)
- Clear scripting for borderline cases
- Rich documentation for seamless handoffs
- Regular calibration and testing
How This Connects to Broader Compliance
RG 271 isn't the only regulation you need to worry about. If you're running ai calls in Australia for financial services, you're also dealing with:
Australia's Telecommunications Laws and AI Calls—covering calling hours, disclosure, and consent requirements.
You'll also want to check The Do Not Call Register: How to Scrub Your AI Dial Lists to avoid telemarketing violations.
And if you're concerned about data handling, Data Sovereignty: Why Your AI Voice Data Should Stay on Australian Servers explains why local hosting matters for compliance.
Why Voxworks Builds This In
We've designed our platform with Australian financial services compliance in mind:
Complaint detection:
- Pre-trained on Australian complaint language
- Configurable thresholds
- Human review for edge cases
Automatic acknowledgment:
- 24-hour compliance built in
- Email and SMS options
- Reference number generation
Escalation workflows:
- Integration with your complaints system
- Rich context transfer
- Timing enforcement
Complete documentation:
- Full transcripts retained
- Classification logged
- Audit trail for ASIC
This isn't bolted on as an afterthought. It's built in from the start because we understand Australian requirements.
Your AI Calls in Australia Need to Meet Australian Standards
Here's the bottom line: ai calls in Australia for financial services must comply with RG 271. That means your AI needs to recognize complaints, acknowledge them within 24 hours, escalate appropriately, and document everything.
The benefit? Consistent compliance at scale. Your complaints team gets properly logged complaints with full context. Customers get professional handling. And you demonstrate the standards ASIC expects.
Don't leave compliance to chance. Build it into your AI from day one.
Need compliant AI for financial services? Voxworks is built for Australian regulations. Start your free trial at voxworks.ai.