Shockey Monkey

You can't fix a business problem with software

I can’t find any decent pictures of me in my “Go away or I’ll replace you with a small shell script” tshirt but yesterday I did just that. Part of doing business with OWN is that we trust you to set your own priority for the support requests. If something is urgent, we will handle it right away. If its a high priority case, we’ll work on it before we work on the other normal priority cases. It’s just good business. By setting your own priority you can rest assured that you get the support under an SLA and that when you really have an urgent issue, we’re there for you.

However, customers consider any matter, even a little annoyance, to be urgent to them. Not quite according to the SLA they agree to which defines an urgent issue as something that affects all users and makes it impossible for any work to get done. High priority is given to something that is affecting a large portion of the business. And just in case you’re wondering, no, it’s not urgent if the CEO is an idiot that nuked his entire inbox, if the business goes on the priority is normal.

It’s just human nature for customers to consider themselves the center of the universe and anything that happens to them needs to be handled urgently. Some MSP’s don’t even allow users to set their own priority, they let their staff judge how important something is. To each his own. Here were our support stats for Sunday and Monday:

Sunday: 31 support tickets, 16 urgent, 9 high
Monday: 89 support tickets, 30 urgent, 41 high

So I bounced an email to the Shockey Monkey mailing list and took some quick feedback. The resulting “replace you with a shell script” move is illustrated below:

Itsurgenteh

So I still trust my customers to tell me if something is urgent, or high. But if you go urgent and it just so happens its not urgent according to the SLA (service level agreement) we both entered in…. you get charged. Quick IM over to Dave Sobel to check if this is too rude and with his blessing it went into production around 10 AM EST.

Notice that you are not given a confirmation screen, just an alert. There is some logic behind that. I don’t want to ask you for a permission to agree with the SLA you already agreed to. I don’t want to automatically reset the priority to normal if the $250/hour bs fee doesn’t appeal to you. Perhaps this will make the customer read the priorities and consider where they would put this issue if it were their own IT staff doing it.

Back to the subject: you can address business issues with software, here are the results.

Tuesday: 75 support tickets, 1 urgent, 3 high
Wednesday:  28 support tickets, 0 urgent, 0 high

So we went from total 96 high/urgent priority cases on Sunday Monday, to only 4 after the warning went in. In all fairness, I have to give credit to Erick Simpson whose support portal always shoots back a confirmation email for every new ticket and explains their response time, SLA, etc – I even sent an email over to their support alias to get the threatening text you see up there.

Delaying Shockey Monkey agents one week

Sad to say this but after a full day of testing the latest Shockey Monkey agent code I am not ready to let it loose yet. I’m buying myself another week and will hope to push out the agents in a beta next Monday (instead of tonight, as planned). The problems are as follows:

  • Shockey Monkey mobile agent designed for Windows Mobile 6 and Windows Mobile 5 utilizes the SQL Server 2005 Compact Edition to provide offline content and caching. So if you update a ticket or create a contact when you have 0 reception, or want to quickly look up a contact, etc – the call is made to the local SQL database on the device. It seems that the rollout of that will require an update of mobile .NET framework and some other kung fu, not to mention prettying up the Interface.
  • The Server Monitoring WMI agent needs some server-side work to integrate properly into the ticket SLA escalation process. The way it currently works, you are required to deploy an executable on the remote server (that you wish to monitor) on which a Windows Service is installed. That service constantly feeds the server various inventory data (peripherals, system events) as well as pingbacks to track uptime, etc. Since its WMI based obviously lots of things can be monitored but designing a friendly interface around that is proving more difficult than I thought (friendly not powerful).
  • Random improvements to the SLA manager, network and system documentation sections, new ACL controls and how it all ties in together is something I have to discuss with Chad at greater length. I know how others are doing it and I think it blows, there has to be a better way.

I’ve literally be doing dev work for about a week now, plus a few other business roadblocks, so I have not had a chance to activate anyone. I will likely do some towards the end of the week.

Hey man, I sold Shockey Monkey!

