Virtual number pool
Pooled phone numbers, lifecycle, and Telnyx/Twilio inventory.
Who this is for
Intry internal administrators managing telephony inventory in Intry Admin. Residents and property managers do not manage virtual numbers.
What is a virtual number?
A virtual number is an E.164 phone number Intry owns in the pool (Twilio or Telnyx). States:
- Available — in inventory, not attached to a unit
- Assigned — linked to a unit for inbound call routing
- Quarantined — cooling down after release (protects caller-ID reputation)
Outbound SMS may use a separate env-configured from-number — not the same as inbound pooled numbers.
Why units, not properties?
Inbound routing matches the number dialed to a unit. A property can have many units; each unit may have its own virtual number.
Pool cap
Each tenant: unit count + 5 virtual numbers maximum.
Pool health
Monitor via Intry Admin → Virtual numbers:
- Available vs assigned counts
- Sync status with carrier (Twilio or Telnyx)
- Low inventory alerts
Provider notes
VirtualNumber.telephonyProviderdetermines webhook path (/twilio/*vs/telnyx/*).- Telnyx migration (IN-189): mixed pools supported; see developer Telephony docs.
Further reading
- Managing virtual numbers
- Engineering:
docs/VIRTUAL_NUMBER_MANAGEMENT.mdin monorepo
Last verified: 2026-06-21 (commit 293c4a7)