Commentary

Verizon Wireless Addresses BlackBerry Tour Issues

Last week an analyst said in a research note that the BlackBerry Tour, made by Research In Motion and sold by both Sprint and Verizon Wireless, was seeing huge return rates due to faulty trackballs. Both Sprint and Verizon have responded to the report.

Last week an analyst said in a research note that the BlackBerry Tour, made by Research In Motion and sold by both Sprint and Verizon Wireless, was seeing huge return rates due to faulty trackballs. Both Sprint and Verizon have responded to the report.The report, issued by Gerard Hallaren, director of research at TownHall Investment Research, noted that the Tour was looking at ridiculous return numbers. Hallaren said as many as 50% of all Tour sold to Sprint customers had been returned. Sprint says, "Bollocks."

Sprint was first out the door with an official response: "We experienced a small percentage of early production BlackBerry Tour smartphones with trackball issues. As soon as the issue was identified, we worked closely with our partners at RIM to resolve the problem quickly. We recommend any customer experiencing issues with the trackball on their BlackBerry Tour smartphone visit a Sprint Service & Repair Center."


More Mobility Insights

White Papers

More >>

Reports

More >>

Webcasts

More >>

Verizon followed up the next day with a statement of its own: "Early on there was an issue with the trackball that affected a small percentage [of] the early production units -- far less than industry norms. The issue was detected early, addressed immediately and is no longer an issue. Returns on this device are some of the lowest among any of our smart phones."

What's interesting is that both companies admitted that there was a problem. The reports of gummy trackballs were at least partially true, even if the returns didn't reach the levels that Hallaren suggested.


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