Answer incoming calls

Use Inbound to bind one inbound DID to one agent process.

Inbound flow

[1] Select inbound DID ──▶ [2] Create process ──▶ [3] Receive calls
                                                            │
                                                            ▼
                              [5] Release DID ◀── [4] Close

Creation binds the DID until the process closes.

Prompt your AI agent

Recommended

Use the `dino-pong` skill to create an Inbound process for <use case>.
Verify my authority, the target owner, agent, region, and inbound DID.
Ask me to choose VAD, call duration, and Lens lifetime.
Explain that the DID stays bound until process close.
Show the exact creation and wait for my approval.
Do not use the process as a disposable infrastructure test.

Use the Dino CLI directly

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

dino process create-inbound \
  --agent-id <agent-genesis-id> --name <name> --region <region> \
  --vox-server-id <dino-runtime-id> --transport-did-id <inbound-did-id> \
  --partner-credentials-id <partner-id> --vad-mode <mode> \
  --hard-close-secs <90-900> --lens-ttl-days <30-180> \
  --confirm-mutation process.inbound.create

Verify and close

dino process get --process-id <process-id>
dino process list-calls --process-id <process-id> --limit 50 --offset 0

# After approval for permanent close and DID release:
dino process close-inbound --process-id <process-id> \
  --confirm-mutation process.inbound.close

Gotchas

• Select a DID from the inbound catalog for the exact target owner.
• Confirm the provider route before you advertise the number.
• Closing the process releases the DID and stops new inbound handling.
• Process call records remain after close.
• Use an agent genesis unless the process must stay on one exact version.