Utilities contractors, HVAC & facilities
Confirm the appointment. Free the dispatcher.
Field work is scheduled by phone and derailed by phone. Confirmations, running-late calls and rebookings consume the dispatcher who is also supposed to be optimising the run.
An illustrative reference architecture, not a customer
case study. No organisation is named and no deployment is described - this is
what the layers look like for a field services & trades organisation,
so you can map it onto your own estate.
Channelswhere the conversation starts
Inbound numberspublished lines
SIP / contact centreexisting estate
Outboundcampaigns and callbacks
In-appbrowser WebRTC
▼
VoiceKernelthe agentic voice layer
Conversationagent, voice, turn taking
Knowledge groundinganswers with citations
Tool callsreads and writes back
Transferto a human, with context
Tenant isolationownership registry
Audit and erasureper call, per mutation
▼
Integrationyour boundary, your rules
REST + typed SDKscoped API keys
Signed webhooksretried, replayable
Live event streamSSE
▼
Field Services & Tradesyour systems of record
Field service managementjobs, technicians, routes
Schedulingwindows and capacity
Asset / equipmentservice history
Parts inventoryavailability for the job
CRM / billingaccounts and quotes
Only the bottom layer is specific to field services & trades. The
three above it are identical in every deployment, which is the point: the
voice layer does not need to know what industry it is in, only which systems
it is allowed to reach and what it may say.
What it changes
Mechanisms, not projections. Each of these follows from something structural
about the work, so you can check whether it holds for your own queues.
Wasted truck rolls fallNo-access is the most common failure and the most preventable by asking the day before.
Dispatchers stop being a phone queueRoute optimisation is a planning job that cannot be done while answering calls.
Customers hear about delays before they complainThe running-late call is the one nobody has time to make, and the one that decides satisfaction.
Emergency triage is consistentUrgency assessed against your rules rather than the tone of the caller.
What the agent actually does
Appointment confirmationOutbound the day before, confirm access, and rebook in the same call if nobody will be there.
Running-late notificationCall the next customers when a job overruns, with a real revised window from the route.
Job booking and triageTake the fault description, decide urgency and required skill, and book the right technician.
What keeps it deployable
Access and safety notes capturedRecorded against the job so the technician arrives informed.
Emergency escalationGas, electrical and water emergencies transfer immediately, with no attempt to triage further.
Site data minimisedThe agent reads what the job needs and nothing else.
A no-access visit costs the travel, the slot and the rebooking, and is usually preventable with one call the night before.
NextRead the source
Everything above is in the open-source Community edition. Nothing on
this page needs a licence.
NextRun it yourself
Point it at your provider account and put one queue through it before
you talk to anybody.
NextThen buy the guarantees
An Enterprise agreement adds the SLA and the
support contract when it carries real volume.