Press "Enter" to skip to content

Richy's Random Ramblings

Techy Fun: Supporting the customer from hell

As I’m in the process of slowing shutting down other sites I’ve worked on (due to time constraints), I’m reposting them here. Here’s an article from “Behind The Frontline” which was going to be a cross between I Work With Fools, Worse Than Failure and Dilbert.

Categories: Gee, I Wonder why? and Just Plain Dumb. Author: Anonymous

here I work, the sales department is available Monday to Friday 9am to 5.30pm (i.e. normal office hours) and technical support is available 24 hours a day, 7 days a week, 365.4 days a year (yep – Christmas day included).

I don’t see this as unreasonable – we promise 24/7 tech support after all, but we can’t afford for the sales office to be staffed 24/7 “just in case” there is an order or query. We also provide detailed welcome emails and online knowledgebase systems.

That’s the scenario….

On our website we have a contact page: At the top of the contact page in big bold writing it practically says “The Sales Department CAN NOT help with technical support queries – if you are an existing customer please contact _technical support_” (with the _technical support_ bit taking them to our helpdesk). After the contact form (headed, “SALES ENQUIRIES ONLY” – yep, in caps!), the “The Sales Department CAN NOT help” messages is again repeated in big bold writing.

5.45pm on a Friday night. Guess what happens. Yep, a customer opens a sales request saying they can’t login. Problem – they neglected to say who they were (no domain name, no username – nothing useful). On Saturday, when I check my email, I feel pity for them and respond asking them to open a technical support ticket on the helpdesk (and I provide the link) giving their domain name.

Saturday night. Guess what. They open another sales request with the comment “See previous message. Domain name is xyz.com”.

Sunday night: They manage to find the help desk and actual open a Complaint that nobody helped them “so how can we advertise 24/7 support”?

Monday – another member of staff replies to the complaint asking them to open a technical support ticket (giving the URL again) and a description of the problem and their domain name (it’s only when I was trawling through the emails did I tie up the “See previous message” message with their original one).

Tuesday: They finally open a ticket for technical support. This time providing their domain name – AND a description of the problem: yippee!

I take a look: password looks to be working for me. I request they send me the username and password they are trying to use as an update to the ticket (and our ticketing system provides a suitable link where it says “DO NOT REPLY TO THIS EMAIL – PLEASE _CLICK HERE_ to update this ticket”). Yep – you guessed it – they replied via email with the message “I’M USING THE ONE YOU GAVE ME” (all in caps).

I reply again asking again for the username and password they are trying to use and ask them to update the ticket using the link provided and not to reply via email.

They decide, instead, to open a brand new ticket and cut and pasted the welcome email we sent them.

I merge the tickets and double-check the username and password (and, as expected, they do work). It’s now 2am in the morning and I’m off to sleep (hoping either another tech will have sympathy or the user figures it out themselves).

Wednesday: We have an angry phone call saying they are going to cancel their account as they can’t log in. Call is passed to management whilst we look up the information. I double-check the log files. He’s been logging in using the wrong password (but logs won’t tell me what password he is using). I send the proper password to management and Management reads out the password nice and slowly (“lowercase L for lima, lowercase Y for yankee” etc etc). Customer says “That works – it wasn’t working before. Oh – I’ve been typing it in capitals” (despite the welcome email saying “Passwords are case sensitive” and the helpdesk automatically prompts with “Ensure you are typing in your login details in the correct case – upper and lower case letters are different” if it recognises a login problem).

5 days wasted. Practically two hours of management and tech time wasted.

Do you want to know how much this customer was paying us?

Absolutely nothing.

Once I realised this, my desk got a “head shaped hole” in it and Management said “If they call up again, just cancel their account”.

Why is it also the cheap people which cause so much hassle?

News: Reuters: Seven years from death

As I’m in the process of slowing shutting down other sites I’ve worked on (due to time constraints), I’m reposting them here. Here’s an article from the 12th of May 2007 from “Treble R News” which was going to be a Register-esque general news site.

