Example of well done system status notices to customers

**stevech** · 12-03-2010 05:05 PM

Example of quick/easy way to get system status by web login and by RSS pushes

http://status.dyn.com/

**ptrowski** · 12-05-2010 06:12 AM

That would be great.

**bill875** · 12-07-2010 07:43 PM

That is how EVERY service provider should announce system status notices. Thank you for pointing this out. I hope VOIPo is paying attention.

**VOIPoTim** · 12-07-2010 08:43 PM

We are considering alternatives to Twitter, but haven't made any decisions yet.

**stevech** · 12-07-2010 09:35 PM

Originally Posted by bill875

That is how EVERY service provider should announce system status notices. Thank you for pointing this out. I hope VOIPo is paying attention.

RIght- web page and RSS feeds.

And Facebook is not a good alternative to Twitter for the VoIP system trouble notices (grin)

**VOIPoTim** · 12-07-2010 10:04 PM

Originally Posted by stevech

RIght- web page and RSS feeds.

And Facebook is not a good alternative to Twitter for the VoIP system trouble notices (grin)

It's on our list of things to look into.

We're considering something along those lines, but it's a little more complicated than just putting up a site with RSS feed on it.

We'd would have to setup something that's easy to update without having to login to a site and at least also had the same functionality as Twitter (ability to send SMS alerts when something posted, etc) so we're not taking functionality away.

Just for one example of why we use Twitter now...before we started using Twitter and just used the forums, people were asking all the time for SMS alerts so if they were at work or not at home they could get an alert about network issues without having to constantly watch a webpage or check e-mail. SMS is an easy way to handle that and Twitter has it built in.

99% of our customers don't know what RSS is so it has to be an easy solution for people to be notified without checking the site or relying on RSS readers, etc.

**stevech** · 12-08-2010 11:53 PM

OK. Twitter is VoIPo's choice - VoIPo doesn't have to login to a web site to update status. That's convenient!
The conversation above not withstanding.

PS: SMS is not Twitter. RSS reading is integral to most browsers now.

**scott2020** · 12-09-2010 09:15 AM

Originally Posted by stevech

OK. Twitter is VoIPo's choice - VoIPo doesn't have to login to a web site to update status. That's convenient!
The conversation above not withstanding.

PS: SMS is not Twitter. RSS reading is integral to most browsers now.

If you get a Tweet, it can SMS you. Many people have it set up this way, in case your phone does not have Twitter capability. If VOIPo posts a tweet, people who have their Twitter set up to receive SMS copies will get the message.

That might actually be a decent solution for people who can't get twitter at work. At least an SMS text message would be sent. I suppose the next debate will be about people who don't have text plans and all of that. What VOIPo needs is something easy for them, and easy for customers. Most people are clueless about RSS.

**VOIPoTim** · 12-09-2010 09:45 PM

Originally Posted by stevech

OK. Twitter is VoIPo's choice - VoIPo doesn't have to login to a web site to update status. That's convenient!
The conversation above not withstanding.

PS: SMS is not Twitter. RSS reading is integral to most browsers now.

We still have to login to the Twitter site to post updates.

As far as SMS..... Like Scott said in his post, we're referring to the fact that Twitter will automatically send an SMS to users when we post something there so they can get instant notifications on their cell phone each time there's an issue.