Telecom and internet businesses

Define the service before choosing an authorisation

Record who contracts with the subscriber, operates network equipment, obtains upstream connectivity and carries customer traffic. An internet-access provider, virtual network operator, equipment distributor and software vendor have different regulatory questions. The commercial label on an invoice does not settle the service classification.

DoT now publishes Internet Service Authorisation information under the 2026 framework, alongside legacy UL/UL-VNO material. For an existing business, identify the instrument actually governing it and any migration requirements; for a new application, use the current service-specific procedure.

Keep service and equipment permissions distinct

A service authorisation does not establish that every radio product or installation is compliant. Assess equipment type approval, notified product standards and import requirements against the exact model and radio characteristics. DoT’s ETA guidance addresses equipment operating in licence-exempt bands and relevant module arrangements.

For network sites, map access rights, installation contracts, electrical safety and applicable local permissions. Keep site evidence linked to the assets and parties responsible for maintenance.

Build the recurring operating file

• Applicable authorisation, service area, conditions, correspondence and renewal or migration records.
• Subscriber onboarding, service terms, complaint handling and access-control responsibilities.
• Upstream agreements, equipment inventory, network changes and incident escalation records.
• Billing reconciliations, customer deposits, prepaid balances, refunds and inter-party settlements.
• Revenue classifications and evidence needed for obligations imposed by the governing instrument.

Manage data and outsourced operations

Assign responsibility for customer information, operational logs, vendor access and security incidents. Determine retention and reporting duties from the applicable instruments instead of adopting a single retention period for every dataset. Outsourced support contracts should identify permitted access, escalation and return or deletion arrangements.

Example: expanding from support to connectivity

A business that previously installed customer routers may decide to sell internet access under its own customer contract. Before launching, it should reassess its regulatory role, upstream arrangement, billing responsibilities and complaint process. Its existing installation-service registrations do not answer those new questions.

How Kosha supports the operating model

We can help organise corporate, accounting, tax and contractual records around the confirmed service classification. Network engineering, security certification and specialist authorisation advice need their own appropriately qualified scope.

Choose support for the change you are making

• Introducing equipment or changing a wireless model: start with telecom and wireless approval coordination. Supply the model identifier, intended use, radio specifications and existing certificates so the assessment follows the actual product.
• Signing an upstream or customer agreement: use commercial contract review to examine service commitments, outage reporting, credits, termination and equipment ownership. Bring both agreements where promises to customers depend on an upstream provider.
• Changing subscriber onboarding: use privacy notice and consent design alongside the applicable telecom requirements. Map the information collected, its purpose, vendor access and the customer-facing journey.

For a network expansion, prepare one change brief identifying new service areas, equipment, contractual parties and launch dependencies. Keep technical readiness and authorisation status visible as separate decisions in that brief.