<?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>Brian Linzy &#187; T-mobile Archives  &#8211; Brian Linzy</title>
	<atom:link href="http://blog.brianlinzy.com/tag/t-mobile/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.brianlinzy.com</link>
	<description>Si vis pacem, para bellum</description>
	<lastBuildDate>Tue, 27 Dec 2011 19:20:00 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
		<item>
		<title>T-Mobile Loophole</title>
		<link>http://blog.brianlinzy.com/2010/04/08/tmobile-loophole/</link>
		<comments>http://blog.brianlinzy.com/2010/04/08/tmobile-loophole/#comments</comments>
		<pubDate>Thu, 08 Apr 2010 16:58:00 +0000</pubDate>
		<dc:creator>Brian</dc:creator>
				<category><![CDATA[Random]]></category>
		<category><![CDATA[Tech]]></category>
		<category><![CDATA[insurance]]></category>
		<category><![CDATA[loophole]]></category>
		<category><![CDATA[N1]]></category>
		<category><![CDATA[Nexus One]]></category>
		<category><![CDATA[T-mobile]]></category>

		<guid isPermaLink="false">http://blog.brianlinzy.com/?p=1581</guid>
		<description><![CDATA[Normally I&#8217;m all about how great T-mobile&#8217;s customer service is. But here&#8217;s an exception &#8211; their handset insurance policy. When we bought our 3 Nexus Ones (Nexuses One? Nexi Ones? Nexus Three?) there was no insurance available. We didn&#8217;t know &#8230; <a href="http://blog.brianlinzy.com/2010/04/08/tmobile-loophole/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
			<content:encoded><![CDATA[<p>Normally I&#8217;m all about how great T-mobile&#8217;s customer service is. But here&#8217;s an exception &#8211; their handset insurance policy.</p>
<p>When we bought our 3 Nexus Ones (Nexuses One? Nexi Ones? Nexus Three?) there was no insurance available. We didn&#8217;t know that because the <a title="Ordering the N1" href="http://blog.brianlinzy.com/2010/02/26/ordering-nexus/" target="_blank">ordering process was so terrible</a>. At some point a few weeks later T-mobile / Google / Asurion quietly made the Premium Handset Protection Bundle available for the N1. It&#8217;s $2.60 / month with a $130 deductible. With a two year commitment to these phones all three of us <em>must </em>have insurance.</p>
<p>But there&#8217;s a catch &#8211; you have to sign up for the Premium Handset Protection Bundle within 14 days of ordering the phone.  Well that was a problem for me, since 1) it wasn&#8217;t available within the first 14 days and 2) even if it was we wouldn&#8217;t have known to ask for it. As far I can tell they still don&#8217;t mention it on google.com/phone. So if you&#8217;re ordering an N1 you need to somehow know to call T-mobile and add the PHPB (with-in 14 days).</p>
<p>The insurance must be added within 14 days of opening your account, upgrading a handset, or completing an account change of responsibility. Wait &#8211; what was that last one?</p>
<p>Me: Is there any way I can add insurance to my phone now?<br />
T-Mo Rep: Not at this point, it has to be done within 14 days&#8230;<br />
Me: But if I transfer my whole account to my wife I can add insurance?<br />
T-Mo Rep: That&#8217;s correct.<br />
Me: I would like to initiate a change of responsibility for this account.<br />
T-Mo Rep: No problem.</p>
<p>About an hour and a half of phone calls later the whole account has been transferred to my wife (still billing to the same credit card), and all three N1s have insurance.</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.brianlinzy.com/2010/04/08/tmobile-loophole/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

<!-- Dynamic Page Served (once) in 0.311 seconds -->

