I understand downtime for upgrades or replacing bad hard drives or what have you. It has to be done. I also understand bandwidth upgrades. Router/switch updates/upgrades or trunks being switched around and so forth.
How about stepping up service a little bit by sending out emails to the users on a particular server when you know service will be disrupted either with your bandwidth or server(s)?
Before I moved, I hosted my own server and used Speakeasy for my bandwidth. Speakeasy virtually never went down. I had a router go bad and never had them drop service for an emergency in 4 1/2 years. Any other time they went down, it was scheduled (about once a year for about 20 minutes). 2-7 days before the scheduled service, they'd send me an email announcing what they were doing, why they were doing it, estimated down time and sent me another email when service was complete.
I also think a spam email could be generated when there is an emergency issue with a customers server letting them know the problem, what's being done, a possible ETA (with updates when ETA's aren't met) and another email when things are back up.
Good example today. The server I'm on started having issues at 4:30am mountain time this morning. Still not up as of 8:54am and I check the status of the server here. Someone posted at 7am that they were working on it and would update in FIVE minutes. There wasn't an update until 8:40am.
Extremely nice feature for customers.
I've been in the customer service arena for 20+ years. Customers don't want to have an issue AND have to figure out why they have an issue. From experience, it's been widely appreciated when the customer has been notified of an issue before they know about an issue. This would be especially true with hosting. The web is 24 hours. As a customer here, I can't monitor a server 24 hours a day, although, to some, it may seem that I do. When one of MY customers has issues during off hours, I now have to go and dig up why they were having issues.
Just a thought.
Bryan


LinkBack URL
About LinkBacks



Reply With Quote




