Operations · Run module
Dispatch runs on a whiteboard and phone calls
The schedule lives on a whiteboard and in one person’s head. How work orders, reasoned priorities and a proposed schedule replace the juggling.
Starts on One module · Run · $350 a month
In your words
We have nine technicians and one whiteboard. Every morning Sylvie writes the day on it from the calls, the emails and what she remembers, then spends the day on the phone moving things around when a job runs long or an emergency comes in.
When Sylvie took a week off in July, two contract customers waited three days for a no-cooling call, and a tech drove to Laval twice because nobody knew he had the part in his van.
Why it happens
Dispatch is a puzzle with many pieces: who has the skill, who is closest, which customer has a contract with a response time, which call is a safety issue, which parts are on which van. A good dispatcher holds all of it in their head, which is exactly why it breaks when they are away.
The information arrives everywhere at once, too: phone, email, texts from techs, a form on the website. A whiteboard shows where people are going, not why, so priorities are rebuilt from memory every morning.
What it costs
Contract customers who wait past their response time start looking elsewhere, and the urgent calls that slip are often the most valuable ones.
Inside the company, the cost is drive time, repeat visits for a missing part and a dispatcher who cannot take a day off. The usual answer is to hire a second dispatcher before anyone has tried to make the first one’s job smaller.
How Humonix fixes it
01Agent
Every job is a work order
Jobs come from a signed quote, an inquiry, a maintenance plan or by hand, each with the customer, the site placed on the map, the equipment and its warranty, the problem, a promised time and the checklist for that job type.
02Agent
A priority with its reasons
Contract and top-tier customers first, then the response-time clock, then the job type (no-cooling and safety calls are urgent), then age. Every point of priority says where it came from.
03Agent
A proposed schedule
Hue proposes slots for the unassigned jobs by skills, territory, response time, working hours and the nearest next stop, with the reason for each. Travel is a straight-line estimate, and the screen says so.
04Agent
On the board, the map and the phone
The dispatch board, the map of the day and each technician’s phone view show the same jobs. Parts are reserved on the job from stock, including a technician’s van.
01Agent
The department
Jobs and dispatch are part of the Run module, in early access and run with Head of Digital. Each job moves new → scheduled → on the way → on site → done → invoiced, and every move is on the ledger.
02Hue
Hue’s part
Hue writes the proposed schedule from rules only, replacing any older proposal, and can tell you which jobs are open, late or ready to invoice.
03You
Your yes
A dispatcher or owner approves or declines each proposed slot. Nothing is assigned, scheduled or texted to a customer before that.
What you see
Approvals: tomorrow’s proposed slots, each with the technician, the reason and the travel estimate, waiting for a yes.
Where to start
One module · Run
One of twelve modules, run end to end by agents; you approve what goes out. No person included. Month to month.
Questions
Do we still need a dispatcher?
Yes, someone decides. The difference is that they approve a proposed schedule with reasons instead of building it from memory, so someone else can do it when they are away.
Does it use real road routing?
Not yet. Travel time is a straight-line distance with a road factor at an average speed, marked as an estimate on screen.
Can technicians use it on their phones?
Yes. Each technician has a phone view of their jobs, with the checklist, photos, parts used and the customer’s sign-off on site.
Can we bring in our existing jobs?
Yes. Jobs can be made from quotes and inquiries already in the app, from maintenance plans, or entered by hand.