> For the complete documentation index, see [llms.txt](https://help.verkada.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.verkada.com/new-alarms/configuration/configure-an-alarm-response/configure-silent-and-duress-alarm-responses.md).
# Configure Silent and Duress Alarm Responses
## Silent Alarm Response
Silent alarms allow site staff to request help without any on-site indication that an alarm has been triggered. This allows staff to signal for assistance discreetly, helping to avoid the escalation of a critical situation.
{% hint style="warning" %}
Silent alarms are commonly used with panic buttons and are configured at the **Response** level.
{% endhint %}
### Configuration
{% hint style="danger" %}
To configure a silent alarm, create a new response flow and toggle on **Silent Alarm**. Existing response flows cannot be converted into a silent response.
{% endhint %}
{% stepper %}
{% step %}
**In Verkada Command, go to All Products > Alarms.**
{% endstep %}
{% step %}
[**Create an Alarm site**](/new-alarms/configuration/alarm-sites.md) **or select the alarm site that you want to configure.**
{% endstep %}
{% step %}
**In the left navigation, select Response.**
{% endstep %}
{% step %}
**Next to Alarm Response, click** :circle-plus:**.**
a. Enter a unique name.\
b. Toggle on **Silent Alarm.**
{% endstep %}
{% step %}
**(Recommended) Set Immediate Dispatch as the response flow.**
{% endstep %}
{% step %}
**Add additional users to the contact list if needed.**
{% endstep %}
{% step %}
**Click Save.**
{% endstep %}
{% step %}
**Move any partitions that should trigger a silent alarm into this Silent Alarm Response flow.**
{% endstep %}
{% endstepper %}
This is how a Silent Alarm Response will appear on the Response page.
|  |  |
| --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
***
## Duress Keycode
A duress keycode allows site staff to silently trigger an alarm if they are forced to disarm the system. When entered on the keypad, the system disarms normally, but an alarm is triggered in the background without any indication on the keypad.
{% hint style="danger" %}
Duress keycodes are configured at the site level. Each alarm site can have only one duress keycode.
{% endhint %}
### Configuration
{% stepper %}
{% step %}
**In Verkada Command, go to All Products > New Alarms.**
{% endstep %}
{% step %}
[**Create an Alarm site**](/new-alarms/configuration/alarm-sites.md) **or select the alarm site that you want to configure.**
{% endstep %}
{% step %}
**In the left navigation, select Keycodes.**
{% endstep %}
{% step %}
**At the top, select Duress Keycode.**
1. On the top right, click :plus: **Add.**
2. A duress keycode is automatically generated. To edit the default keycode, click and enter the desired code.
3. By default, Immediate Dispatch is selected as the response flow.
4. Add additional users to the contact list if needed.
5. Click **Save.**
{% endstep %}
{% step %}
**This creates a new Silent Alarm Response for Duress Alarms. You can view and manage the Duress Response from the Response page.**
{% endstep %}
{% endstepper %}
{% hint style="warning" %}
Silent and duress alarms provide no on-site indication that an alarm has been triggered.
* No outputs are activated
* No automated announcements or agent talkdowns occur
* The keypad shows no visual or audio alerts
{% endhint %}
---
# 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.verkada.com/new-alarms/configuration/configure-an-alarm-response/configure-silent-and-duress-alarm-responses.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.