> 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/wire-a-video-intercom/set-up-td63-keypad-directory.md).

# Configure Intercom Directories

Enable multitenant functionality on TK74 and TD63 Video Intercoms.

{% hint style="info" %}
**Before you begin:** Review how to [configure intercom receivers](https://help.verkada.com/intercom/configuration/add-and-configure-receivers-in-intercom.md).
{% endhint %}

***

{% tabs %}
{% tab title="TD63" %}

### Enable Keypad Directory

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

{% step %}
**Select your intercom and click Settings.**
{% endstep %}

{% step %}
**Under Device, toggle on Multitenant Directory.**
{% endstep %}
{% endstepper %}

### Enable long call codes

By default, extensions are limited to three digits or fewer to prevent conflicts with access PIN codes (four digits or more). You can disable access PIN codes to allow for longer extensions.

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

{% step %}
**Select your intercom and click Settings.**
{% endstep %}

{% step %}
**Under Device, toggle on Enable Long Call Codes.**
{% endstep %}
{% endstepper %}

***

## Configure your Directory

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

{% step %}
**Select your intercom and click Receivers.**

{% hint style="info" %}
The directory always includes one default entry tied to the call button. Pressing the button triggers that call flow.
{% endhint %}
{% endstep %}

{% step %}
**At the top, click Add Tenant.**

1. Enter a tenant name.
2. Enter the call code (extension).
3. (Optional) Upload a tenant logo. This will appear in the directory.
4. Click **Continue**.
   {% endstep %}

{% step %}
**Configure the receivers tied to the call code.**

{% hint style="warning" %}
See [Add and Configure Receivers in Intercom](https://help.verkada.com/intercom/configuration/add-and-configure-receivers-in-intercom.md) for more information.
{% endhint %}
{% endstep %}

{% step %}
**Repeat these steps until all directory entries have been added.**

<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-629c8ca5c71d9f18e60fd93b7f3e123c90e403cc%2F422609a21c7848e83078c19ce38c00c35c75d3ac.png?alt=media" alt=""></div>
{% endstep %}
{% endstepper %}

***

## Dial a tenant

{% stepper %}
{% step %}
**Enter the tenant’s extension code (e.g., 123).**
{% endstep %}

{% step %}
**Press # to start the call.**

You’ll be connected to the call flow linked to that extension.

{% hint style="info" %}
The **#** key serves different purposes on the TD63 keypad:

* **Directory calls:** Enter the tenant extension, then press **#** to start the call (for example, **123#**).
* **Entry codes:** Enter the entry code, then press **#** to unlock the door (for example, **1234#**). See [Grant Temporary Intercom Access with Visit Keys](https://help.verkada.com/intercom/configuration/grant-temporary-access-with-visit-keys.md) for more information.
  {% endhint %}
  {% endstep %}
  {% endstepper %}

***

## Print your Directory

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

{% step %}
**Select your intercom and click Receivers.**
{% endstep %}

{% step %}
**Select Print Directory.**

1. (Optional) **Upload a logo** to display in the directory header.
2. Enter a unique name.
3. Add visitor instructions to explain how to use the directory (for example, dial the extension and press **#** to call). If visitors also use entry codes on the same device, include instructions to enter the code followed by **#** to unlock (for example, **1234#**).
4. Select the directory entries to display.
5. (Optional) Toggle on **Tenant Logos** to display logos.
6. Click **Download PDF** to generate the directory.

<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-c68a29e5657511420284d03d3e2d666469988500%2Fac03642ae82d4f174206a0253703535238765f3f.png?alt=media" alt=""></div>
{% endstep %}
{% endstepper %}
{% endtab %}

{% tab title="TK74" %}

## Enable Multi Tenant

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

{% step %}
**Select your TK74 and click Receivers.**
{% endstep %}

{% step %}
**Select Enable Multi Tenant.**
{% endstep %}

{% step %}
**At the top, click Add Tenant.**

1. Enter a tenant name.
2. Enter the call code (extension).
3. (Optional) Upload a tenant logo. This will appear in the directory.
4. Click **Continue**.
   {% endstep %}

{% step %}
**Configure the receivers tied to the call code.**

{% hint style="warning" %}
See [Add and Configure Receivers in Intercom](https://help.verkada.com/intercom/configuration/add-and-configure-receivers-in-intercom.md) for more information.
{% endhint %}

**Repeat these steps until all directory entries have been added.**
{% endstep %}
{% endstepper %}

***

## Call a tenant

{% stepper %}
{% step %}
**Click Directory.**
{% endstep %}

{% step %}
**Tap on the tenant of your choosing.**
{% endstep %}

{% step %}
**You’ll be connected to the call flow linked to that extension.**
{% endstep %}
{% endstepper %}
{% endtab %}
{% endtabs %}

{% hint style="info" %}
**Prefer to see it in action?** Check out the [video tutorial](https://youtu.be/PN-Ef4sv2NI).
{% 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/wire-a-video-intercom/set-up-td63-keypad-directory.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.
