<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>CSP Central &#187; sfoa</title>
	<atom:link href="http://cspcentral.com.au/tag/sfoa/feed/" rel="self" type="application/rss+xml" />
	<link>http://cspcentral.com.au</link>
	<description>Australia&#039;s ISP and Telco Law Site</description>
	<lastBuildDate>Sun, 31 Jan 2010 23:48:02 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0</generator>
		<item>
		<title>Optus toughens up mobile contract</title>
		<link>http://cspcentral.com.au/2009/07/optus-toughens-up-mobile-contract/</link>
		<comments>http://cspcentral.com.au/2009/07/optus-toughens-up-mobile-contract/#comments</comments>
		<pubDate>Wed, 29 Jul 2009 07:24:17 +0000</pubDate>
		<dc:creator>Peter Moon</dc:creator>
				<category><![CDATA[New laws]]></category>
		<category><![CDATA[Trade Practices Act]]></category>
		<category><![CDATA[consumer]]></category>
		<category><![CDATA[optus]]></category>
		<category><![CDATA[sfoa]]></category>
		<category><![CDATA[unfairness]]></category>

		<guid isPermaLink="false">http://cspcentral.com.au/?p=2649</guid>
		<description><![CDATA[Last December Optus incurred customer wrath, effectively torpedoing mobile access to cheap international VoIP services by charging them at international rates.  At the time, Optus insisted that: International calls within the meaning of your Optus Mobile Standard Form of Agreement for all Timeless and Cap plans includes calls that re-route or divert to international numbers. CSP Central [...]]]></description>
			<content:encoded><![CDATA[<p><img class="alignleft size-full wp-image-2648" style="margin-bottom: 20px; margin-right: 20px;" title="optus-5a" src="http://cspcentral.com.au/wp-content/uploads/2009/07/optus-5a.jpg" alt="optus-5a" width="141" height="305" /></p>
<h4>Last December Optus incurred customer wrath, effectively torpedoing mobile access to cheap international VoIP services by charging them at international rates. </h4>
<p>At the time, Optus insisted that:</p>
<blockquote>
<p style="text-align: left; padding-left: 120px;">International calls within the meaning of your Optus Mobile Standard Form of Agreement for all Timeless and Cap plans includes calls that re-route or divert to international numbers.</p>
</blockquote>
<p><a href="http://cspcentral.com.au/2008/12/dear-optus-please-show-us-where/" target="_blank">CSP Central asked Optus</a> to tell us where the SFoA said that.  We couldn&#8217;t be sure &#8211; because the document is a confused mish-mash &#8211; but as far as we could tell it said no such thing.</p>
<p>Apparently Optus didn&#8217;t feel too sure of its grounds, either.  So it has bolted on a powerful, unbalanced  new contract term that is sure to attract the interest of consumer regulators who have unfair contract terms legislation in their armory.  Today, that&#8217;s only Victoria.  On 1 January 2010, it will be every Australian State and Territory, and the ACCC.</p>
<p><span id="more-2649"></span><br />
<strong>The new Optus contract term</strong></p>
<p>The following little gem has been added to Optus&#8217; standard terms:</p>
<blockquote><p>5.2A  <em>Blocking Calls<br />
</em>Effective 12 August 2009, we may block access to a number (other than an emergency service number) if we reasonably require this to be done for technical, operational or commercial reasons.</p></blockquote>
<p><strong>Seems pretty rude, to us</strong></p>
<p>It&#8217;s the &#8216;commercial reasons&#8217; that trouble us most. </p>
<p>It&#8217;s a &#8216;commercial reason&#8217; to block a particular number that it relates to a service that competes with Optus. </p>
<p>It&#8217;s a &#8216;commercial reason&#8217; to block access because the number represents a call type that is unprofitable for Optus.</p>
<p>For many purposes, the word &#8216;commercial&#8217; can reasonably be translated as &#8216;money making&#8217;.  That&#8217;s not a cheap shot.  &#8216;Commercial real estate&#8217; is real estate used for money making purposes.  &#8216;Commercial loans&#8217; are financial arrangements made to facilitate money making activities.</p>
<p>So substitute that for &#8216;commercial&#8217; in Optus&#8217; new term and you get:</p>
<blockquote><p>5.2A  <em>Blocking Calls<br />
</em>Effective 12 August 2009, we may block access to a number &#8230; if we reasonably require this to be done for &#8230; money making reasons.</p></blockquote>
<p>It&#8217;s a pretty unbalanced and unreasonable power to have, unless Optus can explain what legitimate interest it is necessary to protect.</p>
<p><strong>Unbalanced and unreasonable equals illegal</strong></p>
<p>Under the <a href="http://cspcentral.com.au/2009/02/new-consumer-law-will-punch-holes-in-isp-telco-contracts/" target="_blank">new national unfair contracts law</a>, due to take effect on 1 January 2010, a term in a standard form contract that is (a) seriously unbalanced and (b) not reasonably necessary to protect a legitimate interest is void.  And the onus of showing the legitimate interest will lie on the party that benefits from it.</p>
<p>Back in January, we were asking <em>Dear Optus, please show us where</em> the supposed definition of international calls could be found.  Now, we&#8217;re asking <em>What legitimate interest of Optus justifies a power to block access to numbers for unspecified &#8216;commercial&#8217; reasons ?</em></p>
<p> </p>
<p><!--more--></p>
]]></content:encoded>
			<wfw:commentRss>http://cspcentral.com.au/2009/07/optus-toughens-up-mobile-contract/feed/</wfw:commentRss>
		<slash:comments>3</slash:comments>
		</item>
		<item>
		<title>SFoA backgrounder released</title>
		<link>http://cspcentral.com.au/2009/06/sfoa-backgrounder-released/</link>
		<comments>http://cspcentral.com.au/2009/06/sfoa-backgrounder-released/#comments</comments>
		<pubDate>Tue, 16 Jun 2009 02:23:37 +0000</pubDate>
		<dc:creator>Peter Moon</dc:creator>
				<category><![CDATA[Making sense of contracts]]></category>
		<category><![CDATA[Telecommunications Act]]></category>
		<category><![CDATA[contract]]></category>
		<category><![CDATA[sfoa]]></category>
		<category><![CDATA[standard form of agreement]]></category>

		<guid isPermaLink="false">http://cspcentral.com.au/?p=2479</guid>
		<description><![CDATA[Many CSPs are already using a &#8217;Standard Form of Agreement&#8217; but many others don&#8217;t &#8230; and don&#8217;t know what it&#8217;s all about. To demystify the topic, here&#8217;s a dowloadable SFoA backgrounder that overviews what they are and why they can improve CSP business processes, with the compliments of CSP Central and Logie-Smith Lanyon Lawyers You should also check [...]]]></description>
			<content:encoded><![CDATA[<h4><img class="size-full wp-image-2481 alignleft" style="margin-right: 10px;" title="contract-2" src="http://cspcentral.com.au/wp-content/uploads/2009/06/contract-2.jpg" alt="contract-2" width="160" height="124" />Many CSPs are already using a &#8217;Standard Form of Agreement&#8217; but many others don&#8217;t &#8230; and don&#8217;t know what it&#8217;s all about.</h4>
<p>To demystify the topic, here&#8217;s a dowloadable <a href="http://cspcentral.com.au/wp-content/uploads/2009/06/lsl-sfoa-guide.pdf">SFoA backgrounder</a> that overviews what they are and why they can improve CSP business processes, with the compliments of CSP Central and <a href="http://www.logielaw.com" target="_blank">Logie-Smith Lanyon Lawyers</a> <img src='http://cspcentral.com.au/wp-includes/images/smilies/icon_smile.gif' alt=':-)' class='wp-smiley' /> </p>
<p>You should also check out <a href="http://cspcentral.com.au/2008/08/managing-your-sfoa-summary-delivery/" target="_blank">this post</a> about complying with the SFoA Summary notification regime.</p>
]]></content:encoded>
			<wfw:commentRss>http://cspcentral.com.au/2009/06/sfoa-backgrounder-released/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Dear Optus, please show us where</title>
		<link>http://cspcentral.com.au/2008/12/dear-optus-please-show-us-where/</link>
		<comments>http://cspcentral.com.au/2008/12/dear-optus-please-show-us-where/#comments</comments>
		<pubDate>Wed, 31 Dec 2008 09:07:01 +0000</pubDate>
		<dc:creator>Peter Moon</dc:creator>
				<category><![CDATA[Trade Practices Act]]></category>
		<category><![CDATA[optus]]></category>
		<category><![CDATA[sfoa]]></category>

		<guid isPermaLink="false">http://cspcentral.com.au/?p=1342</guid>
		<description><![CDATA[To describe the Optus standard customer contract as a dog&#8217;s breakfast is unkind to dogs.  We know many canines that can at least keep their food inside the bowl. In this case, the clarity (or otherwise) of the contract documents matters more than most.  Optus is basing a controversial decision to deny Timeless or Cap [...]]]></description>
			<content:encoded><![CDATA[<h4><img class="alignleft size-full wp-image-1346" title="dog-food" src="http://cspcentral.com.au/wp-content/uploads/2008/12/dog-food.jpg" alt="dog-food" width="207" height="126" />To describe the Optus standard customer contract as a dog&#8217;s breakfast is unkind to dogs.  We know many canines that can at least keep their food inside the bowl.</h4>
<h4>In this case, the clarity (or otherwise) of the contract documents matters more than most.  Optus is basing a controversial <a href="http://apcmag.com/optus_threatens_customers_over_voip_calls.htm" target="_blank">decision to deny</a> Timeless or Cap plan customers access to cheap VoIP calls on a claim that its standard contract is quite clear about it.</h4>
<p> <span id="more-1342"></span><br />
<strong>No cheapie calls via our network, says Optus</strong></p>
<p>Until Christmas, Optus Timeless or Cap plan customers could use their mobile or landline accounts to dial the Australian number of a VoIP service provider.  Optus carried the call as far as the VoIP service, and the VoIP service provided an IP link to an international number at low cost.</p>
<p>Then came the SMS from hell:</p>
<p>IMPORTANT:  All calls that re-route or divert to international numbers are charged at 29c per min + 27c flagfall.  See optus.com.au/international for details.</p>
<p><strong>So we checked out optus.com.au/international for details </strong></p>
<p>Here&#8217;s how Optus <a href="http://personal.optus.com.au/web/ocaportal.portal?_nfpb=true&amp;_pageLabel=Template_woRHS&amp;FP=/personal/mobile/plansandratesmobile/internationalrates&amp;site=personal" target="_blank">explains its purported right</a> to block access to third party VoIP services that allow customers to use a local or national Optus call as the first stage of a cheap international connection:</p>
<blockquote><p>Optus is concerned that some customers may be being misinformed or misled by non-Optus related entities that are making claims that Optus customers can make free, or included cap value, international calls on their Optus Plan. This is not correct. International calls within the meaning of your Optus Mobile Standard Form of Agreement for all Timeless and Cap plans includes calls that re-route or divert to international numbers.</p>
<p>If you are on a Timeless or Cap plan, all calls made to any number that re-routes, diverts or switches to an international number is an international call and is charged from 29c per minute with a 27c flagfall. International calls are not included as part of your Timeless unlimited offer, and are excluded from some Cap plans included value. A complete copy of the Standard Form of Agreement can be viewed at www.optus.com.au/sfoa</p></blockquote>
<p>Now, that may be true.  But if that&#8217;s what the standard agreement says, we can&#8217;t locate it.  No surprise since the contract documents comprise a bevy of separate components.</p>
<p>We even googled the entire Optus site for the word &#8216;re-route&#8217; but could turn up just four results, none of them relevant.</p>
<p><strong>Optus had better hope its assertion is correct</strong></p>
<p>Even if Optus is right about &#8216;international calls within the meaning of your Optus Mobile Standard Form of Agreement for all Timeless and Cap plans&#8217;, there are questions about the conscionability of its exercise of power.</p>
<p>And if Optus is wrong  it has made a nasty mistake indeed. </p>
<p><strong>So give us a hand, Optus</strong></p>
<p>We&#8217;re not saying you&#8217;re wrong, but in the jumble you describe as &#8216;a complete copy of the Standard Form of Agreement&#8217;, the term that &#8216;If you are on a Timeless or Cap plan, all calls made to any number that re-routes, diverts or switches to an international number is an international call&#8217; isn&#8217;t easily found.</p>
<p>Where is it, please ?</p>
]]></content:encoded>
			<wfw:commentRss>http://cspcentral.com.au/2008/12/dear-optus-please-show-us-where/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Struggling to make sense of Dodo&#8217;s liability clauses</title>
		<link>http://cspcentral.com.au/2008/10/struggling-to-make-sense-of-dodos-liability-clauses/</link>
		<comments>http://cspcentral.com.au/2008/10/struggling-to-make-sense-of-dodos-liability-clauses/#comments</comments>
		<pubDate>Tue, 28 Oct 2008 12:35:44 +0000</pubDate>
		<dc:creator>Peter Moon</dc:creator>
				<category><![CDATA[How not to do it]]></category>
		<category><![CDATA[contract]]></category>
		<category><![CDATA[Dodo]]></category>
		<category><![CDATA[liability]]></category>
		<category><![CDATA[sfoa]]></category>

		<guid isPermaLink="false">http://cspcentral.com.au/wordpress/?p=714</guid>
		<description><![CDATA[Regular readers will know that T&#38;C clauses that (supposedly) limit CSP liability are very important.  If you don&#8217;t get them right, you can be exposed to unnecessary legal risk. Worse, you may commit a criminal offence under the Trade Practices Act &#8211; of misrepresenting peoples&#8217; legal rights. Dodo&#8217;s most recent brush with the law caused [...]]]></description>
			<content:encoded><![CDATA[<h4><img class="alignright size-thumbnail wp-image-721" title="wrong-way" src="http://cspcentral.com.au/wordpress/wp-content/uploads/2008/10/wrong-way.jpg" alt="" width="150" height="112" />Regular readers will know that T&amp;C clauses that (supposedly) limit CSP liability are very important.  If you don&#8217;t get them right, you can be exposed to unnecessary legal risk.</h4>
<h4>Worse, you may commit a criminal offence under the Trade Practices Act &#8211; of misrepresenting peoples&#8217; legal rights.</h4>
<p>Dodo&#8217;s <a href="http://cspcentral.com.au/wordpress/?p=695" target="_blank">most recent brush with the law</a> caused us to take a look at its ‘liability limitation&#8217; clause.  All we can say is ‘Wow !&#8217;  What planet&#8217;s legal system generated this weird stuff ?</p>
<p><span id="more-714"></span></p>
<p><strong>First, a refresher</strong></p>
<p>Before we go any further, let&#8217;s re-read <a href="http://cspcentral.com.au/wordpress/?p=590" target="_blank">an earlier article about liability limitation</a>.</p>
<p><strong>Next, take a look at Dodo&#8217;s clause</strong></p>
<blockquote><p>As Your service is provided to You for the primary purpose of personal use, We do not accept liability for losses that result from the use of Your service in connection with the conduct of a business.</p>
<p>We are liable to you for breach of contract or negligence.</p>
<p>However, We will accept that liability if it cannot be excluded under any legislation.</p>
<p>If that liability cannot be excluded but can be limited under any legislation, We limit Our liability to resupplying, repairing or replacing the relevant goods or services, or payment of the cost of resupply, repair or replacement, where it is fair and reasonable to do so.</p></blockquote>
<p><strong>What did they get wrong ?</strong></p>
<p>Umm, this is a hard call.  Which do you rank first &#8230; the potential criminal offence or the apparent omission of the word ‘not&#8217; ?</p>
<p><strong>Let&#8217;s start with the potential offence</strong></p>
<p>The statement that ‘As Your service is provided to You for the primary purpose of personal use, We do not accept liability for losses &#8230;&#8217; is bizarre.  From our earlier article, you&#8217;ll understand that the ‘primary purpose&#8217; of supply is as relevant as Dodo&#8217;s left foot.  Dodo can&#8217;t deny liability for a service it provides on that basis.</p>
<p>It just isn&#8217;t lawful to (try and) do that in Australia.</p>
<p>And trying to do it may breach section 53(g) of the Trade Practices Act:  ‘A corporation shall not, in trade or  commerce, in connexion with the supply or possible supply of goods &#8230; make a false or misleading representation concerning the existence, exclusion or effect of any condition, warranty, guarantee, right or remedy.&#8217;</p>
<p>Section 75AZC of the TPA goes on to make that an offence &#8230; with a maximum penalty of over $1 million.</p>
<p><strong>Now let&#8217;s look at the ‘not&#8217; problem</strong></p>
<p>It&#8217;s pretty obvious that Dodo did not mean to say ‘We are liable to you for breach of contract or negligence.&#8217;  The next sentence reads:  ‘However, We will accept that liability if it cannot be excluded under any legislation.&#8217;  You don&#8217;t begin a sentence with ‘<em>However</em>, we will accept that liability&#8217; when the previous sentence already says ‘We <em>are</em> liable to you for breach of contract or negligence.&#8217;</p>
<p>It looks like some careless dork has left out ‘not&#8217;.  Maybe it was intended to say ‘We are <strong>not </strong>liable to you for breach of contract or negligence.&#8217;  Then it would make sense for the next sentence to begin with ‘However, We <strong>will</strong> accept that liability &#8230;&#8217;.</p>
<p><strong>And there&#8217;s a second, different liability clause in the same document</strong></p>
<p>We won&#8217;t dwell on it, but there&#8217;s a second clause about liability that works differently.  It also mis-states the law, though.</p>
<p><strong>Our take on it</strong></p>
<p>If anyone takes Dodo on in court, claiming heavy losses, the company will have to rely on a court reading this mish-mash with sympathy.  Good luck, Dodo.</p>
]]></content:encoded>
			<wfw:commentRss>http://cspcentral.com.au/2008/10/struggling-to-make-sense-of-dodos-liability-clauses/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>CSPs fail simple compliance test</title>
		<link>http://cspcentral.com.au/2008/09/csps-fail-simple-compliance-test/</link>
		<comments>http://cspcentral.com.au/2008/09/csps-fail-simple-compliance-test/#comments</comments>
		<pubDate>Wed, 10 Sep 2008 12:54:28 +0000</pubDate>
		<dc:creator>Peter Moon</dc:creator>
				<category><![CDATA[How not to do it]]></category>
		<category><![CDATA[Telecommunications Act]]></category>
		<category><![CDATA[ACMA]]></category>
		<category><![CDATA[contract]]></category>
		<category><![CDATA[regulation]]></category>
		<category><![CDATA[sfoa]]></category>

		<guid isPermaLink="false">http://cspcentral.com.au/wordpress/?p=629</guid>
		<description><![CDATA[It&#8217;s surprising how many service providers trip up on basic compliance requirements.  We surveyed 36 Aussie CSPs against a simple benchmark.  21 of them failed. The smaller the company, the more likely it was to get the requirement wrong.  But Adam Internet, Crazy John&#8217;s and Soul Mobile all got it wrong, too. The benchmark requirement [...]]]></description>
			<content:encoded><![CDATA[<h4><img class="alignright size-thumbnail wp-image-635" title="feedback_form" src="http://cspcentral.com.au/wordpress/wp-content/uploads/2008/09/feedback_form.jpg" alt="" width="132" height="150" />It&#8217;s surprising how many service providers trip up on basic compliance requirements.  We surveyed 36 Aussie CSPs against a simple benchmark.  21 of them failed.</h4>
<p>The smaller the company, the more likely it was to get the requirement wrong.  But Adam Internet, Crazy John&#8217;s and Soul Mobile all got it wrong, too.</p>
<p><span id="more-629"></span></p>
<p><strong>The benchmark requirement</strong></p>
<p>We wanted something so simple and clear that it doesn&#8217;t take a law degree to get right.  So we chose clauses 5 and 6 of the <em><a href="http://www.comlaw.gov.au/ComLaw/Legislation/LegislativeInstrumentCompilation1.nsf/framelodgmentattachments/38388906F4A10306CA2571690015D8C8" target="_blank">Telecommunications (Standard Form of Agreement Information) Determination 2003</a></em>.</p>
<p>Under this Determination, a CSP with a ‘Standard Form of Agreement&#8217; under Part 23 of the Telco Act is required to offer a summary of the contract in a particular format.</p>
<p>Clauses 5 and 6 simply say:</p>
<ul>
<li>The summary must include the heading ‘Important Customer Information: Your Rights and Obligations&#8217; or equivalent.</li>
<li>The heading must be in a prominent position.</li>
<li>If the heading is not in a colour that&#8217;s different from the rest of the summary, it must be bolded and at least two points larger than any other typeface.</li>
</ul>
<p>Is that so difficult ?  It was for our test selection.</p>
<p><strong>Our method</strong></p>
<ul>
<li>We chose 36 CSPs pretty much at random by googling ‘sfoa summary&#8217;.</li>
<li>We located the online version of their summary via the Google results.</li>
<li>We checked for compliance.</li>
</ul>
<p><strong>The results</strong></p>
<p>We awarded ‘passes&#8217; only to CSPs that got everything right.  Several others were very close, but after choosing such a simple test we thought it was fair to adopt a strict standard.</p>
<ul>
<li>Some CSPs omitted the required heading completely.</li>
<li>Others used the same font size and colour as other headings in the document.</li>
<li>One just used body text, and located the heading very ‘non-prominently&#8217;.</li>
<li>One used larger text, but didn&#8217;t bold it.</li>
</ul>
<p>Full results are set out at the foot of this post.</p>
<p><strong>What&#8217;s going on here ?</strong></p>
<p>We doubt that <a href="http://www.acma.gov.au" target="_blank">ACMA</a> will be keelhauling the CSPs over this issue.  But we&#8217;re mystified as to why such a simple, clear regulatory requirement trips up so many players.</p>
<p>Maybe there&#8217;s just too much regulation for CSPs to cope with.</p>
<p style="text-align: center;">
<p style="text-align: center;"><strong>Full results</strong></p>
<table border="1" cellspacing="0" cellpadding="0" width="603">
<tbody>
<tr>
<td width="234" valign="top">Internode</td>
<td width="57" valign="top">Pass</td>
<td width="312" valign="top"> </td>
</tr>
<tr>
<td width="234" valign="top">1800 Reverse</td>
<td width="57" valign="top">Fail</td>
<td width="312" valign="top">Heading is in same colour and font size as other headings</td>
</tr>
<tr>
<td width="234" valign="top">GRLmobile</td>
<td width="57" valign="top">Fail</td>
<td width="312" valign="top">Heading is in body text, in body text size and colour</td>
</tr>
<tr>
<td width="234" valign="top">Bendigo Community Telco</td>
<td width="57" valign="top">Pass</td>
<td width="312" valign="top"> </td>
</tr>
<tr>
<td width="234" valign="top">iiNet</td>
<td width="57" valign="top">Fail</td>
<td width="312" valign="top">Heading is in same size and bolded like other headings</td>
</tr>
<tr>
<td width="234" valign="top">PacNet</td>
<td width="57" valign="top">Pass</td>
<td width="312" valign="top"> </td>
</tr>
<tr>
<td width="234" valign="top">Highway1</td>
<td width="57" valign="top">Fail</td>
<td width="312" valign="top">Heading completely missing</td>
</tr>
<tr>
<td width="234" valign="top">1800PhoneHome</td>
<td width="57" valign="top">Fail</td>
<td width="312" valign="top">Heading completely missing</td>
</tr>
<tr>
<td width="234" valign="top">Nextgen Pure Data</td>
<td width="57" valign="top">Pass</td>
<td width="312" valign="top"> </td>
</tr>
<tr>
<td width="234" valign="top">Adam Internet</td>
<td width="57" valign="top">Fail</td>
<td width="312" valign="top">Heading same size and colour as title heading</td>
</tr>
<tr>
<td width="234" valign="top">Crazy John&#8217;s</td>
<td width="57" valign="top">Fail</td>
<td width="312" valign="top">Part of heading is in same size and bolded like other headings</td>
</tr>
<tr>
<td width="234" valign="top">Soul Prepaid Mobile GSM</td>
<td width="57" valign="top">Fail</td>
<td width="312" valign="top">Doesn&#8217;t contain all words / Heading is in same size and bolded like other headings</td>
</tr>
<tr>
<td width="234" valign="top">Hunter &amp; Coast Community Telco</td>
<td width="57" valign="top">Pass</td>
<td width="312" valign="top"> </td>
</tr>
<tr>
<td width="234" valign="top">Living Networks</td>
<td width="57" valign="top">Fail</td>
<td width="312" valign="top">Heading is in same size as other headings / not bolded / same colour as body text</td>
</tr>
<tr>
<td width="234" valign="top">ACC</td>
<td width="57" valign="top">Fail</td>
<td width="312" valign="top">Heading in same colour but not bolded</td>
</tr>
<tr>
<td width="234" valign="top">Telarus</td>
<td width="57" valign="top">Fail</td>
<td width="312" valign="top">Heading in same colour but not bolded</td>
</tr>
<tr>
<td width="234" valign="top">PowerTel</td>
<td width="57" valign="top">Pass</td>
<td width="312" valign="top"> </td>
</tr>
<tr>
<td width="234" valign="top">WebSecure</td>
<td width="57" valign="top">Fail</td>
<td width="312" valign="top">Heading completely missing</td>
</tr>
<tr>
<td width="234" valign="top">Commander</td>
<td width="57" valign="top">Pass</td>
<td width="312" valign="top"> </td>
</tr>
<tr>
<td width="234" valign="top">EFTel</td>
<td width="57" valign="top">Fail</td>
<td width="312" valign="top">Heading completely missing</td>
</tr>
<tr>
<td width="234" valign="top">Austar</td>
<td width="57" valign="top">Fail</td>
<td width="312" valign="top">Heading completely missing</td>
</tr>
<tr>
<td width="234" valign="top">AAPT</td>
<td width="57" valign="top">Fail</td>
<td width="312" valign="top">Heading completely missing</td>
</tr>
<tr>
<td width="234" valign="top">Engin</td>
<td width="57" valign="top">Pass</td>
<td width="312" valign="top"> </td>
</tr>
<tr>
<td width="234" valign="top">Netspeed</td>
<td width="57" valign="top">Fail</td>
<td width="312" valign="top">Heading completely missing</td>
</tr>
<tr>
<td width="234" valign="top">Trinity Telecom</td>
<td width="57" valign="top">Fail</td>
<td width="312" valign="top">Heading completely missing</td>
</tr>
<tr>
<td width="234" valign="top">Brennan IT</td>
<td width="57" valign="top">Pass</td>
<td width="312" valign="top"> </td>
</tr>
<tr>
<td width="234" valign="top">Ansego</td>
<td width="57" valign="top">Fail</td>
<td width="312" valign="top">Standard, non-bolded body text</td>
</tr>
<tr>
<td width="234" valign="top">TransACT</td>
<td width="57" valign="top">Fail</td>
<td width="312" valign="top">Heading completely missing</td>
</tr>
<tr>
<td width="234" valign="top">Demand Broadband</td>
<td width="57" valign="top">Fail</td>
<td width="312" valign="top">Heading completely missing</td>
</tr>
<tr>
<td width="234" valign="top">Spirit Telecom</td>
<td width="57" valign="top">Pass</td>
<td width="312" valign="top"> </td>
</tr>
<tr>
<td width="234" valign="top">Multelink</td>
<td width="57" valign="top">Pass</td>
<td width="312" valign="top"> </td>
</tr>
<tr>
<td width="234" valign="top">People Telecom</td>
<td width="57" valign="top">Pass</td>
<td width="312" valign="top"> </td>
</tr>
<tr>
<td width="234" valign="top">iRoam</td>
<td width="57" valign="top">Fail</td>
<td width="312" valign="top">Heading same font size and colour as other headings</td>
</tr>
<tr>
<td width="234" valign="top">Simplus</td>
<td width="57" valign="top">Pass</td>
<td width="312" valign="top"> </td>
</tr>
<tr>
<td width="234" valign="top">NewTel</td>
<td width="57" valign="top">Pass</td>
<td width="312" valign="top"> </td>
</tr>
</tbody>
</table>
]]></content:encoded>
			<wfw:commentRss>http://cspcentral.com.au/2008/09/csps-fail-simple-compliance-test/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>Managing your SFoA summary delivery</title>
		<link>http://cspcentral.com.au/2008/08/managing-your-sfoa-summary-delivery/</link>
		<comments>http://cspcentral.com.au/2008/08/managing-your-sfoa-summary-delivery/#comments</comments>
		<pubDate>Wed, 27 Aug 2008 03:15:22 +0000</pubDate>
		<dc:creator>Peter Moon</dc:creator>
				<category><![CDATA[General]]></category>
		<category><![CDATA[Telecommunications Act]]></category>
		<category><![CDATA[ACMA]]></category>
		<category><![CDATA[regulation]]></category>
		<category><![CDATA[sfoa]]></category>

		<guid isPermaLink="false">http://cspcentral.com.au/wordpress/?p=489</guid>
		<description><![CDATA[Some CSPs do it well, and many fail to do it at all.  A copy of your Standard Form of Agreement summary has to be given to customers at the start of the contract, and then a short reminder each two years. Are you compliant ?  Can you prove it ? Here are some hints [...]]]></description>
			<content:encoded><![CDATA[<h4><img class="alignright size-thumbnail wp-image-495" title="envelope" src="http://cspcentral.com.au/wordpress/wp-content/uploads/2008/08/envelope.jpg" alt="" width="150" height="150" />Some CSPs do it well, and many fail to do it at all.  A copy of your Standard Form of Agreement summary has to be given to customers at the start of the contract, and then a short reminder each two years.</h4>
<h4>Are you compliant ?  Can you prove it ?</h4>
<p>Here are some hints for getting it right.</p>
<p><span id="more-489"></span></p>
<p><strong>There&#8217;s more to an SFoA than an SFoA</strong></p>
<p>There are several good reasons to use an SFoA instead of individual customer contracts.  But the convenience comes at a cost.  For instance, you must comply with the <a href="http://www.comlaw.gov.au/comlaw%5Cmanagement.nsf/lookupindexpagesbyid/IP200507511?OpenDocument" target="_blank">Telecommunications (Standard Form of Agreement Information) Determination 2003</a>.</p>
<p>The Determination requires that a CSP with an SFoA:</p>
<ul class="unIndentedList">
<li> creates a summary of it in a specific form</li>
<li> gives the summary to ACMA</li>
<li> makes any changes ACMA requires</li>
<li> gives customers a copy of the summary at the start of the contract</li>
<li> gives them a reminder notice about it every two years.</li>
</ul>
<p><strong>New customers must receive a copy of the summary</strong></p>
<p>The Determination requires you to give a copy of the summary at the time of first supply, or a.s.a.p. afterwards.</p>
<p><em>Permitted methods of delivery</em></p>
<ul class="unIndentedList">
<li> personal delivery</li>
<li> post to address in your records</li>
<li> email, if the customer has agreed to receive notices at that address</li>
<li> it is OK to send it with a bill or other document, by one of the above methods.</li>
</ul>
<p><em>What about notice by hyperlink ?</em></p>
<p>We&#8217;re often asked whether you can send an SFoA summary as a hyperlink in an email &#8211; assuming the customer has agreed to receive notices by email.</p>
<p>The Determination doesn&#8217;t allow for it, but the Australian Communications Authority (which has since become ACMA) informally agreed that this was an acceptable practice <em>as long as the hyperlink is direct to the document itself</em> and not merely to a web site where the customer can find the document.</p>
<p>We think this position would apply with ACMA today.</p>
<p><em>What if you don&#8217;t give the copy ?</em></p>
<p>The customer remains a ‘new customer&#8217; for the purposes of the Determination until they have received the summary.</p>
<p>So the obligation to send it never goes away.</p>
<p><strong>Existing customers must receive a notice <em>about</em> the summary, each 24 months</strong></p>
<p>No less often that each 24 months (starting on the date they received the original copy of the summary) a customer must receive a particular notice <em>about</em> your current summary.</p>
<p>This is where many CSPs fall down.</p>
<p><em>What the notice must say</em></p>
<p>The notice must include statements that:</p>
<ul class="unIndentedList">
<li> an up-to-date copy of the relevant summary is available from the CSP</li>
<li> customer can get a free copy by:</li>
</ul>
<p style="padding-left: 60px;">(a)   calling a number in the notice</p>
<p style="padding-left: 60px;">(b)  downloading it from the CSP&#8217;s web site</p>
<p style="padding-left: 60px;">(c)   lodging a request on the CSP&#8217;s web site.</p>
<p><em>Permitted methods of delivery</em></p>
<ul class="unIndentedList">
<li> personal delivery</li>
<li> post to address in your records</li>
<li> email, if the customer has agreed to receive notices at that address</li>
<li> by SMS</li>
<li> it is OK to send it with a bill or other document, by one of the above methods.</li>
</ul>
<p><strong>SMS ???</strong></p>
<p>Yes, it&#8217;s a rare example of a consumer protection law that permits SMS notification.  But remember, that&#8217;s only for the reminder notice <em>about</em> the summary, not for the summary itself.</p>
<p><strong>Getting the evidence right</strong></p>
<p>Across their regulatory compliance, many businesses fall down in record keeping, or having some good proof that they have complied with the law.</p>
<p>If a particular customer denies receiving the summary or a notice, you need to be able to show it was sent.  If you&#8217;re not systematic about that, you may not have sufficient evidence.</p>
<p>Some businesses include the summary in a Welcome Pack, and that&#8217;s especially suitable where the pack includes log on details or something else that proves the customer must have received it.</p>
<p>Some of my clients send the reminder notice to all customers on a fixed date every two years.  That means that a customer who joined only recently may get a reminder a relatively short time later, but so what ?  It means that the CSP only needs to send one mass email on (for instance) New Year&#8217;s Day every second year, and compliance is assured &#8211; assuming your sign up processes include customer consent to receiving the reminder by email.</p>
]]></content:encoded>
			<wfw:commentRss>http://cspcentral.com.au/2008/08/managing-your-sfoa-summary-delivery/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Talk about tangled up ! Sorry, Voda.  Your prepay contract terms don&#8217;t work.</title>
		<link>http://cspcentral.com.au/2008/08/talk-about-tangled-up-sorry-voda-your-prepay-contract-terms-dont-work/</link>
		<comments>http://cspcentral.com.au/2008/08/talk-about-tangled-up-sorry-voda-your-prepay-contract-terms-dont-work/#comments</comments>
		<pubDate>Sat, 02 Aug 2008 02:19:21 +0000</pubDate>
		<dc:creator>Peter Moon</dc:creator>
				<category><![CDATA[General]]></category>
		<category><![CDATA[How not to do it]]></category>
		<category><![CDATA[contract]]></category>
		<category><![CDATA[sfoa]]></category>
		<category><![CDATA[vodafone]]></category>

		<guid isPermaLink="false">http://203.100.228.50/wordpress/?p=176</guid>
		<description><![CDATA[A thread on Whirlpool about early termination fees under Vodafone mobile prepays led us into the maze of Voda&#8217;s complex contract terms.  And guess what ?  They don&#8217;t say what Voda thinks they say. It&#8217;s a great lesson to telcos and their lawyers &#8230; Super-complex contracts don&#8217;t only confuse your customers. The Whirlpool thread Here&#8217;s [...]]]></description>
			<content:encoded><![CDATA[<h4><img class="alignleft size-thumbnail wp-image-199" title="spaghetti" src="http://203.100.228.50/wordpress/wp-content/uploads/2008/08/spaghetti.jpg" alt="" width="150" height="112" />A thread on Whirlpool about early termination fees under Vodafone mobile prepays led us into the maze of Voda&#8217;s complex contract terms.  And guess what ?  They don&#8217;t say what Voda thinks they say.</h4>
<p>It&#8217;s a great lesson to telcos and their lawyers &#8230; Super-complex contracts don&#8217;t only confuse your customers.</p>
<p><span id="more-176"></span></p>
<p><strong>The Whirlpool thread</strong></p>
<p>Here&#8217;s the <a title="Voda Prepay" href="http://forums.whirlpool.net.au/forum-replies.cfm?t=1025058&amp;p=-1#top" target="_blank">Whirlpool thread</a>.</p>
<p>Basically, the question was about the lump sum Voda will bill you if you buy a prepay handset from their website and don&#8217;t activate within 30 days.  In some places, they call it an ‘Early Exit Fee&#8217;.</p>
<p>Understandably, one member of the thread assumed Voda could do it:</p>
<p><em>Since you are ordering this and having the phone sent to you, yes you&#8217;d need to activate the SIM card in the prepay pack in the 30 days. (Otherwise it&#8217;ll be followed by an invoice in the mail which they could/can legally make you pay).</em></p>
<p><strong>But let&#8217;s look closer at Voda&#8217;s T&amp;Cs.</strong></p>
<p>They&#8217;re amazingly convoluted.  We can&#8217;t give you a URL because the terms are squirreled away in so many places.</p>
<p>But as far as we can follow this labyrinth, here&#8217;s what it says.  We&#8217;ll analyse the current Vodafone 226 Prepay Pack that the Whirlpool member was interested in.</p>
<p>A scroll box at foot of screen contains the terms &amp; conditions.</p>
<p>We won&#8217;t bother you with the full guff.  All you need to know is that:</p>
<ul type="disc">
<li>‘Early Exit Fees apply if not connected within 30 days of supply of handset on this Contract.&#8217;</li>
<li>There is no mention of a minimum or fixed contract term, either in the T&amp;Cs or anywhere else on the page.</li>
</ul>
<p><strong>No Plan Term</strong></p>
<p>What&#8217;s the significance of ‘no minimum term&#8217; ?  Well, if you take the time to seek out the definitions section in Voda&#8217;s SFoA, you learn that:  ‘Early Exit Fee means the payment or fee We will charge You, based on the Plan you are on at the time of disconnection, if, subject to the terms of this Agreement, You or We terminate Your contract with Us prior to expiration of Your Plan Term.&#8217;</p>
<p>So, an Early Exit Fee can only apply if customer terminates during a Plan Term.</p>
<p><strong>What&#8217;s a Plan Term ?</strong></p>
<p>According to the definitions, ‘Plan Term the term or commitment period of the relevant Plan as set out in Section 4 of this Agreement.&#8217;</p>
<p>Maybe Section 4 will tell us that a Plan Term applies for this prepay.</p>
<p><strong>What we found at Section 4</strong></p>
<p>Guess what ?  It doesn&#8217;t state a Plan Term for any prepay service.</p>
<p><strong>The result ?</strong></p>
<p>The so-called Early Exit Fee for failing to connect within 30 days cannot apply where there is no Plan Term.</p>
<p>Or, if this ‘Early Exit Fee&#8217; means something different to the normal ‘Early Exit Fee&#8217; referred to by the SFoA, there&#8217;s no basis in the documents (that we can see) for calculating it.  It&#8217;s an unspecified charge.</p>
<p><strong>What would a court / the TIO do ?</strong></p>
<p>Who knows ?  It&#8217;s a mess.  Maybe they&#8217;d do Voda a favour and recognise that a handset has value and stretch its terms to say that customer has to pay a fair amount.</p>
<p>More likely they&#8217;d just say that CSPs who pitch pages of complicated, layered T&amp;Cs at customers deserve to get stung when their own legal team can&#8217;t keep it all together.</p>
<p><strong>So we called Voda to check &#8230; and it got worse.</strong></p>
<p>At 11:34 a.m. on 2 August 2008, we reached Voda&#8217;s sales team by phone, and were assured there were no Early Exit Fees applicable to the 226 offer.  ‘There aren&#8217;t any,&#8217; they said.</p>
<p>We pointed out that the T&amp;Cs at the foot of the page specifically said that Early Exit Fees could apply.  Voda rep&#8217;s best guess was that the T&amp;Cs were ‘just a generic one&#8217; i.e. didn&#8217;t actually apply to the prepay offer.  (Isn&#8217;t that comforting ?)</p>
<p>He was clear:  We could order and pay for the handset, and keep it and pay no more.  That would be our loss for not taking advantage of the prepay Maxi Cap offer, but we could do it if we wanted, with no Early Exit Fee.</p>
<p>He pointed out that the handset would be locked to Voda, and an unlock fee would apply to use it outside the network.</p>
<p><strong>How bad is all this ?</strong></p>
<p>The way Voda&#8217;s legals and web site are set up:</p>
<ul type="disc">
<li>An honest, god fearing Whirlpool member has concluded that a lump sum pay out charge applies, and is contractually enforceable.  Poor fellow assumed the contract terms on the page were sound.</li>
<li>Legal analysis suggests that the terms don&#8217;t support such a charge.</li>
<li>Voda rep says ‘Don&#8217;t worry about it.  Those aren&#8217;t the right T&amp;Cs anyway.&#8217;</li>
</ul>
<p><strong>Our take on it</strong></p>
<p>We intensely dislike overly complex documents, especially when terms and conditions are located in several different places.  Voda&#8217;s are a prime example of what we regard as worst practice.  No wonder everybody, from legal to web developer to sales rep to potential customer, thinks it all works differently.</p>
]]></content:encoded>
			<wfw:commentRss>http://cspcentral.com.au/2008/08/talk-about-tangled-up-sorry-voda-your-prepay-contract-terms-dont-work/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
