Yippie! Our September update adds live call routing as well as a voice mailbox with notification feature to SIGNL4. All details can be found in this article.

In the SIGNL4 web portal you can manually export historic alert reports as.csv files. In some cases it might be useful to export alert data programmatically. For example you can forward all alerts including specific parameters to InfluxDB and show the alert history in Grafana to recognize peaks, trends and abnormalities over time. You can even use AIOps to recognize certain trends automatically. By using the SIGNL4 REST API it is possible to export alert data automatically.

What do IT security, production monitoring and technical field service have in common? In all scenarios there is need to notify the right people immediately in the event of technical malfunctions, urgent maintenance requests or emergencies to resolve the incident quickly and efficiently.

We would like to thank our loyal customers for the numerous reviews of SIGNL4! We are excited that you share your opinion on various rating platforms with other people and support us.

The time has come! Users in SIGNL4 can now be a member of multiple teams. This allows for staff to be on duty in multiple groups or departments in parallel and to receive related alert notifications for incidents that occur in the different teams. In addition, you can now also send Signls to multiple teams. All details are available in this article.

SIGNL4 offers powerful duty scheduling for routing alerts to the right people at the right time. In some cases, customers use other tools as leading system for duty scheduling, e.g. SAP, Excel, etc. Here we describe how to import duty schedules from .csv files. If you use other tools or other formats you can first export your scheduled into a .csv file and proceed from there.