> 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/faqs/network/spn-faq.md).

# SPN FAQ

Custom SPN setup so devices show your brand name on Reach Common.

### Quick answers

<details>

<summary>What is an SPN?</summary>

SPN (Service Provider Name) is the label shown on a customer’s device.

It indicates which carrier or service provider a SIM or eSIM belongs to.

</details>

<details>

<summary>What does a custom SPN do on Reach Common?</summary>

A custom SPN lets an MVNO display its own brand name.

It replaces a default network or platform name (where supported).

</details>

<details>

<summary>Who owns the SPN?</summary>

The SPN is owned by the brand, not Reach.

</details>

<details>

<summary>Is custom SPN enabled by default?</summary>

No. Custom SPN is a governed bolt-on on Reach Common / Common MVNO.

</details>

### SPN values (long vs short)

<details>

<summary>What values do we need to provide?</summary>

You must provide **two values**:

* **Long SPN:** full brand name (example: `Acme Mobile`)
* **Short SPN:** abbreviated name for compact displays (example: `ACME`)

Both are required.

</details>

<details>

<summary>Where do long vs short SPNs show up?</summary>

* **Long SPN** shows on devices/UIs that support longer text.
* **Short SPN** shows in status bars and compact displays.

</details>

{% hint style="info" %}
SPN display depends on device and UI context. Long SPN is not shown everywhere.
{% endhint %}

### Why brands request a custom SPN

<details>

<summary>Why do brands use a custom SPN?</summary>

Brands typically request a custom SPN to:

* strengthen brand visibility on customer devices
* deliver a branded network experience
* support premium or strategic MVNO launches
* align device identity with marketing and customer communications

</details>

### Eligibility and commercial guardrails

<details>

<summary>When is custom SPN typically offered?</summary>

Custom SPN is typically:

* contracted explicitly
* used for larger or premium MVNO launches

</details>

<details>

<summary>When is custom SPN typically not enabled?</summary>

Custom SPN is typically **not** enabled for:

* demos
* very small or non-strategic opportunities

This protects operator resources and prevents misuse of SPN allocations.

</details>

### Setup

<details>

<summary>What are the supported setup paths?</summary>

There are two supported paths:

* during onboarding (recommended)
* post-launch (after go-live)

</details>

<details>

<summary>How do we set up a custom SPN during onboarding?</summary>

This is the simplest path. It avoids post-launch operational impact.

1. **Submit SPN values.** Provide **Long SPN** and **Short SPN** during onboarding.
2. **Reach validates inputs.** Reach checks format and alignment with operator rules.
3. **Operator configuration.** Reach coordinates configuration with the underlying network operator.
4. **Launch with SPN enabled.** The brand launches with the custom SPN enabled from day 1.

</details>

<details>

<summary>What does post-launch SPN setup look like?</summary>

Post-launch SPN setup is supported.

Reach coordinates the change with the underlying network operator.

Timing and practical impact depend on operator processes.

</details>

### What changes once enabled

<details>

<summary>What changes once the custom SPN is enabled?</summary>

Once configured, the custom SPN:

* appears on customer devices as the network/service provider name
* applies across SIM and eSIM activations (on supported devices and UI contexts)
* reinforces brand identity without requiring app or UI changes

</details>

<details>

<summary>Does SPN change product behavior or network functionality?</summary>

No. SPN is a branding and network identity feature.

</details>

### Behind the scenes (operator + platform)

<details>

<summary>What happens behind the scenes?</summary>

At a high level, Reach:

* validates the requested SPN values against operator rules
* submits the request to the underlying network operator
* coordinates confirmation and enablement timing

</details>


---

# 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/faqs/network/spn-faq.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.