<?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: Bell Canada &#8216;technical support&#8217;</title>
	<atom:link href="http://www.p2pnet.net/story/16698/feed" rel="self" type="application/rss+xml" />
	<link>http://www.p2pnet.net/story/16698</link>
	<description>p2pnet.net - reader powered</description>
	<lastBuildDate>Wed, 01 Feb 2012 15:11:09 -0300</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Reader's Write</title>
		<link>http://www.p2pnet.net/story/16698/comment-page-1#comment-686488</link>
		<dc:creator>Reader's Write</dc:creator>
		<pubDate>Tue, 12 Aug 2008 00:43:14 +0000</pubDate>
		<guid isPermaLink="false">http://www.p2pnet.net/story/16698#comment-686488</guid>
		<description>well, it is not that Ma Bell would be the first company with crappy phone support :-P

http://dir.salon.com/story/tech/feature/2004/02/23/no_support/index.html


And don&#039;t forget the old sketch by 3 dead trolls in a baggie

http://www.deadtroll.com/video/helldeskcable.html</description>
		<content:encoded><![CDATA[<p>well, it is not that Ma Bell would be the first company with crappy phone support <img src='http://www.p2pnet.net/wp-includes/images/smilies/icon_razz.gif' alt=':-P' class='wp-smiley' /> </p>
<p><a href="http://dir.salon.com/story/tech/feature/2004/02/23/no_support/index.html" rel="nofollow">http://dir.salon.com/story/tech/feature/2004/02/23/no_support/index.html</a></p>
<p>And don&#8217;t forget the old sketch by 3 dead trolls in a baggie</p>
<p><a href="http://www.deadtroll.com/video/helldeskcable.html" rel="nofollow">http://www.deadtroll.com/video/helldeskcable.html</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Rekrul</title>
		<link>http://www.p2pnet.net/story/16698/comment-page-1#comment-685680</link>
		<dc:creator>Rekrul</dc:creator>
		<pubDate>Mon, 11 Aug 2008 17:53:35 +0000</pubDate>
		<guid isPermaLink="false">http://www.p2pnet.net/story/16698#comment-685680</guid>
		<description>This type of thing isn&#039;t unique to Bell. My dialup ISP, LocalNet, was the same way whenever I called them about something. Periodically, their authentication server would go down, meaning that I couldn&#039;t login because it couldn&#039;t verify my information. If it lasted more than 20-30 minutes, I&#039;d give them a call and the first words out of the tech&#039;s mouth were always &quot;Ok, I need you to go into Dialup Networking...&quot; At this point, I&#039;d stop them and ask them to trying logging in from their terminal, which would invariably get the response &quot;Umm, yeah, it&#039;s not working here either...&quot; If I&#039;d followed their advice, they would have had me delete the DUN entry and create a new one from scratch.

I had frequent disconnects using a USR modem and they could never tell me why I kept getting disconnected all the time. When my average download speed went from an average of 6K/s to 2-3K/s, literally overnight, they blamed line noise. Even after I had the phone company test the line and pronounce it clearer than the average line, they still blamed my end. I had a professional IT tech run a couple tests on my account and he found the same problems. They ignored this. In the end, they claimed that an average speed of 2-3K/s was normal for dialup.</description>
		<content:encoded><![CDATA[<p>This type of thing isn&#8217;t unique to Bell. My dialup ISP, LocalNet, was the same way whenever I called them about something. Periodically, their authentication server would go down, meaning that I couldn&#8217;t login because it couldn&#8217;t verify my information. If it lasted more than 20-30 minutes, I&#8217;d give them a call and the first words out of the tech&#8217;s mouth were always &#8220;Ok, I need you to go into Dialup Networking&#8230;&#8221; At this point, I&#8217;d stop them and ask them to trying logging in from their terminal, which would invariably get the response &#8220;Umm, yeah, it&#8217;s not working here either&#8230;&#8221; If I&#8217;d followed their advice, they would have had me delete the DUN entry and create a new one from scratch.</p>
<p>I had frequent disconnects using a USR modem and they could never tell me why I kept getting disconnected all the time. When my average download speed went from an average of 6K/s to 2-3K/s, literally overnight, they blamed line noise. Even after I had the phone company test the line and pronounce it clearer than the average line, they still blamed my end. I had a professional IT tech run a couple tests on my account and he found the same problems. They ignored this. In the end, they claimed that an average speed of 2-3K/s was normal for dialup.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Reader's Write</title>
		<link>http://www.p2pnet.net/story/16698/comment-page-1#comment-685344</link>
		<dc:creator>Reader's Write</dc:creator>
		<pubDate>Mon, 11 Aug 2008 14:25:53 +0000</pubDate>
		<guid isPermaLink="false">http://www.p2pnet.net/story/16698#comment-685344</guid>
		<description>I can&#039;t stand Bell&#039;s Technical Support.
Basically the main issue I have is they require you to go through the whole troubleshooting process even though the issue is obvious.
2 years ago I was able to phone a support tech directly without having to go through the automated process.
But now that ability is blocked and now I have to call my buddy at bell on his cellphone to get things fixed asap
I&#039;m a very busy IT Admin who doesn&#039;t need to use the automated system since I have the knowledge needed to troubleshoot where the issue is coming from (9/10 times its bell, 1/10 times its faulty hardware)

Wake up Bell, your clients should be #1 not your bs ideas</description>
		<content:encoded><![CDATA[<p>I can&#8217;t stand Bell&#8217;s Technical Support.<br />
Basically the main issue I have is they require you to go through the whole troubleshooting process even though the issue is obvious.<br />
2 years ago I was able to phone a support tech directly without having to go through the automated process.<br />
But now that ability is blocked and now I have to call my buddy at bell on his cellphone to get things fixed asap<br />
I&#8217;m a very busy IT Admin who doesn&#8217;t need to use the automated system since I have the knowledge needed to troubleshoot where the issue is coming from (9/10 times its bell, 1/10 times its faulty hardware)</p>
<p>Wake up Bell, your clients should be #1 not your bs ideas</p>
]]></content:encoded>
	</item>
</channel>
</rss>


