The call becomes a job assigned to someone who accepted it — not a note you find on the dash at nine at night.
7 days, 20 answered calls, no card
The call does not wait until you are free. It comes in while you are under a sink, in a crawl space or behind the wheel. And the question right after is the same one every time: who goes, when, and does that person know about it yet?
This add-on turns a qualified request into an assigned job. It weighs the service area, the skill or the equipment the work needs, who is genuinely free, and the priority you set between an emergency, a contract visit and a project. Then it offers the job to a technician and waits for an answer: a proposed assignment is not a confirmed job.
When the day shifts — a backed-up drain that jumps the queue, a technician held up two more hours on a site — it reschedules what can move, escalates what cannot wait, and keeps the completion report: work done, parts installed, next step.
Address and postal code, fixture or line involved, water running or not, building access, who authorizes the charges: your base asks all of it during the call. Dispatch therefore starts from answers, not from a callback you owe someone by suppertime.
It matches the request against real capacity: who covers that area, who holds the licence or carries the right tool, who is open in the window asked for. Between two requests of equal weight, it is the priority rule you configured that decides, not a hunch.
The technician receives the job offer and accepts or declines it. Until someone accepts, the request sits in a visible queue and the caller has a requested window, not a confirmed visit. That distinction is what prevents an angry callback the next morning.
Work performed, parts, time on site, next step: the report attaches to the same request. A warranty return reads differently from a new job, and the history of that address shows it on the following call.
The Trades and maintenance base answers, qualifies and sends you the request with a clear next step. It assigns nobody. Dispatch is added on purpose, over the jobs of one crew, within that crew's operating capacity.
If you take the Contracts and recurring service add-on, it already covers dispatch for work performed under those contracts: the same job is not counted twice. Dispatch keeps its place alongside it, for one-off work outside any contract.
Water running, no heat in deep cold, a system fully down: the request is flagged urgent and looks for the on-call technician in the rotation. A smell of gas follows the preset's safety instruction instead, and does not become a job to assign.
Customer account, site, declared skill, authorized shutdown window, technician acceptance: these are the criteria your dispatcher already applies. The final call stays with that person when two emergencies land at once.
Routes by area, the trigger threshold you configured, gate access and time-of-day restrictions. The last confirmed pass stays on file, which answers the customer calling in to ask whether their property was serviced.
The technician accepts or declines, and nobody is sent to a customer without that acceptance. Until it is given, the caller does not hear that a truck is on the way.
The add-on carries its own monthly allowance, separate from the calls in the base.
Any third-party fees — message transport from an outside carrier, the subscription to a field-service tool you already run — are separate and billed by that provider.
The status shown is technical qualification, not a sales claim. With no qualified software, the job lives in Zenvox and nothing is blocked.
No. The job is offered to the technician, who accepts or declines it. Until someone accepts, the request sits in a visible queue and the caller has a requested window, not a confirmed visit.
On your real capacity: who covers that area, who holds the licence or carries the right tool, who is open in the window asked for. Between two requests of equal weight, the priority rule you configured decides, not a hunch.
No. A smell of gas follows the preset's safety instruction and does not become a job to assign. Emergencies that stay jobs — water running, no heat in deep cold, a system fully down — look for the on-call technician in the rotation.
No. The Contracts and recurring service add-on already covers dispatch for work performed under those contracts, and the same job is not counted twice. Dispatch keeps its place alongside it, for one-off work outside any contract.
One hundred coordinated jobs per month, reset at each period, over one crew and its operating capacity. Calls stay metered on the base, separately from this add-on.
Go back to your trade, or look at the add-on that covers maintenance contracts.
Dispatch and field work
