> 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/launching-with-reach/what-is-included-and-optional-add-ons.md). # What Is Included and Optional Add-Ons Core launch capabilities included in the platform, plus optional customizations. ### What is included The platform includes the core capabilities needed to launch and operate mobile. No custom development is required. Reach delivers this through proprietary platform features and integrated third-party services. That gives partners one operating layer instead of a fragmented stack. #### End-to-end customer experience Reach provides fully white-labeled web and mobile experiences across the full subscriber journey. That covers purchase, activation, account management, and support. * **White-labeled web experience:** Templatized design is ready for partner branding. * **White-labeled mobile app:** The "That's My Mobile" app is available on the App Store and Google Play. * **Self-service portal:** MyAccount gives subscribers a self-serve management experience. * **Device and SIM management:** Ordering, fulfillment, and activation flows are built in. * **Lifecycle communications:** Promotions and notifications support the subscriber journey from day one. #### Commerce, billing, and payments Reach covers the full financial lifecycle from purchase through recurring billing. Built-in tax and compliance handling supports standard regulatory needs. * **Payment processing:** Secure handling of customer payments * **Billing engine:** One-time and recurring charge management * **Invoicing:** Automated customer billing statements * **Tax and compliance:** Standard regulatory handling * **Product catalog:** Plan, pricing, and offer management * **Business rules:** Policy and workflow configuration #### Network and provisioning Complete network integration and service activation across multiple carriers. Includes eligibility checks, provisioning, SIM/eSIM management, and diagnostics—supporting both MVNE and MVNA models. * Eligibility checks * Service provisioning and activation * SIM and eSIM management * Inventory coordination * Diagnostics and service troubleshooting #### Reporting and insights

These are sample figures for illustration purposes.

Standard dashboards and operational reports: * Growth dashboards * Operational dashboards * Support dashboards * Standard performance reports #### Care and support Multi-tier support capabilities with Level 1 tools for your front-line agents and Reach-provided Level 2/3 support. Complete customer visibility across profiles, orders, billing, and fulfillment for efficient issue resolution. * **Escalation & Ticketing:** Technical routing * **Level 2/3:** Reach-provided * **Reach Central:** Back office Reach Central is the web-based back office your team uses daily. It is available from day one. It provides role-based access for sales, support, and business stakeholders. Full training is provided before go-live. * **Sales agent access** * Order creation * Customer onboarding * Promotional tools * **Support agent access** * Customer profile management * Billing views * Ticketing * **Business stakeholder access** * Analytics * Reporting * Operational oversight **What your team can do** * **Subscriber management:** View and manage mobile subscribers in real time. * Activate lines * Suspend accounts * Update plans * Process SIM replacements * Track port-in status * Review the audit trail for every action * **Plan and catalog management:** Configure plans, pricing, and promotions. * Manage rate decks * Enable VAS products * Update device listings * Push storefront changes in real time * **Reporting and analytics:** Track core operating metrics and export data for internal analysis. * Activations * Port-ins * Plan distribution * VAS attach rate * Revenue * Exportable data for internal BI tools * **Support and escalation:** Manage support workflows and monitor operational issues. * Internal ticket management * Real-time porting status * Carrier incident tracking * SLA monitoring {% hint style="warning" %} Train at least 2–3 internal users before launch: an ops lead, a support lead, and the mobile owner. {% endhint %} ### Optional add-ons and customizations Additional customizations are available on a time-and-materials basis to meet unique business requirements and brand standards. #### Experience and UI * UI and UX customizations beyond standard ECHO templates * Custom mobile application * Custom SIM kits, packaging, and inserts * Custom SPN. The standard SPN is `Mobile` #### Platform and logic * Custom business logic and workflows * Advanced discount validation logic * Client-specific feature enhancements #### Integrations and access * Custom third-party integrations * Single sign-on for agents and customers #### Data and reporting * Custom dashboards and reporting views * Client-specific metrics and analytics #### Communications * Email customizations beyond default branding * Lead nurturing series campaign {% hint style="info" %} Questions or clarification? Email us at . {% 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/launching-with-reach/what-is-included-and-optional-add-ons.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.