The response tab displays response plans with the associated action plan. The Call List can be overwritten by creating client level response plan assignments.
Response plans originating at the global, client or template level will appear when the Response Plan filter is enabled. Each of these response plans has an Override button visible below the list of response plans. When pressed this button gives you options for overriding the higher level response with a client level response plan assignment.
Both priority and non-priority action plans are listed on the client response tab. In the the response plan preview represents the actual keyholders, guards and other users who will be displayed, in descending Call Order, and along with contact details and instructions in the event of alarm activation. Non-priority action plans on the other hand will never generate an activation in Patriot. Therefore response plans assigned to non-priority action plans will never be "seen" by operators, but they can still be very useful for creating fully automated signal responses using assignable tasks.
When setting up a multi area client, configure your client level response first in the base account and enable the "Share Response" option. Then make sure all area clients have their response linked to the base account, with "Include Base Response" enabled on all the areas. If a particular area needs a customised response, you can easily achieve this by unchecking the Include Base Response option on the response tab of the area client. When overriding the response in this way, make sure that the Include Base Users option is enabled on the Users Tab of the area account. This means that the full complement of site keyholders are available for creating your area level response.
The Response Plans area in the Response Tab of a Client allows response plans to be assigned to an Action Plan at the client level. Client level response plan assignments take precedence over (override) all other levels of response plan assignment (Global, Dealer & Template). See Action Plans for more information about actions plans and their response plan assignments.
By clicking the next to the override button, will allow you to create a new response plan.
This button is primarily for legacy support. If you need to create a new client response plan for a particular action plan(s) the recommended way to do this is by overriding the global response plan already assigned to this action plan(s). If however you cannot do this because no global action plan is assigned to the action plan(s) then you should begin by assigning one globally first in preference to using the insert new client response plan button. By working in this recommended way you should minimise the number of response plans in your system.
The form allows you to switch between User Types tab and the Users tab. Therefore you can choose specific users to assign to the response plan. You also get to assign the response plan to a specific action plan.
This can be edited by switching through the 'Site Instructions' tab (see image)
Instructions that are saved here will appear in users who are of type 'Site'.
Note: This feature is on limited released at this stage, and has only been made available at certain sites. This feature will be given a general release in the near future.
Response Plan Extensions can be used to extend the existing response instead of overriding it. This is useful when you simply need additional behaviours for specific events. When building a response plan, in addition to the standard response plan chosen, any response plans with a matching extension filter will be applied as well. For example, as shown in the image below, ResponsePlanA has one user Jay Tocker, and he wants to be notified for all events on zone 1 and module 0, and all type 120 events.
Note that response plan extensions can currently only be applied at client level. Extensions configured on templates will not have any effect for clients using those templates. For example if a client is using a Contact ID template, if you set a response addition to a event type in the template itself, this will be ignored for any clients using the contact id template.