Commentary

Amy DeCarlo
 

Too Much Time

Cell service has improved enough that enterprises are now comfortable relying on the technology to conduct business. But improved service quality has not come with corresponding advances in the cost-effectiveness of contracts. Consider your own personal cell phone contract: Are you satisfied with it or are you paying for minutes you will never use? If you have too much of a good thing, then you aren't alone.
Cell service has improved enough that enterprises are now comfortable relying on the technology to conduct business. But improved service quality has not come with corresponding advances in the cost-effectiveness of contracts. Consider your own personal cell phone contract: Are you satisfied with it or are you paying for minutes you will never use? If you have too much of a good thing, then you aren't alone.My collegue David Haskin, editor of the Mobile Pipeline, recently asked this question in an effort to get confirmation of what we all seem to know intuitively and have heard anecdotally. The results so far more than confirm our suspicions. Eighty-percent of the respondents have more minutes than they can use. As of Tuesday morning, a pretty astounding 34 percent said they are using less than 50 percent of their allotted minutes.

David is hoping this evidence will help coax mobile operators to make some changes that he suspects may already be the offing. Given the fairly radical shifts that are already underway, my guess is this is will only help speed the inevitable. If you want to add your voice to the mix, please take a minute to vote.


More Infrastructure Insights

White Papers

More >>

Reports

More >>

Webcasts

More >>


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