Concepts
Numbers
How inbound phone numbers are configured.
An OpenPhn number is the config surface for one phone line you own. Each number ties together:
- Greeting — the first thing a caller hears.
- Flow (optional) — a published graph that runs the conversation.
- Transfer destinations — up to 5 phones to hand off to, with order and per-destination labels.
- Post-call SMS — templates that fire after the call completes when a trigger expression matches.
- Recording + voicemail — toggles, plus transcript persistence.
Outbound vs. inbound
- Outbound calls run strictly on your own Twilio subaccount. You supply
the SID + token; OpenPhn verifies and uses one of your numbers as
from_number. - Inbound numbers for supported compliance-gated use cases are
provisioned by OpenPhn via a managed Twilio subaccount. The number is
attached to your tenant and configured via
/v1/numbers.
Operations
GET /v1/numbers— list numbers with their full config.PATCH /v1/numbers/{number_id}— update greeting, transfer chain, SMS templates, flow binding, recording toggles.POST /v1/numbers/{number_id}/sms/preview— dry-run a post-call SMS template against a synthetic call outcome.
Twilio is the only supported carrier today. Credentials for Vonage, Telnyx, and SIP can be stored but calls do not route through them yet.