Feb 11,
So guys since last Tuesday i have been taking calls and each one has an interesting story behind it. I talked to an Indian malayali software engineer working with SAP, a Russian and a whole lot of other interesting characters. Right now in the 450-minute call time for a day we are supposed to average about 15 calls but till date my highest has been 13. On an average a call lasts for about half an hour and once it took me a cool two and a half hour.
Some of the guys are real comp illiterates. But one thing thats great about these guys is that they are amazingly patient. At times when we make mistakes some of the guys even go on to the extent of reassuring us. Every now and then we end up with some very hilarious. I'll share some of them with you guys.
Once a very irate customer called up and told the tech on phone that she wants to talk to his supervisor. The poor fellow calmed her down and listened to problem on hand. The lady in question had received a message on the screen asking her to "Press any key to continue". And she was angry because she did not find an "Any" key on her keyboard.
We guys are rated on various parameters. One of them is called the FTR or the First Time Resolution. This measures how successful you have been in solving the cust's problem. According to the rules if the cust calls back for the same issue within 2 days of the call the techie gets a 0 FTR for the call in question.
So the guys try to see to it that the custs don't call back in the next two days. Once it so happened that a techie messed up the system while troubleshooting. To save his ass he came up with an ingenious solution. He told the cust that the comp had a virus and it will take two days to cure and in the two days anyone touching the comp will get infected. So pls wait for two days and then call back.
Even I faced a very interesting case. The fellow was a Russian who did not know English and to my unfamiliarity with Russian added to the problem. He had some problem with the video card and I wanted to run some dos based diagnostics. I forgot the name of the file so I asked him to use the DIR command. The fellow after following my instructions told me that he got a message which said "Bad command or file". By chance I asked what did he type in. He replied BIR. I tried to correct him and told him that it "D as in Delta" IR. He replied B for Belta, now what is Belta. Finally I gave up and asked him to send us an email.
There are hundreds of similar instances and I will tell about them next time we meet.
So guys since last Tuesday i have been taking calls and each one has an interesting story behind it. I talked to an Indian malayali software engineer working with SAP, a Russian and a whole lot of other interesting characters. Right now in the 450-minute call time for a day we are supposed to average about 15 calls but till date my highest has been 13. On an average a call lasts for about half an hour and once it took me a cool two and a half hour.
Some of the guys are real comp illiterates. But one thing thats great about these guys is that they are amazingly patient. At times when we make mistakes some of the guys even go on to the extent of reassuring us. Every now and then we end up with some very hilarious. I'll share some of them with you guys.
Once a very irate customer called up and told the tech on phone that she wants to talk to his supervisor. The poor fellow calmed her down and listened to problem on hand. The lady in question had received a message on the screen asking her to "Press any key to continue". And she was angry because she did not find an "Any" key on her keyboard.
We guys are rated on various parameters. One of them is called the FTR or the First Time Resolution. This measures how successful you have been in solving the cust's problem. According to the rules if the cust calls back for the same issue within 2 days of the call the techie gets a 0 FTR for the call in question.
So the guys try to see to it that the custs don't call back in the next two days. Once it so happened that a techie messed up the system while troubleshooting. To save his ass he came up with an ingenious solution. He told the cust that the comp had a virus and it will take two days to cure and in the two days anyone touching the comp will get infected. So pls wait for two days and then call back.
Even I faced a very interesting case. The fellow was a Russian who did not know English and to my unfamiliarity with Russian added to the problem. He had some problem with the video card and I wanted to run some dos based diagnostics. I forgot the name of the file so I asked him to use the DIR command. The fellow after following my instructions told me that he got a message which said "Bad command or file". By chance I asked what did he type in. He replied BIR. I tried to correct him and told him that it "D as in Delta" IR. He replied B for Belta, now what is Belta. Finally I gave up and asked him to send us an email.
There are hundreds of similar instances and I will tell about them next time we meet.
Comments