Creating ShadowCuff Protocols for an Entity

Creating ShadowCuff Protocols for an Entity

Purpose of Hardware Protocols

Alert
Any enrollee who is assigned hardware should have a protocol assigned to them
A hardware protocol allows you to designate automated steps of action to occur when an alarm is triggered for the hardware. The action steps can include:
  1. Notifications to assigned officers
  2. Notifications to tenant admins
  3. Notifications to a contact
  4. Notifications to any email address

Accessing the Protocol Groups Tab

Info
You must have Tenant Admin permissions in order to create hardware protocols
  1. Search for the desired entity by name
  2. Go to the "Protocol Groups" tab
  3. Select the "+Protocol Group" button

Creating the Protocol

  1. Enter a name for the protocol
    1. Naming the protocol something that indicates the intended enrollees it will be assigned to and/or type of hardware are helpful (Ex - "Low Risk - ShadowDevice")
  2. Select the type which indicates what type of hardware the protocol is for
    1. ShadoWatch
    2. ShadowDevice
    3. ShadowPhone
    4. ShadowCuff
  3. Active - defaults to yes
  4. Begin adding your protocol steps by selecting the "+Protocol" button
Info
Protocol steps should be created for each alarm type
  1. Fill in the following fields:
    1. Alarm Type - designates which alarm you want to set this protocol step for.  
    2. Grace Period - allows you to designate a buffer period so an alarm is not triggered instantly. If the alarm is resolved before the grace period ends, the alarm is ignored. 
    3. Active - defaults to active. To make a protocol inactive disable this field. 
    4. Auto-Resolve - defaults to being enabled. Allows for automatic alarm clearing when the issue that triggered the alarm is resolved. If this feature is disabled, all alarms will require to manual resolution by a user.
  1. Select the "+Step" button to enter protocol steps when an alarm is triggered. Your options are:
    1. Send email - send an email to any user, contact, tenant admin, or email address
    2. Send SMS - send a text to any user, contact, tenant admin, or email address
    3. Reboot device - will automatically initiate a reboot on the hardware
    4. Place call - places an automated call to the user using Shadowtrack's IVR system when an alarm is triggered
    5. Place call with delivery confirmation - places an automated call to the user using Shadowtrack's IVR system when an alarm is triggered. The user is required to acknowledge receipt of the notification. 
    6. Send Push Notification- notification sent to the enrollee or victim via the EnrolleeApp alerting the recipient of the violation. (Only for EnrolleeApp users. This action will not occur if the enrollee or victim is not logged in to the app)
    7. Send Silent Location Request - silent location sent to the enrollee's phone via the EnrolleeApp when a Device Comm Timeout occurs. These requests can be set to re-cur every 10 or more minutes, are send out only once. This step is specific to Device Comm Timeout only.
  2. You can repeat the same process to enter protocol steps when an alarm clears
  3. Select the action Type. Your options are:
    1. Automated - this is the default type. The action will be automated if this is enabled.
    2. Manual - the action must be completed manually by a user
      1. Select "Save"
  4. After adding a protocol step for each alarm, select "Save
    " to create the protocol.
Once all alarm steps and clear steps have been configured for the Protocol Group select "Save". The Protocol Group will now be available to assign to enrollees wearing the ShadowCuff. 


    • Related Articles

    • Creating Device Protocols for an Entity

      Purpose of Hardware Protocols Any enrollee who is assigned hardware should have a protocol assigned to them A hardware protocol allows you to designate automated steps of action to occur when an alarm is triggered for the hardware. The action steps ...
    • Creating ShadowDevice Protocols for an Entity

      Purpose of Hardware Protocols Any enrollee who is assigned hardware should have a protocol assigned to them A hardware protocol allows you to designate automated steps of action to occur when an alarm is triggered for the hardware. The action steps ...
    • Creating Interview Questions and Protocols 

      What Are Interview Questions and Protocols A Protocol should be assigned to the Enrollee so that someone is notified in the event of an Alarm. Questions are made of two parts, the primary question and the follow up question. Questions must be created ...
    • ShadowVisit Protocols

      What is ShadowVisit ShadowVisit is an in app feature that allows the enrollee to answer a series of questions upon arriving to the office for a scheduled appointment with their officer. Enrollees are able to check in and out using this feature, as ...
    • Creating a ShadoWatch Protocol for an Entity

      Purpose of Hardware Protocols Any enrollee who is assigned hardware should have a protocol assigned to them A hardware protocol allows you to designate automated steps of action to occur when an alarm is triggered for the hardware. The action steps ...