Surveylab logo
Measuring-Satisfaction.com - Surveylab's Blog

A cautionary tale about ISP Customer Care – the power of negative word of mouth

The ISP and domain registrar 123-Reg upset me enough to turn me from an already dissatisfied customer into an angry customer a couple of weeks ago. The disappointing thing is that they had the opportunity to convert me to “quite satisfied” status by simply giving me an explanation that would go some way to giving reassurance, but they blew it by ignoring what the customer was saying and hiding behind their terms and conditions.

Edit 3 Jun: 123-Reg saw this post yesterday and responded giving an explanation and a reassurance that it won’t happen again. The agent did reply 2 weeks ago, but that email never turned up.

It all started four weeks ago when my mobile phone emited the dreaded tap-tap to announce I had a text-message. I dread receiving text messages these days because I don’t get many, and if they’re out of the blue I immediately fear it’s a notification reporting that one of our servers are down (even though it is an extremely rare event); alas the tap-tap was indeed “server down”.

For the sake of staying non-technical our mailserver was offline because a domain name had been deleted. This was 123-Reg’s fault – I had renewed the domain registration more than 3 weeks earlier, received confirmation that renewal was completed successfully (credit card debited too), but something went wrong between 123-Reg and the registrar that they deal with for .eu domains behind the scenes. So while my transaction was successful, 123-Reg’s renewal (with Tucows I believe) was not.

Naturally, I was furious with 123-Reg simply because the downtime was allowed to happen when it could have been avoided. I’m guessing that at the end of the month it looked (to the other registrar) like our .eu domain was not renewed so it was taken offline. I didn’t know any of this until I telephoned 123′s helpdesk and the agent told me I wasn’t the only one to have a problem with .eu domain renewals! And yet once I reported the issue, the domain was restored very quickly (about 24 hours). Clearly the problem was known, but nothing was being done about it resulting in downtime that was definitely avoidable.

I made a formal complaint to 123-Reg. I politely stated the facts and asked for an explanation. I regret suggesting that compensation might be in order – expecting they might refund the renewal fee (which is about £10) as an acknowledgement that they messed up – but no, their reply grasped the wrong end of the stick, somehow they think it’s my fault and for good measure refer to their terms and conditions four times. (I’ll post a copy of the reply in the comments below)

No explanation, no reassurance that they have identified the cause of the problem so it won’t happen again, and an afterthought of an apology after they thoroughly managed to piss me off.

Edit 3 Jun: Yesterday’s email exchange has offered an explanation and a reassurance (which was originally sent a few days after their first response but never received). Might be too late for me but my feedback has been passed to 123-Reg’s product development team so hopefully the renewal process will be improved in the future. I’ll append the reply to the comments for completeness.

The outcome:
I was already a somewhat dissatisfied customer (see comments below) and had transferred out most domains or registered new domains (more than 30)  before this issue occured. Registering a domain is cheap but I am an influencer – friends regularly ask me for technical advice including choice of suppliers – previously I just would have listed who I recommend, but 123-Reg have only themselves to blame for motivating me to also list the one that falls into the “definitely would not recommend” category.

If I changed the title to Who should I register a .eu domain with? a few more people might stumble upon this post. Isn’t word of mouth great?

