> 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/panic-button-overview-wsper.md).
# Panic Button Overview (WSPER)
Solink has partnered with [WSPER](https://getwsper.com/) to offer a panic button that allows you to dispatch police in urgent situations and record the associated camera footage as a Solink event (accessible from the Events page).
The panic button is a wireless alerting device that is powered by two AA Batteries and is connected to an LTE-M network. WSPER's platform monitors the device’s battery, health and allows for customizable panic button contacts and security PINs (separately from Solink).
See the following section for an overview of how the panic button works with Solink.
**Note**: You can refer to WSPER's [FAQs here](https://getwsper.com/#faq-area). Please also note, while WSPER does monitor temperature and door state detection, these features are beyond Solink's current scope of our integration.
## Panic Button Event in Solink
You can review the camera footage associated with the panic button shortly after pressing.
To review panic button events:
1. Navigate to the **Events** page in the Solink platform.
2. Select the **Alarms** tab:
3. Search for "WSPER" in the Events page search bar. This returns all panic button events and you can watch the camera footage directly from any of these events.
The following fields are recorded in the event card:
* **imei**: Unique device ID number.
* **mode**: "production" means the panic button event was generated during a live/real scenario. Otherwise, this field displays "testing" if the panic button event was generated in test mode.
* **name**: Device name, managed by WSPER.
* **wsperID**: device ID from WSPER.
* **alarmId**: ID from the monitoring partner.
* **status**: "success" means the event was successfully sent to our monitoring partner.
## Change Camera(s) Associated with Panic Button
When someone presses the panic button, footage from one or more of your cameras is recorded in Solink on the Events page.
Solink can associate any of your cameras with the panic button so that only the designated cameras record footage when the panic button is activated.
If you require any additional changes to the configuration, please reach out to our [Support](/docs/get-started/introductory-guides/how-to-contact-our-team.md) team.
**Note**: There is a limit of **10 cameras** that can be associated with the WSPER panic button.
## How to Purchase Panic Button
If you are interested in ordering a panic button from WSPER, please contact your Solink Customer Success representative, or Solink Sales at **1-888-817-6546.**
---
# 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/panic-button-overview-wsper.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.