# Feature release cycle

> Talon.One features can go through a set of release stages. Understanding these stages helps you know what to expect and how to access new functionalities.

> For the complete documentation index, see [llms.txt](https://docs.talon.one/llms.txt).

## Campaign Manager features

Features of the Campaign Manager can go through the following stages:

### Closed beta

A feature in closed beta is still under active development and might not be fully
functional. You can get access to such features by reaching out to your Customer Success
Manager.

Closed beta features are not covered by standard support agreements and help requests
may be handled directly by our engineering team. Documentation for closed beta features is
also evolving and may have gaps or change as the product is refined. Always align with
your Technical Account Manager or Customer Success Manager before
using closed beta features in your production environment.

These features are indicated as beta in the Campaign Manager after you get access to
them and are marked with <ClosedBetaBadge/> in the documentation.

Features in this stage can be promoted to beta or general availability depending on the
feedback received from customers and the development progress.

### Beta

A feature in beta is available to all customers but is still considered under active
development and might not be fully functional. Every customer has access to beta features.

Beta features are not covered by standard support agreements and help requests
may be handled directly by our engineering team. Documentation for beta features is
also evolving and may have gaps or change as the product is refined. Always align with
your Technical Account Manager or Customer Success Manager before
using beta features in your production environment.

These features are indicated as beta in the Campaign Manager and are marked
with <BetaBadge/> in the documentation.

Features in this stage are promoted to general availability when sufficiently tested to
ensure reliable production stability.

### General availability

Once features are ready for production use, they are released as generally available. Most
features are released in this stage.

## API endpoints

Talon.One API endpoints can go through the following stages:

### Beta

Endpoints marked as beta in our API reference documentation are in the early
stages of development. They are not yet fully tested and may undergo significant changes
before they are finalized. These endpoints are not recommended for production use, and
access to them may be limited.

### General availability

Once endpoints are ready for production use, they are released as generally available. Most endpoints are released in this stage.

### Deprecated

Endpoints marked as deprecated in our API reference documentation are still functional but
are no longer recommended for use. They may be removed in future releases. You should
transition away from them as soon as possible.

Talon.One does not have a strict duration for the deprecation period, but it typically
lasts for several months to a year, depending on the complexity of the endpoint and the
impact of its removal.

### Sunset

Endpoints are sunset after a deprecation period, meaning they are removed from the API and
are no longer functional.