An FNO escalation ticket is a formal fault request submitted by an ISP to a Fibre Network Operator after confirming an access-layer fault. It contains validated diagnostic evidence and triggers FNO-controlled repair and dispatch processes.
ISP Support Ticket vs FNO Escalation Ticket
These are not the same.
An ISP Support Ticket:
- Is created when a customer reports an issue
- Begins diagnostic validation
- Remains within the ISP’s control
An FNO Escalation Ticket:
- Is created only after escalation criteria are met
- Is submitted to the infrastructure owner
- Triggers access-layer investigation
- Moves into FNO-controlled workflow
Escalation boundary reference: When Does an ISP Escalate to an FNO?
Why Escalation Requires a Separate Ticket
In South Africa’s open-access model:
- ISPs do not own the fibre infrastructure
- FNOs control cabinets, OLTs, and physical lines
- Dispatch authority sits with the FNO
An ISP cannot send a technician to repair physical fibre unless the FNO authorises it. An escalation ticket formalises:
- Fault classification
- Diagnostic evidence
- Responsibility boundary
Escalation Ticket Lifecycle
ISP Diagnostic Validation
- Before escalation: WAN sync status confirmed, router integrity validated, LAN causes eliminated, packet loss classified (if applicable), and telemetry attached.
- Only confirmed access-layer faults qualify.
Escalation Ticket Creation
- The ISP submits: customer service ID, location details, FNO reference ID, access-layer fault classification, diagnostic logs and telemetry, and timestamp of failure.
- This becomes an official FNO Escalation Ticket.
FNO Acceptance & Review
- FNO reviews escalation criteria compliance, signal history, area-level fault patterns, and infrastructure alarms.
- The ticket may be accepted, rejected (insufficient evidence), or reclassified as area outage.
Dispatch Scheduling
- If accepted: technician assigned, access to cabinet or property scheduled, and repair action planned.
- Repair progression reference: Typical Fibre Repair Timelines in South Africa.
Repair & Status Updates
- FNO updates ticket status through stages: Accepted, In Progress, Technician Assigned, Resolved, or No Fault Found.
- The ISP relays status updates to the customer.
Resolution Confirmation
- After FNO marks resolved: WAN sync verified, stability confirmed, monitoring reviewed, and ticket closed in ISP system.
- Resolution must be validated, not assumed.
What Information Is Included in an FNO Escalation Ticket?
| Data Category | Purpose |
|---|---|
| Service Identifier | Identifies affected line |
| Fault Classification | Confirms access-layer issue |
| Diagnostic Evidence | Validates escalation |
| Timestamp of Failure | Cross-checks network logs |
| Signal State | Confirms sync loss |
| Area Correlation | Detects wider outage |
Incomplete tickets risk rejection.
Key Term: FNO Escalation Ticket
A formal infrastructure-level fault request submitted by an ISP to a Fibre Network Operator after confirming an access-layer fault requiring physical network intervention.
What an Escalation Ticket Does NOT Mean
It does not mean:
- Immediate technician dispatch
- Guaranteed same-day repair
- ISP-level control over timeline
- Automatic SLA credit
It means responsibility has formally transferred to the infrastructure owner.
Common Escalation Outcomes
Each outcome affects repair timeline differently:
- Accepted – Individual Fault: line-specific issue, technician scheduled
- Accepted – Area Outage: infrastructure fault affecting multiple subscribers
- Rejected – Insufficient Evidence: further validation required
- No Fault Found: signal stable at time of inspection
South African Multi-FNO Environment
UrbanX operates across multiple FNOs, including:
- Vumatel
- Openserve
- Frogfoot
- MetroFibre
Each FNO has independent escalation portals, separate dispatch queues, and different operational capacities. Escalation does not equal uniform response time.