Brand onboarding workflow

High-level onboarding flow, ownership, and launch checklist for a new MVNO brand.

Overview

Use this workflow to take a new MVNO brand from kickoff to launch.

Use the companion onboarding pages in this section for exact fields, asset specs, and broader platform scope.

At a glance

• Brand provides inputs and assets.
• Reach configures the tenant and journeys.
• Brand reviews staging and signs off.
• Reach launches production.
• Brand + Reach run post-launch changes through a controlled request process.

Workflow

1

Kickoff and scope

Confirm what you’re launching. Lock owners, dates, and sign-off criteria.

Decisions to confirm:

• Brand name and legal entity
• Service availability model
• Plans and pricing model
• Support model
• Any required add-ons

Output: scoped launch plan and owners.

2

Provide onboarding inputs

Share the required business details and brand assets.

Brand provides:

• Completed onboarding inputs (fields + assets)
• Credentials and IDs for any brand-owned integrations (if applicable)

Output: onboarding packet marked complete.

3

Reach configuration and build

Reach sets up your tenant, journeys, content, and policies.

Common parallel workstreams:

• Domain readiness
• Marketing and analytics tags
• Support tooling and contact points
• Optional device store enablement

Output: staging environment ready for review.

4

Staging review and acceptance

Validate the end-to-end customer experience.

Minimum checks:

• Homepage content renders correctly across devices
• Plan selection, checkout, and payment descriptor
• Eligibility gates behave as intended
• Support contact details are correct
• SEO and social cards preview correctly when shared

Payment rules, fraud controls, and purchase screening should be confirmed before sign-off.

Output: sign-off to launch.

5

Launch and post-launch rhythm

Reach takes production live after sign-off. Then the program moves into BAU operations.

Align on:

• Escalation path and operational contacts
• Reporting cadence and distribution lists
• Who approves future catalog, content, and policy changes

Most BAU changes later route through the catalog, communications, or bolt-on change process.

Output: brand live, with an operating rhythm.

Suggested owners (minimum)

• Brand onboarding owner: accountable for inputs and sign-off.
• Reach onboarding lead: accountable for configuration and launch.
• Brand marketing owner: content and SEO approvals.
• Brand care/ops owner: support model, contacts, and escalation readiness.

Also read

• Brand onboarding configuration for the exact fields and assets required before launch
• Reach Platform offering for the standard scope and operating model
• Payments, fees, and compliance for checkout, payment, and dunning rules
• Bolt-ons catalog for add-ons that can affect scope and timeline

Questions or clarification? Reach out to your respective account manager or email us at [e-mail] for help and support.