> For the complete documentation index, see [llms.txt](https://docs.limecall.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.limecall.com/virtual-numbers.md).

# Virtual Phone Numbers

Buy or port business numbers, route them to people, teams or your AI, and text from them.

A virtual number is a phone number that belongs to your LimeCall account rather than to a handset. Nothing is plugged in anywhere. You decide what each number does, and you can change it whenever you like.

## What you can do with one

* Publish a local number in a city you have no office in.
* Take a toll-free number so customers are not charged.
* Route each number somewhere different — a person, a team, voicemail or your AI receptionist.
* Send and receive SMS, where the number supports it.
* Keep personal mobiles private while still taking business calls on them.
* Give each campaign or region its own number and see which generates calls.

## Getting a number

Two routes:

**Buy one** — pick from the catalogue and it is live in minutes. See [Buy a number](/virtual-numbers/buy-a-number.md).

**Bring your existing one** — port it from your current provider, keeping the number your customers already know. Takes days to weeks. See [Bring your number (porting)](/virtual-numbers/bring-your-number.md).

{% hint style="info" %}
Numbers require a paid plan. On a trial you can browse the catalogue but not purchase.
{% endhint %}

## Regulatory requirements

Many countries require a verified local address, and some require identity documents, before they will issue a number. This is telecoms regulation, not a LimeCall policy.

Start this early — approval can take several business days and is the usual reason a number takes longer than expected. See [Addresses & verification](/virtual-numbers/address-and-verification.md).

## Deciding who answers

Each number has a destination, set under **Who answers your calls**:

| Destination             | Behaviour                 |
| ----------------------- | ------------------------- |
| **Team member**         | Rings one person.         |
| **Team**                | Rings a group.            |
| **Forward to a number** | Rings an external number. |
| **Voicemail**           | Straight to a greeting.   |
| **AI receptionist**     | Your AI answers, 24/7.    |

You can set a different destination for **When busy**. See [Call forwarding & routing](/virtual-numbers/call-forwarding-and-routing.md).

## In this section

* [Buy a number](/virtual-numbers/buy-a-number.md)
* [Bring your number (porting)](/virtual-numbers/bring-your-number.md)
* [Addresses & verification](/virtual-numbers/address-and-verification.md)
* [Caller ID](/virtual-numbers/caller-id.md)
* [Call forwarding & routing](/virtual-numbers/call-forwarding-and-routing.md)
* [Voicemail](/virtual-numbers/voicemail.md)
* [SMS & messaging](/virtual-numbers/sms-and-messaging.md)
* [US carrier registration (10DLC)](/virtual-numbers/us-carrier-registration.md)
* [Devices](/virtual-numbers/devices.md)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.limecall.com/virtual-numbers.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.