-
-
Login status
Hello, Login to start. Not a member? Join Today!-
2015 Compliance Attestations due in
Topics
- Advertising
- Backgrounders
- Billing
- Code Enforcement
- Communications Compliance Ltd
- Complaint Handling
- Compliance Attestation
- Compliance Plan
- Credit & Debt Management
- Critical Information Summary
- Criticising the Code
- Customer Contracts
- Customer Information Compliance Statement
- Customer Service
- Customer Transfers
- External Compliance Assessment
- Financial Hardship
- International Roaming
- Sales
- Selling a Telco Business
- Staff Training
- TIO
- Unfair Contract Terms
- Unit Pricing Rules
- Usage Notifications
Links
Author Archives: Peter Moon
Cooper Mills releases Financial Hardship Template & Guide
ACMA has warned of an “early focus on compliance with the financial hardship provisions of the new Telecommunications Consumer Protection Code.” Cooper Mills has responded with a template for an updated Financial Hardship Policy, with Guidance Notes.
Critical Information Summary: Optus gets it wrong
Optus has misunderstood the Critical Information Summary requirements of the TCP Code, showing how easy it is to slip up under the new law. The issue relates to disclosure of ‘mandatory goods included in the offer’.
Posted in Critical Information Summary
Tagged CIS, Critical Information Summary, Optus
Leave a comment
Critical Information Summary: ACMA takes literal approach
ACMA is taking a literal approach to Critical Information Summary requirements, judging by some recent comments. Specifically, if a plan doesn’t include any hardware, you need to say that it doesn’t include any hardware. Even if it is called a … Continue reading
ACMA on CIS enforcement blitz
We’re seeing a high level of activity by the TCP Code enforcement team at the Australian Communications and Media Authority. Within a couple of days after it became mandatory for a telco to produce and publish a ‘Critical Information Summary’ … Continue reading
Posted in Code Enforcement, Critical Information Summary
Tagged ACMA, audit, CIS, Critical Information Summary, enforcement
Leave a comment
TCP Code clause 4.1.3(f) Compliance Guide released
Telcos are now starting to realise how much detail there is in the TCP Code. For instance, clause 4.1.3(f) requires telcos to publish website information about the warranties that apply to any hardware they supply, like handsets and modems. That … Continue reading
Posted in Backgrounders, Customer Information Compliance Statement
Tagged CICS, hardware, warranty, Website
Leave a comment
Compliance Attestation: Cross-referencing mistake solved
A cross-referencing mistake in the 2012 Telecommunications Consumer Protections Code has confused some readers about what is required in a Compliance Attestation under the Code. Let’s clear up the confusion. According to the definitions section of the Code: Compliance Attestation … Continue reading
Posted in Compliance Attestation, Criticising the Code
Tagged Compliance Attestation
Leave a comment
Cooper Mills releases Critical Information Summary Template – only $10 for Members until 1 April
Clause 4.1 of the Telecommunications Consumer Protections Code requires a telco to provide potential customers with a summary of each ‘offer’ the telco has in the market. This summary of offer must be called a ‘Critical Information Summary’. Cooper Mills … Continue reading
Compliance Attestation: Who will file yours?
TCP Code Compliance Attestations are no longer a distant prospect. By 1 April 2013 and no more than once a year after, someone from each telco is going to have to sit in front of a computer, tap in a … Continue reading
Complaint Handling: Get with the program
A moment ago, we were happily reading through random Critical Information Summaries on the web (as you do) and, almost at the end of one that looked pretty good, struck the paragraph above. Read on to find out why a … Continue reading
Complaints Analysis: Telcos should now have two QCAs completed
The TCP Code requires: Suppliers must classify and analyse complaints at least every 3 months to identify recurring problems and issues including areas of non‐compliance with this Code. Last Friday marked six months since the TCP Code commenced, so …
