> ## 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.

# Locations

> Running multiple branches, franchises, or service areas in one workspace.

Locations subdivide a workspace for businesses operating more than one branch, franchise, or distinct service area. One account, one bill, one team — with per-location configuration where it matters.

## What a location can have of its own

| Setting                    | Per location                                 |
| -------------------------- | -------------------------------------------- |
| Phone numbers              | Yes — a local number per branch              |
| Hours                      | Yes                                          |
| Service area               | Yes                                          |
| Calendars and availability | Yes                                          |
| Agents                     | Yes, where behavior differs                  |
| Knowledge base             | Shared, with location-specific overrides     |
| Team and roles             | Shared, and access can be scoped by location |
| Billing                    | Shared across the workspace                  |

## When to use them

<Columns cols={2}>
  <Card title="Use locations" icon="circle-check">
    Separate branches with their own crews, phone numbers, and hours. Franchises under one parent account. Distinct metro service areas.
  </Card>

  <Card title="Don't use locations" icon="circle-xmark">
    Separating service lines you run from one place — use services and tags. Or organizing your own reporting — filters do that already.
  </Card>
</Columns>

## Setting one up

<Steps>
  <Step title="Create the location">
    Under **Locations**, add it with its address, hours, and service area.
  </Step>

  <Step title="Assign a phone number">
    A number local to that area. Local caller ID answers materially better. See [Phone numbers](/phone/numbers).
  </Step>

  <Step title="Connect its availability">
    Point it at the calendar or CRM schedule the branch's crews actually work from. See [Calendars](/booking/calendars).
  </Step>

  <Step title="Override what differs">
    Hours, service area, and any location-specific facts. Leave everything else shared — duplicating your whole knowledge base per location creates a maintenance problem that grows with every branch.
  </Step>

  <Step title="Test from that number">
    Call the branch's number and confirm you get the right hours, the right service area, and a booking on the right calendar.
  </Step>
</Steps>

<Tip>
  Share as much as you can. The right instinct is one knowledge base with a handful of location overrides, not a copy per branch.
</Tip>

## Scoping access

Team members can be scoped so branch staff see their own location's calls, contacts, and bookings without seeing the whole business. See [Team & roles](/account/team-and-roles).

## Locations over the API

Pass the `x-location-id` header to scope a request to one location:

```bash theme={null}
curl https://api.recepta.ai/api/v1/api/calls \
  -H "x-api-key: $RECEPTA_API_KEY" \
  -H "x-location-id: LOCATION_ID"
```

Omit the header and the request covers the whole workspace. The same header works against the [MCP server](/api-reference/mcp).

## Reporting

Analytics can be filtered per location, so you can compare branches on call volume, booking rate, and transfer rate. Differences between branches on the same configuration usually point at availability or crew capacity rather than at the agent.