SIGNL4

Mobile Alerting and Anywhere Incident Response

SIGNL4
  • Product
    • Feature Overview
    • On-Call Management
    • Mobile Alerting App
    • Why SIGNL4
    • First Steps
    • Security, Data Privacy & GDPR
    • Online Help & FAQ
    • Blog and what’s new
    • System Status
  • Use Cases
    • IT Alerting
    • SIEM & SecOps Alerting
    • IoT Service Alerting
    • Industry 4.0 Maintenance Calls
    • After-Hours Service Desk
    • Field Service Dispatching
    • Emergency Alerting
  • Integrations
  • Pricing
  • Company
    • About
    • Partner Program
    • Podcast
    • Media
    • Contact us
    • Newsletter
  • Free Trial
  • My Account
  • Deutsch

Inspiration

  • Home
  • Inspiration
  • Updates
  • November 2021 Update – Improved incident response with team escalation and more

November 2021 Update – Improved incident response with team escalation and more

  • By René
  • November 3, 2021
  • Updates
November 2021 Update – Improved incident response with team escalation and more

Our November update introduces new team settings and, along with them, entirely new options for escalating Signls. This will allow you to make your incident response even more reliable. One application is to create a ‘managers on duty’ teams with full duty scheduling capabilities and escalate missed Signls to such 2nd level response team. As always, you can find all the details in this article.

New Settings for Teams

First of all, we have cleaned up the SIGNL4 web portal a bit and given the alerting and response settings of the individual teams their own page.

Under Team -> Settings you can now see all options around alerting and response of this team at a glance. Some of them were previously located on the members page, others are new (see below).

New Escalation Features

In the middle of the page you can now set whether a missed Signl should be escalated further.

When are Signls escalated?

A Signl is considered missed when it is not acknowledged within the “Signl response time” (at the top of the page). This is regarded as a ‘breach’ of the set response time. In case of such breach, an escalation can be triggered.

To whom can be escalated?

Signls breaching response time can be escalated to all punched-in managers of the team or – and this is completely new – to another team.
In general, each team can be a target of an escalation. However, this needs to be explicitly enabled through the “Team can be escalation target” in the “Privacy settings“. If this option is disabled, this team will be shown in the drop-down list as a target for escalations.

How do you recognize escalated Signls?

You recognize a Signl escalated (to your team) by an orange stripe on the left in the overview (web portal or mobile app). Signls escalated away from your team to other team or the manager have an orange stripe on the right.

Details of such Signls also display an area that shows the escalation chain.

The escalation process and handling

Incident response becomes super effective, also across teams. Are you are in full control. If you see a missed Signl as escalated away, you can comment on it to communicate with the escalation target (team). If you comment on Signls that have been escalated to you, those comments will also be synchronized to the original team and its Signl.

The same happens with the Signl status (alert lifecycle status). If you see a Signl after it was escalated to you and then realize that the originally responsible team confirmed it, you can simply close your Signl. Vice versa, a Signl acknowledged by the escalation target team, can still be acknowledgded/closed/annotated by the originally responsible team. This is because SIGNL4 creates copies that are linked to each other for a fully transparent and flexible incident response process.

How often can escalation take place?

Each team can set one escalation target. In total, 3 escalation levels are supported.

Set persistent notifications

New on the page in the alert settings section at the top is that you can now finally set at what interval you want to receive persistent notifications for new Signls. The default value here is 5 minutes, but you can now also change it to match your Signl response time.

An interval of 10 minutes with a Signl response time of 30 minutes would mean that as long as you don’t acknowledge it, you would be re-notified for a Signl up to 3 times before it would escalate further. Which channel is used for this is still determined by each user in the mobile app itself.

As always, we wish you a lot of fun while discovering and are already working on the next update. 😎

 

Tagged

escalation

Share

Related Posts

August 2022 Update – Change duty status of colleagues, configurable duty notifications and revised password change

August 17, 2022

July 2022 update – Remote actions for super-fast incident remediation

July 12, 2022

May 2022 Update 2 – New category features and improved zooming in the scheduler

May 23, 2022

