Numbers own routing state
Allocation, ownership, inbound, outbound, and lifecycle.
A platform story in three moves
From phone numbers to one telephony system.
First, numbers became first-class. Then, connections became self-serve. Next, trunk consolidation brings everything into one operating model.
Connections own the wire
Guided setup, number linking, and readiness checks.
One source of truth
Bring number and connection routing into one model.
The foundation
A phone number became a real platform object.
The first delivery replaced scattered configuration with an explicit number record and assignment model. Calls can now resolve through the number a team owns or is allowed to use.
Available today
Provisioned number
The durable control point between organizations, scenarios, providers, and call routing.
Allocation
Shared or dedicated
Ownership
Sarj or client
Inbound
Organization + scenario
Outbound
Authorized organizations
-
One lifecycle
Register, allocate, activate, deactivate, and reassign.
-
Inbound and outbound resolution
Scenario routing and caller-ID authorization now follow the number model.
-
Operational control
Super-admin management plus read-only organization visibility.
-
Guardrails in code
Ownership and routing rules stay consistent as numbers change.
The self-serve layer
Connections made telephony operable from the product.
The platform gained a guided flow for provider setup, credentials, safety checks, number linking, and readiness verification.
The important shift is visible here: PMs and operators can reason about a telephony connection as a managed object—with a provider, readiness status, linked numbers, and one guided setup flow. The values shown in the mock are illustrative.
- Connection status is explicit
- Numbers attach to connections
- Creation starts in one guided flow
The delivery ledger
What’s live—and what’s underway.
Work is separated by what teams can use today and what is still being completed.
Live
First-class provisioned numbers
Numbers can be registered, assigned, activated, and routed for both inbound and outbound calls.
Available in the platform
Live
Self-serve SIP connections
A guided setup for providers, credentials, safety checks, number linking, readiness, and ongoing management.
Available in the platform
In progress
One setup flow for connections + numbers
Register a number while setting up a connection, without entering the same routing configuration twice.
In progress
In progress
Safer completion and recovery
Support outbound-only connections and continue setup from the same place after an interruption, reducing duplicate configuration.
In progress
What comes next
Consolidation is the cutover from two truths to one.
Today, the product experience is unified, but routing still has overlapping configuration paths. The next phase removes that ambiguity.
We still maintain two routing paths.
Overlapping configuration makes ownership and support harder to explain.
NUMBER
Provisioned number
Allocation, assignments, status, and routing choices.
CONNECTION
SIP connection
Provider, route, credentials, verification, linked numbers.
PARALLEL PATH
Existing trunk routing
Separate organization assignments and manual routing rules.
Number selects identity. Connection selects the wire.
One routing model, a controlled transition, and clear failure states.
IDENTITY + POLICY
Provisioned number
Who owns it, who may use it, and where inbound calls go.
TRANSPORT + HEALTH
SIP connection
How calls reach the provider and whether the path is ready.
ONE RESOLUTION PATH
Call routing
Deterministic selection with observable failures.