> 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/customer-care-model.md).

# Customer Care Model

Decide how Tier 1 support works and how issues escalate to Reach and the carrier. Mobile support needs a defined operating model before launch. Customers expect fast answers.

Mobile support is different from broadband support. Customers expect immediate help with activation issues, porting delays, device compatibility, billing questions, and network performance. You need to decide before launch exactly how those calls get handled.

### Support tiers

| Tier                              | What it covers                                                                                                        | Who handles it / what you need                                                                                                                                         |
| --------------------------------- | --------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Tier 1 — Frontline**            | Account questions, billing inquiries, basic plan changes, SIM replacement requests, and general troubleshooting       | Your existing care team after training. Reach provides a Tier 1 training module. Option: Reach can handle Tier 1 white-label on your behalf.                           |
| **Tier 2 — Technical escalation** | Porting failures, activation errors, SIM provisioning issues, network connectivity problems, and device compatibility | Reach's technical support team. Your Tier 1 reps escalate through a defined path. Response should be SLA-governed. Establish the escalation contact before launch day. |
| **Tier 3 — Carrier-level**        | Network outages, carrier-side provisioning failures, and regulatory matters                                           | Reach works with the carrier. Your role is to communicate proactively to affected subscribers. Reach provides status updates throughout.                               |

{% hint style="info" %}
A clear Tier 1 script and escalation path prevents most early care failures.
{% endhint %}

{% hint style="danger" %}

### First-30-day reality

Call volume is usually higher right after launch. Plan for that spike.
{% endhint %}

### What to align on

Before launch, decide:

* Will you handle Tier 1 in-house or contract it to Reach
* Do you have a staffing plan for the first 30 days post-launch when call volume spikes

{% 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/customer-care-model.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.
