For contractors, the business number is often printed on vans, invoices and directory listings. A Zanus AI phone evaluation should protect that route to the office. Confirm how calls reach the assistant, how staff receive transfers and how to restore the previous setup if the pilot has problems.

Map the number before changing it

List the public number, its carrier, any existing forwarding rules, the office destinations and the voicemail fallback. Record whether calls already go through a business phone system. Ask the vendor and carrier which forwarding or number-transfer arrangements apply to your exact setup.

Keep a written copy of the original configuration. Avoid making a permanent number move just to answer the first evaluation call. Choose a test arrangement you can reverse and confirm who is authorised to make carrier changes.

Route by the work staff must do

Draw separate routes for new enquiries, existing jobs and supplier calls. Give each route an owner and an unanswered-call fallback. Test whether staff receive the caller’s reason and relevant job context before they accept a transfer.

CheckExpected evidence
Public line forwardingA call reaches the intended entry point
Office transferThe correct destination rings and can accept
Caller identityStaff can return a missed call using the saved number
Unanswered transferThe caller reaches a defined fallback

Look for loops and conflicting voicemail

Call the public number while the office destination forwards unanswered calls back to the same entry point. This exposes a possible routing loop. Also check whether carrier voicemail answers before the transfer fallback can run.

Test from a mobile and another network. Include a busy office line, a caller who hangs up during transfer and an office user who declines the call. Inspect both sides of the handoff; a transfer event in a log does not prove that two people connected.

Keep a practical rollback plan

Name the person who can restore the original carrier settings, the circumstances that trigger rollback and the way staff will be notified. Test that procedure during office hours while the people responsible are available.

During the pilot, monitor completed transfers, abandoned transfers, voicemail collisions and missed callback details. Expand after the routing works consistently and the team knows how to recover. Number continuity is part of customer service, not simply a telecommunications setup task.

Questions and answers

Do I need to port the main business number to run a trial?

Ask the vendor and your carrier which forwarding or test-number options are available. Confirm the arrangement for your existing phone system before changing the live line.

Structuring Call Ownership Before the Pilot Begins

Before any forwarding rule is touched, a contracting business benefits from assigning a named owner to every type of incoming call it expects to receive. Ownership here means a specific person or role that is accountable for a call being answered, recorded and acted upon — not simply the person who happens to pick up. Without that assignment, evaluation results become ambiguous: if a transfer goes unanswered, no one knows whether the routing failed or the responsible staff member was unavailable.

A practical way to establish this is to list every call category the business actually receives during a normal working week. For a trade contractor, those categories might include first-contact enquiries from homeowners, callbacks on open quotes, progress updates from site crews, parts queries from suppliers, and warranty or complaint calls from previous customers. Each category carries a different urgency, requires different information at the point of answer, and may have a different acceptable fallback when the primary owner is unavailable.

Once the list exists, a simple ownership grid can be drafted. Columns identify the call type, the primary owner, the secondary owner, the fallback action when neither is available, and the information the answering person needs before they can usefully respond. That last column matters most for an AI phone evaluation, because it forces a concrete answer to the question: what should the routing system hand to a staff member at the moment of transfer? A crew scheduling call needs the job reference and site address. A new enquiry call needs the caller's contact details and the work type they described. A supplier call about a delivery may need nothing more than the supplier's name.

Producing this grid before configuring any routing reveals gaps that technology cannot fill. If no one is designated to handle supplier calls after midday, an AI routing layer cannot resolve that problem. Identifying it in advance means the business can decide on a deliberate fallback — voicemail to a shared inbox, a redirect to a site supervisor's mobile — rather than discovering the gap when a time-sensitive delivery is delayed.

Designing a Fictional Enquiry Walk-Through to Test the Full Route

A useful acceptance exercise for the pilot period is to construct a fictional inbound enquiry and walk it through the entire system from first ring to completed action. The purpose is to generate observable evidence at each stage, rather than relying on a summary log entry that says a call was handled.

