Commentary

Marin Perez
 

Cell Phone Fees OK For Consumers, Not Government

I hate early termination fees. Big shock, I know. But what's even more infuriating is seeing reports that Sprint didn't charge government subscribers an ETF because "the government will never, never accept such penalty amounts."

I hate early termination fees. Big shock, I know. But what's even more infuriating is seeing reports that Sprint didn't charge government subscribers an ETF because "the government will never, never accept such penalty amounts."Consumer anger already is reaching a boiling point with a few lawsuits already being filed, and these leaked confidential e-mails by the AP show then-Nextel marketing VP Scott Wiener saying that customers' complaints are real.

AT&T and Verizon Wireless already have made some adjustments to their ETFs, and the FCC is currently mulling a nationwide policy. For some reason, I just don't think we need the FCC's help on this, just some common sense.


More Mobility Insights

White Papers

More >>

Reports

More >>

Webcasts

More >>

The refrain from carriers is that they have to charge these fees because many handsets are subsidized. While some buy their own phones outright (particularly the first iPhone), the majority of consumers still get their phones free or at a carrier discount. Because of this, I'm not completely opposed to an ETF.

But not all subsidies are equal. Carriers should simply adjust the ETF according to how much of a discount they got for the handset. If you brought your own handset to the party, then you shouldn't be charged.

Additionally, Verizon and AT&T are reducing the cost of living depending on how long you've been under contract and that's a step in the right direction.

What do you think? Are the ETFs shady, or is it the consumer's fault for signing a contract they don't understand? I mean, even if you can't get the latest and greatest phone, there are options to get mobile service without a contract.

How would you fix early termination fees?


Related Reading




Currently we allow the following HTML tags in comments:

Single tags

These tags can be used alone and don't need an ending tag.

<br> Defines a single line break

<hr> Defines a horizontal line

Matching tags

These require an ending tag - e.g. <i>italic text</i>

<a> Defines an anchor

<b> Defines bold text

<big> Defines big text

<blockquote> Defines a long quotation

<caption> Defines a table caption

<cite> Defines a citation

<code> Defines computer code text

<em> Defines emphasized text

<fieldset> Defines a border around elements in a form

<h1> This is heading 1

<h2> This is heading 2

<h3> This is heading 3

<h4> This is heading 4

<h5> This is heading 5

<h6> This is heading 6

<i> Defines italic text

<p> Defines a paragraph

<pre> Defines preformatted text

<q> Defines a short quotation

<samp> Defines sample computer code text

<small> Defines small text

<span> Defines a section in a document

<s> Defines strikethrough text

<strike> Defines strikethrough text

<strong> Defines strong text

<sub> Defines subscripted text

<sup> Defines superscripted text

<u> Defines underlined text

InformationWeek encourages readers to engage in spirited, healthy debate, including taking us to task. However, InformationWeek moderates all comments posted to our site, and reserves the right to modify or remove any content that it determines to be derogatory, offensive, inflammatory, vulgar, irrelevant/off-topic, racist or obvious marketing/SPAM. InformationWeek further reserves the right to disable the profile of any commenter participating in said activities.

Disqus Tips To upload an avatar photo, first complete your Disqus profile. | View the list of supported HTML tags you can use to style comments. | Please read our commenting policy.
T-Shirt Giveaway T-Shirt Giveaway: Each week we're selecting one great comment from our readers. The author of the comment will receive an InformaitonWeek Community t-shirt. So get posting!
Subscribe to RSS

Resource Links