Numbers

Every number knows its app.Inbound lands in your code.

Assign DIDs from your pool to applications, point inbound calls at your own handlers, and rotate caller ID for local presence. Self-serve search and purchase is honestly on the roadmap; today the team provisions with you.

telvox connect · number rackassigned
your did pool+1 415 555 0134+1 646 555 0188+1 306 555 0142+1 212 555 0177porting ininbound routes hereyour applicationanswer_url setyour handler answers the call

What's real today

Assignment and routing now. Self-serve buying later.

DID assignment, per-application routing and caller-ID rotation ship today. Self-serve number search and purchase is honestly on the roadmap.

DID pool assignment

Assign numbers and DIDs from your pool to applications and campaigns. Each number knows which handler owns it, so inbound traffic lands exactly where you intend.

Per-application routing

Point each number at its own answer URL. Inbound calls hit your endpoint and your app decides what happens next, per application or per campaign.

Round-robin & sticky rotation

Rotate caller ID across your DID pool round-robin for spread, or sticky so a given lead always sees the same number. Both are shipped in Dial today.

Area-code match for local presence

Present a number that matches the destination's area code to lift answer rates. Local-presence caller-ID matching is a real, shipped capability.

Inbound to your handlers

Inbound calls to an assigned number are delivered to the answer URL you configure, so your application is in control of every inbound flow.

Team-assisted provisioning

Today the TelVox team provisions and ports numbers with you. Self-serve search and purchase via the API is on the roadmap, not yet available.

Caller-ID strategies · shipped

  • round-robin
  • sticky
  • area-code match

Spread calls across your pool, pin a number to a contact, or match the destination's area code. All three are real, shipped strategies.

Assignment

One call points a number at your handler.

Set the answer URL and the caller-ID strategy on a number in your pool, and inbound calls to it are delivered to your endpoint from then on. The snippet is illustrative; the shape may change before general availability.

Honest status

Self-serve number search and purchase is roadmap.

To be explicit: there is no in-API number search or purchase today, and toll-free and multi-country inventory are not self-serve yet. Today the TelVox team provisions, ports and assigns numbers with you. Assigning numbers to applications, routing inbound to your handlers and caller-ID rotation are real and shipped. The buy-it-yourself flow is honestly on the roadmap, not a commitment we present as already live.

Provision with the team

POST/v1/phone-numbers/{sid}

# illustrative: shape may differ at GA
# point an assigned number at your application's answer URL
curl -X POST https://api.telvox.dev/v1/phone-numbers/PN3f9c... \
  -H "Authorization: Bearer $TELVOX_API_KEY" \
  -d answer_url="https://your.app/voice/answer" \
  -d caller_id_strategy="area_code_match"

200 ok · state: assigned · shape may differ at GA

Questions

Numbers FAQ

No, and we want to be explicit about that. Self-serve number search and purchase is on the roadmap, not shipped. Today the TelVox team provisions, ports and assigns numbers with you. What is real right now is assigning numbers from your pool to applications, pointing them at your handlers, and caller-ID rotation.

Get the right numbers pointed at your app.

Sign up and we'll provision your DIDs and wire inbound routing to your handlers.