For a contractor, estimate follow-up starts with a homeowner who already requested a quote. A useful Zanus AI Auto Call brief asks whether that specific estimate needs a decision, clarification or revision. It should not treat the whole customer list as a new cold-calling audience.

Build the list from open estimates

Prepare the estimate reference, property, named customer, responsible estimator and latest revision. Remove jobs already accepted, declined or withdrawn. If the office cannot explain why someone belongs on the list, resolve that before scheduling a call.

Keep a reason for contacting the person and apply the calling rules appropriate to the business and recipient. A record in a CRM is not, by itself, permission for every kind of automated outreach. This article describes an operational test rather than a legal clearance for a campaign.

Give the agent a small, useful brief

For an illustrative replacement enquiry, the purpose could be: ask whether the customer wants the estimator to explain the existing proposal. Supply the correct estimate identifier and approved contact options. Do not let the agent invent a discount, installation date or revised scope.

Distinguish a question from an acceptance. “Can someone explain the warranty?” needs a knowledgeable callback. “We are proceeding” needs the office’s actual acceptance process. Neither should silently become a completed installation booking.

Route responses into separate queues

ResponseNext owner
Question about the proposalEstimator with the latest revision
Different work requestedScope review before a new price
No longer interestedOffice to close the enquiry
Wrong person or propertyRecord correction before further contact

Test an accepted estimate before the next retry

In a controlled trial, mark a sample estimate accepted after the first unanswered attempt. Check whether the remaining follow-up still runs and who can stop it. Ask the supplier how order lists are refreshed when the source CRM changes; do not assume a list remains synchronised after it is created.

Also test a customer who asks to speak tomorrow. Staff need the requested time and an assigned task, while the calling list needs the correct disposition. An answer that exists only in a transcript is easy to overlook.

Measure decisions the office can use

Track estimates clarified, requested revisions assigned and obsolete records removed. Count incorrect quote references and extra calls separately. Compare staff review time with the manual process using the same small set of enquiries. Answer rate alone cannot tell you whether the follow-up helped the estimator progress real work.

Official documentation and related reading

Explore the relevant Sysevo product, Voice Agents and CRM. Compare Sysevo plans and pricing or book a demo using the same requirements.

Reviewed 3 November 2026. Independent Sysevo editorial guide using the linked official documentation. Scenarios are proposed evaluation steps, not reported customer results or a hands-on vendor benchmark. Sysevo sells its own business software; availability and deployment requirements need confirmation.

Qualifying the Open-Estimate List Before Any Call Is Placed

The list that feeds an automated follow-up campaign is a working document, not a static export. Before a single call is scheduled, the office should be able to answer four questions for every record: who requested the estimate, which property it covers, which estimator produced the current revision, and what the last known status of the enquiry was. A record that cannot answer all four questions cleanly is a candidate for manual review, not automated outreach.

That distinction matters because automated calling amplifies list quality problems. A phone call placed to the wrong person, or to someone whose estimate was already verbally accepted at a site visit, creates confusion that is harder to recover from than a missed manual follow-up would be. Staff who prepare the list should treat each record as if they were about to make the call themselves. The question is whether they would feel confident explaining to that homeowner exactly why the call is happening.

A useful pre-campaign checklist might include confirming that the customer name on the estimate matches the contact record, that no subsequent enquiry has superseded the open estimate, that the estimator named on the record is still available to take a callback, and that the quoted scope has not been informally revised in a site visit note that was never entered into the system. Each of these is a separate verification step because each can fail independently.

Some offices find it helpful to apply a brief ageing review before building the final call list. An estimate that has been open for a long time may have an informal history that the system does not reflect. The right response to an aged record is usually a quick estimator check rather than an immediate automated call. This is not a system configuration question; it is an office workflow question that should be answered before the campaign runs.

Designing the Agent Brief for Each Estimate Category

A contractor's estimate portfolio is not uniform. A roofing replacement, a boiler service contract, and a kitchen refit each involve different decision timelines, different numbers of stakeholders, and different kinds of follow-up question. An agent brief that works well for a straightforward single-trade repair may be inadequate for a multi-phase project where the homeowner is waiting on a council decision or a mortgage release.

When drafting the brief, consider sorting estimates into two or three broad categories and writing a separate purpose statement for each. For a simple single-trade estimate, the purpose might be to offer the estimator's availability for a short call to answer any remaining questions. For a more complex project estimate, the purpose might be narrower still: to confirm whether the homeowner has had a chance to review the written scope and identify which section, if any, they would like discussed. Neither purpose should include any invitation for the agent to negotiate, adjust pricing, or commit to a start date.

The brief should also specify what the agent is not authorised to confirm. This is as important as specifying what the agent should say. If an estimator has informally indicated a possible discount subject to a specific condition, that condition and any figure attached to it should not appear in an automated call unless it has been formally incorporated into the estimate revision on file. The gap between what a salesperson said in a conversation and what appears in the written estimate is a frequent source of disputes, and an automated call that repeats an informal figure without context can make that gap worse.

For illustrative purposes, consider a fictional scenario: a homeowner who received a bathroom refurbishment estimate and who has not responded in several days. An appropriate brief might instruct the agent to introduce itself, reference the estimate by job identifier rather than a full quoted amount, ask whether the homeowner has any questions about the scope or materials described, and offer to arrange a callback with the named estimator at a convenient time. The agent should not confirm that the trade team is available on a particular date, because the office scheduling system has not been queried at the point the call is placed.

Handling the Response When the Homeowner Is Not the Decision-Maker

In residential contracting, the person who requested the estimate is not always the person who will authorise the work. A homeowner may have a spouse, a landlord, a managing agent, or a family member whose agreement is needed before a decision can be made. An automated follow-up call that treats the initial contact as the sole decision-maker can either create premature pressure or produce an apparent acceptance that later unravels.

