Virtual numbers & entry points
Carrier numbers, units, and how buzzers reach Intry.
Overview
Intry's voice entry point is a VirtualNumber (E.164) assigned to a Unit. When a visitor dials or the intercom triggers a call, Core resolves number → unit → residents via /twilio/* or /telnyx/* webhooks.
See Virtual numbers API for the full admin endpoint list.
Fields
| Field | Purpose |
|---|---|
e164 | Canonical phone string (+15551234567) |
telephonyProvider | twilio or telnyx |
providerSid | Carrier resource SID |
status | Operational state |
quarantineUntil | Cool-down before reuse |
Linking to units
Unit.virtualNumberId binds the buzzer path. Changing numbers mid-lease requires coordination so carrier routing and resident apps stay consistent.
Carrier webhooks
Inbound voice hits /twilio/inbound-call or /telnyx/inbound-call on Core — not the admin API. Configure webhook URLs in the carrier console per environment.
Access points (hardware)
Physical gate hardware (DKS callboxes, etc.) stores the virtual number in the unit directory. Property managers configure hardware separately from the Intry admin API.
Last verified: 2026-06-21 (commit 293c4a7)