“The decomposed corpse of a German man was found alone in his bed after nearly seven years” Reuters News reports.

Techy Fun: More Information Please!

As I’m in the process of slowing shutting down other sites I’ve worked on (due to time constraints), I’m reposting them here. Here’s an article from “Behind The Frontline” which was going to be a cross between I Work With Fools, Worse Than Failure and Dilbert.

Category: More Information, Please!. Author: Anonymous

It’s a nice relaxing Thursday at mission control when a tech support ticket is raised on the helpdesk. It looks like correspondence between two people (“Company XYZ: It looks like account 123 isn’t working, but 124 is”), but with no indication as to why and how it concerns us. I then request further information about what the problem is and shufty off to play Roller Coaster Tycoon for a bit.

An hour or two later and a new ticket is opened with exactly the same details (and by the same user). Update ticket again asking for a couple of bits of information “What is the problem? What is meant to happen? What software are you using? Are you getting any error messages?” – basically, something for me to start working from – at the moment, I’ve got no idea what the problem is, let alone how I could offer assistance.

I continue losing a bit of money on RCT3.

Check back on the helpdesk and more correspondence between the customer and this unknown third party – it looks like they are having a problem getting a piece of software working, but what software it is, I don’t have a clue. The third party themselves say things appear to be working.

I close the ticket with a note “Unable to assist – I can’t offer support for third party applications and I haven’t got sufficient information from yourselves to be able to diagnose problem”.

Grab a drink.

They’ve responded to the closed ticket. First of all with some more strange third party correspondence and then asking what information I need (I cut and paste “What is the problem? What is meant to happen? What software are you using? Are you getting any error messages?”).

I wait a bit more – it’s now 11pm at night.

They close the ticket themselves – “Oh, I see the problem: I’ve missed some files”.

11 hours later, the problem is resolved and I’ve still got no idea what the problem was! I need an alcoholic drink!

Techy: Discontinuation of PHP4

I’ve already blogged about 13 facts about Friday the 13th which is paraskevidekatriaphobia or just triskaidekaphobia if you only fear the number 13. But Friday the 13th of July 2007 will go down as a “notable date” for some web developers – it’s the day that the End of Life of PHP4 was announced.

PHP4 as a programming language will become discontinued on the 31st of December this year – so if you’ve got an essential program which depends on PHP4 – contact the developers to make it PHP5 compatible now (after all, PHP5 has been out 3 years and they are now working on PHP6!). Ok, some people will be stuck (if I remember correctly, osCommerce doesn’t work brilliantly on PHP5 but I may be mistaken), but unfortunately that’s life…

Techy: Setting up Private Key Authentication in Linux for Rsync

If you wish to be able to automatically log in from one (server a) to another (server b), or you wish to setup rsync so that you can automatically send your backups from “server a” to the remote backup server “server b”, then the following steps should help in the configuration of this:

  • Login to server “A” via SSH as root
  • See if an RSA encryption key already exists by typing the following command:
    cat ~/.ssh/id_rsa.pub
    If the key does NOT exist (i.e. you do not receive any output or the system reports “No such file or directory”), then you’ll need to generate an RSA encryption key using the command:
    ssh-keygen -t rsa -N ''
    (note: those are two single quotes and NOT a double quote)
    You’ll then be prompted where to save the key (it should auto-suggest something like /root/.ssh/id_rsa which you should accept)
  • Now you’ll need to copy the RSA encryption key to the remote server (server B). Still via SSH on server A”, enter the following commands (replacing serverb.example.com with the name/IP address of server B, and entering server B’s password where prompted):
    ssh serverb.example.com
    mkdir .ssh
    exit
    scp ~/.ssh/id_rsa.pub root@serverb.example.com:/root/.ssh/remotekey
    ssh root@serverb.example.com
    cd .ssh
    cat remotekey >> authorized_keys

    exit

  • Now typing “ssh root@serverb.example.com” from server A should automatically log you in.