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

# Endpoints

> Addressable transfer destinations that join a location and department and dial a phone, team member, or SIP URI.

## Overview

A routing endpoint is a transfer destination. It joins one [location](/routing/locations) and one [department](/routing/departments), references a [schedule](/routing/schedules), and points at a single destination. When the assistant transfers a call, it resolves the matching endpoint, checks whether it is open, and dials the destination.

The Endpoints tab lists endpoints grouped by location with a live open/closed status that polls in the background.

***

## Fields

| Field            | Type       | Required | Default   | Description                                                                                                                                          |
| ---------------- | ---------- | -------- | --------- | ---------------------------------------------------------------------------------------------------------------------------------------------------- |
| Name             | string     | Yes      | —         | Endpoint name, e.g. "Sydney Sales". Unique per team.                                                                                                 |
| Location         | location   | Yes      | —         | The location this endpoint serves.                                                                                                                   |
| Department       | department | Yes      | —         | The department this endpoint serves.                                                                                                                 |
| Schedule         | schedule   | No       | inherited | Explicit schedule override. When empty, the endpoint inherits department → location → team default. See [Schedules](/routing/schedules#inheritance). |
| Destination type | string     | Yes      | `phone`   | One of `phone`, `member`, or `sip_uri`.                                                                                                              |
| Destination      | string     | Yes      | —         | The destination value, matching the type (see below).                                                                                                |
| Extension        | string     | No       | none      | Optional internal short code.                                                                                                                        |
| Priority         | integer    | No       | `0`       | Tie-breaker when more than one active endpoint matches a location × department. Lowest wins.                                                         |
| Active           | boolean    | No       | `true`    | Inactive endpoints are skipped during resolution.                                                                                                    |

***

## Destination Types

| Type      | Input        | Notes                                                                  |
| --------- | ------------ | ---------------------------------------------------------------------- |
| `phone`   | Phone number | Validated as a real number (E.164).                                    |
| `member`  | Team member  | Dials the member's verified mobile on file. Every team member has one. |
| `sip_uri` | SIP URI      | Must start with `sip:`.                                                |

Exactly one destination value is set, matching the selected type.

***

## Open / Closed Status

An endpoint is **open** when it is active, has a valid destination, and its effective schedule reports open right now. It shows **closed** outside the schedule's hours, on excluded public holidays, and on date-override closures.

An endpoint is flagged **broken** when its destination cannot be dialled — for example a `member` whose account is no longer on the team or has no number on file, or a destination value that is missing. Broken endpoints surface on the Overview dashboard.

***

## Resolution

When a transfer targets an endpoint (directly, or by location + department), Voxworks:

1. Finds the matching active endpoint. If more than one matches, it picks the lowest `priority`.
2. Determines the effective schedule (endpoint → department → location → team default).
3. Checks the schedule. If **open**, it dials the destination.
4. If **closed**, it falls back — voicemail by default.

Every resolution is recorded in the **Audit Log** with the endpoint chosen, the open/closed state, and the destination dialled, linked to the call.

***

## Next Steps

* [Schedules](/routing/schedules) — Control when an endpoint is open
* [Warm Handoff](/tools/warm-handoff) — The tool that transfers a caller to a human