Consider a scenario where a homeowner calls the business's advertised number to ask about a boiler replacement. They have found the number on a van they saw parked in their street. They do not know the business's name with certainty. They call during a period when the office coordinator is on another call.

At each stage of that journey, a reviewer can ask specific questions with observable answers. Does the caller reach a prompt quickly, or do they encounter silence? If the system asks for information, does the question make sense for a homeowner who may not know trade terminology? When the coordinator becomes available, does the transfer carry through the caller's stated reason for calling and their contact number? If the coordinator is still unavailable when the transfer attempt is made, does the caller reach a fallback that gives them a genuine path to a callback, or does the call end without any record?

Walking this fictional scenario during office hours, with the relevant staff present and the reviewer observing both the system log and the staff member's screen or phone simultaneously, surfaces discrepancies that log-only reviews miss. A transfer event appearing in a system record does not confirm that the staff member heard a clear caller summary before accepting. Asking the staff member, immediately after the test call, what information they had before they picked up is the most direct check available.

Vary the scenario across at least three conditions: a call answered on the first attempt, a call where the primary owner is unavailable, and a call where the caller ends the interaction partway through. Each condition may produce different evidence about routing behaviour, and all three are realistic for a trade contractor's working day.

Distinguishing Caller Identity from Request Content and Responsibility

A routing evaluation for a contractor should treat three separate things as distinct: who is calling, what they are asking for, and who within the business holds responsibility for the outcome. Conflating these creates practical problems that become visible only when something goes wrong.

Caller identity matters for callback purposes. If a caller's number is saved against the record of their enquiry, a staff member can return a missed call without asking the caller to explain their situation again. That is a customer service outcome, not a technical feature. The evaluation question is whether the business can retrieve a caller's number from whatever record the system creates, and whether the person retrieving it has access to enough context to make the callback useful.

Request content matters for routing accuracy. A caller asking about a new installation and a caller asking about a fault on existing work may sound similar in the first few seconds. The information needed to help them and the staff member best placed to respond may be different. If the routing system categorises requests before transfer, the evaluation should check whether that categorisation reflects the actual distinctions the business makes in its work, not just broad labels.

Responsibility matters for accountability. When a call results in a commitment — a site visit booked, a quote promised, an emergency response indicated — the business needs to know which staff member holds that commitment. A routing log that records a call as completed does not identify who made the commitment or what it was. The evaluation should confirm that the handoff between the routing layer and the staff member produces a record sufficient to attribute responsibility and follow up on it.

These three things — identity, content and responsibility — should each have a home in whatever record the system produces. Checking for all three, rather than only whether the call connected, gives a more useful evaluation result.

Handling Exception Cases That Arise in Trade Contracting Specifically

Trade contracting businesses receive calls that do not fit standard enquiry categories, and a routing evaluation should include at least a few of these exception cases rather than testing only the ideal path.

A caller may phone to report an urgent situation — a leak discovered after a recent installation, a heating system that has stopped working in cold weather, a gas smell near work that was carried out. These calls require human judgement about urgency and may require action that falls outside normal office hours. The routing evaluation should ask explicitly: what happens when a caller indicates urgency? Does the system provide a path to a human, and how quickly? This is not a question about a specific vendor capability; it is a question about what the business has configured and whether that configuration reflects the reality of trade work. Human professional judgement must remain in the chain for any call that could involve safety.

A caller may be a previous customer calling about work that carries an implied or explicit warranty. They may be dissatisfied. The staff member who needs to handle that call may not be the same person who handles new enquiries. If the routing system does not distinguish this call type, it may transfer the caller to someone who lacks the context to respond appropriately, creating a worse customer experience than a simple voicemail would have.

A caller may be a supplier or subcontractor who knows the business well and expects to reach a specific person by name. If the routing system treats this call identically to a new enquiry, it may create friction for a relationship that the business values. The evaluation should consider whether the business wants to distinguish known callers from unknown ones, and if so, how that distinction would be made and maintained.

