Version 2.9 - January 2020
by Dan Simms, on Feb 3, 2020 10:39:02 PM
- Voice incident notifications – the ability to send voice based incident notifications via a telephone call, for recipients that are blind or have poor vision. This is compatible with the multiple action response functionality, allowing an end-user to respond to an action response using a telephone.
- Multiple action response functionality – support for custom action response buttons, to engage with recipients. e.g. ‘I need help’, ‘I’m affected’, ‘I’m not affected’. These work across all supported channels. These can be assigned independently to incident notifications giving greater control over response options.
- Template simplification - templates can now be configured to hide or make elements of the user interface read only for a specific template e.g. hide ‘users affected’ for specific service template.
- Incident subscription override - administrators can choose to ignore end-user profile preferences and send incident notifications to all end-users in the specified location.
- Channel override - administrators can choose which channels to use for incident notifications when sending an incident notification.
- Incident follow-up - administrators can choose to send incident notification to only the people that did not reply to the previous incident notification (follow-up).
- Message delivery – new user interface for viewing the delivery status of incident notifications. This includes if/when a notification was delivered, if/when a recipient responded and what the response was.
- Groups – groups can now be created, and used as a target for incident notifications.
- Private incidents – private incidents can now be created, meaning they will only be visible on the web portal to recipients of the incident. This is useful for business continuity communications that target specific groups such as the Gold Team, Silver Team or Bronze Team.
- Incidents can be raised with 'Under investigation' status.
- A ‘mandatory service’ *1 can be created from template (client specific functionality – *1 Platinum service)
- Notification messages can ignore end user day and times preferences.
- The administrator will be able to view who did not click the default action response 'I'm affected' easily.
- Incidents on dashboard will be sorted by status first and then by creation time.
- Incidents viewed on the smartphone will be shown only for user location in correct order.
- Planned maintenance entries can be created without specific technology while ignoring user preferences (sending email digest to everyone that's in specified location).
- Administrators can create custom action response options without leaving Incident creation page.
- Administrators can control if the voice notification channel should be enabled for end users.
- Administrators can adjust default text-to-speech template for phone call channel.
- Administrators can configure text-to-speech voice actor from list of available ones 'https://developer.nexmo.com/voice/voice-api/guides/text-to-speech'
- Administrators can select 'Allow paid channels' functionality when sending notifications out (that will allow SMS and voice functionality).
- Administrators can specify who can use templates to create entities (incidents and others)
- Administrators can see invalid SMS responses provided by end users.
- Administrators can see invalid phone call (DTMF) responses provided by users
- Users can be properly removed by administrator via UI