Commercial
Named in the agreement
- Contracting party
- Brand
- Seller
- Biller
Viewing: All audiences
Wholesale and enablement
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

Start with the offer and operating model
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
Capability framework
A wholesale operating model has six capability areas. Each is labelled for the relevant partner model and is subject to live capability.
Approved services, eligibility, pricing, terms, product status and partner permissions.
Qualification, proposal, approval, order capture and supplier submission using the live process.
Milestones, dependencies, exceptions, activation, acceptance and inventory updates.
Charges, usage where applicable, taxes, adjustments, disputes and reconciliation under the agreed model.
Customer contacts, ticketing, incident routing, escalation, maintenance and reporting.
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 assessmentCapability status
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.
Available now for the relevant partner model. Only Live capability is described as available today.
Available with stated limitations and eligibility.
Discussed in a controlled roadmap conversation, not offered as a public promise.
Not available for that partner model.
Customer and data responsibility
The agreement must name who holds each responsibility. Customers should not have to find the boundaries in the middle of a problem.
Named in the agreement
Named in the agreement
Named in the agreement
Each responsibility is assigned to a named party for every service in the agreed model.
Read the Privacy PolicyIntegration and security
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.
Where integration is available, it is built and run with:
Discovery covers
Questions
Straight answers about white labelling, provisioning, integration and customer ownership.
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.
It depends on the product and supplier. For each service, we confirm the exact live workflows and limitations rather than making a blanket claim.
Possibly, where there is a supported interface and an approved commercial model. Integration needs discovery, security, data mapping, testing and operational ownership.
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.
Related
Not every partnership needs a wholesale model. Compare the pathways, see how we manage services and look through the full range.
Referral, co-solution, reseller or channel and technology partnerships with clear ownership.
ExploreOnboarding, incidents, changes, reporting, renewals, supplier coordination and transition.
ExploreConnectivity, mobile and IoT, voice, cloud, AI voice and digital marketing across every audience.
ExploreQualify the model
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
Do not include customer data, credentials or technical integration secrets in a first enquiry.
For service, billing or complaints, go to Support.