For a small plumbing, roofing or HVAC company, test whether the proposed Zanus workflow captures the job details your dispatcher needs and hands urgent or uncertain requests to a person. Confirm each integration and booking action in your own configuration before relying on it.
Independent buyer guide from Sysevo, a competing provider. We are not affiliated with Zanus AI. This is not a hands-on product review. Vendor sources checked on 1 November 2026; confirm current terms and capabilities directly.
Start with the calls your field team misses
The Zanus Front Office site describes answering and follow-up capabilities, and the vendor’s phone page explains its phone workflow. Those pages do not establish that a particular trade dispatch system, field-service calendar or emergency procedure is included in your quote. Ask for a live demonstration against your actual call types.
List the situations that interrupt a working day: a leaking pipe, a roof inspection request, a heating breakdown, a customer asking for an estimate and a supplier calling back. Rank them by urgency and decide which questions the agent is allowed to ask before a team member takes over.
Capture a usable job request
For each enquiry, identify the minimum useful information: caller name, verified callback number, service address or area, type of work, urgency and access details. Ask the agent to repeat key details so the caller can correct them. Keep the intake short enough for someone calling from a noisy site or while managing a household problem.
Use fictional examples for a job outside your service area, a caller who does not know the equipment model and a customer who changes the address mid-call. Check that uncertainty remains visible instead of becoming a guessed diagnosis or confirmed appointment.
| Scenario | What the owner should verify |
|---|---|
| Emergency or active damage | The urgent route, limits on advice and immediate human escalation |
| Estimate request | Property details, requested work and an assigned estimator |
| Routine service booking | Available capacity and a confirmed versus requested time |
| Out-of-area enquiry | A clear explanation and no false promise of a visit |
| Caller cannot stay on the line | Callback number, summary and named follow-up owner |
Separate a job request from a confirmed booking
A collected preferred time is not automatically a confirmed visit. Confirm which calendar or job system is connected, what availability the workflow can read and whether it can write a booking. If an employee must approve the slot, label it as a request and tell the caller what happens next.
Test a reschedule, a cancelled visit and two requests competing for one slot using an agreed test environment. Inspect the customer record and field team schedule after each call. Ask who receives the alert if the connected system is unavailable or rejects the action.
Build safe escalation around trade work
Set plain limits for what the agent may say about price, safety, diagnosis and arrival times. A call assistant can collect a report and route it; it should not promise a repair result or provide technical instructions outside your approved process. Decide when it should stop asking questions and connect the caller to your on-call person.
Test the transfer when the intended employee is busy or does not answer. Your fallback may be an urgent queue, a clear callback task or a message to the dispatcher. Check that the caller hears an accurate next step and that the staff record includes the urgency and any safety concern they reported.
Check the workflow while the owner is on a job
Run calls during the same hours you are typically on a roof, in a plant room or driving between customers. Afterward, review the job summary from a phone. A useful result makes the next action obvious without requiring you to replay every call or copy details into a separate system.
Track missed calls, complete job requests, confirmed bookings, urgent transfers, callback delay and staff corrections. Compare those outcomes with your current baseline over a representative period. Include the subscription, usage, setup and time spent maintaining the workflow in the business case.
A practical buyer checklist
Before you choose, ask for a written list of supported phone routes, calendars, CRM or field-service connections, included implementation and support. Verify what happens to call recordings and customer information under the agreement. The exact scope depends on the product and configuration offered to your business.
Compare the call flow with Sysevo for trade services, voice agents and plans. Bring five real but anonymised scenarios to a workflow demonstration and ask the person who will own dispatch to judge the saved job record.
Questions buyers ask
Can Zanus AI dispatch a plumber or HVAC technician?
Do not assume a dispatch integration or automatic assignment is included. Ask the vendor to demonstrate the exact system, supported actions and failure route in the configuration you would buy.
Can an AI confirm an emergency service visit?
Only if the approved workflow can verify capacity and your business has authorised that action. Otherwise collect the request, make its status clear and route it to the appropriate person.
What should a small trade business test first?
Test an urgent request, an estimate enquiry and a routine booking while the owner is unavailable. Review the saved record, escalation and caller-facing next step.