Comments

  1. Dan says:

    Copy of my original complaint:

    Dear Sir, Madam,

    I am writing to you having contacted 123-Reg Support about the renewal processing problem and resulting downtime we experienced on April 30th/May 1st.

    I did raise the complaint online (ticket number 090506-000205) but was asked to write a letter to yourselves. I have copied the complaint below. I look forward to your reply.

    Original ticket raised sent 6 May 2009
    123-Reg username: ******

    I wish to raise a formal complaint to 123-Reg following the domain renewal failure and resulting downtime that occurred on surveylab.eu last week.

    I renewed the domain surveylab.eu on 6th April 2009, the transaction completed ok (my credit card was debited), and the 123-Reg control panel showed that the renewal was correctly processed.

    On Thursday 30th April the domain was taken down without any warning. The 123-Reg support person told me this was because the renewal between 123-Reg and another registrar failed, and 123-Reg were having problems with other .eu domain renewals. The problem would take 24 hours to resolve.

    I accept that problems occur, but it is totally unacceptable that 123-Reg failed to do anything about this internal problem for 3 weeks until after our domain was taken down without warning and we reported it. It is clear the problem can be resolved quickly and could actually have been fixed without any downtime, and this is why I am raising a complaint.

    The surveylab.eu domain was used for our email – collecting emails (not just for this domain) and had a major impact on our business between 30 April and 1 May. I spent between 4 and 6 hours to implement a workaround while colleagues spent Thursday afternoon and Friday apologising to our clients that our communications were down and that clients’ projects were delayed (we send various mailings to our clients’ customers).

    I am a very dissatisfied customer, and am seeking an explanation why this issue was allowed to happen. I also feel that compensation would be in order, not least for having to spend £4 telephoning 123-Reg Support to report the problem. (money isn’t what I’m after – I want my confidence restored).

    To be honest, I am torn whether to view 123-Reg as “probably ok really” or something else. The issue did get resolved as quickly as it could once it was reported, but the fact it was allowed to happen just undermines my trust altogether.

    I look forward to your reply.

    I am happy to discuss my complaint over the telephone if you prefer. I hope that you will take my complaint seriously and use it to improve your future service.

    Yours faithfully,

  2. Dan says:

    This is the reply (which was received 24 hours later). Count the number of references to “terms and conditions”. Like I say in my post, I regret suggesting compensation thinking they might pay back a few pounds for having to hang on the phone because that’s all they honed in on:

    Dear Mr Wardle

    I write further to your letter dated 13 May 2009.

    123-reg provide an automated service for the registration and renewal of domain names. Such systems are robust, but deal in high volumes and involve interaction with third party systems – including the Registry’s. Responsibility for ensuring the renewal contract has been completed vests with the Registrant (Dan Wardle). If we are notified of any errors which do occur, in time, it is possible to manually register or renew any domain names which have not been processed automatically. 123-reg were notified of this error on 30th April 2009 and the issue was rectified on 1 May 2009.

    It may assist to review the contracts in place when a domain is registered and renewed; which confirms the responsibility to check the renewal of the Domain lies with the Registrant and not with the Registrar (123-reg). We are unable to cover any consequential loss incurred as a result of your recent account experience. It is not something covered as part of your account with us and under our terms and conditions of service it is expressly excluded. I refer to our terms and conditions because they cover the service that we as a company provide to our customers and it is these terms and conditions which cover your account with us and which you agreed to in taking out your account. In view of the foregoing, 123-reg deny all liability in this matter.

    Please be assured this does not mean we do not value your custom. 123-reg aim to provide a high level of service, however due to the nature of the services provided, under our terms and conditions we do not guarantee the services we provide will be uninterrupted or error free. We aim to resolve any issues which do occur as quickly as possible and in this case the error was rectified within 24 hours.

    I appreciate the inconvenience the recent disruptions to your service will have caused and would like to take this opportunity to apologise for any disruption caused.

    Yours sincerely,
    XXXXXX
    Customer Solutions
    Email: xxxxxx
    WebFusion, 123-reg, SupaNames, Donhost

    GX Networks Limited. This e-mail is subject to: http://www.gxn.net/disclaimer

  3. Dan says:

    And my last response (I haven’t had any reply):

    Dear XXXXXX,

    Thank you for your reply. More than anything else I was looking for a reassurance that this problem is not likely to occur again, and I kindly ask again why did the problem occur and what steps 123-Reg are taking to prevent it from occuring in the future?

    I do not see how having completed the renewal process with 123-Reg, which included a confirmation message on screen that renewal was successful and being sent an email copy of the invoice, why I should think the renewal was not successful? My credit card was also duly debited. The renewal problem was between 123-Reg and another registrar (I was told Tucows when I spoke to 123-Reg Support). The renewal problem was not between myself (the registrant) and 123-Reg – but it did have a major impact on me, the customer.

    Once one has paid and been told the renewal was successful, this should be confirmation enough and I think it is reasonable to assume at this point that the ISP will fulfil its responsibility. On this occasion, 123-Reg did not. If I also have to check and follow up with 123-Reg’s suppliers, then 123-Reg should make this very clear at the time of renewal, and help its customers with where and how to check this information. I doubt the terms and conditions are meant to imply this, and if they do then they would probably be deemed unfair.

    Your email felt like a standard answer that involves hiding behind your terms and conditions and, despite the problem I experienced, does not even give me the courtesy of an individual response to what was a very serious customer service failure on 123-Reg’s part.

    If you could answer my questions, that would be helpful in restoring my confidence.

    Yours sincerely,

  4. Dan says:

    In my original post I eluded to already being a dissatisfied customer. This is the reason why:

    You might think that it’s only where your website is hosted that affects speed of website and reliability, but don’t neglect where your domain is registered either…

    We use a service called Hyperspin to monitor our webservers’ uptime and alert us as soon as one of our sites go offline for any reason. Two summers ago, one of our domains began being reported offline for 5-10 minutes at a time each day. Everytime we received the alert, we would check the server to find everything looked ok, but the problem was at the nameservers (which were 123-Reg’s) – it’s just that DNS propagation hadn’t reached our connections yet.

    When I contacted the helpdesk about it they didn’t offer any explanation – their view was that either the alerts were false or it was a problem at our end. Personally, I don’t think they understood. So we transferred all the nameservers to http://www.DNSmadeeasy.com (highly recommended) or to UK-Dedicated (where we host our servers, also highly recommended). Unfortunately, even though our .eu domain’s nameservers were set to dnsmadeeasy, the billing remained with 123-Reg, simply because there are few .eu domain registrars. I’ll be changing that asap.

  5. Colin Adamson says:

    angry Dan! like the point about your influence/ power – long live Word of Mouth made even more powerful by you knowing what you are talking about.

  6. Wow! I’m actually angry too! The only thing worse than having a problem (any kind of problem – but made worse when it servery impacts your business) is when the company that made the mistake doesn’t seem to care or respond as actual human beings. Those that realize it’s important for a company to appear “human” and respond to customers that way I think will emerge from this WOM shift much stronger – leaving competition in the dust!

  7. Dan says:

    The 123-Reg contact did try to reply 3 days later, but the message never turned up.

    Dear Dan,

    The error was caused as a result of an error in the renewal system due to a change in the way the domain names are renewed with Eurid, the registry. This has been fixed and the same error will not occur again in the future. As soon as we became aware of the issue, we put measures in place to manually renew the domain name.

    The confirmation you received from 123-reg was a confirmation of payment and it does not confirm the renewal has been successful. This message confirms the customer should check the domain name has been renewed successfully with the appropriate registry and provides a means to do this. I have provided the screen which shows this below for your reference.

    We had a brief exchange of emails yesterday and my stance basically remains the same:

    I do think 123-Reg should improve their renewal process to send a confirmation to their clients that the actual renewal, not just payment, was also successful – even if this occurs a few hours later or overnight. Telling the customer that it is their fault (and responsibility) is not constructive.

    Which they seem to have taken onboard:

    Thank you for your email and feedback. There are some complications with this however. Each registry has separate rules and procedures for renewing domain names. .eu domain names are not renewed until the last day of the month, or on the expiry date (whichever is sooner) regardless of when the renewal request is sent through to the registry. I have however forwarded your comments to our Domain manager and the product development team and we will be looking to make improvements to the domain renewal process.

    Ultimately, I don’t think either of us are going to climb down. 123-Reg believes it was my responsibility to check everything is ok. I don’t really remember what I did (I have a feeling I thought at the time it must take a little while for the changes to show up but I can’t recall), but I think it is wrong to take payment and let the customer sort it out and report the issue if there is a chance that the renewal they’re paying for hasn’t taken effect. But hopefully it’ll get fixed.

    • I came surveylab while doing a search for failed 123 req renewals.
      It’s not pleasant for me to discover that 123 reg appear to have done nothing about their failed domains renewal problem. I’ve just had 2 domains fail to renew even though 123-reg were paid and the control panel showed the renewal had taken place. Only by checking nominet and whois, could I see that they had failed to renew my domains. Although, that’s not how I found out for one of my domains – it expired and went down. So 3 years on, and 123-reg still don’t check domains have been renewed. They just blindly tell you they have been.

Trackbacks

  1. [...] Contact Us ← A cautionary tale about ISP Customer Care – the power of negative word of mouth [...]

Please leave a comment

*

Please note that if you have not posted on our blog before, your comment will be moderated by an administrator.