> ## Documentation Index
> Fetch the complete documentation index at: https://docs.vocily.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Carrier accounts (BYOC)

> Connect a Plivo or VoBiz account you already own and import its numbers.

If your business already pays a telephony provider, connect that account to Vocily and
bring your own numbers. This is often called **BYOC** - bring your own carrier.

Vocily supports two carriers today:

<CardGroup cols={2}>
  <Card title="Plivo" icon="phone">
    Global telephony with number management, call routing, and real-time audio streaming
    over WebSocket.
  </Card>

  <Card title="VoBiz" icon="phone-call">
    SIP trunks, number management, call routing, and real-time audio streaming via
    WebSocket.
  </Card>
</CardGroup>

<Note>
  Carrier accounts are connected on the **Phone Numbers** page, not on Integrations.
  They belong to the whole organization, so one connection serves every workspace.
</Note>

## Before you connect

Have your provider credentials ready. Both carriers use the same two values:

* **Auth ID** - your account identifier. Plivo IDs start with `MA`; VoBiz IDs look like
  `MA_XXXXXXXX`.
* **Auth Token** - your account token. Treat it like a password.

Find them in your provider console: the [Plivo Console](https://console.plivo.com) or
the [VoBiz Console](https://console.vobiz.ai).

Vocily stores the token encrypted and never shows it again - the Phone Numbers page
displays only a masked Auth ID.

## Connect an account

<Steps>
  <Step title="Open Phone Numbers">
    Switch the toggle in the top right to **Organization**.
  </Step>

  <Step title="Connect account">
    In **Carrier accounts (BYOC)**, select **Connect account**.
  </Step>

  <Step title="Choose the provider and enter credentials">
    Pick Plivo or VoBiz, then enter the Auth ID and Auth Token. Give the account a
    label if you want to recognise it later.
  </Step>

  <Step title="Save">
    Vocily verifies the credentials with the provider before saving, so a wrong token
    fails immediately rather than at the first call.
  </Step>
</Steps>

An organization can connect **more than one account per provider** - useful when
different parts of the business hold separate carrier accounts.

## How the connection works

Two things happen behind the two steps, and knowing them explains every inbound problem
you are likely to hit.

**When you save the credentials**, Vocily creates a **voice application** in your
provider account and points its answer URL at Vocily. That application is what turns an
incoming call into a live conversation with your agent. The **Inbound ready** badge on
the account means this application exists.

**When you import a number**, Vocily attaches that number to the application. A number
sitting in your provider account with no application attached rings nowhere.

<Warning>
  **Do not detach the number from that application in your provider console.** Inbound
  calls stop immediately - the call reaches the provider, finds no application, and never
  arrives at Vocily. Outbound keeps working, which is what makes this confusing to
  diagnose: the number looks fine until someone calls it.

  If it happens, re-import the number in Vocily to reattach it.
</Warning>

Deleting the application itself breaks inbound for **every** number attached to it, not
just one.

## Import numbers

Connecting an account does not import its numbers. Choose which ones Vocily should
manage:

<Steps>
  <Step title="Select Import number">
    In **Organization phone numbers**, select **Import number**.
  </Step>

  <Step title="Pick the number">
    The list shows numbers live on your connected accounts that are not yet in Vocily.
  </Step>

  <Step title="Choose a workspace">
    Assign it straight away, or leave it in the organization pool to allocate later.
  </Step>
</Steps>

Imported numbers appear with the source **Own account** and become available in the
agent's [Deploy](/building-agents/deploy) tab.

## Provider billing stays with your provider

Your carrier account, its number charges, subscription, invoices, and account status are
managed by your business with that provider. Vocily connects to the account you
authorize and uses its numbers for routing.

Keep the account active and funded. If a number is disabled, suspended, or removed at the
provider, it stops working in Vocily - the number's **Status** column reads `Inactive`
when Vocily can no longer see it in the account it belongs to.

Vocily billing and provider billing are separate. Vocily charges for platform usage;
your carrier charges you directly for the numbers and the minutes.

<Info>
  This is the main difference from [renting a number from
  Vocily](/phone-numbers/rent-from-vocily), where Vocily holds the provider relationship
  and bills you a single monthly price from your wallet.
</Info>

## Rename or disconnect an account

**Rename** changes only the label shown in Vocily.

**Disconnect** removes the account and every number imported from it. Agent inbound
routes and default outbound numbers pointing at those numbers are cleared. Reconnecting
restores the account but **not** the routing, so you have to reassign agents.

Because it is destructive, disconnect asks you to type `disconnect` and lists exactly
what will be removed first.

## What's next

* Route an imported number to an agent in [Deploy](/building-agents/deploy).
* Compare with [Rent a number from Vocily](/phone-numbers/rent-from-vocily).