Phone numbers and regions

Select a DID that matches the target owner, region, direction, and process capacity.

Selection flow

[1] Target owner ──▶ [2] Region ──▶ [3] Direction ──▶ [4] Capacity
                                                               │
                                                               ▼
                                                        [5] Select DID

Use sanitized catalogs to select infrastructure that is already available to the target account.

Prompt your AI agent

Recommended

Use the `dino-ping` and `dino-pong` skills to select phone infrastructure.
Confirm the target owner, region, inbound or outbound direction, and capacity.
Use only secret-free catalogs for that same target context.
Reject cross-owner or cross-region combinations.
Show the selected DID, runtime, partner credential, and capacity evidence.
Do not create, probe, delete, or place a call.

Use the Dino CLI directly

dino catalog transport-dids --direction outbound
dino catalog transport-dids --direction inbound
dino catalog vox-servers
dino catalog partner-credentials

Capacity rule

For Batch and Drip, select a process limit no greater than the DID's available on-demand capacity. Inbound process creation does not use a Batch or Drip process limit.

Gotchas

• Do not combine catalog results from different target owners.
• A DID direction must match the process type.
• Admin authority does not bypass infrastructure ownership or runtime grants.
• Ask your DinoDial operator to provision missing infrastructure.
• Raw provider credentials never belong in chat, documentation, or process commands.
• A local carrier test call is an operator workflow, not a public process probe.

Next

Return to Choose a call workflow after you select eligible infrastructure.