If you're not duping items or some such, it's because you're in front of the game for hour after hour after hour hording things to sell on ebay. Bet you anything he works longer hours than he did at his 'real job' to make anywhere near as much money.
It doesn't work in practice for you because you aren't going about it the right way.
You can get to dun properties through file -> properties, why bother doing it the other way if it's apparent they aren't grasping what you're asking them to do?;)
3. Your mileage will vary. Even within companies you're going to get quite a varience with regards to tech quality. Rule here is that if you're not happy, call back until you are.
Very true - had an interesting situation come up not too long ago, some asshat used my e-mail address as the return address for some spam they sent out, hence I got several bounced messages from invalid targets. I looked at the headers and found Verizon all over the point of origin, so I called them up to find out if they had an abuse address I could forward that e-mail on to.
First call: got this clown in India who told me it was either a virus on my computer or it was something I'd have to contact my local authorities about. Spent a couple of minutes trying to reason with him and he just wasn't having it.
Second call: After explaining the situation again the second tech apologized and gave me exactly what I wanted - immediately. We spoke for a grand total of about 90 seconds.
Where I work all you have to do is just ask to be escalated and it'll be done as a matter of policy.
Also depending on who you call the level 2 people may not be getting paid more than the inbound people - I did level 2 for 5 months and went back to inbound because the headaches involved (cleaning up mistakes made by previous techs, listening to people bitch when your schedule prevents you from calling them back exactly when they want, filling in for missing supervisors, etc) were not worth being paid the same amount of money.
At this point, I'm getting a little irritated..."no, I'm not, I'm reporting a outtage...there is NOTHING wrong with my equipment. Nothing has changed on my settings. I'm not going to sit here, re-route my cables and change settings just so you can finally know there is an outtage in my area. Trust me, the problem is on your end."
Hehe.. I can't tell you the number of times I've heard lines like that and it ends up being something on the customer's end - from something as simple as a username/password problem because they changed their password and forgot they did it to something as wierd as them getting their phone service cut off and hence not having any luck getting online.
That said, I've learned to never say never when someone calls up reporting a network issue.;)
I'd always check the current dun first in cases involving telco recordings. Clients usually seem to catch on to problems with their dialing before I have to ask them if they need 7, 10, or 11 digit dialing, if they're using *70 but don't have call waiting, etc. Note I said usually, but not always.;) At any rate it eliminates having to guess the OS and recreating the dun.
I've been doing dialup tech support for over a year now. Honestly I think I should be able to reasonably expect these things:
1) You know what version of your operating system you're running, and you know how to operate it.
2) You know what mail client/browser you're running.
3) If you got an error messages, you remember what it was.
You know what make and model your car is, if it has 2 or 4 doors, automatic or manual transmission, etc. There's no reason you shouldn't know basic things about your computer too. That's all I expect from an client - that and the ability to follow directions. I don't expect any further training and I certainly don't expect them to come on the line talking like they've been in front of a pc their whole life.;)
Now techs who don't know what they're doing - of which I've seen more than my fair share... those are the ones that irritate me.
Voice chat for an mmog is a decent idea, provided that:
A) Everyone you're going to be grouping/associating with has access to it
B) You're not playing in a roleplaying environment. (Hey, that elf chick is really an old dude from Alabama!)
I've read that FAQ before, and I still don't see how an SNES emulator is going to cost anyone at Nintendo their jobs. They've got better things to deal with - like what went wrong with the Gamecube such that they had to halt production on it just to clear current inventories, or why they're being slapped around by competitors in the industry they were once king of.
Yes nostalgia is a part of it, but I'll still take an older game over the new stuff any day, regardless of how technologically advanced it is. Realistic or not, Out Run and F-Zero beat the hell out of Gran Tourismo. I won't touch Final Fantasy X-2 because I'm too busy enjoying Final Fantasy 3. And you won't find me playing any new boxing games, because none of them will match up to Mike Tyson's Punch Out.
The owner of that Subaru is going to get their car back, the assclowns who shot up a bank and stole the car are going to the big gray bed and breakfast where they'll take it in the dumper for a few years... it's all good.
Slashdot Mirror
If you're not duping items or some such, it's because you're in front of the game for hour after hour after hour hording things to sell on ebay. Bet you anything he works longer hours than he did at his 'real job' to make anywhere near as much money.
You can get to dun properties through file -> properties, why bother doing it the other way if it's apparent they aren't grasping what you're asking them to do? ;)
Very true - had an interesting situation come up not too long ago, some asshat used my e-mail address as the return address for some spam they sent out, hence I got several bounced messages from invalid targets. I looked at the headers and found Verizon all over the point of origin, so I called them up to find out if they had an abuse address I could forward that e-mail on to.
First call: got this clown in India who told me it was either a virus on my computer or it was something I'd have to contact my local authorities about. Spent a couple of minutes trying to reason with him and he just wasn't having it.
Second call: After explaining the situation again the second tech apologized and gave me exactly what I wanted - immediately. We spoke for a grand total of about 90 seconds.
Also depending on who you call the level 2 people may not be getting paid more than the inbound people - I did level 2 for 5 months and went back to inbound because the headaches involved (cleaning up mistakes made by previous techs, listening to people bitch when your schedule prevents you from calling them back exactly when they want, filling in for missing supervisors, etc) were not worth being paid the same amount of money.
At this point, I'm getting a little irritated..."no, I'm not, I'm reporting a outtage...there is NOTHING wrong with my equipment. Nothing has changed on my settings. I'm not going to sit here, re-route my cables and change settings just so you can finally know there is an outtage in my area. Trust me, the problem is on your end." Hehe .. I can't tell you the number of times I've heard lines like that and it ends up being something on the customer's end - from something as simple as a username/password problem because they changed their password and forgot they did it to something as wierd as them getting their phone service cut off and hence not having any luck getting online.
That said, I've learned to never say never when someone calls up reporting a network issue. ;)
I'd always check the current dun first in cases involving telco recordings. Clients usually seem to catch on to problems with their dialing before I have to ask them if they need 7, 10, or 11 digit dialing, if they're using *70 but don't have call waiting, etc. Note I said usually, but not always. ;) At any rate it eliminates having to guess the OS and recreating the dun.
1) You know what version of your operating system you're running, and you know how to operate it.
2) You know what mail client/browser you're running.
3) If you got an error messages, you remember what it was.
You know what make and model your car is, if it has 2 or 4 doors, automatic or manual transmission, etc. There's no reason you shouldn't know basic things about your computer too. That's all I expect from an client - that and the ability to follow directions. I don't expect any further training and I certainly don't expect them to come on the line talking like they've been in front of a pc their whole life.
Now techs who don't know what they're doing - of which I've seen more than my fair share
Voice chat for an mmog is a decent idea, provided that: A) Everyone you're going to be grouping/associating with has access to it B) You're not playing in a roleplaying environment. (Hey, that elf chick is really an old dude from Alabama!)
I've read that FAQ before, and I still don't see how an SNES emulator is going to cost anyone at Nintendo their jobs. They've got better things to deal with - like what went wrong with the Gamecube such that they had to halt production on it just to clear current inventories, or why they're being slapped around by competitors in the industry they were once king of.
Yes nostalgia is a part of it, but I'll still take an older game over the new stuff any day, regardless of how technologically advanced it is. Realistic or not, Out Run and F-Zero beat the hell out of Gran Tourismo. I won't touch Final Fantasy X-2 because I'm too busy enjoying Final Fantasy 3. And you won't find me playing any new boxing games, because none of them will match up to Mike Tyson's Punch Out.
Keep whining.
... it's all good.
The owner of that Subaru is going to get their car back, the assclowns who shot up a bank and stole the car are going to the big gray bed and breakfast where they'll take it in the dumper for a few years