1. The TPIA support brief
A Canadian independent ISP serves retail customers over wholesale cable access. The customer contacts the ISP, while some installation, access network, appointment, and repair actions depend on the wholesale carrier process. A weak intake causes rejected tickets, repeated diagnostics, unclear ownership, and poor customer updates.
MY-VA can staff the retail intake and coordination desk around the ISP’s approved procedures and each applicable carrier interface. The team works for the ISP. It does not represent the carrier, the CRTC, or an independent complaint body, and it does not control wholesale acceptance, dispatch, restoration, or appointment availability.
TPIA processes differ by carrier, region, service, tariff, interface, and ISP agreement. This example does not promise ticket acceptance, appointment dates, restoration times, or regulatory outcomes.
2. Distinguish the retail relationship from wholesale access
The CRTC describes TPIA as an aggregated wholesale high-speed access service provided by large cable carriers. Independent providers can use that access to deliver their own retail Internet service. The retail support desk therefore needs to understand which actions belong to the ISP and which require the applicable wholesale process.
The operating map identifies the carrier, access region, service profile, supported modem or access equipment, order or ticket interface, required fields, diagnostic requirements, appointment process, status source, escalation path, and customer communication owner.
Industry reference: CRTC Telecom Order 2020-60 on TPIA services
3. Complete the ISP checks before opening a wholesale ticket
The agent verifies the retail account and service address, identifies the active plan and carrier context, checks known ISP notices, reviews previous cases, and records the exact customer symptom. Approved checks can cover equipment power and indicators, physical connections, local network scope, recent changes, and service tests available to the ISP.
The team separates account, billing, customer equipment, ISP platform, general outage, installation, and access network issues. A wholesale ticket is opened only when the case meets the ISP and carrier requirements. Unsupported assumptions are not presented as a carrier fault.
4. Submit installation and trouble ticket details completely
The ticket package follows the current carrier process and may include the service address, order or service reference, permitted equipment identifier, issue start time, symptom, affected scope, tests completed, observed results, customer availability, contact details, and required appointment information.
The agent records the submission reference, status, next review time, and information still required. If the carrier rejects or returns a ticket, the reason is preserved and routed for correction. The customer receives an accurate explanation without unsupported blame or a restoration promise.
- Installation order and activation status questions.
- No service, intermittent service, or degraded service intake.
- Required diagnostics and evidence capture.
- Appointment availability and access coordination.
- Carrier status, return reason, and escalation tracking.
5. Keep the customer updated while ownership crosses organizations
The ISP defines when customers receive status updates, which channel is used, what can be stated, and when a supervisor takes over. The support desk tracks open tickets and appointments instead of waiting for the customer to call again for information already available.
Missed appointments, unavailable access, new outage information, customer equipment changes, repeat faults, and carrier requests for more evidence each follow a named path. Complaints and credits remain with the ISP owner authorized to apply policy and meet applicable obligations.
6. Review ticket completeness and customer ownership
Quality review checks identity handling, symptom capture, required diagnostics, ticket fields, carrier selection, status notes, customer explanation, appointment communication, and escalation. Rejected tickets are reviewed for a process gap, missing evidence, incorrect routing, or a requirement outside the support desk’s control.
Reporting can include retail contacts, installation inquiries, trouble tickets submitted, carrier returns, requested evidence, appointment statuses, age of open tickets, repeat customer contacts, escalation reasons, and quality findings. The ISP sets definitions and targets from its agreements and systems.
The ISP owns the customer conversation, the wholesale carrier receives the required evidence, and every open item has a reference, next review point, and responsible party.