Home / For ISPs & support teams
For ISPs, support desks and IT teams

Your customer calls with a report, not a complaint.

Right now a “my Internet is slow” call starts from nothing. Your agent asks twenty questions and still cannot tell whether the line is bad or the router is in the wrong room. Diagnostix360 lets the customer run a check on their own phone first, then send one page that answers it.

Free to use — no licence, no contractNothing to install on your network
WHAT YOUR AGENT OPENS
WATCH Wi-Fi in the bedroom — weak signal, −74 dBm
OK Line to the Internet — 38 ms, 0.2% loss
OK DNS resolving normally — 22 ms
WATCH 2 drops in 90 minutes, both inside the home
OK Router reachable the whole time
A Customer report is usually one page. Open the fictional public sample above to see the format.
What changes for your team

The first ten minutes of the call can disappear.

This does not replace your NOC, your CPE platform or your own telemetry. It fixes one specific thing: the customer arriving with nothing but a feeling. The effects below are what a pilot is designed to test; we will publish measured results once pilots report them.

Shorter calls

Your agent stops rebuilding the story from scratch and starts on the part that actually needs a human.

You see the line, not the mood

Delay, packet loss, DNS and stability, measured — instead of “it feels slow sometimes”.

Fewer trucks for Wi-Fi problems

When the fault is a router in a cupboard, the customer can see it, move it and retest before anyone drives out.

Escalations that read the same every time

Second line gets a structured report instead of a free-text note from whoever picked up.

Every agent asks the same questions

The check is identical whoever runs it, so cases stop depending on which agent answered.

The customer feels informed, not dismissed

They can see what was tested and what to try, which is a very different conversation from “we see no problem on our side”.

A CALL TODAY
  • “It’s slow.” Since when? Which room? Wired or Wi-Fi?
  • Agent guesses, tries a line test, sees nothing wrong
  • Customer insists, agent books a visit to be safe
  • Technician arrives, moves the router, closes the ticket
THE SAME CALL WITH A REPORT
  • Agent opens one page before saying hello
  • Line is fine, Wi-Fi in the bedroom is weak — visible in seconds
  • Customer already tried the suggested fix and retested
  • Call ends, or escalates with evidence attached
How it works in practice

The customer does the first ten minutes. Your team does the rest.

01

They run the check

They pick what is actually bothering them and run it in the room where it goes wrong.

02

The app follows the path

Phone, Wi-Fi, router, Internet, DNS, and how steady it all stayed while measuring.

03

They get something to try

One clear action, then a retest. Some tickets can end right here.

04

You get the page

If they still need you, they send the report. Your agent reads it before the call starts.

Real app flow

Simple enough for your customer. Detailed enough for your second line.

The short walkthrough shows the diagnosis finishing and the weak-Wi-Fi finding appearing. The Customer and Technical samples below use that same demo run.

Guided symptom selectionConnection-path diagnosisClear first actionCustomer + Technical reports
Example of a full connection check in progress
Current UI preview with identifying network and system details removed.
What you would be dealing with

Independent, with a method you can check.

Diagnostix360 is more than a speed test: it separates Wi-Fi and local-path observations from DNS, internet-path and service measurements. Evidence and limitations appear in the Technical report.

The public examples are reconstructed from fictional data, not exported customer records. You can review the report structure and the measurement methodology before testing the app on your own network.

Direct contact, no queue

Pilot questions go straight to the people who build it. No account manager, no ticket system, no contract to sign before you can try it.

Get in touch →
What it actually measures
Probes2 independent references, every 3 s
Monitoring sessionup to 90 minutes
Survives Wi-Fi ↔ mobileyes, one session
Detects a filtered resolveryes, not counted as loss
Radio signalsampled and averaged per network
ExportPDF and CSV
Runs onthe customer’s own Android phone
Leaves the phonenothing, unless they send it

Every line above is true of the shipping app today. If a claim here does not hold up in your pilot, tell us and we will either fix it or remove it.

See exactly what lands in your inbox

Illustrative report previews—real structure, fictional data.

Public PDFs use demonstration-only data—not actual customer evidence.

The public reports are newly reconstructed using fictional test values. Real Technical reports can be substantially longer and contain sensitive network identifiers; customer consent and content review are essential before sharing.

The smallest possible first step

Do not commit to a pilot. Just try one ticket.

Pick one open “my Internet is slow” case. Ask that customer to run the check and send the report. Read it before your agent calls them back. That is the whole test, and it costs you one ticket.

If it does not save your agent time, tell us and we stop there. If it does, we can talk about the rest — your logo on the reports, a ticket reference on each session, and getting them to your desk instead of over WhatsApp.

Free while Diagnostix360 is in its first release. No licence, no contract, nothing to install on your network.

Important boundary

Useful phone-side evidence. Your network tools remain the authority for your network.

Diagnostix360 helps narrow the investigation and improve the support conversation. A single run does not prove contractual ISP fault, replace provider telemetry or act as an SLA measurement.