ai receipts
Search your own problem
Case study · From the Pluris libraryReceipt no. 5945
What sucked

A regional telecommunications provider was relying on manual dispatch support for field technicians, creating delays whenever technicians needed to check equipment health, validate service information, update work orders, or close jobs.

Dispatchers also had to manually triage newly created work orders against account, equipment, and outage data, which slowed response times and increased the risk of avoidable truck rolls or misrouted work. The organization needed a production-ready AI workflow that could securely connect to operational systems, support technicians in the field, and validate work orders in real time.

TelecommunicationsOperations2–4 months
What they built

An AI field-operations assistant, built on OpenAI's Agents SDK, that lets technicians run their work orders in one chat and automatically triages new work orders against account, equipment, and outage data.

What changed
$1.78/mo in tokens vs $11K/mo saved

In one dispatch use case, the automated workflow costs about $1.78 per month in model tokens against roughly $11,000 per month in salary savings.

30-70% targeted cut in dispatch calls

By automating routing to special-request and callback categories, the solution is designed to reduce technician-to-dispatch calls, with results targeted by end of 2025.

Real-time work-order validation

Newly created work orders can be checked immediately against account, equipment, and outage data, helping teams identify invalid or misrouted work earlier in the service workflow.

Time to results
2–4 months
Company size
251-1,000 people
Who did it
Ekaterina Kouznetsova
Director of Marketing and Engagement, BlueLabel

Vetted by Pluris.