> 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/bolt-ons-catalog/custom-service-provider-name-spn.md).
# Custom Service Provider Name (SPN)
Display your MVNO brand name on supported customer devices with a Custom Service Provider Name (SPN) on Reach Common.
### Overview
A **Custom Service Provider Name (SPN)** displays your MVNO brand name on supported customer devices. It replaces the default network or platform name.
Custom SPN is a bolt-on. Your brand owns the displayed name.
* **What it is:** Device-level branding for your SIM and eSIM service.
* **Why brands use it:** Create a consistent, branded network experience.
* **When to request it:** During onboarding or post launch
{% hint style="info" %}
Custom SPN changes the displayed network identity. It does not change product behavior.
{% endhint %}
Buy this bolt-on
### What customers see
The SPN appears as the network or service-provider name. Display varies by device and interface.
* It supports SIM and eSIM activations.
* It applies where the device and UI support SPN display.
* It requires no custom application or interface changes.
### Required brand inputs
Provide both values before setup begins.
* **Long SPN:** Your full brand name for interfaces with more space. Example: `Reach Mobile`.
* **Short SPN:** Your abbreviated brand name for compact interfaces. Example: `Reach`.
Reach validates both inputs before submitting the configuration.
### Setup options
#### During onboarding — recommended
Include the Long SPN and Short SPN in your onboarding inputs. This delivers the branded experience at launch.
{% stepper %}
{% step %}
#### Submit your SPN values
Provide the Long SPN and Short SPN during onboarding.
{% endstep %}
{% step %}
#### Reach validates and coordinates
Reach validates the inputs and coordinates configuration with the network operator.
{% endstep %}
{% step %}
#### Launch with your brand displayed
Your Custom SPN is enabled for launch, subject to operator approval.
{% endstep %}
{% endstepper %}
This is a one-time setup. It avoids post-launch provisioning and reporting impacts.
#### After launch
You can add a Custom SPN after launch through a formal request.
{% stepper %}
{% step %}
#### Submit a request
Raise the request through the Client Connect Portal or your Account Manager.
{% endstep %}
{% step %}
#### Use the required request subject
`Post-Launch SPN Configuration – [Brand Name]`
{% endstep %}
{% step %}
#### Provide both SPN values
Include your Long SPN and Short SPN.
{% endstep %}
{% step %}
#### Reach submits the configuration
Reach validates the request and submits it to the network operator.
{% endstep %}
{% step %}
#### Operator implements the change
The operator reviews and implements the SPN configuration.
{% endstep %}
{% endstepper %}
{% hint style="warning" %}
Timelines depend on operator approval
{% endhint %}
### Implementation details
Reach and the network operator coordinate the required internal configuration:
* Create a Sub-Class ID under Reach.
* Map the Custom SPN to that Sub-Class ID.
* Optionally configure `611` routing to your support number.
* Update provisioning, reporting, and cost-tracking systems as needed.
### Frequently asked questions
#### Does Custom SPN change service behavior?
No. It changes only the displayed network identity.
#### What happens after we purchase?
Reach validates your Long SPN and Short SPN values.
Buy this bolt-on
---
# 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/customizations-and-bolt-ons/bolt-ons-catalog/custom-service-provider-name-spn.md?ask=&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.