You’ve asked for it – and it’s my pleasure to say that we’ve delivered. Shockey Monkey now chats, has a desktop client, mobile HTML5 app for your iPhone and Android and plays nicely with Quotewerks, Kaseya, LPI, nAble, GFI Max, Quickbooks and more.
Over the past few months we’ve been focusing on integration between our partners and even improving the network communication in our own software. One of the biggest challenges in the software industry is foresight and being able to determine what comes next. If you have ever written a piece of software and then had to make a change to that software (even something small), maybe 1, 3, 6, 12 months later. You can probably understand how important it is to think ahead. Sure, you can rush software and have to rewrite the same code everyday several times. If you’re like me and don’t like to create (unnecessary) extra work, you can think about what functions & methods you may need for future revisions and implement at least a template that is extensible.
Truly Open API and Fat Client API Demo
That’s the approach we’ve been taking for that last year and it’s really starting to show now. We are able to (design, code & implement and actually sleep) software changes & additions a lot quicker and a lot cleaner. One of the ways we achieved this was to take all of the code that we use all over the place and centralize it into a single location. This is how we got our first API version and we started to build on top of that structure. Since we designed the API, one of our biggest concerns was SECURITY SECURITY SECURITY. We thought: You know what, one day our clients/partners will want to use this API. So when that time came and we were ready to allow the API to become public, we literally flipped one switch and it was all lights go!
A lot of people want access to an API and access to it is usually the first request. However, not a lot of clients/partners will utilize that API, until you show them what’s possible! That’s when it starts to get fun interesting! So, we released the Shockey Monkey Fat Client BETA! It takes advantage of our API and demonstrates the possibilities. Yes, it really is possible to create something useful from these publicly available resources. It’s the first release, so right now we kept it simple. It will allow you to view/update (tickets, contacts & companies). It even comes with a ticket dashboard, which shows you the status and urgency of all your open tickets.
On the other side of the office our Shockey Monkey team has been working on integrations with other Software vendors and helping to bridge that gap in resources. They’ve just finished integrations with (Level Platforms, N-able, GFI MAX). There are still a few others they are trying to complete very soon.
We literally completed these integrations within a week of actively working on them. What made it so simple was the initial template design we created when we made our first Integration point with Kaseya. It allowed all additional Integrations to be designed in a module structure allowing for easy design and implementation. We’ve moved away from the model of “Let’s just get it to work”, we created a few integrations like that in the past. They work great… until the method, you used to obtained information, has now been changed and no longer works.
Our current integration portfolio:
1. Email Gateway – Any device or service that can generate an email can automatically create a ticket in our system. Remember that this is free to you with ExchangeDefender so use it!
2. RMM – Kaseya, LPI, nAble, GFI Max (Labtech in development). We’re currently working with a number of companies that are interested as well as Shockey Monkey’s own built-in lightweight WMI/VNC tool.
3. Accounting – Quickbooks. Exports to xls, csv and data feeds for other ERP. We’re exploring adding more integrations here as requested but we’re spending even more effort into bringing the transaction processing and reporting capabilities into Shockey Monkey. We find that most partners don’t have a very formal accounting backend, especially for tracking cloud subscriptions, and ShockeyMonkey already supports Authorize.net as a payment gateway so look for a development there.
4. Business – Quotewerks. This is currently one of the best integrations out there because it was developed by Quotewrks and is tightly integrated in their software.
We’ve learned a lot from all of these integrations and have amazing ideas for future releases. One of the first things we want to implement is a SOAP version of our API. Currently, they are all written in XML/RPC and that has served us rather well. However, in the future we are envisioning an even more rapid development environment for Shockey Monkey. It’s always nice when most of the data translation is done for you. So we are thinking that SOAP and Shockey Monkey are going to get to know each other very well over the next few months!
Finally, I manage all the development projects and products at ExchangeDefender, including all our integrations, PSA/RMM and our automation infrastructure. I work with many partners but at the end of the day I’m just one guy. So here is how to plug in with the whole team and make sure your requests are being taken care of:
1. Use the portal bug/feature tracking. Located at https://support.ownwebnow.com under the Development tab there are Features and Bugs. We use this as the central storage for all our features and requests. You can see public stuff that was reported by our clients and even some stuff that our internal teams are tracking.
2. Get in touch with someone. Our support team is fantastic and they often bring the issues you are facing to me directly. Sometimes in the office but mostly at meetings and our weekly staff bar crawl where we do our best to complain about everything that isn’t perfect. If you can get someone to hear you out, you can rest assured it will get taken care of faster.
3. Make a compelling, detailed case. There are lots of great ideas. Unfortunately, time is very limited to build them all. If there is a problem that affects a lot of people or a feature that would benefit a lot of people, tell us about it in as many details as possible and recommend suggestions and ideas. You’ve clearly spent more time dealing with it than we do so you have a unique opportunity to make a good argument over why we should work on problem #9881 instead of feature #810. The more perspective and benefits/pitfalls the better.
VP Development, ExchangeDefender