> 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/alarm-motion-zones-quick-tips.md).
# Alarm Motion Zones: Quick Tips
A good motion zone setup is crucial for your Solink alarms to be successful.
[Alarm motion zones](/docs/protect-your-locations-with-alarms/alarm-setup/alarm-motion-zones.md) **capture suspicious activity** that can lead to false alarms. However, motion zones must be configured correctly to be effective.
To get started, navigate to **Alarms** > **Alarm Configurations** > select the **Add** toggle button for the camera you want to configure motion zones for:
Follow the tips below to ensure your motion zones are working successfully.
***
## **1. Do - Highlight pathways**
Highlight areas where people can walk in your store.
When you highlight pathways, try and think like a burglar - where would they go in your store? What assets would they want? How would they get those assets?
See the following image - walkways are highlighted, but the store counter is not:
***
## **2. Don't - Highlight reflective surfaces**
Avoid highlighting objects with reflective surfaces, such as computer screens and glass containers. Light can move on reflective surfaces and trigger false alarms.
See the areas outlined in red in the following image - you should never highlight these:
***
## **3. Do - Check the "estimated number of motion alarm items"**
The closer the number is to 0, the more effective your motion zone will be at capturing suspicious activity and avoiding false alarms:
***
## Video Tutorial
Want to see motion zone setup in action? Watch this video for a quick tutorial.
{% embed url="" %}
---
# 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/alarm-motion-zones-quick-tips.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.