Viewing: All audiences

Wholesale and enablement

Build a technology offer with less operational friction

Start with authorised services. Then agree the commercial and operating model: how quoting, ordering, billing and support will work, and who owns the customer.

Capability framework

  • Catalogue
  • Quote and order
  • Provisioning
  • Billing
  • Service
  • Insight
Two colleagues discussing a process flow drawn on a whiteboard
Define first Operating model
  • Target customers and services
  • Brand and commercial ownership
  • Contracting and billing
  • Support, data and compliance

Start with the offer and operating model

Decide how the offer works before choosing features

First, define your target customers, services, brand, commercial ownership, contracting, billing, provisioning, support, data handling and compliance. Then choose platform features.

A portal does not solve an unclear operating model.

Define before choosing platform features

  • Target customers
  • Services
  • Brand
  • Commercial ownership
  • Contracting
  • Billing
  • Provisioning
  • Support
  • Data handling
  • Compliance

Capability framework

From catalogue to reporting, with status shown

A wholesale operating model has six capability areas. Each is labelled for the relevant partner model and is subject to live capability.

  1. Catalogue

    Approved services, eligibility, pricing, terms, product status and partner permissions.

  2. Quote and order

    Qualification, proposal, approval, order capture and supplier submission using the live process.

  3. Provisioning

    Milestones, dependencies, exceptions, activation, acceptance and inventory updates.

  4. Billing

    Charges, usage where applicable, taxes, adjustments, disputes and reconciliation under the agreed model.

  5. Service

    Customer contacts, ticketing, incident routing, escalation, maintenance and reporting.

  6. Insight

    Pipeline, orders, service inventory, support and commercial reporting where live.

Capability varies by service, supplier and partner model. During the assessment, we confirm what is available and what needs further discovery.

Request a wholesale assessment

Capability status

We label capability honestly

Every capability is labelled Live, Beta, Planned or Not offered for the relevant partner model, so you know what is available today and what is not.

  • Live

    Available now for the relevant partner model. Only Live capability is described as available today.

  • Beta

    Available with stated limitations and eligibility.

  • Planned

    Discussed in a controlled roadmap conversation, not offered as a public promise.

  • Not offered

    Not available for that partner model.

Customer and data responsibility

Clear boundaries before the first customer

The agreement must name who holds each responsibility. Customers should not have to find the boundaries in the middle of a problem.

Commercial

Named in the agreement

  • Contracting party
  • Brand
  • Seller
  • Biller

Customer care

Named in the agreement

  • Service desk
  • Complaint owner
  • Hardship process, where applicable

Data and regulatory

Named in the agreement

  • Privacy roles
  • Data access
  • Regulatory responsibilities

Each responsibility is assigned to a named party for every service in the agreed model.

Read the Privacy Policy

Integration and security

Integration only when we can support it

Where integration is available, it uses approved authentication, least privilege, logging, error handling, test environments and change control.

We offer API or automation access only once the technical documentation, support ownership and commercial access are ready.

Integration standards

Where integration is available, it is built and run with:

  • Approved authentication
  • Least-privilege access
  • Logging and error handling
  • Test environments
  • Change control

Discovery covers

  • Security
  • Data mapping
  • Testing
  • Operational ownership

Questions

Frequently asked questions

Straight answers about white labelling, provisioning, integration and customer ownership.

Is white labelling available?

Only if we confirm it for the specific service and partner model. The brand, contracting, billing, support, disclosure and regulatory requirements must also be documented.

Do you offer automated provisioning?

It depends on the product and supplier. For each service, we confirm the exact live workflows and limitations rather than making a blanket claim.

Can the platform integrate with our CRM or billing system?

Possibly, where there is a supported interface and an approved commercial model. Integration needs discovery, security, data mapping, testing and operational ownership.

Who owns the end customer?

It is set in the executed agreement, which must define customer ownership, contracting, data, marketing permissions and what happens after termination. Don’t rely on an informal assumption.

Qualify the model

Request a wholesale assessment

Share your proposed customer segment, catalogue, expected volume, brand model, systems, billing approach, support design and target date. We’ll confirm what is available and what needs further discovery.

Helpful to have ready

  • Customer segment and geography
  • Catalogue and expected volume
  • Brand model: referral, reseller, wholesale or white label
  • Systems, billing approach and support design
  • Target date

Do not include customer data, credentials or technical integration secrets in a first enquiry.

Already a customer?

For service, billing or complaints, go to Support.

Find the right option

Which best describes you?

Choose the option that best matches you. We will show the services, support and next step designed for your needs.

Not sure which option fits? Tell us what you need.