# Prepare tenant names before enabling Verkada voice routing

> Validate tenant call routing and ambiguous names before making an AI voice directory available to visitors.

- Canonical URL: https://update.dsesecurity.com/updates/verkada-intercom-ai-voice-directory-readiness/
- Publisher: Detection Systems & Engineering (DSE Security)
- Author: DSE Security Editorial Team
- Published: 2026-10-15T00:43:19+00:00
- Modified: 2026-10-15T00:44:33+00:00
- Last reviewed by DSE: 2026-10-14
- Resource type: Guide
- DSE priority: Information
- Topics: Access Control
- Reading time: 2 minutes

## What you need to know

Validate tenant call routing and ambiguous names before making an AI voice directory available to visitors.

## Potentially affected

This guide concerns the documented AI voice-directory feature, not every Verkada intercom. Calling the correct tenant and deciding whether to unlock a door remain separate acceptance questions.

## DSE recommendation

DSE recommends reviewing tenant names, department labels, similar-sounding entries, and call-flow ownership before enabling the feature.

## Article

Validate tenant call routing and ambiguous names before making an AI voice directory available to visitors.

## Source facts

Verkada’s voice-directory guide currently identifies the TD63-HW as the supported intercom and requires Site Admin permissions for configuration. The keypad directory must be configured first. Visitors can name a tenant, user, or department to reach the associated tenant call flow. When names are similar, the directory can ask for clarification. The configuration includes a starting language and welcome message.

Source: [Verkada — Configure AI-Powered Voice Directory](https://help.verkada.com/intercom/configuration/configure-ai-powered-voice-directory).

## Applicability

This guide concerns the documented AI voice-directory feature, not every Verkada intercom. Calling the correct tenant and deciding whether to unlock a door remain separate acceptance questions.

## DSE recommendation

DSE recommends reviewing tenant names, department labels, similar-sounding entries, and call-flow ownership before enabling the feature. Use the language and wording visitors are expected to understand. Have each tenant confirm where its call should arrive and who maintains that destination. Include reception staff in a pilot so they can identify confusing prompts or unexpected routing. Define how visitors obtain assistance when the spoken name is not recognized, and keep the existing entry procedure available during the pilot.

## Verification

Run approved calls for exact names, ambiguous names, departments, unanswered destinations, and the intended assistance path. Record the actual destination and user experience. Validate any door-release authorization separately instead of treating a successful voice match as visitor identity proof.

## Official reference

[Verkada — Configure AI-Powered Voice Directory](https://help.verkada.com/intercom/configuration/configure-ai-powered-voice-directory). Reviewed October 14, 2026.

## Primary reference

- Name: Verkada — Configure AI-Powered Voice Directory
- Authority: help.verkada.com
- URL: https://help.verkada.com/intercom/configuration/configure-ai-powered-voice-directory
- Source publication date: Not stated by the source

## Citation and use

Preferred citation: “Prepare tenant names before enabling Verkada voice routing,” DSE Security, https://update.dsesecurity.com/updates/verkada-intercom-ai-voice-directory-readiness/
Publishing principles: https://update.dsesecurity.com/updates/dse-updates-editorial-methodology/
Usage and citation policy: https://update.dsesecurity.com/usage/
Copyright © 2026 Detection Systems & Engineering. All rights reserved.