I don’t know why the subject cracks me up so much, after all, I sell Microsoft vaporware for living (“Sure, of course it can handle a 14GB mailbox!”) but when someone goes out and sells my “Solutions built on a toilet (tm)” software I crack up.

Shockey Monkey, as some of you have noticed, has been in use by people worldwide since about the early October. It is a heavilly optimized portal software for SMB consultants, but more than a few people have managed to sell it to everything from SMB up to the government. I kid you not. Todays conversation:

Dave: It’s hot.

Vlad: Welcome to Florida.

Dave: I sold Shockey Monkey!

Vlad: What?

Dave: I logged into it to wrap up a ticket and the person liked it so much they want it for their own business.

Vlad: What do they do? (crossing fingers, hoping its not a drug dealer… again)

So keep on selling that monkey. Lord knows I can use some more backlog, almost two weeks now. But seriously, SM is not a good CRM solution. There are plenty of good CRM solutions for the problem of large SMB technology budget. 

MSN/Live Messenger Protocol Gotchas

It’s almost 4 AM and I’m sitting around coding in MSN/Live/com IM integration for Shockey Monkey. The basic premise is that the system will IM me when there is a new ticket waiting or when a user had updated/escalated their request. I finished coding this thing about a week ago and it works fairly well for what it is (a dumb sql->messenger gateway) but tonight I sat down to get rid of some annoyances. Here is what I found out.

For the most part, MSNP 9 is the most thoroughly documented implementation out there.

MSNP 9 is also very outdated, and MSN is trying very hard to move/force you up (I think they are on 13 now).

There is a gotcha in the signup process. For example, if you sign up for a live.com/msn.com passport id and initiate the first connection via MSNP 9, you will be prohibited from logging into it with that protocol – forever. However, if your first session is initiated via live.com messenger client (MSN P 10+) you can use any of the higher and lower edition clients.

Also, MSN does not tollerate bots on their network. The proper way to integrate your bot in the MSN network is to do your development/etc via IM Provisioning Center.

Shocking the Monkey in new ways: Now via RSS and integrated via VoIP, SharePoint, Vista Gadget and more

Every now and then you need a break from writing useful code that people will really rely on… and you start coding crap just to see if it would work. Earlier today I had lunch with one of my buddies that just passed the Asterisk/Fonality - Certified Asterisk Administrator training and just had to have Shockey Monkey integrate with Asterisk!

So, move over accounting integration. Forget about partial page rendering and display optimization. Who cares about a more extensible WMI reporting agent? It’s the stupid feature day for Shockey Monkey.

Today I took a big break from the studying, writing useful code and solving problems… to work on more creative ways of shocking the monkey. The big idea behind the monkey was to integrate all the features that are currently a part of the everyday IT interface and rely on them, instead of replacing them. So, today I worked on some syndication and integration features that precisely 3 people will use: RSS XML feed and HUD Lite integration into Asterisk.

RSS/XML

Implemented using as barebone RSS 2.0 spec as functionality will permit, Shockey Monkey tickets are now available as an RSS feed. The XML file is dynamically generated and supports updating tags as well, meaning that the stuff will stick in your RSS feed at the top until you close it. Thats right, RSS is for closers!

Upon clicking on the item you will see the support request details, such as which company its opened for, who opened it, when, priority, status, category, etc. Click on the subject of the item and it logs you straight into Shockey Monkey with ability to update.

How have I implemented this so far? Well, I’ve thrown it into a Vista RSS gadget, into my Google Reader and into the SharePoint portal. The big idea, of course, is for the open tickets to reach your users in as many ways as possible. Let’s face it, we don’t look / live in the same place all day, I catch things out of the corner of my eye all the time. Again, I hope this helps the 3 people that will actually use it 

VoIP Integration

As I mentioned, we’re sitting around and Judd says: “I want this integrated into Asterisk. When the user calls I want to look up their Caller ID and bring up their contact. If we can bring up their contact we can know what they want, work on it immediately. If we can’t, off to the sales they go!”

Why didn’t you say we could make money from this from the getgo?