May 2022 Update – Templates, scheduler enhancements, landline numbers, and more

May 3, 2022

Why SIGNL4?

SIGNL4® reliably notifies mobile operations teams and provides for a 10x faster response to critical alerts, major incidents and urgent service requests. Read more

 

Most Popular

  • Being a powerful ‘pager app’ SIGNL4 ca...
  • Microsoft Flow – send mobile Alert Notificat...
  • Geofencing Alerts with Automate or Tasker
  • Website Down Alert Notifications AWS CloudWatch Alarms to your mobile phone during...
  • Maintenance Call Machine Breakdown Maintenance Call using the AWS I...
  • Paging App Android settings for making SIGNL4 an even better...
  • Code Webhook CSharp C# C# code for the SIGNL4 webhook
  • Setting up the AWS IoT Button – and SIGNL4

FOLLOW US

  • Twitter
  • LinkedIn
  • Facebook
  • Vimeo

CATEGORIES

  • Communication (11)
  • Customer References (1)
  • Developer (11)
  • DevOps (12)
  • General (105)
  • Healthcare (1)
  • Integrations (24)
  • ITOM & ITSM (21)
  • Manufacturing (8)
  • OT & IoT (21)
  • Security (5)
  • Updates (32)

Tags

alert alert management alerts Android Application Insights Automate AWS IoT Button Azure B2B software c# Call Routing do not disturb Duty Scheduling emergency escalation Field Services geofencing handover Hotline ifttt Industrie 4.0 IoT IT Alerts IT Operations ITSM location Manufacturing Monitoring mute override on-call duty On-call Scheduling oncall duty Pager paging app press release SaaS splunk Tasker temperature voice voice recognition weather webhook Website zapier

ABOUT US

Derdack® is a long-standing innovator for enterprise-class mobile alerting and alert management solutions. Our global customer list includes The Boeing Company, Daimler, BMW, Porsche and many other leading brands. With SIGNL4® we have reinvented mobile alerting and alert management for operations teams in IT, IoT, Industry 4.0 and other areas where swift response to critical events matters.

SIGNL US

Phone +1 (202) 4 700 885
Intl +49 331 29878-20
CH +41 31 539 19 90
Email info (at ) signl4.com
Feedback online
Newsletter Sign-up

© 2023 - Derdack SIGNL4

  • Twitter
  • LinkedIn
  • Vimeo
  • GitHub
  • Feedback
  • About
  • Terms of Use
  • Privacy Policy (Website)
  • Cookie Policy (EU)
  • Product
    • Feature Overview
    • On-Call Management
    • Mobile Alerting App
    • Why SIGNL4
    • First Steps
    • Security, Data Privacy & GDPR
    • Online Help & FAQ
    • Blog and what’s new
    • System Status
  • Use Cases
    • IT Alerting
    • SIEM & SecOps Alerting
    • IoT Service Alerting
    • Industry 4.0 Maintenance Calls
    • After-Hours Service Desk
    • Field Service Dispatching
    • Emergency Alerting
  • Integrations
  • Pricing
  • Company
    • About
    • Partner Program
    • Podcast
    • Media
    • Contact us
    • Newsletter
  • Free Trial
  • My Account
  • Deutsch
Manage Cookie Consent
We use cookies to optimize our website and our service.
Functional Always active
The technical storage or access is strictly necessary for the legitimate purpose of enabling the use of a specific service explicitly requested by the subscriber or user, or for the sole purpose of carrying out the transmission of a communication over an electronic communications network.
Preferences
The technical storage or access is necessary for the legitimate purpose of storing preferences that are not requested by the subscriber or user.
Statistics
The technical storage or access that is used exclusively for statistical purposes. The technical storage or access that is used exclusively for anonymous statistical purposes. Without a subpoena, voluntary compliance on the part of your Internet Service Provider, or additional records from a third party, information stored or retrieved for this purpose alone cannot usually be used to identify you.
Marketing
The technical storage or access is required to create user profiles to send advertising, or to track the user on a website or across several websites for similar marketing purposes.
Manage options Manage services Manage vendors Read more about these purposes
View preferences
{title} {title} {title}