On-site AI agents for your toughest remote-site network problems
The dashboard says the site is up. The people there say everything is slow. Ragent investigates from inside the site and puts the likely cause on the ticket.
- Starts on every ticket, from a person or an alert
- Gathers fresh evidence, not just what monitoring collected
- Your team decides every fix
See Ragent work a real ticket
Prefer to talk?
Book a CallWhy is the network slow at one site and not the others?
Same complaint, different cause. From head office the provider, one laptop and a weak access point all look the same, so your team finds out by phone or by truck.
Tickets this morning
Example: three sites, one complaint
Everything is slow
Main St store
Likely cause: Internet provider, whole site
9:02
Everything is slow
Riverside clinic
Likely cause: This laptop
9:03
Everything is slow
Harbour St restaurant
Likely cause: Access point
9:03
How does Ragent troubleshoot a remote site?
1
A problem is reported or an alert fires
By email, Teams, chat, phone or a monitoring alert. Each one becomes a ticket.
2
Ragent investigates on site
It tests the internet connection, the local network, the apps the site uses and the person’s laptop, and picks each next check from what it finds.
3
The likely cause lands on the ticket
With the evidence, ready for your technician. Your team decides the fix.
Ticket note from NetZen AI
Example: Riverside clinic
- Ragent at the site
- Internet and access point normal from inside the clinic.
- The reporter’s laptop
- Memory full. An update has been stuck in the background since 8:40.
- Likely cause
- This laptop. Suggested next step: restart the update, which waits for your approval.
How is Ragent different from other network AI?
Most network AI answers from what its monitoring already collected. Ragent goes and gets the evidence the problem needs.
| Question | Other network AI | Ragent |
|---|---|---|
| Starts from | A person opening the AI on an alert, or typing a question | Every ticket, from a person or an alert, on its own |
| Works from | Data its monitoring already collected | Checks it chooses and runs inside the site, while the problem is happening |
| Answer | A dashboard or a chat | The ticket, with the evidence |
Who decides the fix?
Your team does. Ragent investigates and proposes, and every check is recorded on the ticket.
What it will not do
- Change a device or setting without your approval
- Look at what people browse or read their traffic
- Need an inbound firewall opening: it only makes outbound connections
Ragent questions
A dedicated always-on computer at the site, such as a small server or a Raspberry Pi. We help you set it up. The device in our video is an illustration.
Yes. Ragent’s findings go on tickets in NetZen, next to email, Teams and chat. You can start with one site.
It needs no inbound firewall opening and connects out to NetZen over an encrypted connection. Every check is recorded on the ticket, and changes follow the approvals you set.
Yes. Any team that supports several locations, such as stores, clinics, restaurants or branch offices.