{ "api_version": "1", "kind": "dse_post", "self": "https://update.dsesecurity.com/api/v1/posts/verkada-intercom-ai-voice-directory-readiness/", "item": { "id": "https://update.dsesecurity.com/updates/verkada-intercom-ai-voice-directory-readiness/", "slug": "verkada-intercom-ai-voice-directory-readiness", "url": "https://update.dsesecurity.com/updates/verkada-intercom-ai-voice-directory-readiness/", "alternate_urls": { "markdown": "https://update.dsesecurity.com/updates/verkada-intercom-ai-voice-directory-readiness.md", "json": "https://update.dsesecurity.com/api/v1/posts/verkada-intercom-ai-voice-directory-readiness/" }, "title": "Prepare tenant names before enabling Verkada voice routing", "summary": "Validate tenant call routing and ambiguous names before making an AI voice directory available to visitors.", "format": { "slug": "guide", "name": "Guide" }, "priority": { "slug": "info", "name": "Information" }, "featured": false, "image": { "theme": "physical-security", "label": "Physical security", "alt": "Integrated video surveillance and controlled entry at a modern commercial facility.", "card_url": "https://update.dsesecurity.com/assets/editorial/physical-security-card.webp?v=1.8.20", "hero_url": "https://update.dsesecurity.com/assets/editorial/physical-security-hero.webp?v=1.8.20", "social_url": "https://update.dsesecurity.com/assets/editorial/physical-security-social-v2.jpg?v=1.8.20", "width": 2400, "height": 1350 }, "topics": [ { "slug": "access-control", "name": "Access Control", "url": "https://update.dsesecurity.com/topic/access-control/" } ], "author": { "name": "DSE Security Editorial Team", "url": "https://update.dsesecurity.com/#editorial-team", "type": "Organization" }, "publisher": { "name": "Detection Systems & Engineering", "url": "https://dsesecurity.com/" }, "published_at": "2026-10-15T00:43:19+00:00", "modified_at": "2026-10-15T00:44:33+00:00", "reviewed_on": "2026-10-14", "reading_minutes": 2, "word_count": 241, "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.", "primary_source": { "name": "Verkada — Configure AI-Powered Voice Directory", "url": "https://help.verkada.com/intercom/configuration/configure-ai-powered-voice-directory", "published_on": null, "authority": "help.verkada.com" }, "publishing_principles": "https://update.dsesecurity.com/updates/dse-updates-editorial-methodology/", "usage_info": "https://update.dsesecurity.com/usage/", "copyright_notice": "Copyright © 2026 Detection Systems & Engineering. All rights reserved.", "content_html": "

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

\n

Source facts

\n

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.

\n

Source: Verkada — Configure AI-Powered Voice Directory.

\n

Applicability

\n

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.

\n

DSE recommendation

\n

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.

\n

Verification

\n

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.

\n

Official reference

\n

Verkada — Configure AI-Powered Voice Directory. Reviewed October 14, 2026.

", "content_text": "Validate tenant call routing and ambiguous names before making an AI voice directory available to visitors.\nSource facts\nVerkada’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.\nSource: Verkada — Configure AI-Powered Voice Directory.\nApplicability\nThis 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.\nDSE recommendation\nDSE 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.\nVerification\nRun 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.\nOfficial reference\nVerkada — Configure AI-Powered Voice Directory. Reviewed October 14, 2026.", "content_markdown": "Validate tenant call routing and ambiguous names before making an AI voice directory available to visitors.\n\n## Source facts\n\nVerkada’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.\n\nSource: [Verkada — Configure AI-Powered Voice Directory](https://help.verkada.com/intercom/configuration/configure-ai-powered-voice-directory).\n\n## Applicability\n\nThis 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.\n\n## DSE recommendation\n\nDSE 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.\n\n## Verification\n\nRun 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.\n\n## Official reference\n\n[Verkada — Configure AI-Powered Voice Directory](https://help.verkada.com/intercom/configuration/configure-ai-powered-voice-directory). Reviewed October 14, 2026." }, "json_ld": { "@context": "https://schema.org", "@graph": [ { "@type": "Organization", "@id": "https://dsesecurity.com/#organization", "name": "Detection Systems & Engineering", "alternateName": "DSE Security", "url": "https://dsesecurity.com/", "logo": { "@type": "ImageObject", "url": "https://update.dsesecurity.com/assets/dse-logo-20260812.png?v=1.8.20" } }, { "@type": "Organization", "@id": "https://update.dsesecurity.com/#editorial-team", "name": "DSE Security Editorial Team", "url": "https://update.dsesecurity.com/", "parentOrganization": { "@id": "https://dsesecurity.com/#organization" } }, { "@type": "WebSite", "@id": "https://update.dsesecurity.com/#website", "name": "DSE Updates", "alternateName": "DSE Security Knowledge Hub", "url": "https://update.dsesecurity.com/", "inLanguage": "en-US", "publisher": { "@id": "https://dsesecurity.com/#organization" }, "potentialAction": { "@type": "SearchAction", "target": { "@type": "EntryPoint", "urlTemplate": "https://update.dsesecurity.com/?q={search_term_string}" }, "query-input": "required name=search_term_string" } }, { "@type": "WebPage", "@id": "https://update.dsesecurity.com/updates/verkada-intercom-ai-voice-directory-readiness/", "url": "https://update.dsesecurity.com/updates/verkada-intercom-ai-voice-directory-readiness/", "isPartOf": { "@id": "https://update.dsesecurity.com/#website" }, "lastReviewed": "2026-10-14" }, { "@type": "BreadcrumbList", "@id": "https://update.dsesecurity.com/updates/verkada-intercom-ai-voice-directory-readiness/#breadcrumbs", "itemListElement": [ { "@type": "ListItem", "position": 1, "name": "DSE Updates", "item": "https://update.dsesecurity.com/" }, { "@type": "ListItem", "position": 2, "name": "Prepare tenant names before enabling Verkada voice routing", "item": "https://update.dsesecurity.com/updates/verkada-intercom-ai-voice-directory-readiness/" } ] }, { "@type": [ "Article", "TechArticle" ], "@id": "https://update.dsesecurity.com/updates/verkada-intercom-ai-voice-directory-readiness/#article", "identifier": "https://update.dsesecurity.com/updates/verkada-intercom-ai-voice-directory-readiness/", "url": "https://update.dsesecurity.com/updates/verkada-intercom-ai-voice-directory-readiness/", "headline": "Prepare tenant names before enabling Verkada voice routing", "description": "Validate tenant call routing and ambiguous names before making an AI voice directory available to visitors.", "abstract": "Validate tenant call routing and ambiguous names before making an AI voice directory available to visitors.", "articleBody": "Validate tenant call routing and ambiguous names before making an AI voice directory available to visitors.\nSource facts\nVerkada’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.\nSource: Verkada — Configure AI-Powered Voice Directory.\nApplicability\nThis 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.\nDSE recommendation\nDSE 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.\nVerification\nRun 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.\nOfficial reference\nVerkada — Configure AI-Powered Voice Directory. Reviewed October 14, 2026.", "datePublished": "2026-10-15T00:43:19+00:00", "dateModified": "2026-10-15T00:44:33+00:00", "mainEntityOfPage": { "@id": "https://update.dsesecurity.com/updates/verkada-intercom-ai-voice-directory-readiness/" }, "inLanguage": "en-US", "isAccessibleForFree": true, "author": { "@type": "Organization", "name": "DSE Security Editorial Team", "url": "https://update.dsesecurity.com/#editorial-team" }, "publisher": { "@id": "https://dsesecurity.com/#organization" }, "image": { "@type": "ImageObject", "@id": "https://update.dsesecurity.com/updates/verkada-intercom-ai-voice-directory-readiness/#primaryimage", "url": "https://update.dsesecurity.com/assets/editorial/physical-security-social-v2.jpg?v=1.8.20", "contentUrl": "https://update.dsesecurity.com/assets/editorial/physical-security-social-v2.jpg?v=1.8.20", "width": 1200, "height": 630, "caption": "Prepare tenant names before enabling Verkada voice routing" }, "articleSection": [ "Access Control" ], "keywords": [ "Access Control", "Guide", "Information priority" ], "genre": "Guide", "about": [ { "@type": "Thing", "name": "Access Control", "url": "https://update.dsesecurity.com/topic/access-control/" } ], "wordCount": 241, "timeRequired": "PT2M", "publishingPrinciples": "https://update.dsesecurity.com/updates/dse-updates-editorial-methodology/", "usageInfo": "https://update.dsesecurity.com/usage/", "copyrightHolder": { "@id": "https://dsesecurity.com/#organization" }, "copyrightNotice": "Copyright © 2026 Detection Systems & Engineering. All rights reserved.", "citation": { "@type": "CreativeWork", "name": "Verkada — Configure AI-Powered Voice Directory", "url": "https://help.verkada.com/intercom/configuration/configure-ai-powered-voice-directory" } } ] } }