BYO telephony
Bring-your-own telephony connects a carrier account you already hold to Woise, so your existing numbers can answer and place calls for your agents. Every organization can use this path regardless of region: the compliance posture for a BYO number is the one you already carry with your own carrier, which is why it needs no separate approval from us.
It is also the only number-sourcing path in the United States. If you are in the US, this page is not an alternative route — it is the route.
What a telephony configuration holds
A telephony configuration is a saved connection to one carrier account: the credentials for that account, plus whatever settings the account needs in order to hand calls to Woise and receive them back.
Two properties of that definition do real work:
- It is created once and attached many times. One configuration can back several numbers, as long as those numbers live in the same carrier account.
- It is separate from the number. Changing which workflow answers a number does not touch the carrier credentials, and rotating credentials does not detach the number.
The fields below are the credentials your carrier issued to you. Woise stores them against your organization and uses them to authenticate outbound calls and to verify inbound webhooks. Anything marked sensitive is masked once saved — you can replace it, but you cannot read it back out of the dashboard.
Supported carriers
The provider list is read from Woise's telephony registry rather than hard-coded into the dashboard, so a new carrier appears in the form as soon as it is registered on the backend. Today that list is seven.
| Carrier | Credentials it asks for |
|---|---|
| Twilio | Account SID (starts with AC), Auth Token, and the phone numbers to use for outbound |
| Telnyx | API Key, and optionally a Call Control App ID and a webhook public key |
| Plivo | Auth ID, Auth Token, and optionally an Application ID |
| Vonage | Application ID, an RSA private key for JWT signing, API key and secret, and a signature secret |
| Vobiz | Account ID, Auth Token, and optionally an Application ID |
| Cloudonix | Bearer Token, Domain ID, and optionally an application name |
| Asterisk ARI | ARI endpoint URL, Stasis app name, ARI password, and a websocket_client.conf connection name |
Every provider also takes a list of phone numbers used as the caller ID for outbound calls.
Most expect them in full E.164 form; Vonage and Vobiz expect them without the leading +, and
Asterisk takes SIP extensions rather than numbers. The form labels the expected shape per
provider — follow the label rather than assuming a house style.
Which fields are optional, and what happens if you skip them
The optional fields are not decorative. Broadly:
- Application or connection IDs (Telnyx, Plivo, Vobiz, Cloudonix) tell the carrier which of its own applications should route calls to Woise. If your carrier account has exactly one, the provider can usually infer it. If it has several, supplying the ID is what stops calls landing at the wrong destination.
- Webhook verification material (Telnyx's public key, Vonage's signature secret) lets Woise prove that an inbound webhook genuinely came from your carrier rather than from someone who guessed your URL. Skipping it means inbound events are accepted unverified. Supply it.
Asterisk and Cloudonix are a different shape
Five of the seven are conventional cloud carriers you hold an account with. Two are not: Cloudonix and Asterisk ARI connect to SIP infrastructure — in Asterisk's case, quite possibly a PBX you run yourself. They are configured through this same form, but what you are entering is an endpoint you operate rather than a vendor account.
SIP covers that path properly, including which of the two is the more complete integration today.
A note on managed numbers
Naming a carrier is correct on this page, because on the BYO path you are the one who chose it. Managed numbers work differently: which carrier sits behind a managed number is deliberately not surfaced, and it is not something these docs will tell you. If you are on a managed +91 number, the carrier is our operational concern, not a configuration option.
Attaching a configuration
Once saved, attach the configuration to a number from Numbers. From that point the number behaves like any other connected number — point a workflow at it for inbound, or reference it from a campaign for outbound.
Common questions
What is Woise?
Woise is a managed platform for voice AI agents. You design an agent in a drag-and-drop workflow editor, connect a phone number, and it handles real inbound and outbound calls over the phone network or in the browser. The infrastructure, carrier setup and scaling are run for you.
Do I need a phone number to start?
You bring a number you already own and import it — that is the primary path today, and it means you keep your carrier relationship and your existing number. Agents can also take and place calls in the browser over WebRTC with no number at all.
How does billing work?
You are billed for the call minutes your agents actually use, metered as credits against your account. There is no seat licence and no per-agent fee, so an agent that takes no calls costs nothing to keep.
Can an agent connect to my CRM or calendar?
Yes. Agents can read from and write to your CRM, calendar and support tools through the integrations marketplace — you authorise each connection once with OAuth, and no credentials are stored in your workflow.
Do I need engineers to build an agent?
The workflow editor is visual, so building and changing an agent needs no code. There is also a REST API, a Python SDK and a TypeScript SDK if you would rather drive the platform programmatically, and an MCP server so coding agents can build workflows for you.
What happens to call recordings and transcripts?
Recordings and transcripts belong to your workspace and are available through the dashboard and the API. Raw transcripts, recordings and phone numbers are never handed to third-party analytics or error tracking without redaction.
What infrastructure do I have to run?
None. Woise runs the speech models, the language model turn, the call recording pipeline and the telephony legs for you, and scales them with your call volume. There is nothing to provision, patch or keep running.
Still stuck? Talk to our team.