Technical Agent · Support and network
Diagnoses your network before you send a truck.
It reaches the ONU through the OLT, reads optical power, checks the LOS light and reboots the device remotely. For wireless links it checks the sector in UISP. It only opens a ticket when one is truly needed.
Available in text and voice · WhatsApp, phone, web chat, social media and Telegram
Impact on your operation
- Of tickets resolved without human intervention.
- 0%
- Fewer truck rolls.
- 0%
- To reboot a modem remotely.
- <0s
Sound familiar?
Your most expensive resource on the road for an unplugged router.
Unnecessary truck rolls
You send a crew only to find the ONU was unplugged (Dying Gasp) or there was a power outage in the area.
The chaos of a mass outage
A PON port or sector goes down and your WhatsApp floods with hundreds of “no internet” messages and duplicate complaints.
Flows it handles
What the agent resolves on its own, end to end.
Slow or intermittent internet
- Situation
- The subscriber says “nothing loads”.
- What it does
- Reads ONU power (dBm), uptime and LOS via the OLT and reboots the port if the signal is low.
- Outcome
- Solved in the chat, no ticket.
No service
- Situation
- The subscriber's ONU shows offline.
- What it does
- Detects a Dying Gasp (power cut or unplugged device) and guides the subscriber step by step.
- Outcome
- Avoids an unnecessary visit.
Mass outage
- Situation
- A PON port or sector goes down.
- What it does
- Identifies affected subscribers and proactively notifies them on WhatsApp.
- Outcome
- Stops the flood of complaints and duplicate tickets.
Wireless subscribers
- Situation
- A wireless subscriber loses connection.
- What it does
- Checks the Access Point or sector status in UISP before escalating.
- Outcome
- Full diagnosis beyond fiber.
Escalation with context
- Situation
- The issue can't be fixed remotely.
- What it does
- Opens the ticket in your management system with the diagnosis attached.
- Outcome
- The crew leaves knowing what to fix.
How it works
Not a chatbot: AI that takes action in your systems.
Intake and triage
The Supervisor Agent reads the real intent of each message, not keywords, and extracts the customer ID automatically.
Routing to the specialist
It wakes the right sub-agent: Technical for network issues, Administrative for payment receipts or Sales for new business.
Execution on your infrastructure
The sub-agent connects via API to your OLT and management system, checks the real status and takes action.
Resolution or escalation
It replies to the subscriber with the final fix. If it can't be solved, it opens a ticket with full context for your team.
Control and security
You decide how far it goes.
- Reads live status: optical power, uptime and payments.
- Write actions, such as reboots, are limited to safe pre-approved commands.
- Never changes your ISP's core configuration.
- Hands off to a person following your protocols, with the case documented.
Using another platform or need a custom integration?
Rollout
Live in under 4 weeks.
Weeks 1–2
Architecture and rules
We map your operation, define business rules and connect the APIs of your OLT and management system.
Week 3
Integration and setup
We load coverage maps, plans and the knowledge base, and test with real cases.
Week 4
Hybrid Go-Live
Zelty takes the front line on WhatsApp and phone; your team only handles complex cases.
Your monthly fee only starts at Go-Live.
Technical Agent
Frequently asked questions.
What support and network teams ask most before handing diagnosis to the agent.
take the leap
Your next billing cutoff can look different.
We show you Zelty running on your ISP's data: your CRM, your OLT and your real conversations. In 30 minutes you'll see how much of your support can be automated and what not doing it costs you today.