> For the complete documentation index, see [llms.txt](https://help.solink.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.solink.com/docs/protect-your-locations-with-alarms/professionally-monitored-video-alarms/alarm-events-with-video-verification.md). # Alarm Events with Video Verification This article guides you through alarm event logs for [Solink Professionally Monitored Video Alarms](/docs/protect-your-locations-with-alarms/professionally-monitored-video-alarms/professionally-monitored-video-alarms-overview.md). For more information on Professionally Monitored Alarms workflows and outreach, [see this guide](/docs/protect-your-locations-with-alarms/professionally-monitored-video-alarms/professionally-monitored-video-alarms-how-it-works.md). When an agent verifies an alarm event, they provide a detailed reason / result for what they determined based on video they watched. All agent responses are displayed in the alarm event log for further review and investigation. You can review these alarm events from the **Alarms** tab via the **Events** page: ![](https://1562067156-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlMN1EUQcXYfv7FYpGJWR%2Fuploads%2Fgit-blob-195b3bdfef5d0c7b03a7b228fb3da0f8cafcd161%2F62d9831cdb2b6ab9.png?alt=media) Some examples of information you might see in the alarm event include: * **Alarm Opened**: A motion event has triggered an alarm verification while the system is armed. * **Camera Name**: The names of the camera(s) where the motion event occurred (e.g: Front Door, Kitchen, etc.). * **Verification Started**: An agent has received the video and is in the process of determining if there is a threat to person or property. * **Verification Error**: The agent has experienced an issue with the video feed (e.g: unverifiable due to loading issues or inclusive threat to person or property). * **Verified False Alarm**: The agent determined there is no threat to person or property and they will include relevant details (e.g: Employee Detected). * **Unverifiable Alarm**: On some occasions the agent may be [unable to load video](https://help.solink.com/docs/protect-your-locations-with-alarms/professionally-monitored-video-alarms/pages/6QAdqy2bC3LuhQ05meD7#id-2.-unable-to-load-video) or [unable to determine if there is an active threat to person or property](https://help.solink.com/docs/protect-your-locations-with-alarms/professionally-monitored-video-alarms/pages/6QAdqy2bC3LuhQ05meD7#id-3.-inconclusive-with-visible-person-on-video), which is classified as an **Unverifiable Alarm**. * **Created Alarm**: The agent has determined there is a real OR potential threat to person or property. For more information on types of and reason for outreach you might receive, see [Professionally Monitored Video Alarms: How it Works](/docs/protect-your-locations-with-alarms/professionally-monitored-video-alarms/professionally-monitored-video-alarms-how-it-works.md). * **Police Dispatched**: The police have been contacted. * **Canceled Alarm**: An agent has cancelled the alarm - this can happen if more context became available showing it was not an emergency, or an alarm contact requested cancellation. * **Alarm Closed**: The alarm is considered resolved. * **Alarm Call Details**: If a verification agent calls the alarm contact(s), information is logged including the call duration, when the agent called and the alarm contact's name and phone number. See more information [here](/docs/protect-your-locations-with-alarms/alarm-setup/alarm-contacts.md#alarm-contact-calls-professionally-monitored-video-alarms). * **Pin Delay**: The time between arming the system via PIN and the time to leave the premises. * **Disarm**: Shows who disarmed and when the alarm was disarmed during an open alarm. Additionally, alarm events can include the **individual camera number**, the **duration of the event** and the **name of the camera,** as shown in the following image: ![](https://1562067156-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlMN1EUQcXYfv7FYpGJWR%2Fuploads%2Fgit-blob-7b4182e80c9be92610e0926fdb7f6353d228dd26%2Fa54661ff3017057d.png?alt=media) *** ### Verified Alarms If the agent has reviewed the video alarm and determined there is a threat to person or property, they notify alarm contact(s). **Note**: See [this guide](/docs/protect-your-locations-with-alarms/professionally-monitored-video-alarms/professionally-monitored-video-alarms-how-it-works.md) for a complete list of all agent communication methods in the event of a Verified Alarm. The agent also provides reasoning within the alarm event log to explain why it was a **Verified Alarm**. Below are all of the possible Verified Alarm reasonings the agent can provide in the event: * Active break-in in progress * Person inside taking items * Person outside taking items * Person taking items * Unknown person inside * Unknown person outside * Person detected * Other *** ### Verified False Alarms If the agent reviews video footage of a potential alarm and determines there is **no threat** to person or property, they close the alarm and provide context in the alarm event for their decision. Below are all of the potential reasonings the agent can provide in the event card when there is a **Verified False Alarm**: * No person detected * Employee detected * First responder on site * Person detected inside, not suspicious * Person detected outside, not suspicious * Person detected * Moving vehicle * Other *** ### Unverifiable Alarms On some occasions the agent may be unable to make a conclusive decision. Below are the possible unverifiable alarm reasonings: * Verification error - time out * Verification error - unknown * Verification error - issue loading video * Camera obstructed or dark * Unable to determine conclusively #### [Unable to Load Video](https://help.solink.com/docs/protect-your-locations-with-alarms/professionally-monitored-video-alarms/pages/6QAdqy2bC3LuhQ05meD7#id-2.-unable-to-load-video) * Video technical issue #### [Inconclusive (with visible person on video)](https://help.solink.com/docs/protect-your-locations-with-alarms/professionally-monitored-video-alarms/pages/6QAdqy2bC3LuhQ05meD7#id-3.-inconclusive-with-visible-person-on-video) * Other - person present * Unable to determine person activity --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://help.solink.com/docs/protect-your-locations-with-alarms/professionally-monitored-video-alarms/alarm-events-with-video-verification.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.