When designing the response routing described in this guide, it is worth adding a category for responses that indicate a third-party decision-maker is involved. The appropriate next action in those cases is usually to log the information, assign it to the estimator, and allow the estimator to make a human judgement about whether to wait, send additional written information, or arrange a joint call. An automated system should not attempt to navigate a multi-party household decision, because the variables involved—who has authority, what timeline they are working to, what their concerns are—are not available to the system.

Staff handling these routed records need a clear brief of their own. The record should show that a third party is involved, what the contact said about that person's role, and whether any specific information was requested for them. A note that reads only "speaking to husband" is not actionable. A note that reads "homeowner will discuss with partner and would like a written summary of the materials warranty to share with them" is actionable and can be used by the estimator to send a targeted follow-up document rather than making a second speculative call.

Worked Scenario: From Automated Call to Accepted Estimate

To illustrate how a well-designed process might flow, consider a fictional sequence for a heating installation estimate. The office builds a list of open estimates that have not received a response within a defined review window. A record for a fictional homeowner, listed as the property contact for a terraced house, shows an estimate for a full heating system replacement. The estimator is noted on the record. No follow-up has been logged since the estimate was sent.

The automated call connects and the agent identifies itself as calling on behalf of the contracting business regarding the heating estimate on file. It asks whether the homeowner has had a chance to review the proposal and whether there are any questions the estimator could help with. The homeowner says they have one question about the type of controls included and would like a callback from someone who can explain the options. They confirm that the timing is otherwise suitable.

The system records the response as a callback request with a subject note about controls. The estimator receives a task with the homeowner's name, the property address, the estimate reference, and the summary of the query. The estimate remains in open status. The estimator calls the following morning, answers the controls question, and the homeowner confirms they would like to proceed.

At that point the acceptance process is a human-to-human exchange. The estimator does not verbally confirm a start date without checking the schedule. The homeowner is told the next step is a written confirmation from the office and a deposit arrangement as per the estimate terms. The office updates the estimate status to accepted, removes the record from the open-estimate call list, and creates a job record. The automated system does not receive any instruction to call again.

This sequence works because each handover is defined. The automated call has a narrow purpose, the response is routed to a named person, the person has enough information to act, and the acceptance is completed by a human who controls the next commitment. None of those steps can substitute for another.

Exception Handling for Calls That Go Wrong

Not every call will proceed cleanly, and the exception cases are where process design matters most. Consider a few scenarios that the office should plan for explicitly before the campaign runs.

A homeowner answers the call and immediately says they did not request an estimate and do not know who the contractor is. This suggests either a list error or a situation where the estimate was requested by someone else at the property without the current contact's knowledge. The appropriate response is to apologise, end the call, flag the record for manual review, and not schedule a retry until the list error is resolved. Staff reviewing the flagged record should attempt to verify the original request source and, if necessary, contact the business owner or property manager rather than the individual who answered.

A homeowner answers, says they accepted the estimate verbally with the estimator last week, and asks when the work is starting. This means the CRM was not updated after the verbal acceptance. The call should not have been placed. The right staff response is to apologise for the confusion, confirm the acceptance is noted, and transfer the enquiry to whoever manages scheduling. The record should be audited to understand why the status was not updated, because the same gap will recur if it is not addressed.

A homeowner answers and says they have already received several calls about this and are finding it intrusive. This may indicate a retry logic problem, a duplicate record, or a manual call that was not logged. The record should be suppressed from further automated outreach immediately. The estimator should make a personal call to acknowledge the inconvenience and confirm the correct status of the enquiry. The incident should be reviewed against the retry settings and the logging records to find the source of the duplication.

Each of these exceptions has a different root cause and a different resolution path. Treating them all as a single category called "call errors" makes it harder to identify whether the problem is in list preparation, system configuration, estimator note-taking, or retry logic. Maintaining a short exception log that records what happened and which part of the process was responsible will help the office improve the next campaign more precisely than a general review would.

Evaluating Whether the Process Is Serving the Estimator

The final measure of a follow-up process is whether it helps the estimator convert more proposals into confirmed work without creating additional administrative burden. That is a harder thing to assess than a call answer rate, but it is the right question to ask.

A practical evaluation might start with a small pilot involving a defined subset of open estimates. After the campaign runs, the estimator should be able to answer: did the callbacks they received contain enough information to be useful, did they receive callbacks they were not expecting because the routing was unclear, and did any accepted estimates appear on the call list after they had already been verbally confirmed? Each of those answers points to a specific part of the process that may need adjustment.

The office manager's perspective is different. They should be asking whether staff time spent reviewing call dispositions and assigning callback tasks is proportionate to the number of estimates that progressed as a result. If the follow-up process is generating a large volume of disposition records but a small number of estimator callbacks that result in revised or accepted estimates, the brief or the list selection criteria may need refinement.

It is also worth asking whether the estimates that did not respond to the automated call would have responded to a personal call from the estimator. For some homeowners, an automated call from a contractor's business is not an effective prompt for a decision. For others, it is sufficient. The office should not assume that an absence of response means the homeowner is uninterested; it may mean the channel was wrong for that contact. A brief manual review of non-responding records, conducted by the estimator, may recover some of those enquiries that the automated process did not reach.

When the pilot is complete, the most useful output is not a summary statistic but a short set of specific improvements: a revised agent brief, an updated list preparation step, a clearer routing rule, or a better template for the callback task. Those changes can be tested in the next cycle and refined again. A follow-up process that improves incrementally through specific operational changes will serve the contracting business better than one that is set up once and left unchanged.