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

# Numbers & pools

> Get sending numbers, group them into pools, and send at volume safely.

You send from **phone numbers** (DIDs) you order into your workspace. Group them
into **pools** so a campaign can rotate across several numbers — the key to
sending at volume without wearing out any single number.

## Order a number

<Steps>
  <Step title="Search what's available">
    Search orderable numbers by country and area code — this is free. (API:
    [Search available numbers](/api-reference), `GET /v1/numbers/available`.)
  </Step>

  <Step title="Order it">
    Order a number into your workspace (this is charged). Optionally set a
    **daily limit** and place it in a pool. (API:
    [Order a number](/api-reference), `POST /v1/numbers`.)
  </Step>

  <Step title="Register for US A2P">
    To send to US numbers at volume you must complete **10DLC** brand + campaign
    registration first — see [Suppression & compliance](/suppression#us-a2p-10dlc).
  </Step>
</Steps>

## Pools

A **pool** is a named set of sending numbers. Point a campaign at a pool and it
**rotates** sends across the numbers in it, spreading volume so no single number
looks like a spammer and deliverability holds up.

|                | Single number                | Pool               |
| -------------- | ---------------------------- | ------------------ |
| Best for       | small or transactional sends | larger campaigns   |
| Deliverability | all volume on one number     | spread across many |

<Steps>
  <Step title="Create a pool">
    Create a pool and give it a name.
  </Step>

  <Step title="Add numbers">
    Put numbers in the pool by setting their pool on each number. A number belongs
    to one pool at a time.
  </Step>

  <Step title="Send from it">
    In the campaign builder's **Delivery** step, choose the pool as the sending
    source.
  </Step>
</Steps>

## Daily limits & status

Cap a number's **daily volume** to keep it healthy, and **pause** a number to
take it out of rotation without releasing it. **Releasing** a number stops
billing and removes your ability to send from it.

## Over the API & MCP

Manage numbers and pools programmatically — [Numbers](/api-reference) — or in
natural language via the [MCP server](/mcp).