Home / Solutions / ISP Ticket Management

ISP Ticket Management

The ISP hears about the outage before your users do.

When a carrier circuit fails, every minute between the alarm and the ISP ticket adds to the outage. AotoNet validates the fault, logs it with the right carrier in its own format, chases acknowledgement and escalation, and closes the loop when the link is stable.

ISP Ticket Management
ISP tickets grouped by carrier, with a multi-site outage linked under one major incident

The challenge

Why the traditional approach breaks down

Carrier fault handling still depends on people noticing alarms and making calls.

Slow to engage the carrier

The clock starts at the fault but the carrier's clock starts at the phone call.

Wrong or missing details

Incorrect circuit IDs and missing diagnostics send tickets back and forth.

Tickets that should not exist

Faults during planned maintenance, or caused by the organisation's own router, waste everyone's time.

Duplicates during flapping

An unstable link generates a new ticket every time it drops.

Escalations missed

Nobody is watching the carrier's escalation timers at 2 a.m.

No data for SLA reviews

Without outage and MTTR records, service credits and carrier reviews rely on memory.

Two ways to do the job

From manual effort to an automated pipeline

Traditional approach

How it is done today

Carrier fault handling still depends on people noticing alarms and making calls.

  1. Notice the alarmThe monitoring tool raises an alert, often while the NOC is busy with something else, or users call first.
  2. Work out whose fault it isCheck whether it is the carrier or the organisation's own router.
  3. Find the circuit detailsLook up the circuit ID, carrier contact and escalation matrix in a spreadsheet.
  4. Call or email the carrierDescribe the fault and wait for a docket number.
  5. Follow up and escalateChase updates and escalate when someone remembers to.
  6. Close and forgetClose the internal ticket after restoration; the reason for the outage and the SLA impact are rarely recorded.
With AotoNet

How AotoNet automates it

AotoNet handles the full lifecycle by rule, with diagnostics and evidence attached.

  1. Ingest monitoring eventsLink down, BGP down, packet loss, latency and flapping from your monitoring tools.
  2. Apply trigger rulesHold times avoid tickets for blips; priority follows the circuit's business criticality.
  3. Check the guardsPlanned maintenance, an unreachable on-premises router and duplicate events are filtered out.
  4. Attach diagnosticsPing, interface counters and BGP state collected automatically, with a verdict.
  5. Log with the carrierTicket raised through the carrier's API, portal or email template, plus the internal incident.
  6. Track and escalateAcknowledgement and docket captured, escalation on the carrier's own matrix, multi-site outages correlated.
  7. Close with evidenceRestoration detected, stability confirmed, outage duration and MTTR recorded, and the reason for the outage requested.

Side by side

What changes, point by point

AspectTraditional approachWith AotoNet
Detection to ticketWhenever someone notices and callsLogged as soon as the fault passes its hold time
Fault validationManual checks, often skippedGuards for maintenance windows, on-premises router health and duplicates
Ticket contentVerbal description, details looked up by handCarrier template with circuit details and diagnostics attached
Multi-site outagesHandled as separate, unrelated ticketsCorrelated into one major incident
EscalationDepends on someone rememberingAutomatic, on each carrier's own matrix
ClosureManual; reason for the outage rarely collectedAutomatic after stability, with MTTR and the reason requested
Carrier performanceAnecdotalOutage and MTTR history for every circuit and carrier

Capabilities

What ISP Ticket Management includes

Trigger rules

Link down, BGP, packet loss, latency and flapping, each with hold time and priority by circuit criticality.

Guards

Maintenance suppression, on-premises router checks and de-duplication keep tickets accurate.

Carrier templates

Each carrier's logging channel, required fields and escalation matrix configured once.

Major incident correlation

Several circuits from one carrier failing together are grouped automatically.

Live circuit board

Every circuit's state by site: up, degraded, down, unstable or in maintenance.

Full ticket timeline

Detection, diagnostics, carrier responses, escalations and closure in one history.

Ticket timeline
Rule match, diagnostics, carrier acknowledgement and escalations, all recorded automatically.
Rule match, diagnostics, carrier acknowledgement and escalations, all recorded automatically.

Benefits of automation

What your team gains

Lower MTTR

Carriers start work minutes after the fault, not after the first phone call.

Fewer wasted tickets

Planned work, on-premises faults and duplicates never reach the carrier.

Evidence for SLA claims

Outage durations and response times for every carrier, ready for service reviews.

A calmer NOC

Engineers handle exceptions instead of dialling carrier helpdesks.

Connects to

Network monitoring & observabilitySNMP traps, syslog & telemetryCarrier APIs, portals & NOC mailboxesITSM incident managementEmail & collaboration

See ISP Ticket Management on your own network.

Book a 30-minute walkthrough, then run a pilot on a sample of your own data.