For the complete documentation index, see llms.txt. This page is also available as Markdown.

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

Buy a bolt-on

Available bolt-ons

  1. SSO — End Customers — Let customers sign in using brand-managed credentials.

  2. SSO — Agents — Use your Identity Provider for Reach Central access.

  3. Product Bundle Integration — Bundle mobile with existing brand services and offer converged pricing.

  4. eCommerce — Launch a branded device store with sales, financing, fulfillment, and post-purchase management.

  5. Custom App Hosting — Choose Reach-hosted or brand-hosted web and mobile applications.

  6. Custom SFTP Setup — Deliver standard Reach reports to your secure SFTP folder.

  7. Custom Service Provider Name (SPN) — Display your brand name on supported customer devices.

  8. Custom Domain Setup — Move customer journeys from a Reach subdomain to your domain.

  9. Mobile for SMB by Reach — Offer shared business account controls for teams of up to 25 lines.

  10. Smart Subs — Benchmark acquisition, churn, and support demand against an anonymized MVNO peer panel.

  11. Accessibility Widget — Add AI-powered accessibility controls and continuous scanning to Echo customer journeys.

Some bolt-ons are only available to some brands, networks, or launch stages.

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

Questions or support

Questions or clarification? Reach out to your respective account manager or email us at account-desk@reachplatform.com for help and support.

Last updated