> 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/use-and-configure-alarms/generate-test-alarm.md).
# Generate Test Alarm
**Generate Test Alarm** creates a sample alarm event for a location **without triggering a live alarm**. Use the Generate Test Alarm feature to generate notifications to alarm contacts (SMS, email and mock call), and to test your on-site phone arm / disarm method.
Generating a test alarm does **not** arm or disarm the location or dispatch emergency services.
**Note:** This is different from [VerifEye](/docs/protect-your-locations-with-alarms/alarms-with-ai-detection/verifeye-alarm-verification.md) test mode. VerifEye test mode is used to walk through verification without dispatching police. Generate Test Alarm creates a labeled test event and sends test notifications.
***
## Access Generate Test Alarm Feature
**Generate Test Alarm** is available in the **web app** only (unavailable in the Solink mobile app).
To see the **Generate Test Alarm** button, you need:
* Access to the **Alarms** page
* Permission to manage alarm settings (typically an **Alarm Administrator** role, configured by a Solink representative)
* The Generate Test Alarm [user permission](/docs/manage-users-locations-and-your-account/users-page.md) must be enabled
The location must also have alarms turned on (not **Disabled**) and at least one **alarm camera**.
If you can open **Alarms** > **Configure** but do not see **Generate Test Alarm**, contact your Solink Customer Success representative or administrator to have it enabled.
***
## How to Generate a Test Alarm
To create a new test alarm:
1. On the Alarms page, select the **Configure** tab.
2. Select the location you want to test from the location list.
3. In the **Test Alarm** card, select **Generate Test Alarm**.
4. Choose an **alarm camera**. Only cameras configured as alarm cameras for this location are available. One camera can be selected at a time.
5. Review the event details:
* **Title** is set automatically to `TEST [ location name ]` and cannot be edited. This makes the event easy to tell apart from a real alarm.
* **Date** is the current date and time at the location (shown in the location's timezone) and cannot be edited.
* **Notes** are optional. Use this field to describe why the test was generated (for example, "staff training").
6. Select **Generate**:
A confirmation message appears: **Successfully created test alarm event**. See the following section to understand what happens next/test alarm event behaviour.
***
## Generate Test Alarm: Expected Behaviour
Once you have created a test alarm, a test event is generated. The event includes video from around the time you generated it.
Navigate to the **Recent Alarm Events** tab to see your test event, indicated by a "Test" label as shown in the following image:
You can close the event and it will appear as a closed test alarm event on the **Events** page > **Alarms** tab.
**Note**: The location stays in its current armed or disarmed state. Nothing about the live alarm system changes.
Additionally, the following happens based on your alarm subscription and enabled alarm features:
* **Self-Monitored Alarms**: The primary alarm contact receives an email and/or text message, based on whichever contact information they have provided within Solink.
* **Professionally-Monitored Alarms**: The primary alarm contact receives a text message and a pre-recorded phone call.
* **Phone Arm/Disarm**: A pre-recorded phone call is placed to the onsite phone listed in the Phone Arm / Disarm tab. To ensure the automated call reaches the on-site phone, you must make adjustments to bypass the store's automated message / IVR tree - see [Arm/Disarm PIN](/docs/protect-your-locations-with-alarms/use-and-configure-alarms/arm-disarm-pin.md#configure-phone-pin) for more information.
Please note the following caveats for generating test alarm events:
* The alarm tablet does not receive any correspondence/notifications related to the test event.
* Test events currently do not trigger any onsite alarm speakers.
---
# 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/use-and-configure-alarms/generate-test-alarm.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.