AlertFlow

ALERTFLOW INCIDENT MANAGEMENT

A simple & easy-to-use incident management system for helping your teams react quickly and a centralized location for communication while resolving issues. Alertflow is useful for every service you offer that when impacted, you need multiple people notified and the ability to track the status of that issue real-time.

Github: https://github.com/jazmy/laravel-alertflow

Features

  • Easy User Interface - Designed to be super easy, no training required!
  • Designed Mobile First - Meaning it looks awesome on phones and mobile devices.
  • Web Application - No downloads, installs, plugins, everything is in the web browser.
  • Notifications - Text or email notification, automatic login & acknowledgement of issue when link clicked.
  • Status Updates - Always know who responded and real-time issue status.
  • Collaboration - Quickly resolve issues with real-time chat and assigning the “ball”
  • Reports - Keep track of issues, responses and time spent on issues.

How do I setup?

Step One: Create an InstanceAn instance of Alertflow is a self-contained department. Your organization may want to have separate instances for each department so that you can customize the services and users specifically for that department.

Example: You may want to have an instance of Alertflow for your "IT Staff" and you may want to have a separate instance for your "Facilities Staff".

Step Two: Setup your Email and SMS setting
Alertflow requires that you use an external SMTP service provider for email and Twilio for SMS.

Mailgun has a free plan if you send less than 10,000 emails a month.
Twilio costs about $ 0.0075 per text message.

Step Three: Create Services
Services belong to an instance and your users can subscribe to service notifications.

Example: Your "IT Staff" instance may have the following services (network, email, phone) and your "Facilities Staff" instance may have the following services (electrical, plumbing, grounds).

Step Four: Create Users Add users to your instance and then you can add them as "subscribers" to services. Being a subscriber means you will be notified of issues with that service.

Issues - Issues belong to a service. Members of an instance can create "issues" for services. Once an issue has been created then email/sms notifications will be sent to everyone subscribed.

Example: Your "IT Staff" instance may have a network outage that needs immediate attention. They would create an issue, under the "Network" service. Your "Facilities Staff" may have a major water leak that need immediate attention.
It is recommended you create user accounts for each employee in your department. Anyone who is a user on your Alertflow instance can create an issue ticket even if they are not subscribed to that particular issue.

Example: A staff assistant may not be the person who resolves an issue but they may be active users on a system that goes down and they may be the first to notice if the system is broken.

If a user notices a service is problematic then they can submit an “issue” ticket for that service. Once the issue is created, everyone assigned to that service will be notified. An example of a service is your email, phone or web server. It does not have to be technology related, it can be your facilities, power outage, flooding or security. Anytime you have a service that when impacted multiple people need to be notified quickly then Alertflow is the perfect tool.

A notification is sent via email or text message with a unique link for that user and that issue. Once the user clicks that link the system lets everyone know they are aware of the issue. They are automatically logged in so no need to remember account information. No more working in the dark and hoping someone received your email or text message.