Light Reading Mobile – Telecom News, Analysis, Events, and Research

On Tuesday, AT&T Inc. acknowledged that a limited number of customers lost one or more services for a few hours on Monday. Let's take AT&T at its word and say it was just a couple of clusters of a few thousand customers out of the millions it serves. Why make such a big deal of it?

We think it's an example of what can happen when the customer experience isn't managed well. A quick poll of my U-verse subscribing neighbors, friends and Twitter followers first alerted me that a few folks in different states were seeing outages of Internet access, pay TV and voice services. But AT&T, via its social media accounts, said nothing for several hours.

Why bother everyone with news about a limited outage? I think any company that trots its executives out on a Las Vegas stage to brag unceasingly about its media reviews, developer prowess and 4G network improvements has set a public expectation that it will be more open.

So we find it surprising that, instead of giving specifics, AT&T would rather let its (disappointed) customers vent on social networks when it could have told a solid story using its own network data. That seems like the sort of thing most companies would be wise enough to address with enough clarity that it doesn't balloon into a bigger story.

Why else should a company as big as AT&T try to set an example in customer experience management? I'll answer that question by posing three more: How should customers reconcile an unexplained, multistate, multiservice outage with the idea of AT&T Digital Life? Would it give anyone pause to turn over more control of their homes -- via home automation and home security services -- to a company that doesn't talk openly about what's going on in its network?

At a time when service providers are trying to get a bigger share of consumer spending, is it too much for consumers to expect better communication and a little accountability when things don't go so well?

— Phil Harvey, Editor-in-Chief, Light Reading

Network operators can overload you with data about upgrades. But ask about a network outage and the silence speaks volumes
January 23, 2013 | Phil Harvey |


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

Network Computing encourages readers to engage in spirited, healthy debate, including taking us to task. However, Network Computing 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. Network Computing 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.
 
Related Videos
White Papers SPONSORED CONTENT
Featured