Less than an hour later it was done. Four hours later, a fight with PEAR, PECL, hash and some more RTFM on the intricacies of encryption… it’s flawless. Someone dials in and the Internet Explorer or Firefox window pops up with the search results of all contacts that have that phone number listed in their phone or contact areas.

Can you wait a day?

This obviously deserves some documentation, I will have a video up tomorrow detailing it all.

However, if you can’t wait, these features are already in your portal.

For the RSS feed:

https://demo.mspticket.com/rss.xml?
username=your@emailaddress.com&password=yourpassword

For the HUD/Asterisk integration:

https://demo.mspticket.com/search.asp
?search=%%caller_number%%

And with that, the stupid-feature-day comes to an end. Is this useless?

Update: Not a minute after the post went live I get an IM: “Awesome! Count me in as #4!” – I’m almost tempted to do Count von Count impressions.

Shockey Monkey Installfest

As usual, Shockey Monkey community installfest happens tomorrow night, Saturday, from 8PM till Midnight. If you haven’t had your service turned up and you plan to hop to the front of the list add shockeymonkey@ownwebnow.com to your MSN IM list and contact me during the window above, I will issue the SSL certificate signing request, DNS and get you up and running immediately. This has worked rather well for a few weeks now so I’m doing it again.

SMB IT provider and you don’t have a customer portal? What are you waiting for?

Update: All done for the evening. I’m in a particularly good mood so the process went far faster than usual. I’ve never activated this many people in one sitting, Shockey Monkey has really picked up on the popularity levels as of late, I’m seeing a lot of “XYZ showed it to me and I’m dying to have it in my business” type of comments on the new signups. It’s all good. It also helps to do the scheduled activation window, the brainchild of Erick Simpson who suggested I pick a time and have a “Vlad free-for-all” slot in my schedule instead of doing 1 on 1 stuff. I originally ignored it because I wanted to get as much direct feedback as possible but I must say that both the satisfaction and the feedback levels (in terms of bugs and feature request numbers) have increased since I started doing this.

So thanks to everyone involved in the project, you guys (and gals) really help!

Shockey Monkey Live! Activations Saturday Night

I’ll be doing the second live activation evening for people that have been in the queue waiting to get activated on Shockey Monkey and for the people that signed up over the last week or so. The nice thing is that I’ve automated about 90% of the account provisioning process so it should go smoothly. I start at 8 PM EST Saturday, finish by midnight.

Just reviewing for the people that are seeing this for the first time:

  • Shockey Monkey is free.
  • You must be a legitimate incorporated entity with a live (that means not under construction) web site and a logo. (no hobbyists)
  • You need to sign up for it.

That’s all, add shockeymonkey@ownwebnow.com to your MSN IM and we’ll git ‘r done tomorrow night. 8 PM. Pass it on.

Update: What an evening.Thanks to all the people that showed up on a Saturday night to get hooked up. I also got a chance to work on a ton of other requests because things are so streamlined now. Hopefully the days of waiting for days or weeks for Shockey Monkey activation are long gone.

Bugs and Mitigation

As mentioned on the Shockey Monkey conference call this week I’ve squashed all the bugs that have been reported throught the last week or so. I’m also addressing the current showstoppers as identifed by the folks on the conference call. Just to clarify the intent here – priority in development is given to people that have adopted the product for their business use and see it causing a lot of pain and issues for them. Those showstoppers are as follows:

  • Ability to create a ticket via email
  • Company update issues
  • Email parsing issues
  • Ability to change subjects
  • Ability to offer user autoregistration*

* = difficult to solve. Someone requested it be supported via email, which isn’t going to happen until email becomes an authentic form of communication (ie: never); With SPAM, spoofing, forging and so on there is no way to provide any level of authenticity to the accounts that are being created via email. However, a web-self-registration stuff is under development, will have it ready by the May 23 feature refresh along with all the rest of the stuff above.

I’ve gone through all the bugs and fixed them, with the exception of about 5 issues that I was unable to replicate on my own. If you could be so kind to login and update the bug report with the detailed actions you took to cause it I’ll gladly get it done, I can virtually promise I will have it update on May 23rd.

