High-Volume Events

Learn now to use high-volume events

Updated over a week ago

A high-volume event is a verification event that raises an alarm regardless of the content of the provided video because there are more than 15 verifications triggered within 1 hour.

Note: No Person Shown responses are not counted to the high-event volume total.

How high-volume events work

The following workflow is a typical scenario of how high-volume events work, but can vary on specific instances.

  1. On the 16th verification sent to our monitoring agents for review within the hour, the agent follows the normal alarm procedure irrespective of:

    • Security prompt selected by the customer

    • Content of the provided video

    • Whether test mode is enabled or not

  2. If there are contacts in the contact list, the agent attempts to reach the contacts through a courtesy call. As part of the courtesy call initiated due to a high-volume event, the agent mentions that this is only a courtesy call due to a high-volume event.

  3. At that moment, the receiver caller may choose to resolve the alarm or dispatch emergency services, if necessary. You may also ask the agent to disarm the site for up to 12 hours.

  4. If the agent cannot reach any listed contacts or if there are no contacts listed, the agent dispatches emergency services to the address of the site (provided test mode is disabled).

Scenarios when a high volume event is initiated

Scenario A

Suppose your business has a cleaning crew that forgets to disarm the alarm system (which is set to "Normal" security and test mode disabled) while entering the building. They proceed to clean the premises, which triggers motion-detected events through our motion sensors. The context cameras set up for these motion sensors provide video for the agent to review.

In this case, the first 15 verification events are not deemed as a threat to person or property and no alarm is raised. However, when there is a 16th verification event within an hour, agents raise an alarm, regardless of whether there is threat to person or property. A courtesy call is initiated to the contacts listed on the contact list and if the agent is unable to reach anyone listed, emergency services is dispatched to the site location.

Scenario B

Suppose your site has a camera that points to an area where there can be heavy foot traffic (such as a sidewalk or a public area). If you arm your site during a busy period of time, this can lead to multiple verification events triggered within 1 hour. In this case, the 16th verification event raises an alarm and the agent follows the normal alarm procedure (courtesy call and dispatch emergency services, if deemed necessary).

How to avoid high-volume events

Such events can be annoying for both you and your business and may lead to false alarms. There are various ways you can avoid this situation:

  1. Check your camera configuration, in particular:

    1. Make sure the camera is not pointing to an area where there can be heavy foot traffic while your site is armed.

    2. Set up regions of interest, line crossing, or loitering on your camera that you'd like to use as an alarm trigger to specify parts of the video on which it should detect movement/people.

    3. Make sure that you are deliberate about selecting which cameras to set up as alarm triggers.

    Note: You can check the number of video verifications on the Agent Reviewed section (on the alarm's site activity page).

  2. Check your site configuration, in particular:

    1. Ensure that your arming schedule is appropriate for your business so that the system only arms when necessary.

      • You can use the mobile app, console keypad, and access controlled doors arm/disarm to manually arm/disarm your site.

      • We also recommend using the arming schedule feature to arm/disarm if helpful.

    2. Remove cameras that may be sending redundant or unhelpful video verification events.

    3. Consider breaking up your site into multiple sites if the cameras need to follow a different arming schedule to minimize unnecessary verification events that may be triggered.

Related resources

Need more help? Contact Verkada Support

Did this answer your question?