Overview
A location is a place your team takes calls for — a branch, an office, or a logical grouping like “Head Office”. Endpoints sit on a location × department pair, so a business with three branches and three departments has nine possible endpoints. A location can exist without an address (e.g. “Remote/Head Office”).Fields
| Field | Type | Required | Default | Description |
|---|---|---|---|---|
| Name | string | Yes | — | Location name, e.g. “Sydney HQ”. |
| Address | address | No | none | Reuses your team’s saved addresses. |
| Timezone | IANA timezone | No | inherited | Optional override; otherwise the location’s schedule timezone applies. |
| Default schedule | schedule | No | none | Schedule that endpoints at this location inherit when they have none of their own. See Schedules. |
| Notes | text | No | empty | Free-text notes. |
| Active | boolean | No | true | Inactive locations are hidden from routing. |
Deletion
Locations are soft-deleted. A location with active endpoints cannot be deleted until those endpoints are removed or reassigned.Next Steps
- Departments — The other half of an endpoint’s location × department pair
- Endpoints — Create a transfer destination on this location