Great to work with both during the initial trial and testing and as we went into deployment and needed some help on a couple of topics.

The ability to have both public and private components on a single portal is something we could not find from other suppliers

Setup is a little more complicated due to the high degree of customisation available. Reporting could be improved.

Honestly, the product is amazing, and it's making my life a lot easier as I can post messages and downtime in the app quickly so that users are aware and if it's a short downtime, I don't have to send out a notice, it's just simply tracked there. I think having a dashboard and being able to show uptime is key in a SAAS based world and allowing users to help themselves rather than submitting cases to Support for updates, is a more efficient way to handle these types of problems going forward.

I like the ability to alert specific groups of users per each component. Having control over who you notify, for what products, or specific functionality so you can cater targeting messaging is huge in the Support realm. Allowing folks to sign up for text messages notifications rather than email so you don't have to deal with IT security restrictions is just a massive help in the healthcare industry were security is extremely strict and traffic is heavily monitored.

I'd like to be able to manage my list of contacts better. I want to know who has never signed in so I can remove them from the list of subscribers. I want to know when people leave that I can remove them from the list with ease. I'd also like a better way to handle and manage templates, because copying and pasting sometimes doesn't adjust well so having to get the HTML version to manipulate changes can sometimes be very time consuming. Posting an incident needs to be a little more streamlined - for example, if you tie a template to a type, it should auto-populate below and it should auto-fill in the date, etc. so you can see it before you post it so you'll know the formatting looks right. Please allow for a better calendar view - looking at newest to oldest is off-putting and users seem to have a hard time reading that - perhaps showing an actual calendar or "TODAY" highlighted in Orange so people's eyes are draw there, would really help. Lastly, the reporting really needs to be exportable - I need to be able to pull a list of folks who have signed in - not just from their creation date so that we can leverage account management to ensure that the contacts we have listed actually are in the "know" about system outages and scheduled maintenance.

Overall, set up was easy, adding users was simple and direct. Administration is a breeze.

Ease of use and deployment. The production page is simple and not busy at all, making for a comfortable and inviting view of our page.

I wish the published page had a bit more flexibility than whats avialable but it gets the job done. The amount of components offered could be a bit higher to offer more flex during set up.

It's been really great, it's super user-friendly and the chat/support team is always reliable and responsive.

I really like its integration potential through the API that it offers. Plus, the documentation of that API is stellar.

This is minor but I'm not a fan of the limit on the number of components we can create. Especially in the context of nested components. Having three components nested within a component simply for the purpose of categorizing the subcomponents shouldn't result in a component total of 4, but rather 3.

StatusCast has provided us a mechanism by which we can notify an ever-changing client/vendor database with up-to-the minute notifications on several different organization applications that otherwise would involve regular maintenance and clunky tracking processes. Furthermore, as a third party application, StatusCast provides the ability to get the word out even when our organizational communication systems are out of service.

Low maintenance requirements, ease of implementation, instant notification to clients, and up-to-date dashboard status. Implemented both an external facing and internal facing application, allowing us to keep our field informed on topics not applicable to clients or vendors.

Minor limitations prohibiting some flexibility in notification specificity; yet, we were still able to adjust and keep the application design applicable to multiple organizational applications with differing client/vendor databases