Live Demo ReadyBuilt for ISP / NOC WorkflowsSupabase Connected

Lightning SLA

AI outage communication for South African ISPs and NOCs.

Lightning SLA helps network teams turn service alerts into SLA-aware customer updates, first-line checks, live ticket links and proof of response time.

Demo flow: create outage ticket β†’ save to Supabase β†’ generate customer link β†’ show service status page.

Current Demo Status

End-to-end ticket workflow is live.

The demo can create a real ticket, save it to the database, display it in the admin queue and open a customer-facing ticket page.

Database

Connected

Supabase ticket storage

Live Hosting

Vercel

Public demo link ready

Customer Page

Live

Ticket status links

Demo Button

Ready

Simulate outage flow

The Problem

ISPs already know when things break. The gap is fast customer communication.

During outages, NOC teams are under pressure to confirm impact, run first-line checks, log tickets, update customers and avoid SLA communication delays. Lightning SLA focuses on that exact workflow.

01

Outage detected

A network event such as downtime, high latency or packet loss is detected by the monitoring workflow.

02

AI classifies impact

Lightning SLA helps classify the likely cause, affected area, priority and customer impact.

03

Ticket created

The NOC creates a customer-facing ticket with SLA status, first-line checks and next update time.

04

Customer link shared

The customer receives a simple status link instead of needing to phone support for basic outage updates.

Product Advantage

Built around the NOC-to-customer SLA layer.

⚑

For the NOC

Reduce pressure on Tier 1 agents by turning alerts into clear first-line actions and customer updates.

πŸ“¨

For Customers

Give clients a clean service status page with ticket reference, likely cause, checks completed and next update.

πŸ“ˆ

For Sales

Show SLA response proof, customer update performance and service reliability stats to future customers.

Pricing Direction

Pilot-friendly pricing with room to scale.

These are projected commercial packages for demo and pilot discussions. Final pricing can be adjusted per ISP size, integrations and support requirements.

Pilot

For a first ISP/NOC trial to prove the workflow and collect real feedback.

Best for first customer

R5,000/month

R10,000 setup

βœ… Admin dashboard

βœ… Client outage portal

βœ… Ticket creation

βœ… Customer status links

βœ… Basic branding

βœ… Supabase ticket storage

Production

For ISPs ready to use Lightning SLA as part of their customer update workflow.

Recommended

From R12,500/month

Setup quoted per ISP

βœ… Branded client portal

βœ… SLA communication workflow

βœ… Active ticket queue

βœ… Demo outage scenarios

βœ… Reporting dashboard

βœ… Priority support

Enterprise

For larger ISPs, FNOs, NOC providers or companies needing integrations.

For larger teams

Custom pricing

Custom onboarding

βœ… Custom integrations

βœ… Multiple regions

βœ… Advanced reporting

βœ… Custom SLA rules

βœ… Team permissions

βœ… Dedicated support

Suggested first offer

Start with a 90-day pilot: R10,000 setup and R5,000/month. After the pilot, move production clients to R12,500/month or custom pricing depending on integrations and NOC size.

Startup Positioning

Not a replacement for monitoring tools β€” an AI layer above them.

The strongest positioning is to plug Lightning SLA into tools ISPs already use, then automate the customer update and SLA proof workflow.

Pitch line

Lightning SLA helps South African ISPs turn network alerts into fast, SLA-compliant customer updates.

Integration Roadmap

βœ… PRTG / Zabbix / LibreNMS alerts

βœ… Ping, latency and packet loss checks

βœ… FNO escalation notes

βœ… SMS and email provider integration

βœ… Role-based admin login

βœ… Monthly SLA reports

These are the next features that would move the demo closer to a production-ready SaaS product.

60 Second Demo Script

What to say when showing the demo

β€œLightning SLA is an AI NOC co-pilot for South African ISPs. The goal is not to replace existing monitoring tools, but to automate what happens after an alert is detected.”

β€œWhen an outage or degradation happens, the system helps classify the likely cause, creates a customer-impacting ticket, starts the SLA communication workflow and prepares a customer update.”

β€œThe NOC can then copy a customer-facing link. The customer sees a clean status page with the ticket reference, affected area, likely cause, checks completed, support details and next update time.”

β€œThis helps reduce unnecessary support calls, improves SLA communication, and gives the ISP proof that customers were updated quickly.”