Testing exception cases during evaluation does not require exotic scenarios. Each of the above happens in ordinary contracting operations. Deciding in advance how each should be handled — and then verifying that the configuration produces that outcome — is more useful than testing only the smooth path.

Criteria for Comparing Routing Arrangements Before Committing

When a contractor is choosing between routing arrangements — whether that involves evaluating an AI phone layer, a traditional answering service, or a reconfigured internal phone system — several criteria are worth examining with specific reasons attached to each.

Reversibility matters because a business phone number is an existing asset with established associations. Any arrangement that cannot be undone without disruption to that number carries more risk than one that can be tested in parallel. The question to ask is not whether rollback is theoretically possible but whether the person responsible for executing it can do so within a timeframe that limits customer impact.

Context at handoff matters because the value of any routing system to a trade contractor is measured at the moment a staff member accepts a transfer or reviews a missed call record. A system that records a call occurred but does not provide the staff member with the caller's reason for calling and a way to reach them back has limited operational value, regardless of how the call was initially handled.

Staff readiness matters because a routing configuration that staff do not understand or trust will be worked around. If coordinators begin giving out a direct mobile number to avoid the routing system, the evaluation has failed even if the system itself functioned correctly. During the pilot, observe whether staff are using the system as intended or developing informal bypasses, and ask them directly whether the information they receive at transfer is sufficient for their work.

Fallback clarity matters because trade contractors often work across sites, meaning office staff availability varies in ways that are difficult to predict. A routing arrangement whose fallback is simply an unanswered call is not adequate for a business where a missed enquiry has a direct commercial consequence. The fallback should be a deliberate decision — voicemail to a specific inbox, redirect to a mobile, a message promising a callback window — not an accidental outcome of an unanswered transfer.

Practical Handover Arrangements When Staff Change During a Pilot

A routing pilot that runs across several weeks is likely to encounter staff absence, role changes or shifts in who covers the office. These are normal operational events, but they expose gaps in how routing ownership was assigned at the start. A business that documented call ownership in the grid described earlier will find handover straightforward; one that did not will find that call handling quality drops when a specific person is absent, making it difficult to distinguish a routing problem from a staffing gap.

A practical handover arrangement for the pilot period should include a written description of each routing rule — not a technical specification, but a plain description of what happens when a specific call type arrives and who is expected to act. This document should be accessible to anyone covering the office, not stored only with the person who set up the system. When a covering staff member handles a transferred call, they should have enough context from that document to understand what record to create and where to log the outcome.

The pilot review should include a check of calls handled by covering staff versus calls handled by the primary owner, not to compare performance but to identify whether the routing and handoff information was sufficient for someone without background knowledge of a specific job or customer. If covering staff consistently found the information provided at transfer insufficient, that is evidence about the routing configuration, not about the covering staff's capability.

At the end of the pilot period, whatever arrangement has been established should be documented in a form that survives individual staff changes. A routing configuration that depends on one person's memory of why it was set up that way is fragile. The documentation does not need to be complex: a one-page summary of what number is in use, where calls go at each stage, who holds ownership of each call type, and how to initiate rollback if needed is sufficient for most contracting businesses and means the pilot's work retains value beyond the evaluation period itself.

Sources and next steps

This is an independent Sysevo planning guide, not a report of a hands-on Zanus AI test. Use the official Zanus AI Front Office overview to confirm current product scope and request a demonstration of the workflow described here. The scenarios and acceptance criteria above are proposed evaluation steps.

For the broader topic, read Zanus AI for home services. If you are comparing providers, explore Sysevo phone numbers and routing and request a Sysevo demo using the same scenarios. Sysevo publishes this guide and offers its own business software.

Related workflow guides

For current Sysevo subscriptions and usage options, compare plans and pricing.