> 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/intercom/configuration/intercom-reader-settings.md).

# Intercom Reader Settings

Configure the readers in your second generation Verkada intercoms

{% stepper %}
{% step %}
**In Verkada Command, go to All Products > Intercom.**
{% endstep %}

{% step %}
**Select an intercom to configure.**
{% endstep %}

{% step %}
**At the top, click Settings > Door.**
{% endstep %}
{% endstepper %}

## Manage Credential Types

You can manage which credential types are allowed or disallowed by using the following toggles:

* **Badge Reader**: Enable or disable RFID and NFC credentials.
* **NFC Unlock**: Allow or disallow NFC credentials.
* **Bluetooth Unlock**: Manage Bluetooth credential access.

## Configuring Gesture Unlock

Verkada Intercoms (TD52 + AD34, TD33, TD53, and TD63) support **Gesture Unlock**, a feature designed to prevent accidental Bluetooth unlocks. Gesture Unlock requires a specific gesture in addition to a Bluetooth credential to unlock a door.

{% stepper %}
{% step %}
**Navigate to Intercom Settings > Reader > Bluetooth Unlock Trigger > Custom Configuration.**

<div align="left" data-with-frame="true"><img src="https://3022285914-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FTH6kITd3Fb5UOnnsfQ9r%2Fuploads%2Fgit-blob-5088590c41458df083bf478051db53a13ead7ca7%2Ff7a116c164fb803532caab9b400834299ff01289.png?alt=media" alt="" width="790"></div>
{% endstep %}

{% step %}
**Select a preset option or click Advanced to define your own parameters.**

<div align="left" data-with-frame="true"><img src="https://3022285914-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FTH6kITd3Fb5UOnnsfQ9r%2Fuploads%2Fgit-blob-611cb1a8ecf04bb65b07e36f72fb33ce0e0a9504%2F010cfd308730b7d6f022a947137670741580f4c0.png?alt=media" alt="" width="783"></div>
{% endstep %}
{% endstepper %}

### Reader compatibility table

|                            |                                  |                                    |
| -------------------------- | -------------------------------- | ---------------------------------- |
| **Mode**                   | **Wiring**                       | **Reader Compatibility**           |
| **Single Door Controller** | Directly to the intercom         | Uses integrated reader             |
| **Paired**                 | To a Verkada access controller   | Reader must be hardwired via RS485 |
| **3rd Party ACU**          | To a 3rd party access controller | Unsupported                        |

***

## Other Bluetooth Settings

* **Bluetooth Cooldown**: Define the minimum time required between Bluetooth unlock attempts.
* **Beep on Bluetooth Unlock**: Toggle to enable or disable audible feedback when a Bluetooth credential grants access.

***

{% hint style="info" %}
**Prefer to see it in action?** Check out the [video tutorial](https://www.youtube.com/watch?v=pWUVHl3gzKc).
{% 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/intercom/configuration/intercom-reader-settings.md?ask=<question>&goal=<user_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.