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

# Phone numbers

> Provisioning numbers, assigning agents, and forwarding your existing business line.

Every workspace gets at least one phone number at signup. Numbers are what connect the outside world to your agents.

## Getting a number

Your plan includes a set number of provisioned numbers — one on Starter, up to ten on Volume. See [Plans](/plans). Additional numbers are available as an add-on.

Add or review numbers under **Phone numbers** in the dashboard. When provisioning, you choose the area code so the number reads as local to the customers you serve.

## Assigning an agent

Each number routes to one agent. That assignment decides who answers:

<Columns cols={2}>
  <Card title="One number, one agent" icon="arrow-right">
    The normal setup. All calls to that number are handled the same way.
  </Card>

  <Card title="Several numbers, several agents" icon="arrows-split-up-and-left">
    Useful for [multi-location](/account/locations) businesses, separate marketing numbers, or a distinct outbound caller ID.
  </Card>
</Columns>

## Two ways to send calls to Recepta.ai

<Tabs>
  <Tab title="Forward your existing line">
    Keep the number your customers already know and forward it to your Recepta.ai number. Nothing changes on your marketing, signage, or Google listing.

    Set this up with your current phone provider. Common options:

    * **Forward everything** — Recepta.ai is the front desk for all calls.
    * **Forward on no-answer** — your team gets first refusal, Recepta.ai catches what would have gone to voicemail.
    * **Forward after hours** — humans by day, Recepta.ai overnight and at weekends.

    <Tip>
      Forward-on-no-answer is the lowest-risk way to start. You keep your existing workflow and Recepta.ai only ever picks up calls you were going to lose.
    </Tip>

    <Card title="Step-by-step guides for your provider" icon="phone-arrow-right" href="/call-forwarding/conditional-forwarding">
      RingCentral, Google Voice, Dialpad, Vonage, 8x8, Talkroute, Phone.com, and CallRail — plus the caller-ID setting that catches most people out.
    </Card>
  </Tab>

  <Tab title="Publish the Recepta.ai number">
    Use the Recepta.ai number directly on your website, ads, and listings. Simpler, and gives you clean per-number attribution — but update your listings everywhere, or you'll split your call history across two numbers.
  </Tab>
</Tabs>

## Before you take real calls

<Warning>
  US numbers must complete **A2P 10DLC registration** before they can reliably send or receive SMS. Carrier review takes days. Start it as soon as your workspace exists — don't wait until launch day. See [A2P 10DLC](/phone/a2p-10dlc).
</Warning>

Voice calling is not gated on A2P; texting is.

## Caller ID for outbound

Outbound calls — whether from a [campaign](/outbound/campaigns) or the [API](/api-reference/calls) — go out from one of your own numbers. Use a number local to the area you're calling where you can; local caller ID answers materially better than out-of-area.

<Note>
  Outbound calling carries its own compliance obligations, including calling-hour restrictions and do-not-call handling. See [Recording & consent](/phone/recording-and-consent) and [Deliverability & compliance](/outbound/email-infrastructure).
</Note>

## Troubleshooting

<AccordionGroup>
  <Accordion title="Calls aren't reaching the agent">
    Check the number is assigned to an active agent, and that forwarding is actually configured at your existing provider — forwarding is set on their side, not in Recepta.ai. Place a test call and check whether it appears in [Call logs](/receptionist/call-logs); if it doesn't, the call never arrived.
  </Accordion>

  <Accordion title="The wrong agent answers">
    Two numbers pointing at the same agent, or a forwarding chain landing on a different Recepta.ai number than you expect. Check the assignment on the number that actually received the call.
  </Accordion>

  <Accordion title="Texts aren't sending">
    Almost always A2P registration — confirm your brand and campaign are approved. See [A2P 10DLC](/phone/a2p-10dlc).
  </Accordion>
</AccordionGroup>