A little note on bugs and releases

I patch the security and critical bugs in realtime. Shockey Monkey has a development and release branches which as the name implies hold the currently active code and the code I am working on.

If a security issue is identified it is patched and automatically rolled out to all the users.

If its a feature fix it gets fixed in the development tree instead. There are a few reasons for this:

  • Security fixes are usually either 1 line or an extra loop check. I can quickly replicate them to the development branch of the code.
  • I intend to release bug fixes on weekends, during the weekly maintenance window for Own Web Now Corp which is 3–7AM EST Saturday.
  • The feature rollups/fixes are released periodically for two reasons: It’s easier to manage and its easier to solve a huge set of bugs and eliminate problems before new ones pop up.

Also keep in mind that as I fix these bugs I am also rolling in new features so the less branches and patches the better. Also remember that this is not a single web app running in an isolated space on a box that nobody ever touches – each code change, given enough stupidity on my part, can take down the entire farm. So every bug/fix I do has to be stress tested, etc.

This week was different from previous weeks in that the patch/update will be held off until Wednesday, May 23rd. Here is what’s at play. I am going to be out of town next Saturday. There is a big conference starting Friday where I will be meeting many of you that are using Shockey Monkey and breaking it down piece by piece. I am introducing two HUGE feature sets into the Monkey and just wanted to go through another few days of testing and checking before it went live.

Of note, Shockey Monkey changelog is now available at http://www.shockeymonkey.com/changelog.asp

Shockey Monkey Dev Conference Call

Conference call covering Shockey Monkey tomorrow (Thursday, 5/17), just in case it missed some of you on the official mailing list.


Dear Shocked Monkeys,

We'll be holding our usual conference call tomorrow night at 7 PM EST (thats roughly midnight London, 9 AM Sydney, 4 PM Los Angeles, etc); The purpose of this call is to discuss the Shockey Monkey feature set and evaluate what needs to be bumped up on the priority list. The roadmap is now published at www.shockeymonkey.com but since so many of you are using Shockey Monkey in production already I am willing to be respectful of that and prioritize development on things that are really painful right now instead of 6 months from now. The benefit of a rapidly deployable infrastructure :)

The dialin numbers for this conference call are:

The conference will be recorded and available as an MP3 on our portal later this weekend. Please keep the phone numbers in confidence, Shockey Monkey is seriously denting the competitions sales in our sector and little birdie told me today that I'm starting to piss them off so please keep the details under wraps for now.

--
-Vlad

Shockey Monkey Help & Announcement List

I have yet again caught up with all the activations and put some more time into perfecting the process here. One of the realities of a hugely popular project is the technical support that comes with it. Unfortunately, until Shockey Monkey goes commercial (at a whopping $50 a month this fall) I have a tradeoff to consider: spend time on development or spend time on technical support?

To that end I have setup two mailing lists, one for development and another for announcements. Here is an email I just sent to the Shockey Monkey users:

Welcome to the Shockey Monkey help list.

First of all, thank you for using Shockey Monkey. I look forward to your feedback and feature recommendations so I can continue to evolve the monkey towards something that truely runs your business.

To that end, this project has grown significantly over the past year, as have its support demands. I am sure you will all agree that it is a far better use of my time to work harder on development than on support. I hope you're willing to offer some assistance on this front, or at the very least ask questions through this list so I can answer them in public and point people to it in the future.

You're more than welcome to unsubscribe from this list if you already get enough list clutter in your inbox, however, my future support until this project goes commercial will be restricted to official bugs/wishlist and this mailing list.

Thank you in advance for anything you may be able to take off my plate so I can dedicate more time to development.

Sincerely,
Vlad Mazek

Sounds fair, doesn’t it? I think this move will allow me to spend more time on whats really important and let users help one another until I get my foot on the ground. There are already so many people using Shockey Monkey in production to do some really awesome things and the tradeoff I had to make was whether I close the project or smash the roadmap deadlines and I think I chose what was in the best interest of all parties interested in Shockey Monkey. I just hope it works out!