What problem does it solve?
Technician visits are expensive: a van, a skilled person and often a customer who took time off to be at home. Some visits should not happen at all, because the fault could have been fixed remotely or was not a fault. Others happen but fail: the technician finds a blocked duct, a missing part or a job that needs a different skill, and the customer has to wait for a second appointment.
When installations run into trouble, customers can be left without clear information. Openreach describes how issues such as blocked underground ducts, complex build requirements or changed survey findings could in the past mean missed appointments, repeat visits and uncertainty. nbn made the same point from the other side in 2017: it wanted its field workforce to connect more homes rather than attend to problems that do not exist. Meanwhile technicians on site search manuals, call colleagues or phone a help desk for answers that already exist somewhere in the company.
How does it work?
- Triage before dispatch. When a fault is reported, a model uses line tests, device telemetry and history to decide whether it can be fixed remotely, needs a visit, or needs a specific skill or part.
- Predict the job. For visits, the system predicts the likely work type, duration and parts, so the right technician arrives with the right kit, and flags jobs likely to need follow on work.
- Plan and communicate. Scheduling uses the predictions to build realistic routes and slots; when a job hits a snag, the customer and the retail provider get a clear update with the expected next step and timing, and can ask questions in their own words.
- Assist on site. The technician asks a copilot on a phone or tablet for procedures, wiring diagrams, known issues and similar past jobs, and gets step by step diagnosis grounded in approved documentation.
- Close the loop. Job notes, photos and outcomes are summarised into the ticket automatically and feed back into triage and prediction models.
- Audience
- Employee facing
- Autonomy
- Copilot
- Adoption
- Emerging
- Channels
- Mobile app, SMS, Internal tools
What is it worth?
Benchmarks are computed from the public deployments below: one data point per organization per KPI, with who made each claim.
No public deployment has disclosed a measurable outcome yet.
Value drivers: Lower cost to serve, Employee productivity, Customer experience, Speed and cycle time.
Indicative value
A fixed line operator that dispatches 1 million technician visits a year
USD 2 million to USD 12 million
Technician visit cost avoided per year
How this is calculated
Formula: visits * avoidedShare * costPerVisit. The low scenario uses every low input, the high scenario every high input.
| Input | Low | High | Basis |
|---|---|---|---|
| Technician visits per year visits, visits per year | 1,000,000 | 1,000,000 | The reference operator. |
| Share of visits avoided through remote fixes, better triage and fewer repeat visits avoidedShare, fraction of visits | 0.02 | 0.06 | Editorial assumption. The evidence on this page reports fewer cancellations and better triage but no verified share of visits avoided; replace with your own repeat visit and no fault found rates. |
| Fully loaded cost of a technician visit costPerVisit, USD per visit | 100 | 200 | Editorial assumption. Replace with your own cost per visit. |
What it leaves out: Visit cost only. It leaves out time saved on site, fewer customer contacts about delayed jobs, fewer cancelled orders, and the cost of the platform and device rollout for technicians.
Who already uses it?
2 public deployments, strongest evidence first. Grades: A regulator or audit, B the organization itself, C vendor case study, D anonymous or estimate.
Openreach
United Kingdom · Telecommunications · 2026
When an Openreach engineer finds a problem during a full fibre installation, a prediction tool called Crystal Ball predicts what type of work is likely to be needed and whether it will take more or less than ten days. That prediction drives a clear text message update to the customer, typically within 24 hours. A generative AI capability, Ask Me Anything, lets customers ask questions about their installation in their own words. Both are part of Openreach's work with the CXone Proactive AI Agent platform. Openreach says the tools help prevent more than 3,000 cancelled orders a month.
No outcome disclosed.
nbn
Australia · Telecommunications · 2017
In a 2017 blog post, nbn described a Tech Lab that would use big data and machine learning, including survey data from consenting end users, to improve the experience of its access network. One stated goal was to help teams determine whether a fault can be fixed remotely or needs a field technician to visit; another was to spot trends in failed activations so problems can be anticipated before a technician arrives. The post describes the programme's aims and reports no results.
No outcome disclosed.
How do you implement it?
A model agnostic playbook: what to prepare, the order to build in, and what goes wrong.
Data you need
- Fault and order history with visit outcomes, including no fault found and repeat visits
- Line test and device telemetry results before dispatch
- Job notes and completion codes from technicians
- Current procedures, manuals and wiring diagrams in a searchable form
Systems to integrate
- Workforce management and scheduling
- Fault management and line test systems
- Order management and customer notification channels
- Technician mobile apps
- Knowledge management for field procedures
Complexity: Medium
Triage and job prediction need joined up data from fault, test, workforce and order systems. The copilot for technicians is simpler but only works if manuals and procedures are current and usable offline or on weak coverage.
- 1
Measure wasted visits
Quantify no fault found, repeat and failed visits by fault type. That tells you where triage and prediction will pay back first.
- 2
Start with triage before dispatch
Use tests and history to recommend remote fix or visit, and let dispatchers compare the recommendation with their decision before automating anything.
- 3
Predict jobs that will go wrong
Predict when an installation will need extra work and use the prediction to update customers and plan the follow up early.
- 4
Give technicians a grounded copilot
Put procedures and past job knowledge behind a copilot on the technician's device, with answers that cite the source and work on weak coverage.
- 5
Keep humans in charge of people decisions
Use the models to plan work, not to rank or discipline individual technicians, and consult works councils or unions early.
Guardrails
- Dispatch recommendations are advisory until measured against human decisions
- No automated performance scoring or disciplinary use of technician data
- Copilot answers cite approved procedures and refuse on safety critical steps without a source
- Customer updates generated from predictions are reviewed for tone and accuracy on a sample basis
KPIs to instrument
- Visits avoided through remote resolution, with repeat faults within 14 days counted against them
- First time fix rate and repeat visit rate
- Missed and cancelled appointments
- Time on site per job type
- Technician satisfaction with the copilot
Human in the loop
Dispatchers and team leaders own dispatch decisions and schedules, technicians own the work on site and can overrule the copilot, and safety procedures always follow the official manual. A sample of remote fix decisions is checked each week against later repeat faults.
Common failure modes
- Remote fixes that do not stick
- The model keeps customers off the visit list but the fault returns. Count repeat faults against avoided visits.
- Predictions nobody tells the customer about
- The system knows a job will slip but customers still wait at home. Connect predictions to proactive updates.
- Copilot that fails in the field
- Answers depend on coverage the technician does not have. Design for weak signal and offline use.
- Surveillance by stealth
- Job data starts being used to rate individuals, and trust collapses. Set and publish purpose limits.
What are the risks and rules?
EU AI Act
Depends on design
Triage and a knowledge copilot for technicians are normally minimal risk. Annex III point 4(b) lists AI systems that allocate tasks based on individual behaviour or personal traits, or that monitor and evaluate the performance and behaviour of workers, as high risk, so dispatch systems that do this need the full high risk controls, and under Article 26(7) employers must inform workers' representatives and the affected workers before using them. A conversational assistant that answers customers directly carries the Article 50 duty to tell people they are dealing with AI.
Rules that apply
Guidance
- Annex III, high risk AI systems referred to in Article 6(2) (European Union, Europe). Point 4 covers employment and worker management, including task allocation based on individual behaviour and performance monitoring.
- Article 50, transparency obligations for providers and deployers of certain AI systems (European Union, Europe). AI systems that interact directly with people must be designed so those people know they are dealing with an AI system, unless that is obvious.
- Article 26, obligations of deployers of high risk AI systems (European Union, Europe). Paragraph 7 requires employers to inform workers' representatives and the affected workers before putting a high risk AI system into use at the workplace.
Controls to put in place
- Documented purpose limits for technician data, agreed with employee representatives where required
- Data protection impact assessment for location and job performance data
- Measurement of dispatch recommendations against outcomes before automation
- Review and ownership of field procedures used by the copilot
Frequently asked questions
- Can AI decide whether a technician needs to visit?
- It can recommend it. In 2017 nbn described a machine learning Tech Lab meant to help determine whether a fault can be dealt with remotely or needs a field technician, so its workforce spends time connecting homes rather than attending problems that do not exist. The 2017 post reports no results, so start with dispatchers comparing the recommendation with their own decision.
- What happens when an installation runs into problems?
- Openreach uses a prediction tool, Crystal Ball, to predict what work a delayed installation will need and whether it will take more or less than ten days. That drives a text message update to the customer, typically within 24 hours of the engineer reporting the issue. Openreach says its AI tools help prevent more than 3,000 cancellations a month.
- Is AI dispatch high risk under the EU AI Act?
- It depends on the design. Planning jobs by fault type and location is normally not high risk; allocating work based on individual technicians' behaviour or monitoring their performance falls under Annex III point 4 and is high risk. A chatbot that answers customers must also be designed so they know they are talking to AI, unless that is obvious (Article 50).
How to cite this page
Blits.ai AI Use Case Library, "AI copilot for field technicians and dispatch optimization", last verified 27 September 2026, https://www.blits.ai/ai-use-cases/field-technician-copilot-and-dispatch. Licensed under CC BY 4.0. Method: how we verify use cases.
Changelog
- 27 September 2026: First published