Notification Action Types

Any of the following scenarios will trigger the secondary notification.

• All endpoints have a status of Error.
• No endpoints are associated with the original notification.
• There are insufficient endpoints for the notification type.
• The original notification is not high enough priority to override a currently running notification.
• The notification is stopped due to running longer than the Global Settings timeout value
• More concurrent notifications than allowed by the Global Settings Maximum Concurrent Notifications advanced setting.

Provide a button that your endpoints can use to respond with a predetermined string.

See Response Options Notification for a detailed example.

See Sent Notification Responses Tab in the Sent Notifications topic for more information.

1. For Action Type, select Add Response.
2. For Action, select Reply.
3. For Notification, select a Notification to activate with the action.
4. For Full Text, enter a longer string to be used by endpoints with more display space, such as the Mobile app or the Desktop Notification Client.
5. For Button Text, enter a short string to be used by endpoints with limited display space, such as desk phones.
6. (optional) Enable any of the following:

   • Allow Text in Response, allows a contact on a mobile device to provide additional text with their response.

     Note: Revolution truncates long responses to 128 characters.

   • Allow Location in Response, allows a contact on a mobile device to send their location with their response.
   • Requests Emergency Response, indicates that responses of this type will have priority reporting on the Sent Notification Details page.

   • Forward audio to linked notification, indicates that recorded audio should be sent with the linked notification. Using this you can use notification actions to stage live notifications

     Note: The notification type must be Recorded.

   • Forward images to linked notification and Forward text to linked notification, indicate that any images and text should be sent with the linked notification. This will allow activator title and activator body text to pass through to secondary notifications.

   • Use Quota, indicates that you would like something to occur after a specified number of responses are received. If your notification is Continuous, then reaching the Quota will also end the notification.

     When enabled, you will see these additional settings

     • Quota, an integer that defines the number of responses to receive before the action. If you leave this value at 0, upon saving the Use Quota field will be unselected and there will be no quota for the response.

     • Over Quota Response, a string that is sent to responders after a quota has been met.

     You can optionally create a Send Notification action that triggers an additional notification once any quota is met. See Sending a notification based on an event.

Examples

• Escalate security issues — Combine a Reply response action with a Send Notification action to send an escalation notification if no one responds to a request.

  Create a Reply response action to send a request to your security team (Contacts) asking for someone to reply with "I Will Respond" (Button Text).

  Create a Send Notification Action that sends an escalation notification (Notification) if this notification does not receive a response (Send Time: On No Response) after 10 minutes (Delay: 10).

• Use quotas for notification responses — Assuming the following scenario:

  An incident occurs at your location and you need two people to respond.

  For the notification, create a Reply response where Full Text is "Yes, I will be there". For that response, enable Use Quota, set Quota to 2, and Over Quota Response to "Enough people have already responded."

  In the given scenario, your contacts will receive a notification that assistance is required. Once Revolution receives two affirmative responses, any other respondents will receive the additional note that enough people have already responded to the situation.

Provide a button that your endpoints can use to activate an additional notification.

1. For Action Type, select Add Response.
2. For Action, select Notify.
3. For Notification, select a Notification to activate with the action.
4. For Button Text, enter a short string to be used by endpoints with limited display space, such as desk phones. Notifications via SMS use this value.
5. For Full Text, enter a longer string to be used by endpoints with more display space, such as the Mobile app or the Desktop Notification Client. Notifications via Mass Dialer use this value.

Examples

• In an emergency allow someone to request assistance – Combine a Notify response action with a Reply response action allowing someone to request assistance or indicate they are fine.

  Create one response action with the Reply action type allowing them to indicate "I'm fine" (Button Text), but do not activate a notification.

  Create a second response action with the Notify action type, allowing the contact to "Request Assistance" (Button Text) that activates a notification that initiates a security response.

These Action types apply only to the Conference Notification type.

Provide a button that endpoints can use to add an endpoint to the Conference.

1. For Action Type, select Add Response.
2. For Action, either:
   1. select Add Endpoint
      1. For Endpoint to Add, select the endpoint to be added when the button is selected
      2. (Optional) enable Auto Escalate if you want this endpoint automatically dialed if no one has joined the conference within 30 seconds. (Your system administrator can adjust this time in Global Settings > Notification > Conference Auto-Escalate Delay Seconds.)
   2. select Add Endpoint DN to create a button a user can use to then enter an additional number to add to the conference.
3. For Button Text, enter a short string to be used by endpoints with limited display space, such as desk phones.
4. For Full Text, enter a longer string to be used by endpoints with more display space, such as the Mobile app or the Desktop Notification Client.

Provide a button that endpoints can use to initiate a call to a predefined number.

Note: Supported only by Cisco and Mitel phones.

1. For Action Type, select Add Response.
2. For Action, select Dial.
3. For Number to Dial, select a number to activate with the action.
4. For Button Text, enter a short string to be used by endpoints with limited display space, such as desk phones.
5. For Full Text, enter a longer string to be used by endpoints with more display space, such as the Mobile app or the Desktop Notification Client.

Provide a button that allows your endpoints to stop or cancel a notification, such as iterative notifications or those with lengthy audio transmissions.

1. For Action Type, select Add Response.
2. For Action, select Stop.
3. For Stop Mode, select one of the following values:
   • Finish – ends the notification after the current iteration or audio transmission completes.
   • Cancel – abruptly ends the notification once selected.
4. For Button Text, enter a short string to be used by endpoints with limited display space, such as desk phones.
5. For Full Text, enter a longer string to be used by endpoints with more display space, such as the Mobile app or the Desktop Notification Client.

Add a button to the Details page of the notification allowing a Revolution user to initiate a notification. This could be useful when combined with a Reply Response where a user can initiate a notification if an endpoint replies in a specific way.

1. For Action Type, select Add Web Action.
2. For Action, select Notify.
3. For Notification, select a Notification to activate with the action.
4. For Button Text, enter a short string to be displayed as the button text.
5. For Button Color, use the color picker to select a color.

The button appears below the notification status indicator.