> 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.md).

# Bolt-ons catalog

All available bolt-ons, plus the standard request process and commercial notes.

**Bolt-ons** are **optional add-ons** to the standard Reach platform.

Use this page to:

* **Find the right bolt-on**
* Understand **how to request one**
* Understand common **commercial** and **timeline expectations**

<a href="https://datami.atlassian.net/helpcenter/Boltons/portal/1488/group/1848/create/2353" class="button primary" data-icon="cart-shopping">Buy a bolt-on</a>

### Available bolt-ons

1. [SSO — End Customers](/customizations-and-bolt-ons/bolt-ons-catalog/sso-end-customers.md) — Let customers sign in using brand-managed credentials.
2. [SSO — Agents](/customizations-and-bolt-ons/bolt-ons-catalog/sso-agents.md) — Use your Identity Provider for Reach Central access.
3. [Product Bundle Integration](/customizations-and-bolt-ons/bolt-ons-catalog/product-bundle-integration.md) — Bundle mobile with existing brand services and offer converged pricing.
4. [eCommerce](/customizations-and-bolt-ons/bolt-ons-catalog/ecommerce.md) — Launch a branded device store with sales, financing, fulfillment, and post-purchase management.
5. [Custom App Hosting](/customizations-and-bolt-ons/bolt-ons-catalog/custom-app-hosting.md) — Choose Reach-hosted or brand-hosted web and mobile applications.
6. [Custom SFTP Setup](/customizations-and-bolt-ons/bolt-ons-catalog/custom-sftp-setup.md) — Deliver standard Reach reports to your secure SFTP folder.
7. [Custom Service Provider Name (SPN)](/customizations-and-bolt-ons/bolt-ons-catalog/custom-service-provider-name-spn.md) — Display your brand name on supported customer devices.
8. [Custom Domain Setup](/customizations-and-bolt-ons/bolt-ons-catalog/custom-domain-setup.md) — Move customer journeys from a Reach subdomain to your domain.
9. [Mobile for SMB by Reach](/customizations-and-bolt-ons/bolt-ons-catalog/mobile-for-smb-by-reach.md) — Offer shared business account controls for teams of up to 25 lines.
10. [Smart Subs](/customizations-and-bolt-ons/bolt-ons-catalog/smart-subs.md) — Benchmark acquisition, churn, and support demand against an anonymized MVNO peer panel.
11. [Accessibility Widget](/customizations-and-bolt-ons/accessibility-widget.md) — Add AI-powered accessibility controls and continuous scanning to Echo customer journeys.

{% hint style="info" %}
Some bolt-ons are only available to some **brands**, **networks**, or **launch stages**.
{% endhint %}

### How to request a bolt-on

1. Share your goal, target date, and impacted customer journeys.
2. Provide the required brand inputs listed on the bolt-on’s page.
3. Reach confirms feasibility, scope, and any constraints.
4. Reach implements the change and shares it in a test environment.
5. After brand sign-off, Reach enables it in production.

### Commercial & timeline notes

* Bolt-ons must be included in the **commercial agreement**
* Some bolt-ons extend onboarding due to **discovery**, **build**, and **testing**
* Post-launch enablement typically requires a **formal change request**

<figure><img src="https://3494749437-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FsUFPSUngLZrTzBOau55s%2Fuploads%2Fu9avxYFSLpjWPjpZwhxT%2Fimage.png?alt=media&amp;token=cfc7a200-1869-40db-85c5-b5f1a6f54be6" alt=""><figcaption></figcaption></figure>

### Questions or support

{% hint style="info" %}
Questions or clarification? Reach out to your respective account manager or email us at <account-desk@reachplatform.com> for help and support.
{% 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/customizations-and-bolt-ons/bolt-ons-catalog.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.