> For the complete documentation index, see [llms.txt](https://docs.reachplatform.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.reachplatform.com/customizations-and-bolt-ons/long-term-plans.md).

# Long-term plans

Configure multi-month service plans with upfront billing, automatic renewals, and renewal-date plan changes.

### Overview

Long-term plans let brands offer service in terms such as 3, 6, or 12 months.

Customers pay for the full plan term up front. Service starts on activation and renews at the end of the term.

These plans work well for prepaid, seasonal, and annual-style offers.

{% hint style="warning" %}
Long-term plans are available only for select mobile network operators (MNOs). Contact your account team to confirm availability for your operator.
{% endhint %}

{% hint style="info" %}
For billing, each month in a long-term plan is treated as 30 days. For example, a 3-month plan runs for exactly 90 days. For the broader billing framework, see [Billing model](/core-product-structure/billing-model.md).
{% endhint %}

### What customers can expect

{% stepper %}
{% step %}

#### Choose a plan term

Customers pick a multi-month term such as 3, 6, or 12 months.
{% endstep %}

{% step %}

#### Pay upfront

The full plan amount is charged at the start of the term.
{% endstep %}

{% step %}

#### Start service

The plan term starts on the activation date.
{% endstep %}

{% step %}

#### Renew automatically

The same plan renews at the end of the term unless the customer changes or cancels it.
{% endstep %}
{% endstepper %}

### Line rules by plan term

The platform supports different line rules depending on the plan length.

| Plan term         | Line support                             |
| ----------------- | ---------------------------------------- |
| 1-month plans     | Multiple lines per account are supported |
| Multi-month plans | Single-line accounts only                |

{% hint style="warning" %}
If a customer wants to move from a 1-month plan to a longer-term plan, the account must meet the single-line rule before the change can go through.
{% endhint %}

### Plan changes

Plan changes do not happen mid-cycle on long-term plans.

Any change takes effect on the renewal date for the next plan term.

#### Supported change behavior

{% tabs %}
{% tab title="From a 1-month plan" %}
Customers can move to another 1-month plan at renewal.

Customers can also move to a longer-term plan at renewal if the account has only one line.
{% endtab %}

{% tab title="From a long-term plan" %}
Customers can move to another eligible long-term plan at renewal.

Customers can also move back to a 1-month plan at renewal.
{% endtab %}
{% endtabs %}

### Billing and renewal

Billing follows the selected plan term.

{% columns %}
{% column %}

#### Billing

The full plan amount is billed for the selected term.

Brands can decide whether the upfront plan charge is collected at purchase or at activation, based on the billing setup for that brand.

Any applicable brand fees or charges are added during checkout.
{% endcolumn %}

{% column %}

#### Renewal

The next invoice is generated after the current term ends.

The same plan and term renew for the next cycle by default.
{% endcolumn %}
{% endcolumns %}

### Why brands use long-term plans

Long-term plans support pricing models that do not fit a standard monthly subscription.

{% columns %}
{% column %}

#### Prepaid annual offers

Offer longer-term plans with upfront payment.
{% endcolumn %}

{% column %}

#### Fixed-term promotions

Launch seasonal or campaign-based offers with a defined term.
{% endcolumn %}
{% endcolumns %}

{% hint style="success" %}
Long-term plans also help brands collect upfront value for multiple months of service.
{% endhint %}

{% hint style="info" %}
Questions or clarification? Reach out to your respective account manager or email us at <account-desk@reachplatform.com> for help and support.
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.reachplatform.com/customizations-and-bolt-ons/long-term-plans.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.