> 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/starter-kit/starter-kit/for-isps/what-to-know-before-launch/carrier-of-record.md).

# Carrier of Record

Choose whether your brand or Reach handles wireless licensing, tax, and compliance obligations. This decision sets your compliance burden. It affects licensing, tax handling, and operational overhead.

The carrier of record is the entity that holds the FCC wireless license, collects and remits wireless taxes, and carries the regulatory and compliance obligation for the service.

This is one of the highest-impact launch decisions.

### Option 1: Brand holds carrier of record

Your company holds the FCC wireless license directly.

That usually means:

* Your company is responsible for federal and state wireless tax filings
* Your company carries the regulatory and compliance obligation
* Your brand owns the wireless relationship directly
* Your team needs legal, tax, and compliance capacity

{% hint style="info" %}
**Best fit when**

* You already have wireless compliance infrastructure
* You want direct long-term control of the operating model
* You are willing to build the required legal and tax capability
  {% endhint %}

{% hint style="warning" %}
Under the NCTC and AT\&T program, the brand must hold carrier of record.
{% endhint %}

### Option 2: Reach holds carrier of record

Reach holds the FCC wireless license on your behalf.

That usually means:

* Reach handles wireless tax and compliance obligations
* Your team has far lower operational burden
* The launch path is simpler for first-time mobile operators
* You still retain full brand control of the customer experience

{% hint style="info" %}
**Best fit when**

* This is your first mobile launch
* Your ops team is lean
* You want the fastest path with the least compliance overhead
  {% endhint %}

### What to align on

Before launch, decide:

* Who will hold the FCC wireless license
* Who will own tax collection and remittance
* Whether your legal and compliance teams can support wireless obligations
* Whether lower burden or direct control matters more in year 1

{% hint style="success" %}
**Reach's Recommendation**

If this is your first mobile launch and you do not already have wireless compliance infrastructure, start with Reach as carrier of record. You can move to brand-held carrier of record later as the operation matures.
{% endhint %}

{% hint style="info" %}
Questions or clarification? Email us at <hi@reachplatform.com>.
{% 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.reachplatform.com/starter-kit/starter-kit/for-isps/what-to-know-before-launch/carrier-of-record.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
