DeyricGet started

Deyric / HVAC

The next service call needs more than a slot on a calendar.

For HVAC owners, service managers and dispatchers coordinating repair calls, maintenance visits and the technicians doing the work.

Deyric engineers software and connected workflows around the people doing this work, with continuing technology services to keep the agreed system useful.

A technician checks diagnostic instruments beside an outdoor air-conditioning unit.

Working demonstration / HVAC

Put the request in the right hands.

Inspect the incoming request. Choose a suitable technician and an available window, then make the dispatch decision yourself.

Dispatch deskService request / DEMO-HVAC-42

Synthetic demonstration. Fictional people and records, local rules and a simulated scheduling service. Nothing is booked, dispatched, saved or sent.

Cooling is not keeping up.

Equipment
AC-04 · split-system cooling
Service history
Previous visit: filter inspection recorded. No diagnosis recorded for this request.
Access
Access arrangements need dispatch confirmation.

The symptom is customer-reported. Dispatch needs a suitable person and a workable window, not an automatic diagnosis.

Who can take this call?

Choose a technician

Rory is already assigned in this window. Choose another window or person.

The commitment stays with you.

Proposed technician
Rory
Proposed window
Today, 14:00–16:00
Suitability
Confirmed in this scenario
Capacity
Not available
Pending your review

Your decision is still open.

Choose the person and window, then review the proposed assignment. Changing a choice clears any previous result.

Follow the request.

  1. Request qualified for reviewDEMO-HVAC-42 carries the reported symptom and equipment record. Access still needs confirmation.
  2. Dispatcher owns the decisionRory · Today, 14:00–16:00. A person reviews the proposed commitment.
  3. No confirmed assignmentA request and a proposed window do not establish an appointment.
  4. Completed work remains unprovenA real trial would reconcile the assignment with the completed visit, revenue and contribution margin. This example ends at the simulated receipt.

What would an engagement deliver?

Inspect the scope, acceptance checks, responsibilities and recovery plan for an illustrative request handoff.

Read the engagement briefTake the one-page brief (PDF)
Inspect the implementation brief

This is the contract behind this local simulation. It is a starting point for an engineering discussion, with no live system connection or measured customer outcome.

Inputs
Reported symptom, equipment and service history, technician suitability, selected window and simulated service response.
Exception
Missing suitability or capacity holds the decision. A scheduling failure returns no receipt. Changing a choice clears the previous result and cancels any pending attempt.
Approval
A dispatcher reviews the assignment and explicitly confirms it. The example does not diagnose equipment or establish safe access.
Measures for a real trial
Track requests reviewed, held decisions, failed attempts, confirmed receipts, time to resolution and completed visits. Agree the baseline, denominator, measurement window and owner before claiming improvement. This example collects no metrics.
Download the simulation contractTrace response through completed, profitable work

A recognizable operating moment

Give dispatch the full picture.

A no-cooling call comes in. One technician is still on a job; another has a maintenance visit. The CSR needs to record the request without promising a slot the dispatch board cannot support.

Give dispatch the job type, service location and equipment context before a person confirms who can attend.

Proposed applications / assessed per engagement

Support the people behind the dispatch board.

Bring the operational gap. We investigate the systems and access involved, then agree what to engineer, validate and support with your team.

From CSR to dispatcher

Prepare a structured service brief: reported issue, service area, contact preference, equipment history where available and the decision still needed. A recorded request is not a confirmed appointment.

Maintenance without losing the agreement context

A proposed coordination workflow could connect an equipment record and agreed maintenance window to an authorized scheduling task. The service manager remains responsible for what the visit requires.

Keep the callback visible

Give a parts delay, return visit or uncertain technician match an owner and a next action, rather than letting it disappear into a free-text note.

Work with the tools you rely on

Your field-service record stays the starting point.

Already working in ServiceTitan or another field-service system? Begin with its job types, customer/equipment records and dispatch permissions. Any proposed connection must use a supported interface and preserve the agreed source of truth.

No ServiceTitan adapter or other FSM integration is connected to these examples. Deyric does not claim vendor partnership or HVAC certification.

Explore the engineering disciplines

Consequential exceptions

The request can wait for a decision. It cannot become a made-up dispatch.

  • No suitable technician or capacity: hold for dispatch review.
  • Missing equipment history: make the gap visible instead of inventing it.
  • Urgent or safety-sensitive report: follow the business’s approved human escalation; this site cannot assess the hazard.
  • Scheduler unavailable: retain the request and report the failure, not a booking.

Built and kept useful

We start by understanding your operating constraint and investigating your existing systems. Engineering, validation and deployment follow an agreed scope. Continuing services define monitoring, maintenance, support hours and human escalation.

Understand the engagement

Questions before you begin

Keep dispatch in control.

Does this replace our dispatcher?

No replacement is assumed. The proposed role is to prepare reliable context and bounded actions around your dispatcher’s decisions. Authority, escalation and acceptance rules are agreed before implementation.

Can you connect to our current field-service software?

We can assess the supported interfaces, account permissions and scope. A named product on this page is workflow context, not evidence of an existing Deyric connector.

Can it handle maintenance agreements as well as repairs?

Maintenance coordination is an engagement possibility. Equipment records, service windows and agreement rules would need investigation. The working example focuses on a service-call dispatch decision.

Will it diagnose equipment or guarantee an arrival time?

No. This website performs no equipment diagnosis or real dispatch. An operational arrival promise would need confirmation from the authorized scheduling process.

Workflow references

Original industry and vendor sources inform these workflow studies. They do not certify Deyric or establish a connection to the named products.

A useful next step for hvac

Bring us the handoff your dispatchers want to improve.

You don’t need a technical specification. Your industry and workflow will carry into the conversation notes, so you can start with what gets in the way. Online submission is temporarily unavailable.

Discuss your dispatch handoffNo account. No mandatory paid audit. Please keep private job evidence out of the initial enquiry.

Find a page, a working example or the next step.

Contact Deyric

Ask Deyric

Contact Deyric