Make arrival status clear

Give the office and customer a clearer view of what is happening before arrival.

ETAFlow combines active-job status, mapped destinations, route-based travel estimates and secure customer links without claiming continuous technician location tracking.

Dispatch and ETAFlow in Serberus
Owner controlRules and results stay visible
01Active-job map and list for administrators02Technician status stepper with call and navigation actions03Google Routes travel estimate with a fallback04Secure public ETA and status links

What is already in the product

The details that make the workflow useful in real operations.

01

See active work together

The office can review active jobs in a list and map without piecing together separate messages.

02

Move through clear statuses

Technicians update the operational step so the office knows whether work is dispatched, underway or complete.

03

Estimate travel time

Google Routes supports travel estimates, with a fallback when the external route result is unavailable.

04

Set an arrival buffer

The owner chooses the latest-arrival buffer used to flag a possible delay.

05

Share status without an account

A secure token link lets the customer check the current status and ETA information prepared for the job.

06

Surface delays for action

Potential delays can be reflected in the operational view and the configured customer communication flow.

How the handoff works

Your rules define the guardrails. Serberus carries the routine work.

Every major workflow answers the same five questions: what starts it, which rules apply, what Serberus completes, when it asks, and where the result remains visible.

01
Trigger

An assigned job approaches its service time and the technician updates its status.

02
Rules

You set the arrival buffer and decide which status notices customers receive.

03
Serberus does

Serberus prepares route-based ETA information, updates the active-job view and maintains the secure status link.

04
When it asks

It asks when a delay or schedule change requires a new customer commitment.

05
Where you see it

See it in ETAFlow, the job status history and the customer's secure tracking page.

HVAC technician servicing an outdoor heat pump at a Quebec home
Residential service

From office to field

The context travels with the work.

The same request, schedule, customer details, photos, notes, status, and next action stay available as work moves from the office to the site.

Real product screen

Built into Serberus, not staged for the website.

This image comes from the current Serberus application. Interface details may evolve, but the workflow shown here is part of the product surface audited for this site.

Dispatch and ETAFlow product screen
Serberus / Dispatch and ETAFlow

Serberus

Put the handoffs somewhere dependable.

Serberus does the heavy lifting, brings the exceptions back to you, and keeps the result visible.

Get started