Often, monitoring companies require three (3) attempts to contact responsible parties before leaving messages or ending their attempts. This action pattern walks through creating a Loop for making these contacts. Keyholder Loops can be created as an Action Pattern bite to use in multiple action patterns. The goal is to create this for where you may need it.
Steps for creating a Loop Action Pattern for use in your system.
- Within your Monitoring Company record, navigate to Action Patterns and add a New Action Pattern. You will create this as a stand-alone piece that may be added to other action patterns where needed.
- Give it an ID and Description.
- Click Done.
- Start with a SET command and set it equal to zero (0).
- Add a Label to return just under the initial SET command.
- Add the CONTACT CUSTOMER KEYHOLDER action item.
- Under Logic - Select IF and select Prior Action Completed. (Meaning if the calls were made successfully).
- If Prior Action Completed - Close the Alarm.
- Under Logic - Select ELSE. (Meaning when contacts were not successful).
- Add a SUSPEND action for the specified number of minutes to wait before making the calls again.
- Add a new SET Command that is also called @COUNTER, and the details will be @COUNTER + 1. This sets the counter from 0 to 1.
- Add a LOG LINE to track the count.
- Add an IF looking at the @COUNTER VARIABLE and if it is LESS than the upper value you require, such as IF @COUNTER < 3 (Counter is less than 3).
- If less than 3, select JUMP TO the LABEL noted above.
- ELSE (Meaning counter is MORE than 3).
- Add a LOG LINE noting the Operator made ALL required attempts to reach the contacts.
- END IF (closes the Counter Logic ).
- END IF (closes the Prior Action Completed logic).
Notes:
Remember, when you open any IF statement, you must always close it with an END IF.
All Script messages (items with the curly brackets) are available in the guide called "Script Message Codes".