<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	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/"
		>
<channel>
	<title>Comments on: Got My Beep Back, Baby!</title>
	<atom:link href="http://www.takebackthebeep.com/got-my-beep-back-baby/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.takebackthebeep.com/got-my-beep-back-baby/</link>
	<description>End Wireless Voicemail Instructions Forever</description>
	<lastBuildDate>Mon, 22 Aug 2011 05:11:57 -0400</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Matt</title>
		<link>http://www.takebackthebeep.com/got-my-beep-back-baby/comment-page-1/#comment-108</link>
		<dc:creator>Matt</dc:creator>
		<pubDate>Mon, 22 Aug 2011 05:11:57 +0000</pubDate>
		<guid isPermaLink="false">http://www.takebackthebeep.com/?p=61#comment-108</guid>
		<description>well, you may laugh, but I tried my own little trick.  I recorded the sound of pressing the &quot;1&quot; key after I was done recording my announcement, in an effort to trick the system into thinking the caller pressed &quot;1&quot;.  Didn&#039;t work...but it sure would&#039;ve been easier than this runaround!</description>
		<content:encoded><![CDATA[<p>well, you may laugh, but I tried my own little trick.  I recorded the sound of pressing the &#8220;1&#8243; key after I was done recording my announcement, in an effort to trick the system into thinking the caller pressed &#8220;1&#8243;.  Didn&#8217;t work&#8230;but it sure would&#8217;ve been easier than this runaround!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Chris Allen</title>
		<link>http://www.takebackthebeep.com/got-my-beep-back-baby/comment-page-1/#comment-106</link>
		<dc:creator>Chris Allen</dc:creator>
		<pubDate>Sat, 20 Aug 2011 21:52:37 +0000</pubDate>
		<guid isPermaLink="false">http://www.takebackthebeep.com/?p=61#comment-106</guid>
		<description>@Yukio -- Send me your e-mail address. I may have a case number that will get this resolved for you.  

What we&#039;re hearing now on a consistent basis is that there are two voicemail systems being used by AT&amp;Tnow.  If you&#039;re on the old system, they can implement the change.  If you&#039;re on the new system, there&#039;s nothing anybody at any level can do.

Why is it that &quot;new &amp; improved&quot; is rarely both?</description>
		<content:encoded><![CDATA[<p>@Yukio &#8212; Send me your e-mail address. I may have a case number that will get this resolved for you.  </p>
<p>What we&#8217;re hearing now on a consistent basis is that there are two voicemail systems being used by AT&#038;Tnow.  If you&#8217;re on the old system, they can implement the change.  If you&#8217;re on the new system, there&#8217;s nothing anybody at any level can do.</p>
<p>Why is it that &#8220;new &#038; improved&#8221; is rarely both?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Yukio</title>
		<link>http://www.takebackthebeep.com/got-my-beep-back-baby/comment-page-1/#comment-105</link>
		<dc:creator>Yukio</dc:creator>
		<pubDate>Sat, 20 Aug 2011 20:38:16 +0000</pubDate>
		<guid isPermaLink="false">http://www.takebackthebeep.com/?p=61#comment-105</guid>
		<description>I too, have been humbly trying to get AT&amp;T to switch off the lady.  And having actually worked for AT&amp;T in the past, I always talk to the CSRs with respect and patience.  (By the way, I&#039;d like to thank Chris for pointing out to his readers that sometimes lack of knowledge on the job isn&#039;t always due to stupidity on the employee&#039;s part, but often from the employer not properly educating their staff.  AT&amp;T changes policies, procedures, terminology and job titles SO often that it&#039;s impossible to keep up)  However, my results have been the same as so many others here.  The reps don&#039;t know where to direct me, and don&#039;t know how to handle my request.  Even when mentioning &quot;voicemail team&quot;, &quot;engineering&quot;, &quot;caller prompt from full to none&quot;...it doesn&#039;t help.  Every single person I&#039;ve talked to has been more than gracious throughout it all but unfortunately when you call customer care you could be getting any one of thousands of reps across hundreds of call centers.  Getting the one who has all the know how to handle your particular problem is kind of like hitting the slots.

Could someone give me any additional info that might help me take back my beep?  Thanks.</description>
		<content:encoded><![CDATA[<p>I too, have been humbly trying to get AT&amp;T to switch off the lady.  And having actually worked for AT&amp;T in the past, I always talk to the CSRs with respect and patience.  (By the way, I&#8217;d like to thank Chris for pointing out to his readers that sometimes lack of knowledge on the job isn&#8217;t always due to stupidity on the employee&#8217;s part, but often from the employer not properly educating their staff.  AT&amp;T changes policies, procedures, terminology and job titles SO often that it&#8217;s impossible to keep up)  However, my results have been the same as so many others here.  The reps don&#8217;t know where to direct me, and don&#8217;t know how to handle my request.  Even when mentioning &#8220;voicemail team&#8221;, &#8220;engineering&#8221;, &#8220;caller prompt from full to none&#8221;&#8230;it doesn&#8217;t help.  Every single person I&#8217;ve talked to has been more than gracious throughout it all but unfortunately when you call customer care you could be getting any one of thousands of reps across hundreds of call centers.  Getting the one who has all the know how to handle your particular problem is kind of like hitting the slots.</p>
<p>Could someone give me any additional info that might help me take back my beep?  Thanks.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Neeks</title>
		<link>http://www.takebackthebeep.com/got-my-beep-back-baby/comment-page-1/#comment-102</link>
		<dc:creator>Neeks</dc:creator>
		<pubDate>Thu, 28 Apr 2011 02:16:38 +0000</pubDate>
		<guid isPermaLink="false">http://www.takebackthebeep.com/?p=61#comment-102</guid>
		<description>So I followed the instructions, got transferred to the Tech Support department. Guy was super cool, I mentioned the blog and how I didn&#039;t want to step on his toes but that it talked about making a case and that it may need a &quot;higher level&quot; of tech support. He was grateful because he hadn&#039;t heard of the issue before and was stoked to learn about it as he was helping me with the process. Got the case made Friday, and today I got a text that it had been completed. Just called my VM and I got my beep back! Thanks guys for all the help!</description>
		<content:encoded><![CDATA[<p>So I followed the instructions, got transferred to the Tech Support department. Guy was super cool, I mentioned the blog and how I didn&#8217;t want to step on his toes but that it talked about making a case and that it may need a &#8220;higher level&#8221; of tech support. He was grateful because he hadn&#8217;t heard of the issue before and was stoked to learn about it as he was helping me with the process. Got the case made Friday, and today I got a text that it had been completed. Just called my VM and I got my beep back! Thanks guys for all the help!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Chris Allen</title>
		<link>http://www.takebackthebeep.com/got-my-beep-back-baby/comment-page-1/#comment-101</link>
		<dc:creator>Chris Allen</dc:creator>
		<pubDate>Tue, 19 Apr 2011 19:21:22 +0000</pubDate>
		<guid isPermaLink="false">http://www.takebackthebeep.com/?p=61#comment-101</guid>
		<description>@Polska -- Send me your e-mail address.  I may have a case number that will get this resolved for you.</description>
		<content:encoded><![CDATA[<p>@Polska &#8212; Send me your e-mail address.  I may have a case number that will get this resolved for you.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Polska</title>
		<link>http://www.takebackthebeep.com/got-my-beep-back-baby/comment-page-1/#comment-100</link>
		<dc:creator>Polska</dc:creator>
		<pubDate>Tue, 19 Apr 2011 18:10:04 +0000</pubDate>
		<guid isPermaLink="false">http://www.takebackthebeep.com/?p=61#comment-100</guid>
		<description>I’m a product development engineer with technical knowledge and have owned both the original iPhone and iPhone 3G.  I have finally decided I can’t hold out for the iPhone 5 (now likely to be released in October instead of the usual June time frame).  I proactively called AT&amp;T customer support this morning to find out if I would potentially lose my “straight to beep” feature during the upgrade.  I also mentioned I would likely be  downgrading my $30 unlimited data plan to the $25 2GB plan.  The initial customer service rep didn’t know what I was talking about for the first 10-15 minutes.  Even once she did, the conversation got nowhere and so I asked for technical support.  I eventually got on the line with a woman in tech support who was just as clueless.  I mentioned phrases like “full to none voicemail option” and “cut through paging” and was told she didn’t know how to do any of this.  I mentioned that the “engineering team” should be able to enable or disable this voicemail option.  I was put on hold again while she spoke to a supervisor.  Ten minutes later I’m told there is a feature called “cut through paging.”  Really?  I just told her the same thing 10 minutes earlier.  She proceeds to tell me that I may lose this feature when I switch to the 2GB data plan and that my original unlimited data plan utilizes a different voicemail system.  She says to me several times, “you can just keep your unlimited plan to make sure you don’t lose the feature.”  I reiterate to her I’ll just be throwing away an extra $5 every month like I have been.  I genuinely felt like she wanted me to keep on paying a higher rate instead of actually trying to figure out how to ensure that I don’t lose this feature.  I was persistent and was put on hold again while she spoke to another supervisor.  When I got back on the line with her, I was told I can access my voicemail menu and enable/disable cut through paging.  At this point she was rude and made it difficult for me to even find out how to access this menu from the iPhone.  Hold down the number “1” I was finally told.  Next, hit “4” for options and then “7” for cut through paging.  I finally got off the phone after 59 minutes of vagueness and ill informed reps feeling like I’ll be taking a risk upgrading my phone.    

So, I tried these voicemail options just now on my iPhone 3G.  And guess what?  The tech support specialist was wrong.  First off, after hitting “4” for options you need to then dial “2” for administrative options.  At that menu, there is no option “7” for cut through paging.  I just spent 59 frustrating minutes on the phone trying to ensure I don’t lose a feature and in the end got nowhere.  This tech support specialist didn’t even know the correct menu options for voicemail on the iPhone.  Seriously?  I am so disappointed lately with AT&amp;T’s lack of interest holding on to long time customers and actually trying to figure things out and find solutions.  I am now leaning towards a Verizon iPhone 4 with its known network limitations.</description>
		<content:encoded><![CDATA[<p>I’m a product development engineer with technical knowledge and have owned both the original iPhone and iPhone 3G.  I have finally decided I can’t hold out for the iPhone 5 (now likely to be released in October instead of the usual June time frame).  I proactively called AT&amp;T customer support this morning to find out if I would potentially lose my “straight to beep” feature during the upgrade.  I also mentioned I would likely be  downgrading my $30 unlimited data plan to the $25 2GB plan.  The initial customer service rep didn’t know what I was talking about for the first 10-15 minutes.  Even once she did, the conversation got nowhere and so I asked for technical support.  I eventually got on the line with a woman in tech support who was just as clueless.  I mentioned phrases like “full to none voicemail option” and “cut through paging” and was told she didn’t know how to do any of this.  I mentioned that the “engineering team” should be able to enable or disable this voicemail option.  I was put on hold again while she spoke to a supervisor.  Ten minutes later I’m told there is a feature called “cut through paging.”  Really?  I just told her the same thing 10 minutes earlier.  She proceeds to tell me that I may lose this feature when I switch to the 2GB data plan and that my original unlimited data plan utilizes a different voicemail system.  She says to me several times, “you can just keep your unlimited plan to make sure you don’t lose the feature.”  I reiterate to her I’ll just be throwing away an extra $5 every month like I have been.  I genuinely felt like she wanted me to keep on paying a higher rate instead of actually trying to figure out how to ensure that I don’t lose this feature.  I was persistent and was put on hold again while she spoke to another supervisor.  When I got back on the line with her, I was told I can access my voicemail menu and enable/disable cut through paging.  At this point she was rude and made it difficult for me to even find out how to access this menu from the iPhone.  Hold down the number “1” I was finally told.  Next, hit “4” for options and then “7” for cut through paging.  I finally got off the phone after 59 minutes of vagueness and ill informed reps feeling like I’ll be taking a risk upgrading my phone.    </p>
<p>So, I tried these voicemail options just now on my iPhone 3G.  And guess what?  The tech support specialist was wrong.  First off, after hitting “4” for options you need to then dial “2” for administrative options.  At that menu, there is no option “7” for cut through paging.  I just spent 59 frustrating minutes on the phone trying to ensure I don’t lose a feature and in the end got nowhere.  This tech support specialist didn’t even know the correct menu options for voicemail on the iPhone.  Seriously?  I am so disappointed lately with AT&amp;T’s lack of interest holding on to long time customers and actually trying to figure things out and find solutions.  I am now leaning towards a Verizon iPhone 4 with its known network limitations.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ugh</title>
		<link>http://www.takebackthebeep.com/got-my-beep-back-baby/comment-page-1/#comment-99</link>
		<dc:creator>Ugh</dc:creator>
		<pubDate>Wed, 09 Mar 2011 18:37:55 +0000</pubDate>
		<guid isPermaLink="false">http://www.takebackthebeep.com/?p=61#comment-99</guid>
		<description>After being on hold and talking to 3 agents over 25 minutes I gave up.  Does anyone have a successful case number?</description>
		<content:encoded><![CDATA[<p>After being on hold and talking to 3 agents over 25 minutes I gave up.  Does anyone have a successful case number?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Shiggity</title>
		<link>http://www.takebackthebeep.com/got-my-beep-back-baby/comment-page-1/#comment-95</link>
		<dc:creator>Shiggity</dc:creator>
		<pubDate>Wed, 12 Jan 2011 01:13:58 +0000</pubDate>
		<guid isPermaLink="false">http://www.takebackthebeep.com/?p=61#comment-95</guid>
		<description>I maintain that this process is very &quot;adult&quot; as it requires a lot of patience and diplomacy to accomplish what should be a simple request.  What seemed to help me - although I&#039;m not out of the woods yet - was to reference previous case numbers filed that concerned this issue.  I&#039;ll follow up after I make more progress in case anyone wants the details.</description>
		<content:encoded><![CDATA[<p>I maintain that this process is very &#8220;adult&#8221; as it requires a lot of patience and diplomacy to accomplish what should be a simple request.  What seemed to help me &#8211; although I&#8217;m not out of the woods yet &#8211; was to reference previous case numbers filed that concerned this issue.  I&#8217;ll follow up after I make more progress in case anyone wants the details.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Chris Allen</title>
		<link>http://www.takebackthebeep.com/got-my-beep-back-baby/comment-page-1/#comment-93</link>
		<dc:creator>Chris Allen</dc:creator>
		<pubDate>Tue, 09 Nov 2010 14:06:27 +0000</pubDate>
		<guid isPermaLink="false">http://www.takebackthebeep.com/?p=61#comment-93</guid>
		<description>@Insider - My biggest reason for removing the prompts is that I use my iPhone for incoming business calls.  When a caller hears the prompts, it&#039;s obvious they&#039;re calling a cell phone.  I think a traditional voicemail sound, which has no prompts, is more professional.

My second biggest reason is that it&#039;s just plain annoying.  It&#039;s 2010.  Do we really need to be told to &quot;begin speaking after the tone&quot; and &quot;when done, hang up?&quot;

Thanks for clarifying the distinction between &quot;voicemail team&quot; and &quot;provisioning team.&quot;  We&#039;re operating completely in the dark when we talk to AT&amp;T Tech Support, so we&#039;re kind of at the mercy of whatever terminology that particular CSR is using at the time.</description>
		<content:encoded><![CDATA[<p>@Insider &#8211; My biggest reason for removing the prompts is that I use my iPhone for incoming business calls.  When a caller hears the prompts, it&#8217;s obvious they&#8217;re calling a cell phone.  I think a traditional voicemail sound, which has no prompts, is more professional.</p>
<p>My second biggest reason is that it&#8217;s just plain annoying.  It&#8217;s 2010.  Do we really need to be told to &#8220;begin speaking after the tone&#8221; and &#8220;when done, hang up?&#8221;</p>
<p>Thanks for clarifying the distinction between &#8220;voicemail team&#8221; and &#8220;provisioning team.&#8221;  We&#8217;re operating completely in the dark when we talk to AT&#038;T Tech Support, so we&#8217;re kind of at the mercy of whatever terminology that particular CSR is using at the time.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Insider</title>
		<link>http://www.takebackthebeep.com/got-my-beep-back-baby/comment-page-1/#comment-92</link>
		<dc:creator>Insider</dc:creator>
		<pubDate>Tue, 09 Nov 2010 13:58:46 +0000</pubDate>
		<guid isPermaLink="false">http://www.takebackthebeep.com/?p=61#comment-92</guid>
		<description>This is ridiculous. Of course it can be done, by someone on a provisioning team, but there is no such thing as a &quot;voicemail team&quot;. They are part of our switch technicians. There is no dedicated voicemail team. If you can get someone to file a ticket for you that&#039;s great, however you could just be an adult about it and deal with the prompts, which are there for the caller who wants to leave additional information such as a callback number or expedited message preference. You are actually only hurting your callers by removing the voicemail prompts.</description>
		<content:encoded><![CDATA[<p>This is ridiculous. Of course it can be done, by someone on a provisioning team, but there is no such thing as a &#8220;voicemail team&#8221;. They are part of our switch technicians. There is no dedicated voicemail team. If you can get someone to file a ticket for you that&#8217;s great, however you could just be an adult about it and deal with the prompts, which are there for the caller who wants to leave additional information such as a callback number or expedited message preference. You are actually only hurting your callers by removing the voicemail prompts.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

