Configure response actions

The Action drop-down list allows you to control what action the system takes based on the response.

For information on setting response count options, see Configure response counts.

Actions specify how each response affects the notification flow. Action options should reflect the goals of your form and the processes that exist in your organization. The following table summarizes the available actions (from the perspective of the recipient who is responding to a notification):

Value Result
Record Response xMatters records the user's response and stops notifying them. When this response action is selected, xMatters does not delink the user from the event. Users can change their responses by responding to the notification again.
Assign to User xMatters stops notifying other recipients, but continues the process for this recipient.
Stop Notifying User xMatters stops notifying this user, but continues the notification process for other recipients.
Stop Notifying Target xMatters stops notifying the targeted user or other members in a target group, but continues notifying other users and members of other groups.
Escalate xMatters stops notifying this user, but continues the process by immediately escalating the event to the next scheduled recipient.
End xMatters stops notifying all recipients, and terminates the event. This stops notifications whether the responses came from an individually targeted user, a user in a group, or from within a nested group.

Response action examples.

Configure response counts

If you have selected the "Count Responses" check box on the Recipients section of your form, the Action drop-down list has different options:

Value Result
Add to Count The response is counted towards the total, and xMatters stops notifying the responder.
Do Not Add to Count The response does not count towards the total. xMatters stops notifying the responder and immediately escalates the event by attempting to notify the next recipient.

For each response, you can specify whether it should be count towards meeting the required minimum number of responses for each group of recipients. Once the defined "fill count" has been met, xMatters stops notifying the target group. Once all groups have met their fill counts, or the total number of responses determines that the fill count cannot be reached, the event is terminated.

Response action examples

The response actions you assign to each response can affect how (and when) xMatters continues to notify other recipients in the escalation path. This behavior, especially for messages that include a "Stop Notifying x" or "Escalate" option, can get complicated when groups are ‘nested’ (i.e., groups are members of other groups), and when other recipients are also targeted by the same event. In addition, recipients can be targeted by several paths; for example, a user may be a member of multiple targeted groups, or may be targeted as a group member and as an individually-targeted user.

The following examples outline the behavior of the "Stop Notifying Target" response in some common situations, and include a few clarifications about the "Escalate" response.