<?xml version='1.0' encoding='UTF-8'?><?xml-stylesheet href="http://www.blogger.com/styles/atom.css" type="text/css"?><feed xmlns='http://www.w3.org/2005/Atom' xmlns:openSearch='http://a9.com/-/spec/opensearchrss/1.0/' xmlns:georss='http://www.georss.org/georss' xmlns:gd='http://schemas.google.com/g/2005' xmlns:thr='http://purl.org/syndication/thread/1.0'><id>tag:blogger.com,1999:blog-14041380</id><updated>2012-02-04T13:41:11.040-05:00</updated><title type='text'>Inside Tech Support</title><subtitle type='html'>An insider's view of the OOL technical support call center.  I am an OOL techical support representative and I've created this blog to give you an insight into the workings of the call center as well as help you get inside the mind of the guy who is helping you.</subtitle><link rel='http://schemas.google.com/g/2005#feed' type='application/atom+xml' href='http://ooltech.blogspot.com/feeds/posts/default'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/14041380/posts/default?max-results=100'/><link rel='alternate' type='text/html' href='http://ooltech.blogspot.com/'/><link rel='hub' href='http://pubsubhubbub.appspot.com/'/><author><name>OOL Tech</name><uri>http://www.blogger.com/profile/05819125769089611661</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><generator version='7.00' uri='http://www.blogger.com'>Blogger</generator><openSearch:totalResults>23</openSearch:totalResults><openSearch:startIndex>1</openSearch:startIndex><openSearch:itemsPerPage>100</openSearch:itemsPerPage><entry><id>tag:blogger.com,1999:blog-14041380.post-113867267352034647</id><published>2006-01-31T01:46:00.000-05:00</published><updated>2006-01-30T21:24:16.863-05:00</updated><title type='text'>Last Post</title><content type='html'>This is my last post as &lt;b&gt;OOLTech&lt;/b&gt;.&lt;br /&gt;&lt;br /&gt;When I started this blog I had a few areas I wanted to explore. The pressures we techs are under, the type of people we have to deal with, incompetence, etc. As time went on more topics came to mind. But two things have happened: 1) &lt;b&gt;I'm out of ideas&lt;/b&gt; and 2)&lt;b&gt; I've moved on&lt;/b&gt;.&lt;br /&gt;&lt;br /&gt;Yes, the good news is that I am now with &lt;b&gt;a company that appreciates me&lt;/b&gt; and &lt;b&gt;pays me what I'm worth.&lt;/b&gt;  Management treats me &lt;b&gt;like a human being&lt;/b&gt;, the work is interesting and varied and &lt;b&gt;I'm not under a microscope&lt;/b&gt; as soon as I walk into the building.  &lt;b&gt;Life is now good&lt;/b&gt;.&lt;br /&gt;&lt;br /&gt;I wish I had back the time I spent in that shithole, I really believe that if I didn't have this blog to vent in, &lt;b&gt;I  would have gone postal&lt;/b&gt;.&lt;br /&gt;&lt;br /&gt;Thanks, all, for reading and I hope I accomplished my primary mission:  &lt;i&gt;to give you an insight into the workings of the call center as well as help you get inside the mind of the guy who is helping you.&lt;/i&gt;&lt;br /&gt;&lt;br /&gt;And now it is time to &lt;b&gt;reveal my identity&lt;/b&gt;:  All of you that work in the call center know me as&lt;br /&gt;&lt;br /&gt;&lt;b&gt; +++NO CARRIER+++....&lt;/b&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/14041380-113867267352034647?l=ooltech.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://ooltech.blogspot.com/feeds/113867267352034647/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=14041380&amp;postID=113867267352034647' title='50 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/14041380/posts/default/113867267352034647'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/14041380/posts/default/113867267352034647'/><link rel='alternate' type='text/html' href='http://ooltech.blogspot.com/2006/01/last-post.html' title='Last Post'/><author><name>OOL Tech</name><uri>http://www.blogger.com/profile/05819125769089611661</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>50</thr:total></entry><entry><id>tag:blogger.com,1999:blog-14041380.post-113461768474689440</id><published>2005-12-23T04:45:00.000-05:00</published><updated>2005-12-24T17:14:55.313-05:00</updated><title type='text'>Bonus time</title><content type='html'>It's that time of year, the time of year when some companies &lt;b&gt;reward their loyal workers&lt;/b&gt; with a &lt;b&gt;Christmas bonus.&lt;/b&gt;  Luckily for us, &lt;b&gt;Cablevision is one of those companies.&lt;/b&gt;&lt;br /&gt;&lt;br /&gt;I know that there are plenty of companies that &lt;b&gt;do not give out Christmas bonuses&lt;/b&gt;.  And I &lt;b&gt;commend and thank Cablevision's management&lt;/b&gt; for giving us bonuses.  But that will not stop me from &lt;b&gt;looking a gift horse in the mouth&lt;/b&gt;.&lt;br /&gt;&lt;br /&gt;The Christmas bonus &lt;b&gt;does not appear to be based on anything but grade level&lt;/b&gt;. Not time of service, not performance incentives, it is simply based on your position in the company. And you know our position in the company, at the bottom to where all the shit flows, and that also can describe our bonus.&lt;br /&gt;&lt;br /&gt;I know I may be biased but we &lt;b&gt;call center workers are the hardest working employees that Cablevision has&lt;/b&gt;. And that is due to the incredible volume of calls that we handle combined with the &lt;a href="http://ooltech.blogspot.com/2005/08/statistics.html"&gt;Statistics&lt;/a&gt; we are forced to maintain.&lt;br /&gt;&lt;br /&gt;So for all our &lt;a href="http://ooltech.blogspot.com/2005/07/managements-obsession.html"&gt;hard work&lt;/a&gt;, &lt;a href="http://ooltech.blogspot.com/2005/08/managements-obsession-part-ii.html"&gt;stress&lt;/a&gt; and &lt;a href="http://ooltech.blogspot.com/2005/07/power-users.html"&gt;aggravation&lt;/a&gt;, Cablevision throws us a bone and gives us &lt;b&gt;ONE weeks pay&lt;/b&gt;.  That's right, we get a check containing a whopping &lt;b&gt;1/52&lt;/b&gt;of our yearly salary.&lt;br /&gt;&lt;br /&gt;Of course &lt;b&gt;the higher up in the company, the greater the percentage of your salary you get&lt;/b&gt;. It is not enough that they make so much more money, their bonus has to be a greater percent of their salary, up to 40% and more at the management level! &lt;b&gt;It's not like Cablevision skimps on management's salary&lt;/b&gt;, in addition to their 6 figure salary, they get $30K-$90K as a bonus? &lt;b&gt;What the Fuck?&lt;/b&gt;&lt;br /&gt;&lt;br /&gt;IMO, &lt;b&gt;that's bullshit&lt;/b&gt;.&lt;br /&gt;&lt;br /&gt;So while &lt;b&gt;management goes yacht shopping&lt;/b&gt;, &lt;b&gt;I get to hand over my bonus to a mechanic&lt;/b&gt; to keep my 10 year old POS car running.&lt;br /&gt;&lt;br /&gt;One week's friggin' pay......Merry Fucking Christmas.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/14041380-113461768474689440?l=ooltech.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://ooltech.blogspot.com/feeds/113461768474689440/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=14041380&amp;postID=113461768474689440' title='19 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/14041380/posts/default/113461768474689440'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/14041380/posts/default/113461768474689440'/><link rel='alternate' type='text/html' href='http://ooltech.blogspot.com/2005/12/bonus-time.html' title='Bonus time'/><author><name>OOL Tech</name><uri>http://www.blogger.com/profile/05819125769089611661</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>19</thr:total></entry><entry><id>tag:blogger.com,1999:blog-14041380.post-112597009449807161</id><published>2005-11-11T23:15:00.000-05:00</published><updated>2005-11-11T23:19:30.553-05:00</updated><title type='text'>Unionizing</title><content type='html'>There has been an underground movement going on at TSG (Tech Support Group) to &lt;b&gt;Unionize&lt;/b&gt;.  The problem is, it is so underground that it is invisible.  I didn't know one existed until after I started this blog.&lt;br /&gt;&lt;br /&gt;A unionizing effort has been going on among &lt;b&gt;Field Techs&lt;/b&gt; for quite a while. They seem to be pretty well organized, (you see their bumper stickers everywhere &lt;b&gt;Cablevision Techs Need Respect&lt;/b&gt;), and they have a &lt;a href="http://www.cablevisiontechsneedrespect.com/"&gt;website&lt;/a&gt;.  The unionizing effort at TSG is NOT organized but at least they have a website, &lt;a href="http://www.organizetsg.com/"&gt;Organize TSG&lt;/a&gt;. One reason why there is no coordinated union organizing going on is the &lt;b&gt;revolving door nature of employment&lt;/b&gt; at TSG. Many of the original union agitators have moved on to other jobs, voluntarily or not.&lt;br /&gt;&lt;br /&gt;Let's see why &lt;span style=";font-size:110;color:red;"  &gt;Unionizing may be a good idea&lt;/span&gt;.&lt;br /&gt;&lt;br /&gt;One of the biggest problems in TSG is the rapid turnover.  As stated in a previous &lt;a href="http://ooltech.blogspot.com/2005/07/incompetence.html"&gt;post&lt;/a&gt;, new hires are temporary employees making about $11/hour.  Maybe Management's thinking goes as such:  &lt;i&gt;Hire cheap and quick so when they leave, because the job is so difficult, you can replace them quickly and cheaply&lt;/i&gt;.  Maybe this makes sense if you only look at the numbers and we all know that Management is all about &lt;a href="http://ooltech.blogspot.com/2005/07/managements-obsession.html"&gt;the&lt;/a&gt; &lt;a href="http://ooltech.blogspot.com/2005/08/managements-obsession-part-ii.html"&gt;numbers &lt;/a&gt;.Management is too short sighted to see this but this is a self-fulfilling prophecy. When techs are hired at $11/hr they really don't have anything invested into staying. Hell, you'd probably make almost as much flipping burgers. The first couple of months are really hard and a tech needs to grow into the job. Starting at $11/yr makes it a lot easier for someone to give up easily. If Cablevision offered a higher starting rate of pay (with benefits like health insurance), I can guarantee you that techs would stick with it a lot longer. &lt;b&gt;Techs who stay around longer become better techs. Better techs mean better tech support. Better tech support means better customer service.&lt;/b&gt; Oh, there's the problem, as I have stated before, Management has no desire to truly improve customer service, they'd rather put a band-aid, aka &lt;a href="http://ooltech.blogspot.com/2005/08/managements-obsession-part-ii.html"&gt;BPA&lt;/a&gt;, on the gaping wound that is customer service.&lt;br /&gt;&lt;br /&gt;&lt;span style="color:red;"&gt;Unionizing would give a higher starting salary, techs would stick with the job, become better and customer service would improve.&lt;/span&gt;&lt;br /&gt;&lt;br /&gt;A big thing we lack here is a fair grievance procedure. Right now if you are a temp, at any time a supervisor can fire you for any stupid reason at all. And if you are a permanent employee they have a huge list of transgressions that will get you &lt;i&gt;written up&lt;/i&gt;.  And of course if you get &lt;i&gt;written up&lt;/i&gt;, down will come &lt;b&gt;the Iron Fist of Management&lt;/b&gt;. First of all, it will reset any progress you have made toward any "career progression" (aka a promotion to the next grade level). If you had been assigned to any of the coveted TSG positions (&lt;b&gt;Comm Desk&lt;/b&gt;, &lt;b&gt;Offline Team&lt;/b&gt;, &lt;b&gt;Live Support&lt;/b&gt;(which takes you off the phone 3 days a week!) you are busted back to the phones full time. A decent grievance procedure can prevent a supervisor with a grudge from abusing his authority.  &lt;br /&gt;&lt;br /&gt;&lt;span style="color:red;"&gt;Unionizing will allow techs to be treated like human beings and be a defense against heavy handed management.&lt;/span&gt;&lt;br /&gt;&lt;br /&gt;Techs need input into the ridiculous work rules, partially covered in my &lt;a href="http://ooltech.blogspot.com/2005/08/statistics.html"&gt;stats&lt;/a&gt; and &lt;a href="http://ooltech.blogspot.com/2005/08/managements-obsession-part-ii.html"&gt;BPA&lt;/a&gt; posts, and someone needs to address the lousy &lt;a href="http://ooltech.blogspot.com/2005/06/working-conditions.html"&gt;Working Conditions&lt;/a&gt; around here. Taking call after call after call is simply grueling, one way to prevent burn-out would be to space out the calls, say a mandatory 1 minute break between calls. The stats have to be overhauled to make it reflect reality and BPA needs a lot of work to make it work right.&lt;br /&gt;&lt;br /&gt;&lt;span style="color:red;"&gt;Unionizing will be good for a tech's well being. A tech who is not overly stressed is a better tech. Better techs mean better customer service. &lt;/span&gt;&lt;br /&gt;&lt;br /&gt;There is no advancement in this department and management’s idea of &lt;i&gt;career progression&lt;/i&gt; is a joke. They have no clearly defined career ladder, simply a series of increasingly difficult to maintain level of stats to match for 6 months before your salary grade level goes up. Once you make that grade, you have to maintain your stats or you get &lt;i&gt;written up&lt;/i&gt;. Get written up a couple of times, and your ass is out the door. That’s management’s way of keeping control of salaries, make goals unrealistic and get rid of the ones who happen to reach them.&lt;br /&gt;&lt;br /&gt;Many techs scour the internal job postings each day desperately looking for a way out. TSG is comprised of many, many talented people but this resource is little used by other departments. Techs have a hard time even landing an interview for an internal position. And even if they are granted an interview, the fact that they work in TSG is held against them.&lt;br /&gt;&lt;br /&gt;&lt;span style="color:red;"&gt;Unionizing will provide a well defined and fair career progression. I’m sure it will not help with the other departments' bias against TSG but since they not hiring us now, that shouldn’t matter &lt;/span&gt;&lt;br /&gt;&lt;br /&gt;I think it is quite clear that &lt;B&gt;Unionizing&lt;/b&gt; is the best thing for techs at TSG and I believe it will help the customer by improving customer service.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/14041380-112597009449807161?l=ooltech.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://ooltech.blogspot.com/feeds/112597009449807161/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=14041380&amp;postID=112597009449807161' title='29 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/14041380/posts/default/112597009449807161'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/14041380/posts/default/112597009449807161'/><link rel='alternate' type='text/html' href='http://ooltech.blogspot.com/2005/11/unionizing.html' title='Unionizing'/><author><name>OOL Tech</name><uri>http://www.blogger.com/profile/05819125769089611661</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>29</thr:total></entry><entry><id>tag:blogger.com,1999:blog-14041380.post-112942981288113914</id><published>2005-10-16T02:22:00.000-04:00</published><updated>2005-10-17T16:37:47.526-04:00</updated><title type='text'>Settlement</title><content type='html'>Here is a how one tech made a difference and an excellent example of how Cablevision's call center management treats us workers.  &lt;br /&gt;&lt;br /&gt;For many years, TSG's official policy was to have a tech take calls as soon as his shift starts.  This ignores the fact it can take more than 10 minutes to log in and get all the needed programs started and logged in to.&lt;br /&gt;&lt;br /&gt;As was indoctrinated in us during training, &lt;b&gt;You are being paid to take calls&lt;/b&gt;.   But Management screws us two ways.  The call center is very, very crowded, and if your shift starts during "prime time", it is hard to find a seat.  You have to wait for someone's shift to end.  When your shift starts you have to &lt;i&gt;sign in&lt;/i&gt; to the phone system, and since you aren't ready to take a call, you have to &lt;i&gt;sign out&lt;/i&gt;.  Eevery moment you are working is monitored, you have to put a reason why you have &lt;i&gt;signed out&lt;/i&gt;, in this case "system issues" would be a good choice. These reasons are tracked and at the end of the month your supervisor will discuss your stats with you. The fact that you &lt;b&gt;signed out&lt;/b&gt; to system issues is guaranteed to be brought up.  This is yet another stat that Management will use against you at raise time.&lt;br /&gt;&lt;br /&gt;But if you were lucky enough to find a seat before your shift, or start at a time when it is less crowded, you were expected to log in to your computer , start all your applications and log into them.  &lt;B&gt;All before your shift starts&lt;/b&gt;.  That this &lt;b&gt;was wrong&lt;/b&gt; was brought up &lt;b&gt;numerous times&lt;/b&gt;.  I myself brought it up in monthly meetings.  Management didn't care and told us &lt;i&gt;that's just the way it is&lt;/i&gt;.&lt;br /&gt;&lt;br /&gt;Finally a tech was let go for only Management knows why and he &lt;b&gt;did something about it&lt;/b&gt; he consulted a lawyer.  It was obvious that Cablevision had broken labor laws.  Obvious to everyone but Management.  Or maybe &lt;b&gt;they just didn't care&lt;/b&gt;.&lt;br /&gt;&lt;br /&gt;A &lt;a ref="http://www.lawcash.com/attorney/3525/cablevision-systems-lawsuit.asp"&gt;lawsuit&lt;/a&gt; was filed, it turned into a class action, and Cablevision folded like a cheap suit.&lt;br /&gt;&lt;br /&gt;&lt;b&gt;I got my settlement check today&lt;/B&gt; and thanks to &lt;b&gt;Robert Wolfson&lt;/b&gt;, I'll be able to go to a couple of nice restaurants for dinner.  &lt;B&gt;Thanks, Rob for standing up for the little guy&lt;/b&gt;.&lt;br /&gt;&lt;br /&gt;After the lawsuit was filed, Management &lt;b&gt;finally&lt;/b&gt; smartened up and changed their policy.  Now we have &lt;b&gt;a whole 5 minutes&lt;/b&gt; to log in.  Not really enough time for us but enough for Cablevision to avoid another lawsuit.&lt;br /&gt;&lt;br /&gt;So what's the moral of the story?  I guess it is that Cablevision engages in unethical and illegal business practices and only will change if forced do by the courts......&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/14041380-112942981288113914?l=ooltech.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://ooltech.blogspot.com/feeds/112942981288113914/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=14041380&amp;postID=112942981288113914' title='27 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/14041380/posts/default/112942981288113914'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/14041380/posts/default/112942981288113914'/><link rel='alternate' type='text/html' href='http://ooltech.blogspot.com/2005/10/settlement.html' title='Settlement'/><author><name>OOL Tech</name><uri>http://www.blogger.com/profile/05819125769089611661</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>27</thr:total></entry><entry><id>tag:blogger.com,1999:blog-14041380.post-112632133428316511</id><published>2005-09-21T21:50:00.000-04:00</published><updated>2005-09-23T20:47:53.346-04:00</updated><title type='text'>Tools</title><content type='html'>One reason why we need all those &lt;a href="http://ooltech.blogspot.com/2005/09/uptraining.html"&gt;Uptrainings&lt;/a&gt; is that we have to work with a mishmash of outdated and poorly integrated tools.  You'd think that once you call in and give the tech your phone number, up pops all your information, right at his fingertips.  &lt;b&gt;HA!&lt;/B&gt;  This is Cablevision, the place where while you are on the phone navigating those endless menus, you enter in your phone number but then have to tell it to the tech when you finally reach a human.  Didn't you just give the menu system your phone number? (Or rather didn't you give it 5+ minutes ago? :( )  Why is the tech asking for it again?  &lt;b&gt;Because Cablevision is &lt;a href="http://ooltech.blogspot.com/2005/07/incompetence.html"&gt;incomptent!&lt;/a&gt;&lt;/b&gt;.  That should be your first clue that we are (by Mangement's design) totally disorganized.&lt;br /&gt;&lt;br /&gt;In the call center we use a ticket tracking application called Remedy.  After we request your phone number (carefully following the &lt;B&gt;&lt;a href="http://ooltech.blogspot.com/2005/08/managements-obsession-part-ii.html"&gt;BPA&lt;/a&gt;&lt;/B&gt; procedures) we enter it and hope your name comes up.  There are a number of reasons why your name may not show up, but the most common is that you've gotten a new phone number (like a new OV number, or you may have moved) but your account is still listed under your old phone number.  When you order OV and are given the new number, why isn't your account updated to reflect that? It's because of the poor integration.  What happens in one application often isn't reflected in another. &lt;br /&gt;&lt;br /&gt;Here is an example of their poor integration.  Let's say you move and you take your modem and your IO boxes with you.  What Cablevision does is disconnect your old account and create a new one.  Your modem mac ID and IO box ID will probably be left attached to your old account.  In a couple of weeks your TV and modem service stops working because &lt;i&gt;The System&lt;/i&gt; does not recognize those boxes as being attached to a valid account.  You call up customer service (not tech support) and the Customer Service Rep fixes your problem.  Now why wasn't it done automatically?  Because it is a manual process, there is no way to link accounts.  This happens &lt;b&gt;all the time&lt;/b&gt;.  But guess where your email address is and will stay forever?  Yep, attached to your old account.  The CSR knows nothing email addresses, they are just concerned with the box numbers.  There are tens of thousands of email addresses attached to disconnected accounts.  Can Cablevision go in and clean out old disconnected email addresses?  &lt;b&gt;Nope!&lt;/b&gt;  They may be used by a customer who has simply moved!  That means if you ever drop OOL, you can pretty much guarantee on using your email address forever.  This brings up another problem, remember &lt;B&gt;Bulk Mail&lt;/b&gt;?  Cablevision's vaunted &lt;i&gt;SpamAway&lt;/i&gt; was to put any identifed &lt;B&gt;Spam&lt;/b&gt; into your bulk mail folder where you could review it for mistakes and report any errors.  That lasted how long, six months?  And I believe this is why, there are tens of thousands of unused email addresses that are no longer being used but still get &lt;b&gt;Spam&lt;/b&gt;.  These emails never get deleted and use up valuable disk space.  The &lt;a href="http://ooltech.blogspot.com/2005/07/incompetence.html"&gt;BISC's&lt;/a&gt; only option was to remove the &lt;b&gt;Bulk Mail&lt;/b&gt; capability in order to reduce disk space.  After all, they can't delete email addresses because they have no idea which are are being used by paying customers and which are not!&lt;br /&gt;&lt;br /&gt;Back to the tools.....&lt;br /&gt;&lt;br /&gt;Let's say we are unable to bring up your account in Remedy but you have your account number handy.  You would think we could bring up your account in Remedy using your account number.  &lt;b&gt;NOPE!&lt;/b&gt;  That would make it too easy for us.  We have to go to another application which accesses the repository of all the customer's billing and service information, &lt;b&gt;Cabledata&lt;/b&gt;.  This POS is a text program which runs in a DOS window.  Believe it or not it is a 16 bit application!  For you non-technical people out there, that shit went out with Windows 95!  Being a text program it is comprised mostly of short acronyms and codes and there are &lt;b&gt;HUNDREDS&lt;/b&gt; of them.  Do we get training on them?  See  &lt;a href="http://ooltech.blogspot.com/2005/09/uptraining.html"&gt;Uptrainings&lt;/a&gt; for an answer on that!  When all we had to do in &lt;b&gt;Cabledata&lt;/b&gt; was to set up truck rolls to fix signal problems it was easy, but then Management dumped all sorts of other responsibilies on us (fixing rates, Changes of service, OV issues,etc).  More responsibility = more pay, right?  &lt;b&gt;HAHAHAHAHA!&lt;/b&gt;  Not in the Cablevision universe!  And the lack of training we get causes errors to be made all the time.  Since we really don't know what we are doing with &lt;b&gt;Cabledata&lt;/b&gt; it is very easy to remove existing services when we make a change to another service.  So if that happens to you, don't blame the tech, blame Cablevision's management for their incomptetent &lt;a href="http://ooltech.blogspot.com/2005/09/uptraining.html"&gt;Training&lt;/a&gt; procedures.&lt;br /&gt;&lt;br /&gt;Remedy and Cabledata are the two main account tools we use but there are a bunch of others.  And testing is never done by the Corp IS idiots.  Man, I should have included those boneheads in my &lt;a href="http://ooltech.blogspot.com/2005/07/incompetence.html"&gt;incompetence&lt;/a&gt; entry.  If we get a new version of a tool, you can guarantee that their will be big problems for the first few days and then they will remove the tool until it is fixed.  Half the time they don't even restore the old version so basically you are &lt;b&gt;SOL&lt;/b&gt;!   Anyway, at any one time we probably have 15+ windows open.  And there is no built-in integration in any of them.  What we have to do is cut and paste and cut and paste.&lt;br /&gt;&lt;br /&gt;There is one bright spot in this mess of tools, a very smart and enterprising tech took it upon himself to write a program (on his own time!) to try to integrate a number of these tools.  It's not perfect and has its flaws but it is &lt;b&gt;MILES&lt;/b&gt; beyond what Cablevision provides us.  He distributed this to a few fellow techs and management noticed their stats improved.  In a rare stroke of intelligence they asked him to continue to improve his program and distributed it to the rest of the call center techs.  For what this guy does, he should get $50/hr.  Cablevision is getting a 60% discount on his programming! &lt;B&gt;BUT&lt;/b&gt; he was still just a &lt;b&gt;phone monkey&lt;/b&gt;.  He was allowed a couple of days a week to work on his program but the other days he had to be a phone tech.  This guy was far more valuable working on his program than answering phones.  But it's like I've said before, &lt;b&gt;Cablevision just cares about throwing bodies at the &lt;/b&gt;&lt;a href="http://ooltech.blogspot.com/2005/07/managements-obsession.html"&gt;queue&lt;/a&gt;.   Eventually his reward was a promotion to the Corporate IS department.  There was no increase in pay of course, I'm sure Management must think &lt;b&gt;that he should just be happy he's off the phones.....&lt;/b&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/14041380-112632133428316511?l=ooltech.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://ooltech.blogspot.com/feeds/112632133428316511/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=14041380&amp;postID=112632133428316511' title='51 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/14041380/posts/default/112632133428316511'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/14041380/posts/default/112632133428316511'/><link rel='alternate' type='text/html' href='http://ooltech.blogspot.com/2005/09/tools.html' title='Tools'/><author><name>OOL Tech</name><uri>http://www.blogger.com/profile/05819125769089611661</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>51</thr:total></entry><entry><id>tag:blogger.com,1999:blog-14041380.post-112441628912931192</id><published>2005-09-06T11:00:00.000-04:00</published><updated>2005-09-06T11:20:20.623-04:00</updated><title type='text'>Uptraining</title><content type='html'>Training around here is nothing but a bad joke.  When you get frustrated with an incompetent tech, don't take it out on the tech, it is not his fault, it is Management's inability to properly train the tech and keep them up to date.  I've already detailed the abysmal &lt;a href="http://ooltech.blogspot.com/2005/07/incompetence.html"&gt;training&lt;/a&gt; given to new techs and how it could be improved.  But after you get on the phones, Management feels that any new features that OOL provides can be handled in a quick 45 minute or so &lt;i&gt;Uptraining&lt;/i&gt;.  &lt;I&gt;Uptraining&lt;/i&gt;.  WTF does that mean?  &lt;i&gt;Uptraining&lt;/i&gt;.  The way management is around here it is more like Up&lt;i&gt; your ass &lt;/i&gt;training.&lt;br /&gt;&lt;br /&gt;Every couple of weeks you will get an appointment for a &lt;i&gt;Uptraining&lt;/i&gt;.  These &lt;i&gt;Uptrainings&lt;/i&gt; will be on either new tools or new features that OOL supports.  They are usually scheduled for 45-90 minutes and are held in a conference room.  A &lt;b&gt;"lead"&lt;/b&gt; technician hosts the &lt;i&gt;Uptraining&lt;/i&gt; and hands out a photocopied document that details "everything" you would need to know about the new feature/tool.  Do we have any computers to view or work with the new feature/tool?  No, but the photocopy has screenshots! Yay! Screenshots!  WooHoo!  So how is the class conducted?  The &lt;b&gt;"lead"&lt;/b&gt; will sit at the head of the conference table and in a monotone, simply read off &lt;b&gt;every fucking line in the document&lt;/b&gt;.  As you can imagine, this is about as informative as watching ice melt. The sad part is you look forward to such &lt;i&gt;Uptrainings&lt;/i&gt;, it gets you off the phones and away from &lt;a href="http://ooltech.blogspot.com/2005/07/customers.html"&gt;customers&lt;/a&gt;.&lt;br /&gt;&lt;br /&gt;These &lt;i&gt;Uptrainings&lt;/i&gt; are supposed to provide the absolute minimum needed to perform the required function.  How to handle anything out of the ordinary is not detailed at all.  So the &lt;i&gt;Uptraining&lt;/i&gt; might be useful 50% of the time.  The rest of the time, well, good luck &lt;a href="http://ooltech.blogspot.com/2005/07/managements-obsession.html"&gt;finding a lead&lt;/a&gt;.&lt;br /&gt;&lt;br /&gt;Another useful thing that was suggested to Management (and promptly relegated to the circular file) is to provide refresher &lt;i&gt;Uptrainings&lt;/i&gt;.  Quite a few times I have talked to fellow techs about a customer's problem I solved and have had the tech tell me "I forgot about that".  But the reason why Management won't do that ties in with the following.&lt;br /&gt;&lt;br /&gt;The hell with keeping techs well trained and able to properly help the customer, what did I state earlier is the most important thing to Management?  That's right, their &lt;a href="http://ooltech.blogspot.com/2005/07/managements-obsession.html"&gt;ASA&lt;/a&gt;.  It doesn't matter if you are scheduled for an &lt;i&gt;Uptraining&lt;/i&gt;, if there is a queue of customers waiting to talk to a tech (and there is &lt;b&gt;ALWAYS&lt;/b&gt; a queue), &lt;I&gt;Uptrainings&lt;/i&gt; are cancelled.  Of course they are supposed to be rescheduled but what happens?  Yep, another queue, &lt;I&gt;Uptrainings&lt;/i&gt; are cancelled again.  Eventually the &lt;i&gt;Uptraining&lt;/i&gt; is forgotten about and then you are on your own. When new features roll out as the new OV portal did recently, I'm sure when customers called in about it, they knew more about what it does than the tech did!&lt;br /&gt;&lt;br /&gt;Other methods of training consist of leads coming around while you are on the phone, dropping off a document and then they make you sign that you read it.  Or it is emailed to you.  When do I have time to read these documents?  Oh that's right, management allows me all of 5 minutes at the beginning of my shift to log in, setup all the tools I need and then go through my email to read and digest these documents.    Or while I am on the phone with a customer I might recall there is something in my stack of documents I have to carry back and forth to work (remember, we aren't given &lt;a href="http://ooltech.blogspot.com/2005/06/working-conditions.html"&gt;drawers&lt;/a&gt; to store our stuff in) that may have something to do with his problem.  &lt;b&gt;Let's see how  Management can screw us.&lt;/b&gt;  If I put the customer on hold, I run the risk of exceeding my hold time &lt;a href="http://ooltech.blogspot.com/2005/08/statistics.html"&gt;stat&lt;/a&gt;.  If I tell the customer &lt;i&gt;Let me research your issue&lt;/i&gt; and &lt;b&gt;NOT&lt;/b&gt; put him on hold, I have to watch out for &lt;a href="http://ooltech.blogspot.com/2005/08/managements-obsession-part-ii.html"&gt;BPA&lt;/a&gt; and fill in the silences.  Yet again, Management sets up the tech to bullshit the customer and not fix his problem.    As we have &lt;a href="http://ooltech.blogspot.com/2005/08/statistics.html"&gt;seen&lt;/a&gt;, it is not in either the tech's nor Management's best interest to help the customer.&lt;br /&gt;&lt;br /&gt;When you speak to a tech remember one thing.  &lt;b&gt;The tech on the phone is considered by Management to be nothing but a phone answering piece of meat.&lt;/b&gt;  The tech only exists to lower the &lt;a href="http://ooltech.blogspot.com/2005/07/managements-obsession.html"&gt;ASA&lt;/a&gt;.  All management cares about is that you get off the phone as quickly as possible.  They don't care if your problem was fixed, they don't care if the tech knows WTF he is talking about, they simply care about you hanging up the phone ASAP.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/14041380-112441628912931192?l=ooltech.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://ooltech.blogspot.com/feeds/112441628912931192/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=14041380&amp;postID=112441628912931192' title='37 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/14041380/posts/default/112441628912931192'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/14041380/posts/default/112441628912931192'/><link rel='alternate' type='text/html' href='http://ooltech.blogspot.com/2005/09/uptraining.html' title='Uptraining'/><author><name>OOL Tech</name><uri>http://www.blogger.com/profile/05819125769089611661</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>37</thr:total></entry><entry><id>tag:blogger.com,1999:blog-14041380.post-112441550964227893</id><published>2005-08-25T02:28:00.000-04:00</published><updated>2005-08-27T00:10:36.383-04:00</updated><title type='text'>Management's obsession - Part II</title><content type='html'>When you call in, do you ever have the feeling you are talking to a machine?  That the techs all say the same thing in the same way?  That their speech pauses in awkward places in their opening? Do the techs ever repeat your questions back to you as a statement or talking around an issue instead of saying no?   If so, it is all because of &lt;b&gt;BPA&lt;/b&gt;.&lt;br /&gt;&lt;br /&gt;&lt;B&gt;BPA&lt;/b&gt; is management's other obsession, their most important tech statistic of all.  As stated previously, this stat has nothing to do with your technical ability to fix the customer's problem. In fact you can completely botch the call and you can still score a 100%!  All that matters is that the tech says the proper things to the customer.  This stat counts for 50% of a tech's rating.&lt;br /&gt;&lt;br /&gt;As usual with Cablevision, on paper this looks good but it fails miserably in practice. You are monitored, randomly, 3 times a month.  For Each call you are graded on the following:&lt;br /&gt;&lt;UL&gt;&lt;br /&gt;&lt;LI&gt;Corporate Response&lt;br /&gt;&lt;LI&gt;Uses Positive Words and Phrases&lt;br /&gt;&lt;LI&gt;Upbeat Tone / Sounds Interested&lt;br /&gt;&lt;LI&gt;Bridges One Part of Call to Another&lt;br /&gt;&lt;LI&gt;Filling Silences&lt;br /&gt;&lt;LI&gt;Offers Help Before Being Asked&lt;br /&gt;&lt;LI&gt;Actively Listens&lt;br /&gt;&lt;LI&gt;Acknowledges Customer/Offers Action&lt;br /&gt;&lt;LI&gt;Identifies Needs&lt;br /&gt;&lt;LI&gt;Takes Ownership&lt;br /&gt;&lt;LI&gt;Focuses on Solution&lt;br /&gt;&lt;LI&gt;Summarizes/Gains Agreement&lt;br /&gt;&lt;LI&gt;Closes Call Politely&lt;br /&gt;&lt;/UL&gt;&lt;br /&gt;&lt;br /&gt;&lt;B&gt;Corporate Response&lt;/b&gt;&lt;br /&gt;The opening of all calls should techs should be the same:  &lt;i&gt;Cablevision, Technical support, my name is Joey, how may I help you&lt;/i&gt;.   Sounds reasonable, right?  But in practice Cablevision fucks it all up.  They expect a half second pause between each phrase.  If you don't pause, you get it marked wrong.  I can understand the desire not to have a tech give you a run on sentence:  &lt;i&gt;CablevisionTechnicalsupportmynameisJoeyhowmay Ihelpyou&lt;/i&gt;, but enforcing a pause for each phrase is ridiculous.  In my experience, all a customer needs to here is &lt;B&gt;Cablevision&lt;/b&gt; or &lt;B&gt;Technical support&lt;/b&gt; and they jump in and start talking.  Meanwhile you are trying to finish your &lt;b&gt;Corporate Response&lt;/b&gt;.  So you're fucked both ways, you are either marked wrong for interrupting the customer or you are marked wrong for not finishing the &lt;b&gt;Corporate Response&lt;/B&gt;.  But wait, the micro managing of the call gets better.&lt;br /&gt;&lt;br /&gt;&lt;b&gt;Uses Positive Words and Phrases&lt;/b&gt;&lt;br /&gt;This should be titled &lt;b&gt;Does not use negative words&lt;/b&gt;.  That's right, you can't tell the customer &lt;b&gt;No&lt;/B&gt;.  Or you can't tell the customer &lt;b&gt;they are doing something wrong&lt;/B&gt;.  You have to talk around it. Even if a customer asks a simple question.  &lt;i&gt;Does Optimum Online support IMAP&lt;/i&gt;?  You can't say &lt;b&gt;No&lt;/b&gt;.  You have to word it so you don't hurt the customer's feelings.  &lt;i&gt;Optimum online supports POP but we do offer a Webmail service that holds 20 MB&lt;/i&gt;.  If the customer doesn't really understand why you didn't answer his straightforward question and asks again, &lt;i&gt;Does Optimum Online support IMAP&lt;/i&gt;?  You have to answer the same thing again, maybe word it a bit differently:  &lt;i&gt;We have Webmail that holds 20 MB of email&lt;/i&gt;.  All the customer wants to hear is &lt;b&gt;Yes&lt;/b&gt; or &lt;b&gt;No&lt;/b&gt;.  But the morons in management feel that the customer cannot handle hearing a simple &lt;b&gt;No&lt;/b&gt;.  To show how ridiculous this metric is try this yourself, go 8 hours without saying a negative word to anyone.  If there is one thing I've learned while dealing with customers is that they &lt;b&gt;don't want to be bullshitted&lt;/B&gt;, they &lt;b&gt;want a straight answer&lt;/b&gt;.&lt;br /&gt;&lt;br /&gt;&lt;b&gt;Bridges One Part of Call to Another&lt;/b&gt;&lt;br /&gt;&lt;S&gt;This has to do with transfers to other departments and it is one metric I agree with.    If you need to transfer the call you should 1) tell the customer you are going to transfer them, 2)contact the other representative 3) put the other rep on hold and tell the customer you are going to transfer them and 4) transfer the customer.  The call center rule is wait 30 seconds while trying to contact the other department, if there is a queue, then go back to the customer, explain there is a wait and then transfer them into the queue.  There is nothing to quibble about here, this is just good customer service.  &lt;B&gt;EVERY&lt;/b&gt; tech should get this correct, no excuses.&lt;/S&gt;&lt;br /&gt;&lt;br /&gt;I have been corrected by someone in the comments.&lt;br /&gt;&lt;br /&gt;&lt;B&gt;&lt;U&gt;Bridges One Part of Call to Another&lt;/u&gt; This standard has nothing to do with transfers. If you recall correctly, what they want you to do here is to use full sentences and avoid short sharp questions and statements (ex: Name?) &lt;/b&gt;&lt;br /&gt;&lt;br /&gt;This is almost as stupid as the next metric, &lt;b&gt;Filling Silences&lt;/b&gt;.  Tech support is all about giving the customer step by step instructions.  Instructions are short, abrupt, quick and to the point. They are not full sentences.  This is yet another instance where &lt;B&gt;BPA&lt;/b&gt; fails in the real world.&lt;br /&gt;&lt;br /&gt;&lt;b&gt;Filling Silences&lt;/b&gt;&lt;br /&gt;This is among the most annoying metric of all.  If I am silent it is because I am working on your problem.  I am probably running a variety of tests on your modem/pc/email, etc but they expect me to fill silences with babble.  Even if I try to cover myself with &lt;i&gt;Please bear with me while I run some tests&lt;/i&gt;, &lt;B&gt;BANG&lt;/b&gt;  marked wrong for &lt;b&gt;not using positive phrases&lt;/b&gt;.  We often have to wait for the customer's PC to reboot.  With some of those dinosaur PC's it takes quite a while to boot.  What am I supposed to say during that time?  Make small talk?  &lt;B&gt;So, what's the weather like by you?&lt;/b&gt;  &lt;b&gt;How's the wife and kids?&lt;/b&gt; &lt;b&gt;Got any nekkid pics of your wife?...Want some?&lt;/b&gt;.&lt;br /&gt;&lt;br /&gt;&lt;b&gt;Offers Help Before Being Asked&lt;/B&gt;&lt;br /&gt;What the fuck  does this mean?  I don't know.   My &lt;b&gt;Corporate Response&lt;/b&gt; already asks &lt;i&gt;how may I help you&lt;/i&gt;?  What else do they want?  And yes, management's guidelines on this are extensive......&lt;b&gt;HA&lt;/b&gt;!&lt;br /&gt;&lt;br /&gt;&lt;b&gt;Actively Listens&lt;/b&gt;&lt;br /&gt;This is related to if you ask a customer to repeat himself.  I've asked a customer for his phone number, entered in our ticket tracking program &lt;b&gt;Remedy&lt;/b&gt; and had it crash.  After I restarted it, I had to ask the customer for his phone number again, explaining my program crashed.  Yep, &lt;b&gt;another black mark&lt;/b&gt;.  It is also difficult to &lt;b&gt;Actively Listen&lt;/b&gt; when the customer babbles on and on and on and on about multiple or completely unrelated issues.  When you try to get the customer to clarify their problem, you run the risk of being marked wrong.  &lt;I&gt;This service sucks, it is sometimes static or I cannot hear the other person, and when I call my brother's wife's daughter's therapist who says his phone service from you also stinks and my PC is running really slow since I got the phone and I cannot get any voicemails and I was unable to call American Idol the other week......&lt;/i&gt;.  Now of course all this is said before you can even ask for their phone number to bring up their account.  And then you have to say  &lt;B&gt;So exactly what is wrong?&lt;/B&gt; BANG!  Black mark.&lt;br /&gt;&lt;br /&gt;&lt;b&gt;Acknowledges Customer/Offers Action&lt;/B&gt;&lt;br /&gt;Here we must emphasize with the customer.  &lt;i&gt;I'm sorry that you are having such an issue, I'll help you with that&lt;/i&gt;.  What a condescending load of shit. Note that you are not apologizing.  It is an empty bullshit phrase. You don't know any of the details yet, all you heard is the initial customer complaint.  Apologize when you hear the full story, when you know it is Cablevision's fault.  The customer doesn't want to hear empty phrases, they want action.  &lt;br /&gt;&lt;br /&gt;&lt;b&gt;Identifies Needs&lt;/B&gt;&lt;br /&gt;Doesn't the customer do this for you already?  They are the ones that called up and asked for help.  &lt;br /&gt;&lt;br /&gt;&lt;b&gt;Takes Ownership&lt;/b&gt;&lt;br /&gt;WTF?&lt;br /&gt;&lt;br /&gt;&lt;b&gt;Focuses on Solution&lt;/B&gt;&lt;br /&gt;I was trying to focus on the solution but I was too busy &lt;b&gt;Filling Silences&lt;/b&gt; with empty babble.&lt;br /&gt;&lt;br /&gt;&lt;b&gt;Summarizes/Gains Agreement&lt;/B&gt;&lt;br /&gt;Yeah, this is a brilliant one.  After a 45 minute call I'm supposed to go over what we did in detail.  After you solve the customer's problem, all they want to do is get off the damn phone, they don't want to hang around to hear you summarize shit.  &lt;B&gt;Gaining Agreement&lt;/B&gt; is asking them if you can help them with anything else.  Let's say I have a pissed off customer that I was unable to help.  Now I'm supposed to &lt;i&gt;Gain Agreement&lt;/i&gt;?  I say: &lt;I&gt;Is there anything else I can help you with?&lt;/i&gt; He says: &lt;B&gt;Fuck you!  You didn't help me with my original problem!&lt;/b&gt;  All I know is that if I have an irate customer the only agreement that I can gain is that &lt;b&gt;Cablevision Sucks&lt;/b&gt;.&lt;br /&gt;&lt;br /&gt;&lt;b&gt;Closes Call Politely&lt;/b&gt;&lt;br /&gt;This is simply saying something like &lt;i&gt;Thanks for calling Cablevision, have a great day&lt;/i&gt;.  Great on paper, lousy in practice.  Again, when you have an irate customer, nothing sounds more empty.  Let's say you have a customer that has major problems with his phone, that we've been unable to fix for a couple of months and the problem has been escalated a couple of times.  He is &lt;B&gt;PISSED&lt;/B&gt;.  After you explain to him that it is still being worked on, how about ending with &lt;b&gt;Thanks for calling Cablevision, have a great day!&lt;/b&gt;  &lt;br /&gt;&lt;br /&gt;And you wonder why people hate customer service reps, we are forced by management to treat customers like idiots, be condescending and utterly insensitive to their situation.  But hey!  Just like the &lt;a href="http://ooltech.blogspot.com/2005/06/optimum-status-page.html"&gt;Status Page&lt;/a&gt;, this is a great thing that management can check off their list, all our techs follow standardized call metrics.  Who cares if it doesn't make sense for every call.  &lt;br /&gt;&lt;br /&gt;All this bullshit counts for 50% of a tech's rating.  Did he fix your problem?  Did he give you good accurate advice on how to or where to get it fixed?  &lt;B&gt;WHO CARES!!!&lt;/b&gt;  Not Management!  Now you don't need to wonder why you get lousy technical support, all the techs are busy &lt;b&gt;blowing smoke up your ass&lt;/b&gt;.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/14041380-112441550964227893?l=ooltech.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://ooltech.blogspot.com/feeds/112441550964227893/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=14041380&amp;postID=112441550964227893' title='38 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/14041380/posts/default/112441550964227893'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/14041380/posts/default/112441550964227893'/><link rel='alternate' type='text/html' href='http://ooltech.blogspot.com/2005/08/managements-obsession-part-ii.html' title='Management&apos;s obsession - Part II'/><author><name>OOL Tech</name><uri>http://www.blogger.com/profile/05819125769089611661</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>38</thr:total></entry><entry><id>tag:blogger.com,1999:blog-14041380.post-112364252180029741</id><published>2005-08-17T01:00:00.000-04:00</published><updated>2005-08-17T23:13:23.643-04:00</updated><title type='text'>Statistics</title><content type='html'>Have you ever felt rushed off the phone like the tech is just blowing you off?  Have you been told you were in an outage but called later to find out you weren’t?   Has a tech ever referred you to a router/OS/PC vendor when the actual problem was on our side?  Has a tech ever hung up on you “accidentally” after about 10 minutes?  It might not have been incompetence, it may have been the need for the tech to meet management’s unreasonable goals.&lt;br /&gt;&lt;br /&gt;  As stated in a previous post, the holy grail of management is the call center’s &lt;a href=http://ooltech.blogspot.com/2005/07/managements-obsession.html&gt;ASA&lt;/a&gt;, or Average Speed of Answer.   &lt;B&gt;EVERYTHING&lt;/b&gt; the tech does affects the ASA so management watch the techs like a hawk.  As soon as you walk in the door, management has you under a microscope.  Even the time you spend taking a dump is recorded.  And any deviation from their specs are met with a heavy hand.&lt;br /&gt;&lt;br /&gt;When your shift starts you sign into your phone and you immediately start to &lt;b&gt;Idle&lt;/B&gt;.  &lt;B&gt;Idle&lt;/b&gt; is bad.  Very, very bad.  Too much &lt;b&gt;Idle&lt;/b&gt; time and you will feel the iron fist of management.   But you need time to log into your PC and then start up and sign into the 10 applications you need to do your job.   Lucky for us we have a special code we can put in the phone that allows us &lt;B&gt;Sign In&lt;/b&gt; time.  Don’t go over 5 minutes though!   Of course management only implemented that sign in time after a class action lawsuit was settled.  Before that you had to be at your desk, and signed in (which takes about 10 minutes) &lt;B&gt;BEFORE YOUR SHIFT STARTED&lt;/B&gt;.  When your shift started you had better be ready to take a call immediately (or feel the iron fist). That this was wrong was brought up numerous times to management, but they ignored it until the lawsuit was filed.&lt;br /&gt;&lt;br /&gt;Now you are signed in, management is watching carefully.  Your entire day consists of &lt;b&gt;idle time&lt;/B&gt;,&lt;b&gt;call Time&lt;/b&gt;,&lt;b&gt;hold time&lt;/b&gt; and &lt;b&gt;wrap time&lt;/b&gt;.  &lt;b&gt;Call time&lt;/B&gt; is the amount of time you spend on the call with the customer.  &lt;b&gt;Hold time&lt;/b&gt; is the time the customer spends on hold.  &lt;b&gt;Wrap time&lt;/b&gt; is the time after the customer hangs up and before you hit the &lt;b&gt;Ready&lt;/B&gt; button to take another call. &lt;br /&gt;&lt;br /&gt;Management is oh so generous with breaks, for an 8.5 hour shift, we get two 15 minutes breaks and a 30 (unpaid) minute lunch.  &lt;B&gt;THE ABSOLUTE MINIMUM REQUIRED BY LAW&lt;/B&gt;.  Yep, along with those crappy-ass &lt;a href=http://ooltech.blogspot.com/2005/06/working-conditions.html&gt;monitors&lt;/a&gt;, Cablevision never fails to go the extra mile for us techs!!!&lt;br /&gt;&lt;br /&gt;Let’s not forget &lt;B&gt;personal time&lt;/b&gt;.  Again management shows their generosity by allowing us a whopping &lt;B&gt;8 minutes&lt;/b&gt; of &lt;B&gt;personal time&lt;/b&gt;.  So, you've got an upset stomach today and have to use the bathroom frequently or take too long doing so?  Or take a couple of quick cigarette breaks?  Don't worry, &lt;b&gt; you’ll hear about it &lt;/b&gt;and it will affect you at raise time.  Once, I was sick and took a while in the bathroom.  A supervisor actually sent a lead to find me.  They weren't concerned about my health, they were concerned I was away from my desk for 10 minutes.  &lt;br /&gt;&lt;br /&gt;But management is most concerned with &lt;b&gt;Call Time&lt;/b&gt;,&lt;b&gt;hold time&lt;/b&gt; and &lt;b&gt;wrap time&lt;/b&gt;.  Those are the most important numbers when it comes to your evaluation.  Management’s &lt;b&gt;Call time&lt;/b&gt; goal is 9 minutes and 30 seconds.  Although I’ve heard from a lying sack of shit manager that this stat does not affect your rating, I’ll believe that when a flock of pigeons fly out of my ass. &lt;br /&gt;&lt;br /&gt;Management is very short sighted about &lt;b&gt;Call time&lt;/b&gt;.  As a competent responsible tech, I’d rather answer all the customer’s questions, and spend the extra time to avoid them calling back.  As an example,  a customer wants to setup his email for himself and his wife.  A tech drinking the management kool-aid would setup the customer’s email in Outlook Express and then tell the customer to do the same thing he did and setup his wife’s email himself.  Of course this customer will call back after being unable to figure out what to do.  Although the tech met management’s goal for his &lt;B&gt;call time&lt;/b&gt;, he created an extra call for the customer.  Even worse are the techs (encouraged by some supervisors), that just tell the customer to use Webmail.   OOL is a POP shop, it is not IMAP.  Email is designed to be temporarily held on the OOL servers, there is no backup, no disaster recovery and you know how I feel about the &lt;A href=”http://ooltech.blogspot.com/2005/07/incompetence.html&gt;BISC&lt;/A&gt;.  &lt;B&gt;DO NOT USE WEBMAIL AS YOUR PRIMARY EMAIL ACCESS!!!&lt;/B&gt;&lt;br /&gt;&lt;br /&gt;Techs are setup to fail when it comes to the other stats, &lt;B&gt;hold time&lt;/b&gt; and &lt;b&gt;wrap time&lt;/b&gt;.  These goals (30 seconds each) were instituted long before OV.  They may have been reasonable when you only had OOL calls but they are unrealistic for OV calls.  First of all, we have the issue of the lack of available leads or floor walkers covered &lt;a href=”http://ooltech.blogspot.com/2005/07/managements-obsession.html”&gt;previously&lt;/a&gt; .  The longer it takes to get your questions answered, the longer your &lt;b&gt;hold time&lt;/b&gt; is.  And OV calls often require you to put the customer on hold and verify the problem by calling other numbers.  This may also require a walk to the &lt;b&gt;Comm Desk&lt;/b&gt; to use some of the special phones there (Simplifying things, if a customer is in a 973 area code and is having problems calling 973 numbers you can use one of the 973 area code phones at the &lt;b&gt;Comm Desk&lt;/B&gt;.  If you are doing your job correctly, there is no way in hell you can keep your hold under 30 seconds.&lt;br /&gt;&lt;br /&gt;  &lt;B&gt;Wrap time&lt;/b&gt; is one of the most problematic of all the stats.  Management expects us to be able to detail everything about a call as we are talking to the customer.   This is why when you say something to a tech, he pauses, you hear typing in the background and then he may ask you another question or ask you to clarify or repeat your statement.  But there are a number of issues that cannot be resolved on the phone, they might have to be escalated.   In that case, you get all the info from the customer and then after they hang up, you have to document all the customers details into the ticket you are escalating.  Or you might have to fill out a web form with about 20 different pieces of info.  In a competent company you might think all these tools are linked and can talk to each other, but we are speaking about &lt;a href=http://ooltech.blogspot.com/2005/07/incompetence.html&gt;Cablevision.&lt;/a&gt;.  Everything is cut and paste.  One big problem with techs needing to match the &lt;b&gt;Wrap&lt;/b&gt; time is that they skimp on the details in the ticket or even just blow off escalating it.  Even worse are the techs that don't bother to save a ticket. No ticket means no wrap time!   So if you ever call in and the tech tells you there is no record that you called before this may be the reason why.  Having a short wrap time encourages techs to be brief on their documentation and that will hinder the next tech if you call in again, he will have to start from scratch with you.  &lt;br /&gt;&lt;br /&gt;  But the statistic that weighs the most on a tech's performance has nothing to do with being technical or even the success of a tech with your problem.  It is concerned only with how the customer is spoken to.  Next to their precious  &lt;a href="http://ooltech.blogspot.com/2005/07/managements-obsession.html"&gt;ASA&lt;/a&gt;, this is what Management pays the most attention.  That's right, they don't care if the tech helps you, they just care that the tech speaks the proper phrases.   It's called &lt;a href="www.bpaworldwide.com"&gt;BPA&lt;/a&gt; and I'll cover it another day.&lt;br /&gt;&lt;br /&gt;With these "goals", management is thinking they are running an efficient call center but if you look deeper at true customer service you see that results do not match the numbers.   Management is simply shooting themselves in the foot.&lt;br /&gt;&lt;br /&gt;But why should they want to reduce calls?  Fewer calls mean less staff means less responsibility which means a smaller bonus.  It is in management's best interest (and thus the tech's)  to have a customer call in 3 times over 3 days for &lt;10 minutes each at different times of the day instead of having 1 30 minute call.  Less &lt;b&gt;call time&lt;/b&gt;, less &lt;b&gt;wrap time&lt;/b&gt; and less &lt;b&gt;hold time&lt;/b&gt;.  It's the Cablevision way, everyone wins but the customer......&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/14041380-112364252180029741?l=ooltech.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://ooltech.blogspot.com/feeds/112364252180029741/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=14041380&amp;postID=112364252180029741' title='46 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/14041380/posts/default/112364252180029741'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/14041380/posts/default/112364252180029741'/><link rel='alternate' type='text/html' href='http://ooltech.blogspot.com/2005/08/statistics.html' title='Statistics'/><author><name>OOL Tech</name><uri>http://www.blogger.com/profile/05819125769089611661</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>46</thr:total></entry><entry><id>tag:blogger.com,1999:blog-14041380.post-112337997732547020</id><published>2005-08-09T14:26:00.000-04:00</published><updated>2005-08-09T17:21:33.350-04:00</updated><title type='text'>Being vindictive</title><content type='html'>I have been accused of being vindictive, of hating Cablevision and writing this blog in order to damage TSG.  This could not be further from the truth. I like the people I work with, I would never do something that would make our jobs more difficult. The supervisors, well you know how I feel about some and the others are just trying to get along in a crappy system.  I don't hate management, I hope they can take some of my constructive criticism and improve the lot of myself and my fellow techs.  Why I am doing this is posted on the description of my blog: &lt;i&gt;... to give you an insight into the workings of the call center as well as help you get inside the mind of the guy who is helping you.&lt;/i&gt;.  If some of my posts are, ahhh, passionate, well, that's how I was feeling at the time.&lt;br /&gt;&lt;br /&gt;  If I were vindictive I sure could make things hell for management.  Note that I have not posted any names, phone numbers, or email addresses.  In fact if any names are mentioned in the comments, they are removed.  If I were out for blood, I'd post the reachable from the outside phone numbers of TSG management and supervisors, you could go right to the top with your complaints. Got network problems?  Here's the number to the VP of RFDN.  Got email issues?  Here, call the VP of the Bisc.  But I would never do that, I want to fix the current system, not destroy it.&lt;br /&gt;&lt;br /&gt;  As an aside: to all my peeps and moles, keep up the email and thanks for the support!  BUT let's have some ground rules.  I have no idea if management is even aware of this blog, I've not heard a whisper about it from a supervisor or above.  But in case they are, and are looking for the people involved, do the following.  These are all common sense but keep them in mind.&lt;br /&gt;&lt;UL&gt;&lt;br /&gt;&lt;LI&gt;Do not email ooltech@hushmail.com from work.&lt;br /&gt;&lt;LI&gt;Do not post comments on the blog from work&lt;br /&gt;&lt;LI&gt;Do not email from your personal @optonline.net acct.  You never know if they are scanning outgoing mail for anyone emailing the hushmail address.&lt;br /&gt;&lt;/UL&gt;&lt;br /&gt; &lt;br /&gt;  Thanks for all your help and remember, keep the comments clean!&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/14041380-112337997732547020?l=ooltech.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://ooltech.blogspot.com/feeds/112337997732547020/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=14041380&amp;postID=112337997732547020' title='65 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/14041380/posts/default/112337997732547020'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/14041380/posts/default/112337997732547020'/><link rel='alternate' type='text/html' href='http://ooltech.blogspot.com/2005/08/being-vindictive.html' title='Being vindictive'/><author><name>OOL Tech</name><uri>http://www.blogger.com/profile/05819125769089611661</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>65</thr:total></entry><entry><id>tag:blogger.com,1999:blog-14041380.post-112312747485955849</id><published>2005-08-03T23:04:00.000-04:00</published><updated>2005-08-04T01:05:53.060-04:00</updated><title type='text'>Optimum Voice</title><content type='html'>What drives the big interest in Optimum Voice?  &lt;B&gt;Greed&lt;/b&gt;.  Cablevision is greedy for offering a service they are unable to reliably provide and customers are greedy because they think they can get a service for 1/3 the price.&lt;br /&gt;&lt;br /&gt;It's not just greed, it's also &lt;b&gt;stupidity&lt;/b&gt;.    The same morons that buy Roluxes off the street in NYC are the same morons that replace their primary telephone line with OV. Why does a Rolex cost so much more than the Rolux you buy on the street?  It is the years of experience Rolex has in making watches as well as the quality of the parts.  &lt;br /&gt;&lt;br /&gt;You should look at telephone service the same way.  Why do you morons think you will get the same reliablity and the same quality of service from OV as you got from POTS (plain old telephone service, aka Verizon).  POTS has been perfecting their infrastructure for &lt;b&gt;120 years&lt;/b&gt; and have had a culture of the "Five Nines".  That means an uptime of 99.999%.  That's &lt;B&gt;5 minutes&lt;/b&gt; of downtime a year. &lt;br /&gt;&lt;br /&gt;Cablevision has been working on their voice infrastructure for maybe 6 years and has a culture of &lt;a href="http://ooltech.blogspot.com/2005/07/incompetence.html"&gt;incompetence&lt;/A&gt;.   How many of you that have OV have been down for only 5 minutes in the past year?  With POTS , you still have phone service if your lights go out, fat chance of that with OV.  And you don't just have to worry about power outages.  As stated earlier, the boobs at RFDN love to experiment with the UBRs, if that fucks the customer, &lt;B&gt;WHO CARES?&lt;/b&gt;  Outside Plant (OSP) performs maintenances and takes nodes offline all the time, if that fucks the customer,  &lt;B&gt;WHO CARES?&lt;/b&gt;  Reliability and redundancy are not concepts Cablevision is familiar with.  Verizon does maintenance all the time, they are also now installing fiber to the home (FIOS).  Does that interrupt your service?  Nope.&lt;br /&gt;&lt;br /&gt;Since it is $35/month, people are signing up with OV in droves.  Don't these idiots do any research?  Why do they believe the bullshit the sales department feeds them?  Do they buy cars based on the salesman's pitch?  They probably spend 100x more energy investigating their next TV purchase than they did looking into the pros and cons of switching to VoIP. Look, if it works for you, and you have no complaints, that's great, good for you.  But if you are having problems and after two tries Cablevision cannot fix it, &lt;B&gt;THEN GO BACK TO VERIZON!!! Give it up!&lt;/B&gt;   I can understand your frustration, but you're paying $35/mon and&lt;br&gt; &lt;font color="red" size=+1&gt;&lt;B&gt;YOU GET WHAT YOU PAY FOR YOU IDIOT!!!!&lt;/b&gt;&lt;/font&gt;  &lt;br&gt;And that is just residential customers, if you are a business and you sign up for OV then you are the &lt;font color="blue"&gt;&lt;b&gt;King of Idiots&lt;/b&gt;&lt;/font&gt;.  There are some things you don't skimp on and phone service isn't one of them.&lt;br /&gt;&lt;br /&gt;OV is the greatest thing since white bread if used as a second line.  But if you use &lt;br /&gt;it as your primary line,&lt;br&gt; &lt;font color="red" size=+1&gt;&lt;B&gt;YOU ARE STUPID&lt;/b&gt;&lt;/Font&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/14041380-112312747485955849?l=ooltech.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://ooltech.blogspot.com/feeds/112312747485955849/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=14041380&amp;postID=112312747485955849' title='31 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/14041380/posts/default/112312747485955849'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/14041380/posts/default/112312747485955849'/><link rel='alternate' type='text/html' href='http://ooltech.blogspot.com/2005/08/optimum-voice.html' title='Optimum Voice'/><author><name>OOL Tech</name><uri>http://www.blogger.com/profile/05819125769089611661</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>31</thr:total></entry><entry><id>tag:blogger.com,1999:blog-14041380.post-112286063586766564</id><published>2005-07-31T23:15:00.000-04:00</published><updated>2005-07-31T23:40:10.780-04:00</updated><title type='text'>Incompetence</title><content type='html'>A culture of incompetence pervades Cablevision.  Everywhere you look there are idiots and the idiots beget idiots.&lt;br /&gt;&lt;br /&gt;  From the HR managers that hire techs that can barely spell their name, to the trainers that couldn't train someone to tie their shoes, to the retread former Verizon supervisors (there's a good reason why Verizon dumped them) to the clueless morons in the networking groups, incompetence is everywhere.&lt;br /&gt;&lt;br /&gt;&lt;b&gt;Techs&lt;/b&gt;&lt;br /&gt;   I feel sorry for our customers, there might be a 25% chance they will speak with a tech that will be able to help them.  Because Cablevision pays so little (you start as a temp making $11/hr) and this is a job that takes you a couple of months to really get into the flow of things, you rarely get techs that 1) are technically proficient when they walk in the door and 2) stick around to become so. For the new tech, Cablevision has a wonderful support structure, there is always someone around to help. &lt;b&gt;HAHAHAHAHA&lt;/b&gt;.  As I've detailed before in &lt;A href="2005/07/managements-obsession.html"&gt;Managements obsession&lt;/A&gt;, any tech or lead that should be available to help new techs get ordered to or are scheduled to be on the phones.  How do these techs learn from their mistakes?  They don't.  Since they don't know they are making mistakes and Management doesn't care about the quality of the tech support, they will just keep making the same mistakes over and over again.  BUT!  Even though the odds say you will have to call in 3 more times before you get someone that can help you, at least be happy for the call center management because you are helping them get their year end bonus.&lt;br /&gt;&lt;br /&gt;&lt;b&gt;Training&lt;/b&gt;&lt;br /&gt;   I don't know what these guys are doing all day because the new techs come out of training almost as clueless as when they come in.  Simple little tasks like determining if a customer is part of an outage is beyond them.  Forget about trying to diagnose a Winsock problem.  New techs get a couple of weeks of classroom training, followed by a day or two listening in with an experienced tech and then they are put on the phones.  Training should be at least 6 weeks long.  Two weeks in class, one week sitting with an experienced tech listening and discussing the calls, one week taking the calls and having the experienced tech discuss their approach and coach them and then two weeks on the phone with a trainer close by to monitor their tickets and answer any questions.  Management will never do this as all they care about are bodies on the phone.  They don't care about properly training their techs, they don't care about proper customer service, they simply care about answering as many calls as quickly as possible.  Is my approach a better long term solution?  Of course, but as I've stated before, it won't help Management make their numbers and thus their precious year end bonus.&lt;br /&gt;&lt;br /&gt;&lt;b&gt;Supervisors&lt;/b&gt;&lt;br /&gt;   In the past year, we have been inundated with former Verizon supervisors.  Cablevision's incompetent management would rather hire retreads than promote from within.  They've probably hired 10 supervisors from Verizon in the past year and promoted maybe 3 people from within.  As a result, the technical abilities of these supervisors are nil.  Techs are told to &lt;i&gt;See a lead or supervisor if you have any questions&lt;/i&gt;.  If your tech puts you on hold to ask one of these Verizon supervisors a question, you'd have been better off had he just used a &lt;a href="http://www.brtb.com/articles/magic8index.shtml"&gt;Magic 8 Ball&lt;/A&gt;&lt;br /&gt;&lt;br /&gt;&lt;b&gt;Field Techs&lt;/b&gt;&lt;br /&gt;  The majority of &lt;b&gt;Field Techs&lt;/B&gt; are excellent.  They come to your house, do a great job and you are happy.  BUT!  We don't hear about them, nobody calls in to tell us what a great job Jose did when he installed their triple play.  We hear the horror stories, of untrained techs (sound familiar?), botched jobs, and rushed incomplete jobs.  And when that happens, the customers that call in are &lt;B&gt;PISSED&lt;/B&gt;.  And for good reason. I hate these calls, all you can do is kiss some ass because you KNOW we fucked up and when you schedule a repair you pray it will be assigned to a good tech.  What you really want to do is go to the customer's house, fix his problem and then track down the &lt;B&gt;Field tech&lt;/b&gt; and kick his lazy incompetent ass. There are two types of &lt;b&gt;Field techs&lt;/b&gt;, Cablevision techs and contractors.  Because of the explosive growth of Optimum Voice, as well as the Triple Play promotion, Cablevision cannot handle the volume of installs and repair calls and must hire contractors.  99% of the problem installs are because of &lt;b&gt;Idiot Contractors&lt;/B&gt; that don't know WTF they are doing.  Next time you have a tech come to your house, just hope to look out the window and see a real Cablevision truck.  If you don't, well, good luck......&lt;br /&gt;&lt;br /&gt;&lt;b&gt;The BISC&lt;/b&gt;&lt;br /&gt;   These are the guys who run the mail servers.  If you are masochistic enough to use an @optonline.net address, you know where this is going.  These guys love performing unplanned maintenances in the middle of the day and bringing down a mail server.  Of course their excuse is &lt;i&gt;It isn't customer affecting&lt;/i&gt;.  Oh no?  Then why do we have 100 angry customers in the queue because they cannot get their email?  Also the mail servers crap out for no apparent reason at all and the first indication the &lt;b&gt;BISC&lt;/b&gt; has of this is a phone call telling them about it!  There are something like 10 &lt;b&gt;mail stores&lt;/b&gt;, each email address is assigned a &lt;b&gt;mail store&lt;/b&gt;.  Why doesn't the &lt;b&gt;BISC&lt;/b&gt; have 10 email address, each on a different &lt;b&gt;mail store&lt;/b&gt; and a program that every minute tries to log into each email address in turn?  If one fails, set off an alarm or something.  I know guys that can write a program to do this in minutes.  This is basic, simple stuff!  Why isn't it done?  Incompetence, plain and simple incompetence.&lt;br /&gt;&lt;br /&gt;&lt;B&gt;RFDN&lt;/b&gt;&lt;br /&gt;  These idiots are responsible for running the UBRs.  They are real winners.  &lt;i&gt;Let's roll out an untested IOS upgrade for this Cisco UBR and wait for call volume to see if it works!&lt;/i&gt;.  When the calls come rolling in, they deny there is a problem on their end, constantly duck the issue, do everything they can to stall and finally when pressed to the wall with an overwhelming amount of evidence that there is a problem, take some action.  Of course this is probably 12 hours later, thousands of customers have been affected and the issue is guaranteed to occur again because they didn't fix the problem they just masked it.  And that is on an issue that affects thousands!  Imagine trying to get them to fix a smaller issue on their end.  Forget it.  &lt;br /&gt;&lt;br /&gt;  All in all, If I have to decide among all the above, it's a close call between the moron field tech contractors and the idiots at RFDN.  But in my final analysis, the group that wins the &lt;font color="red"&gt;&lt;b&gt;Incompetence award&lt;/b&gt;&lt;/font&gt; are the knuckleheads in &lt;b&gt;RFDN&lt;/b&gt;.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/14041380-112286063586766564?l=ooltech.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://ooltech.blogspot.com/feeds/112286063586766564/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=14041380&amp;postID=112286063586766564' title='28 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/14041380/posts/default/112286063586766564'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/14041380/posts/default/112286063586766564'/><link rel='alternate' type='text/html' href='http://ooltech.blogspot.com/2005/07/incompetence.html' title='Incompetence'/><author><name>OOL Tech</name><uri>http://www.blogger.com/profile/05819125769089611661</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>28</thr:total></entry><entry><id>tag:blogger.com,1999:blog-14041380.post-112121643308665145</id><published>2005-07-21T22:45:00.000-04:00</published><updated>2005-07-21T22:50:27.546-04:00</updated><title type='text'>Power users</title><content type='html'>Oh man, these guys are a challenge.&lt;br /&gt;&lt;br /&gt;Some of them call in and they right away don’t want to talk to you..  They know the issue cannot be on their end. They don't want to troubleshoot, they don't want to deal with a lowly worm like yourself,  they want a supervisor, or even better, &lt;i&gt; they guy in charge of the network&lt;/i&gt;.   They want their "issue" acknowledged and escalated &lt;B&gt;RIGHT NOW&lt;/B&gt;.   &lt;i&gt;"Oh my GOD!  In the past year my speeds have dropped from 900K to 600K!  Fix it NOW!!!&lt;/i&gt;  There is usually no data to back up their talk, they frequently curse, and they are very angry.  This is NOT the way to deal with someone you are asking for help.  Acting like this will NOT put me in a mood to help you.&lt;br /&gt;&lt;br /&gt;So go ahead, call in.  Bitch about the company, bitch about your speeds, complain about the customer service, threaten to disconnect (&lt;B&gt;PLEASE DO!!!&lt;/B&gt;).  Demand I escalate your complaint. Be a big important man and act like an ass.  Yes, yes, yes I'm &lt;b&gt;SURE&lt;/B&gt; you are smarter than I am.  I'm &lt;b&gt;SURE&lt;/B&gt; you are better looking, better paid (well duh!), drive a better car, have a prettier girlfriend, and I'm &lt;b&gt;SURE&lt;/B&gt; you have a bigger dick.  But guess what, you're the one with the problem.&lt;br /&gt;&lt;br /&gt;Go ahead, treat me like a piece of shit.  I'll escalate your ticket alright, right into the fucking Recycle Bin.&lt;br /&gt;&lt;br /&gt;But thankfully that is not the most common kind of &lt;b&gt;Power User&lt;/b&gt; that calls in.  I find there are three kinds.  &lt;b&gt;The Angry Guy&lt;/b&gt; as related above, &lt;b&gt;Real Power Users&lt;/b&gt; and &lt;b&gt;Posers&lt;/b&gt;.  &lt;br /&gt;&lt;br /&gt;&lt;b&gt;Posers&lt;/b&gt; call up and think they know what they are doing.  &lt;b&gt;"I'm a &lt;i&gt;programmer/MSCE/CEO of a tech company/Linux user&lt;/i&gt; and I KNOW there is nothing wrong on my end.&lt;/b&gt;  Meanwhile you have them reboot their PC or power cycle/bypass their router (all the while they are bitching and moaning) and viola, they are online.  I recall one moron calling right after he couldn't retrieve email.  After checking his settings and determining he can't connect to port 110 I asked him if he had rebooted since this issue occurred.  Of course such a thing never crossed his mind.  And of course that fixed the problem.  I've never understood the immediate reaction of people to call in the instant they are unable to retrieve their email.  &lt;b&gt;Can't it wait?&lt;/B&gt; Do you really need that joke from Uncle Charlie/mailing list email from Anal-retentives R Us/how-are-you email from your bored-friend-at-work/increase your penis size|viarga|save money on software|Nigerian business proposal| spam- &lt;b&gt;RIGHT NOW&lt;/b&gt;????? Yeah,yeah,yeah, all of you are awaiting &lt;i&gt;vitally&lt;/i&gt; important email every damn second.  Geez, if it is that important, use the damn phone......&lt;br /&gt;&lt;br /&gt;  &lt;b&gt;Real Power Users&lt;/b&gt; are a lot more pleasant to deal with.  They come armed with information.  Trace routes, pingplots, complaints from dslreports, etc.  Sure, they’d rather deal with a lead because they’ve called in before and  have probably had some idiot tech that can barely spell their name(Yes, I am well aware of the wide disparity in the quality of OOL’s tech support – there are many good techs but with the turnover there are many more who are poorly trained and inexperienced).  .I’d love to be able to help them.  I’d love to be able to fix their problem.  But here's another &lt;i&gt;dirty little secret&lt;/i&gt;.  Even if you have a legitimate complaint and I escalate your complaint,  &lt;b&gt;NOBODY CARES&lt;/b&gt; that you have proof the network is having problems.  You are just one caller.  Yep, that's right, it's true. You, with all your proof, your trace routes, your pingplots, etc, are treated just like the Grandma next door who calls in complaining of slow speeds.  Your call will be lumped in with the rest of the slow speed calls and maybe, just maybe, at the end of the month, someone will analyze the tickets and see that there were a larger number than average calls from a specific area.  And only then will we do something about it.  Of course all the call center can do is tell the networking groups that we see a larger than normal call volume from that area.  And they will promptly blow it off and say it will be addressed in a future maintenance.   Now will that fix your problem?  I think you know the answer to that question……&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/14041380-112121643308665145?l=ooltech.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://ooltech.blogspot.com/feeds/112121643308665145/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=14041380&amp;postID=112121643308665145' title='8 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/14041380/posts/default/112121643308665145'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/14041380/posts/default/112121643308665145'/><link rel='alternate' type='text/html' href='http://ooltech.blogspot.com/2005/07/power-users.html' title='Power users'/><author><name>OOL Tech</name><uri>http://www.blogger.com/profile/05819125769089611661</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>8</thr:total></entry><entry><id>tag:blogger.com,1999:blog-14041380.post-112079654264019544</id><published>2005-07-12T08:45:00.000-04:00</published><updated>2005-07-12T23:26:02.066-04:00</updated><title type='text'>Management's obsession</title><content type='html'>Everything at the call center is ruled by one thing:  &lt;b&gt;Statistics&lt;/b&gt;.  While I'll cover tech statistics in a later post, this one will describe a management statistic.&lt;br /&gt;&lt;br /&gt;Management is ruled by one number over all - &lt;b&gt;ASA&lt;/b&gt;, average speed of answer. That is the average amount of time all customers have had to wait before talking to a rep in a 24 hour period.  Right now the goal is 60 seconds.  When the queue goes up, the wait to speak with a rep gets longer and the ASA rises.  And management starts running around like a chicken with his head chopped off trying to figure out why the queue is so high.  &lt;br /&gt; &lt;br /&gt;  Management's slavish obsession with the ASA comes at a price.  Let me give you some background.  In order to allow the techs to work more efficiently, you should have a few experienced techs or even lead technicians walking the floor to help out with questions.  This is why techs will put you on hold, to confer with a &lt;b&gt;floor walker&lt;/b&gt;.  But management frequently short staffs that position and it causes lines of techs standing next to the one or two available &lt;b&gt;floor walkers&lt;/b&gt;.   Also when the queue goes up, &lt;b&gt;floor walkers&lt;/b&gt; will get ordered to take calls.  This is, of course, short sighted.  &lt;br /&gt;&lt;br /&gt;   Here's an example.  Let's say a &lt;b&gt;floor walker&lt;/b&gt; can help one tech in one minute and we have two &lt;b&gt;floor walkers&lt;/b&gt;. And let's say techs come for help at a rate of one every 30 seconds. If your tech goes to ask for help, he should be back in a minute.  The queue now rises and one &lt;b&gt;floor walker&lt;/b&gt; gets ordered to the phone and his first call takes 10 minutes which is about average.  The first tech who asked a question is back at his desk after a minute which is expected, but the second tech had to wait 30 seconds extra, the 3rd tech, a minute, the 4th, 90 seconds, etc.  Eventually some techs may give up and possibly go back and tell the customer something incorrect.  So in the 10 minutes that the ordered to the phone &lt;b&gt;floor walker&lt;/b&gt; has taken one call and the 10 callers, whose techs needed help, have had their calls extended a total of 12.5 extra minutes.  Now how many customers have called in and have been on hold during those extra 12.5 minutes?&lt;br /&gt;&lt;br /&gt;Now &lt;b&gt;THAT'S&lt;/b&gt; the way to lower your ASA!!!&lt;br /&gt;Brilliant!!!!&lt;br /&gt;&lt;a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href="http://photos1.blogger.com/blogger/3380/1258/1600/brilliant.jpg"&gt;&lt;img style= "margin:0 10px 10px 0;cursor:pointer; cursor:hand;" src="http://photos1.blogger.com/blogger/3380/1258/400/brilliant.jpg" border="0" alt="" /&gt;&lt;/a&gt;&lt;br /&gt;  &lt;br /&gt;&lt;P&gt;So when you are on hold for an extended amount of time, well, now you know why.  &lt;br /&gt;Management feels that making their goal and thus increase their end of the year bonus is more important than any inconvenience an individual customer may experience.&lt;br /&gt;&lt;br /&gt;Or maybe they are just stupid.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/14041380-112079654264019544?l=ooltech.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://ooltech.blogspot.com/feeds/112079654264019544/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=14041380&amp;postID=112079654264019544' title='5 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/14041380/posts/default/112079654264019544'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/14041380/posts/default/112079654264019544'/><link rel='alternate' type='text/html' href='http://ooltech.blogspot.com/2005/07/managements-obsession.html' title='Management&apos;s obsession'/><author><name>OOL Tech</name><uri>http://www.blogger.com/profile/05819125769089611661</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>5</thr:total></entry><entry><id>tag:blogger.com,1999:blog-14041380.post-112010047046059179</id><published>2005-07-07T19:00:00.000-04:00</published><updated>2005-07-07T19:47:47.920-04:00</updated><title type='text'>Customers</title><content type='html'>You deal with all sorts of customers in this job.  They run the gamut from the petty tyrant who takes out his frustrations on the poor sap on the other end of the phone and feels like a big man (or woman) when he curses at him or belittles him, to the people who are genuinely happy and grateful that you helped them.  &lt;br /&gt;&lt;br /&gt;  It is the latter customer I'd like to salute.  When a customer calls in and is pleasant and willing to work with me and I do my best to solve their problem, most of the time both of us walk away happy.  That is the customer I try to think about on the ride home after a long shift.&lt;br /&gt;&lt;br /&gt;  And the others?  Well, they gave their name and address.  Keep that in mind the next time you are rude, demanding, condescending or just plain nasty to a tech.    Remember, you're not talking to a far away Indian and now &lt;span style="font-weight:bold;"&gt;He knows where you live...&lt;/span&gt;&lt;br /&gt;&lt;br /&gt;Hey, don't be taking this as a threat, it's reality, you really don't know to whom you are speaking with.  Your tech may be a former postal worker.  But don't worry about me, at the worst a tough customer might make me take a break to cool off and then I'll go home and take out my frustrations on the characters in GTA.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/14041380-112010047046059179?l=ooltech.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://ooltech.blogspot.com/feeds/112010047046059179/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=14041380&amp;postID=112010047046059179' title='3 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/14041380/posts/default/112010047046059179'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/14041380/posts/default/112010047046059179'/><link rel='alternate' type='text/html' href='http://ooltech.blogspot.com/2005/07/customers.html' title='Customers'/><author><name>OOL Tech</name><uri>http://www.blogger.com/profile/05819125769089611661</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>3</thr:total></entry><entry><id>tag:blogger.com,1999:blog-14041380.post-112009767502177305</id><published>2005-07-01T22:13:00.000-04:00</published><updated>2005-07-01T22:18:31.193-04:00</updated><title type='text'>Slow speeds Part II</title><content type='html'>In some cases the problems with slow speeds may not be OOL's fault.  Sometimes the problem lies outside of our network.  I've had customers show me traceroutes that show spikes of hundreds of millseconds but when when examined the spikes appear after they leave the OOL network.&lt;br /&gt;&lt;br /&gt;  You would think that once we are notified that our peering networks have issues we would route around them or use another peer but no, the networking groups don't care.  &lt;span style="font-style:italic;"&gt;Not our network, not our problem&lt;/span&gt; is their motto.&lt;br /&gt;&lt;br /&gt;  So go ahead and call it in but don't expect much.  The tech will not be aware of it.  If it ain't in our network, it ain't an outage and thus will not be on the &lt;span style="font-weight:bold;"&gt;Outage board&lt;/span&gt;.  If you insist, the tech can escalate it to the &lt;span style="font-weight:bold;"&gt;Comm Desk&lt;/span&gt; but they're useless, since it is one customer, and it is not in our network, they won't do anything with it.  Your complaint will fall on deaf ears.&lt;br /&gt;&lt;br /&gt;  Hell, I don't like it, I know &lt;span style="font-weight:bold;"&gt;YOU&lt;/span&gt;&lt;span style="font-weight:bold;"&gt;&lt;/span&gt; don't like it but that's the way it works.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/14041380-112009767502177305?l=ooltech.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://ooltech.blogspot.com/feeds/112009767502177305/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=14041380&amp;postID=112009767502177305' title='2 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/14041380/posts/default/112009767502177305'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/14041380/posts/default/112009767502177305'/><link rel='alternate' type='text/html' href='http://ooltech.blogspot.com/2005/07/slow-speeds-part-ii.html' title='Slow speeds Part II'/><author><name>OOL Tech</name><uri>http://www.blogger.com/profile/05819125769089611661</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>2</thr:total></entry><entry><id>tag:blogger.com,1999:blog-14041380.post-112017647924884791</id><published>2005-06-30T20:07:00.000-04:00</published><updated>2005-06-30T20:07:59.253-04:00</updated><title type='text'>Upload Cap</title><content type='html'>Ah yes, a subject near and dear to all the rabid P2P (Pirate2Pirate) app users.  I'm sure you are all dying for me to spill the beans on what triggers the upload cap and how to avoid it.&lt;br /&gt;&lt;br /&gt;  But yet again us tech support guys are useless.  We don't know that the limit is, the networking guys won't tell us.  From a management viewpoint this makes plenty of sense.  The reason why they have a cap is to preserve the limited upload bandwidth.  If we tell you what the limit is, you will use the bandwidth right up to that limit and we would still have a saturation problem.&lt;br /&gt;&lt;br /&gt;  The good news is that after you are capped and call in, when you ask the rep what triggers the upload cap and he tells you he doesn't know, at least now you know he is not lying, he really does not know. And don't bother speaking with a supervisor, they don't know either.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/14041380-112017647924884791?l=ooltech.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://ooltech.blogspot.com/feeds/112017647924884791/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=14041380&amp;postID=112017647924884791' title='5 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/14041380/posts/default/112017647924884791'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/14041380/posts/default/112017647924884791'/><link rel='alternate' type='text/html' href='http://ooltech.blogspot.com/2005/06/upload-cap.html' title='Upload Cap'/><author><name>OOL Tech</name><uri>http://www.blogger.com/profile/05819125769089611661</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>5</thr:total></entry><entry><id>tag:blogger.com,1999:blog-14041380.post-112009681705723837</id><published>2005-06-30T09:45:00.000-04:00</published><updated>2005-06-30T09:52:17.966-04:00</updated><title type='text'>Working conditions</title><content type='html'>Have pity on us, we work in a shithole.  It's a depressing cube farm overcrowed with people talking loudly on the phone.  The desks are bare, since there are no assigned seats who can customize their environment with pictures or other personal effects when you have no idea where you will be sitting tomorrow?  You aren't even given a desk drawer to store your stuff in, you have to carry it to and from work (headset, manuals, recent training docs,etc).  You have to supply your own pens, the PCs always crash and the monitors are 5 years old.  They've upgraded the computers twice in the past 2 years but there seems to be no budget for montitors.  Either the screen is scratched, blurry or dark.  I need to find a crooked opthamologist who will swear that my eyes have permanent damage from having to stare at Cablevision's crappy screens for 8 hours a day so I can sue the bastards.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/14041380-112009681705723837?l=ooltech.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://ooltech.blogspot.com/feeds/112009681705723837/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=14041380&amp;postID=112009681705723837' title='5 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/14041380/posts/default/112009681705723837'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/14041380/posts/default/112009681705723837'/><link rel='alternate' type='text/html' href='http://ooltech.blogspot.com/2005/06/working-conditions.html' title='Working conditions'/><author><name>OOL Tech</name><uri>http://www.blogger.com/profile/05819125769089611661</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>5</thr:total></entry><entry><id>tag:blogger.com,1999:blog-14041380.post-112010573967042869</id><published>2005-06-30T02:11:00.000-04:00</published><updated>2005-06-30T00:30:16.616-04:00</updated><title type='text'>Higher speeds</title><content type='html'>I'm sure everyone has seen the &lt;a href="http://slashdot.org"&gt;Slashdot&lt;/a&gt; article about the &lt;a href="http://hardware.slashdot.org/article.pl?sid=05/06/28/2254219&amp;tid=215&amp;tid=95&amp;tid=103"&gt;50Mbps&lt;/a&gt;&lt;br /&gt;speeds supposedly coming down the pike.&lt;br /&gt;&lt;br /&gt;   We were told a few months ago that OOL has been upgrading the network (all that tweaking possibly causing the slowdowns we've been seeing?) and that by the fourth quarter we will be offering tiered service.  We were told this will include the ability to &lt;span style="font-weight:bold;"&gt;run servers&lt;/span&gt; and it will include &lt;span style="font-weight:bold;"&gt;web space&lt;/span&gt;.  We were told that "&lt;span style="font-style:italic;"&gt;all we need to do is flip a switch&lt;/span&gt;".  &lt;br /&gt;&lt;br /&gt;  I really doubt this.  OOL has enough trouble running a 10Mbps network at top speed.  Can we really expect them to wave a magic wand and suddenly run fine at 50Mbps???&lt;br /&gt;&lt;br /&gt;  I found the most interesting part of that article to be this:&lt;br /&gt;&lt;br /&gt;&lt;span style="font-style:italic;"&gt;In the initial targeted deployment of this high-speed service in Oyster&lt;br /&gt;Bay, Long Island, Cablevision is providing a committed information rate of 50&lt;br /&gt;Mbps, out of the available 100 Mbps, &lt;span style="font-weight:bold;"&gt;symmetrical services&lt;/span&gt;.&lt;/span&gt;&lt;br /&gt;&lt;br /&gt;Right now we have 10Mbps down,1Mbps up.  And that is why we have a cap, people use up too much of the limited upstream bandwidth.  If it is symmetrical, meaining 50Mbps down/50Mbps up will there still be a reason for a cap?&lt;br /&gt;&lt;br /&gt;  &lt;span style="font-weight:bold;"&gt;&lt;/span&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/14041380-112010573967042869?l=ooltech.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://ooltech.blogspot.com/feeds/112010573967042869/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=14041380&amp;postID=112010573967042869' title='5 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/14041380/posts/default/112010573967042869'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/14041380/posts/default/112010573967042869'/><link rel='alternate' type='text/html' href='http://ooltech.blogspot.com/2005/06/higher-speeds.html' title='Higher speeds'/><author><name>OOL Tech</name><uri>http://www.blogger.com/profile/05819125769089611661</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>5</thr:total></entry><entry><id>tag:blogger.com,1999:blog-14041380.post-112008862916341562</id><published>2005-06-29T23:24:00.000-04:00</published><updated>2005-06-29T23:24:19.860-04:00</updated><title type='text'>Slow speeds</title><content type='html'>A lot of you have been complaining about slow speeds or rather a reduction in the speeds you used to have.  You also complain that when you call in, tech support knows nothing about it and when you show them proof, they really don't do anything but reset and bypass your router and clear your cookies and cache.&lt;br /&gt;&lt;br /&gt;There is a wide variation in speeds on the OOL network.  I've seen ftp downloads from the OOL ftp server range from 400 kB/s to 1.1MB kB/s.  It's a dirty little secret but management has an acceptable minimum speed.  If the acceptable minimum doesn't live up to the advertised &lt;span style="font-style:italic;"&gt;3 times faster than DSL&lt;/span&gt;, tough.  OOL is 3 times faster than DSL &lt;span style="font-style:italic;"&gt;on average&lt;/span&gt;.  If you are below the top of the bell curve, too bad. (&lt;==Management's viewpoint, not mine, don't flame me now!)&lt;br /&gt;&lt;br /&gt;  Now what is causing these slowdowns?  We have no idea.  There is a culture of secrecy at Cablevision, everything is on a need to know basis.  That is why when you call in with proof of your slowdown, we have no idea there is a problem because the networking groups (who I'm sure have tons of reports on all their systems and know to the kb/s what is the speed on the UBRs) don't tell us.  The call center has to figure out there is a problem by analyzing call volume over a period of time.  We then open an outage and we'll see it sit for weeks while the network groups do nothing.  One day I'll come in and the outage is off the &lt;span style="font-weight:bold;"&gt;Outage board&lt;/span&gt;.  Did they fix it?  Who knows?  But I doubt it and I'm sure I'll be getting some more calls from people in that area and I'll have to blame their slowdown on &lt;span style="font-style:italic;"&gt;"There are no problems in your area so something must be running on your PC that is causing it"&lt;/span&gt;.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/14041380-112008862916341562?l=ooltech.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://ooltech.blogspot.com/feeds/112008862916341562/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=14041380&amp;postID=112008862916341562' title='4 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/14041380/posts/default/112008862916341562'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/14041380/posts/default/112008862916341562'/><link rel='alternate' type='text/html' href='http://ooltech.blogspot.com/2005/06/slow-speeds.html' title='Slow speeds'/><author><name>OOL Tech</name><uri>http://www.blogger.com/profile/05819125769089611661</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>4</thr:total></entry><entry><id>tag:blogger.com,1999:blog-14041380.post-112001931853228485</id><published>2005-06-29T02:11:00.000-04:00</published><updated>2005-06-29T00:28:38.536-04:00</updated><title type='text'>It's not always our fault</title><content type='html'>Operating a computer is not as easy as turning on your TV.  You do need some training to operate one properly. Unfortunately, unlike a car, you don't need a license to use a computer, but you should!&lt;br /&gt; &lt;br /&gt;The number of compeletly clueless morons that call in and demand to have us fix their computer because it has a million popups is astounding (&lt;span style="font-style:italic;"&gt;I didn't have this problem when I was on AOL!&lt;/span&gt;).  PLEASE!  Do us a favor and go back to AOL, we didn't make your PC go to all those porn sites or made you click on every toolbar you're offered.   You messed it up, fix it yourself or pay to fix it.&lt;br /&gt;    &lt;br /&gt;Back to the car analogy, Your PC is the Car, OOL is the Road, the Website you want to go to is the Store. &lt;br /&gt;     &lt;br /&gt;Do you call up your Town's Public Works dept if your Car is running like crap?&lt;br /&gt;     &lt;br /&gt;No, you either fix it yourself or you take it to someone who has more Car knowledge than you do.&lt;br /&gt;     &lt;br /&gt;If you are having a problem with the Store, do you call up your Public Works dept and complain?&lt;br /&gt;&lt;br /&gt;   No, you would contact the Store.&lt;br /&gt;    &lt;br /&gt;Now if the Town put a roadblock at your driveway or the road has a bunch of detours that keep you going in circles, THEN you would call the Town.&lt;br /&gt;&lt;br /&gt;In my experience, 75% of the PC related calls are problems on the customer's end but we're the bad guys when your computer can't get online and (after 20 minutes of troubleshooting) we tell you to contact your vendor.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/14041380-112001931853228485?l=ooltech.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://ooltech.blogspot.com/feeds/112001931853228485/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=14041380&amp;postID=112001931853228485' title='2 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/14041380/posts/default/112001931853228485'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/14041380/posts/default/112001931853228485'/><link rel='alternate' type='text/html' href='http://ooltech.blogspot.com/2005/06/its-not-always-our-fault.html' title='It&apos;s not always our fault'/><author><name>OOL Tech</name><uri>http://www.blogger.com/profile/05819125769089611661</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>2</thr:total></entry><entry><id>tag:blogger.com,1999:blog-14041380.post-112001623346833641</id><published>2005-06-28T14:26:00.000-04:00</published><updated>2005-06-29T00:11:39.796-04:00</updated><title type='text'>Optimum status page</title><content type='html'>&lt;span style="font-style:italic;"&gt;My OOL is down, why does the Optimum status page say "All systems go"? &lt;/span&gt;&lt;br /&gt;&lt;br /&gt;  The status page is useless.  IMO it was created by management just so they can tick off a mark on a checklist:  "&lt;span style="font-style:italic;"&gt;Has online status page?&lt;/span&gt;"  &lt;span style="font-weight:bold;"&gt;CHECK&lt;/span&gt;&lt;br /&gt;&lt;br /&gt;  The status page is only for large scale outages such as entire UBRs or mail issues. So if you are in one of the outages as described in &lt;B&gt;How it works&lt;/b&gt;(99% of the outages) you can forget about finding it on the status page.&lt;br /&gt; &lt;br /&gt;  Such large scale issues are usually discovered by the call center and only when the queue shoots up quickly.  Some investigation needs to be done to see why the queue is going up.  When the &lt;span style="font-weight:bold;"&gt;Comm Desk &lt;/span&gt;, who monitors incoming tickets, finally figures out from the calls what is happening, they declare the outage and alert the NOC who alerts the group responsible.  These outages are usually fixed quickly so by the time the status page is updated (by the call center who besides doing the above also have to post the issue to the outage board, alert the supervisors and page management), the issue is over.&lt;br /&gt; &lt;br /&gt;   You would think they would have better monitoring on such critical equipment but I'll save my rant on the useless networking groups for a later post.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/14041380-112001623346833641?l=ooltech.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://ooltech.blogspot.com/feeds/112001623346833641/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=14041380&amp;postID=112001623346833641' title='1 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/14041380/posts/default/112001623346833641'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/14041380/posts/default/112001623346833641'/><link rel='alternate' type='text/html' href='http://ooltech.blogspot.com/2005/06/optimum-status-page.html' title='Optimum status page'/><author><name>OOL Tech</name><uri>http://www.blogger.com/profile/05819125769089611661</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>1</thr:total></entry><entry><id>tag:blogger.com,1999:blog-14041380.post-112001497480967069</id><published>2005-06-28T14:08:00.000-04:00</published><updated>2005-06-29T00:10:57.753-04:00</updated><title type='text'>How it works</title><content type='html'>On the various boards and mailing lists, I see many complaints like&lt;br /&gt;    &lt;br /&gt;  &lt;span style="font-style:italic;"&gt;I called in, they made me jump through hoops, I setup a tech to come and 3 hours later it came back on.  Why didn't they know it was  an outage?&lt;/span&gt;&lt;br /&gt;   &lt;br /&gt; A &lt;span style="font-weight:bold;"&gt;modems offline&lt;/span&gt; outage is declared one of two ways&lt;br /&gt;  &lt;OL&gt;&lt;LI&gt; By the Network Operation Center (NOC). If 30% of the modems on a node are offline a ticket gets sent to the &lt;span style="font-weight:bold;"&gt;Communications Desk&lt;/span&gt; aka &lt;span style="font-style:italic;"&gt;Comm Desk&lt;/span&gt; at the call center and they add it to the  &lt;span style="font-weight:bold;"&gt;Outage board&lt;/span&gt;.  &lt;br /&gt;  &lt;LI&gt; If more than 5 people call in on the same node and their modems are offline, the &lt;span style="font-weight:bold;"&gt;Comm Desk&lt;/span&gt; will declare it an outage, create the ticket and alert the NOC.&lt;br /&gt;&lt;/OL&gt;&lt;br /&gt;     &lt;br /&gt;  In both cases techs get sent out into the field to investigate what is going on.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/14041380-112001497480967069?l=ooltech.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://ooltech.blogspot.com/feeds/112001497480967069/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=14041380&amp;postID=112001497480967069' title='1 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/14041380/posts/default/112001497480967069'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/14041380/posts/default/112001497480967069'/><link rel='alternate' type='text/html' href='http://ooltech.blogspot.com/2005/06/how-it-works.html' title='How it works'/><author><name>OOL Tech</name><uri>http://www.blogger.com/profile/05819125769089611661</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>1</thr:total></entry><entry><id>tag:blogger.com,1999:blog-14041380.post-112001376508259107</id><published>2005-06-28T12:47:00.000-04:00</published><updated>2005-06-30T00:37:56.403-04:00</updated><title type='text'>Welcome</title><content type='html'>Welcome to Inside Tech Support. I am an OOL technical support representative and I've created this blog to give you an insight into the workings of the call center as well as help you get inside the mind of the guy who is helping you.&lt;br /&gt;&lt;br /&gt;I've been working here for a while (hey, the technical job market sucks). The pay is bad, the stress is high and the schedule worse.The turnover is unbelievably high so that is why your YMMV when you call in. You might be lucky and get me or you might get Joe Blow right out of training who doesn't know a node from a doughnout.&lt;br /&gt;&lt;br /&gt;Contrary to rumors and common belief, tech support is not there to blow you off but we are there to help.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/14041380-112001376508259107?l=ooltech.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://ooltech.blogspot.com/feeds/112001376508259107/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=14041380&amp;postID=112001376508259107' title='5 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/14041380/posts/default/112001376508259107'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/14041380/posts/default/112001376508259107'/><link rel='alternate' type='text/html' href='http://ooltech.blogspot.com/2005/06/welcome.html' title='Welcome'/><author><name>OOL Tech</name><uri>http://www.blogger.com/profile/05819125769089611661</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>5</thr:total></entry></feed>
