Reported operating use · Telecommunications
Voice-network diagnosis and reviewed remediation
One New Zealand
Operational VoLTE investigation deployment with human review on most action paths; fully closed-loop operation not established.
A published third-party example, not a Nuvepro customer case or evidence of a partnership.
What the source reports
The supplier reports a VoLTE investigation deployment at One NZ. Its later retrospective says most VoLTE action paths retain human review. One NZ describes live network optimization and human accountability. The supplier's detailed L3 workflow-mapping example is portfolio practice, not direct evidence of the exact One NZ deployment.
Reported technology: Google Cloud / Gemini with Future Connections. Scope and outcomes are source-reported.
What the enterprise environment would need
The following is a proposed project design for an enterprise doing similar work. Published details are marked; the remaining systems, data and scenarios would be agreed for your project.
- Systems and tools
- Inferred test scope: Existing network testbed or read-only replay of approved telemetry.
- Data and state
- Inferred test scope: Aligned timestamps, equipment configuration and counter semantics.
- People and handoffs
- Inferred test scope: Engineer reviews proposed remediation and owns operating impact.
- Rules and authority
- Inferred test scope: Allowed network changes require explicit authority and safe rollback.
- Normal and exception cases
- Proposed test cases: Actual outage, stale counter, conflicting telemetry, tool failure, false correlation.
- Reset and replay
- Not reported. Proposed: Replay historical traces; reset only a controlled testbed, never live network state.
A proposed simulation
An illustrative practice design derived from this work, not an executed assessment.
Diagnose a VoLTE issue amid stale counters and misleading correlations, then hand supported remediation to an authorized engineer.
Review gate: Check counter semantics, known incident cause, confidence, change authority and rollback; do not treat a fluent diagnosis as correct.
Challenge the result: Misalign counter timestamps or inject a misleading correlation. The assessment must detect unsupported diagnosis and prevent an unauthorized change.
What needs checking
- Published supplier practice: consistent tool schemas, structured errors, safe retries and provenance.
- Proposed: test diagnosis and recommendations against incident outcomes and engineer review.
- Published supplier lesson: explicit workflow mapping precedes agent design.
- Proposed: validate telemetry semantics and temporal alignment against operational reference traces.
Review environment fidelity, human capability and agent performance separately. The enterprise’s accountable owners decide acceptance of the shared workflow and any operating use.
Shape this around your enterprise
Bring a similar workflow and the people responsible for it. Together, define the records and systems to use, the result your team will build or configure, and how its owners will check it. Nuvepro scopes the simulation, environment and preparation. Agree any existing-agent evaluation, implementation assistance and production responsibilities separately.
Sources and limitations
Curation review: . This is the date this source example was reviewed, separate from source publication dates.
- Independent incident-outcome accuracy, full reset design and evidence for unrestricted closed-loop network operation are not supplied.
- Scaling the autonomous network: introducing the Data Steward & Core Network agentsSource publication: 2026-03-04
- A year of building agents for telco operatorsSource publication: 2026-05-26
- Responsible Artificial Intelligence (AI)