For providers, IT teams and support desks

Start the support conversation with measurements, not just a symptom.

A customer can run Diagnostix360 on the affected Android phone and, if they choose, send the resulting report to your support team. It gives you a phone-side view of the connection at the time of the problem, to use alongside your own telemetry and troubleshooting process.

What arrives

Two reports from the same check.

Nothing is sent automatically. If the customer decides to share a result, they can choose the report that fits the case.

Sanitized Diagnostix360 Customer report sample — **Customer report**A concise conclusion, what was checked and the recommended next step. It is intended for the support conversation.

Sanitized Diagnostix360 Technical report first page — **Technical report**Path timing, reliability, score evidence and the supporting detail a support or engineering team may need.

Select either report to open a larger, readable preview.

Where it can help

Use the report alongside your own tools.

Remote triage

A report can help separate an obvious Wi-Fi or local-network concern from a case that may need investigation farther upstream before a visit is booked.

Better escalation context

Second-line support gets more than a symptom description. It can see the measurements captured by the customer's phone during that check.

Before-and-after comparison

Ask the customer to repeat the same check after one change. You then have a before-and-after comparison instead of relying on memory.

A result the customer can follow

The Customer report keeps the conclusion in plain language, making the next step easier to explain on the same call.

A practical workflow

It can fit into the support process you already use.

01The customer runs Diagnostix360On the affected connection, from the place where the problem normally occurs.

02The reports are created on the phoneCustomer and Technical PDFs come from the same completed run.

03The customer chooses what to sendBy email, messaging or the ticketing channel you already use.

04Your team reviews the evidenceReview where the first concern appears, together with the timing and reliability measurements.

05Continue remotely or escalateUse your own diagnostics and process to decide whether the next step is a remote change, further investigation or a dispatch.

Limits matter

A phone-side result can narrow the search; it cannot assign fault.

Diagnostix360 can show where a problem appears within the part of the path the phone can observe. It cannot see every provider element, application server or routing decision, so the report should not be treated as proof that a particular party caused a fault.

Each result describes one phone, one connection and one measured window. It is not a certified network audit, a service-level measurement or a replacement for provider-side telemetry.

✓
Point in time
Conditions can change immediately after a check finishes.
✓
Device visibility varies
Android permissions, handset capabilities and the connection type affect what can be measured.
✓
Use it with your own telemetry
Treat the report as one input alongside CPE, access, core, application and operational telemetry.

Privacy & sharing

The customer remains in control of sharing.

Reports remain on the user's phone until they choose to share them. Because the Technical report can contain network identifiers and detailed path information, the app asks for explicit confirmation before sharing.

Want to evaluate the reports?

Run the app on a test connection, export both report types, and see whether the information fits your support process.

Questions about the reports: support@diagnostix360.com