> 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/isp-responsibilities.md).

# ISP Responsibilities

Ownership model, operational tasks, logistics, porting, and the first 30 days after launch.

{% columns %}
{% column %}

#### ISP responsibilities

* Front-line customer sales (all channels)
* Tier 1 customer support — account questions, basic troubleshooting (option to delegate to Reach)
* Marketing, promotions, and subscriber communications
* Internal staff training and ongoing enablement
* Tax and compliance obligations (if brand holds CoR)
  {% endcolumn %}

{% column %}

#### Reach responsibilities

* Carrier network access and SIM provisioning infrastructure
* MVNO platform, APIs, and all back-end systems
* Number porting — initiation, tracking, and completion
* Plan management and rate deck configuration
* Reach Central back office — all subscriber data, activations, port status
* Tier 2 and Tier 3 technical support escalation
* Federal wireless regulatory compliance and FCC licensing (if Reach holds CoR)
* Federal and state wireless tax filing (if Reach holds CoR)
* Carrier relationship management
* Platform maintenance, updates, and new feature deployment
* VAS vendor relationships and fulfillment logistics
  {% endcolumn %}
  {% endcolumns %}

{% hint style="info" %}
If Reach is carrier of record, Reach handles wireless tax and compliance obligations.

If your brand is carrier of record, your team owns those obligations.

This is one of the most important reasons to decide carrier of record early.
{% endhint %}

{% hint style="danger" %}
The cleaner this division is documented before launch, the smoother everything runs after launch. Ambiguity here is the biggest source of post-launch friction.
{% 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/isp-responsibilities.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.