On this page

A customer calls with your estimate in front of them. They understand most of it, but want to ask about one line before approving the work.
“Does preparation include moving things out of the way, or do I need to arrange that? Can I speak with someone about it?”
They hear that their call is being transferred. Then the phone rings. If nobody answers, does the customer get another option, or does the conversation end there?
A useful customer handoff process covers both possibilities. When someone answers, they need enough information to help. When nobody is available, the customer needs a clear way to leave the question with someone who will handle it. Following the same request through those situations shows where your virtual assistant, phone routing and team need to work together.
When someone answers, start with the customer’s question
Imagine the person responsible for estimates is available. The call reaches them, and they open with:
I have your estimate open. You’re asking whether preparation includes moving things out of the way. Let’s look at what’s covered.
The customer can continue where they left off. They do not have to explain why they called, identify the line again and repeat the question before getting help.
For that opening to work, the employee needs the estimate reference, the customer’s question and anything already explained. They also need access to the estimate itself. A message saying “customer wants to discuss an estimate” gives them less to work with than the actual question.
How that information arrives depends on your setup. A basic phone menu may identify the department the caller selected. A virtual assistant may already have collected the question. Some systems can introduce the caller before connecting them; others deliver a note alongside the call. Ask your provider what your arrangement supports, then check what the receiving employee can actually see when they answer.
If the customer has already asked for a person, keep any further questions brief. An estimate reference may be necessary to find the right record. A new round of general intake usually does little to help that conversation.
The employee may still need to investigate. “I have your question, and I need to check the estimate with the person who prepared it” gives the customer an honest next step. That employee should then own getting the answer or arranging the next conversation.

Give an unanswered call somewhere useful to go
Now follow the same call when the estimating team is busy.
A transfer can ring without anyone picking up. Decide what happens at that point, including how long the customer waits and what alternative they receive. Repeatedly sending them through the same unanswered route leaves them doing the work of trying to reach you.
Your fallback might be voicemail, a callback request or another available person. Choose an option your system supports and your team can manage. Some setups can return a caller to an assistant; others need a voicemail or phone-system rule configured before the transfer begins.
Where the assistant can continue the conversation, it could say:
I couldn’t reach the estimating team just now. Would you like them to call you about the preparation line on your estimate?
If the customer agrees, confirm the callback number and any preference you still need. Once the request has reached the team’s callback list, a confirmation could say:
Your callback request is with the estimating team, including your question about what preparation covers.
The wording should match what happened. A request waiting for review should be described that way. Give a callback time when your team can meet it. If working hours affect the next step, explain them accurately.
Your website should set the same expectation. Our six-question website checklist includes explaining what happens after someone contacts you, so the website and the conversation can describe the same process.
Behind that confirmation, someone needs to be responsible for the request. Decide who checks the callback list, when they check it and who covers their absence. The person calling back should be able to review the estimate and the question before contacting the customer.
A saved request is useful when it leads to that follow-through. Check the receiving side as carefully as the message the caller hears.
Pass on questions that need knowledge of the job
The customer might then ask:
If moving things isn’t included, can you add it and let me know what that changes?
An assistant may be able to explain a general service policy from information your business has approved. Whether a particular estimate includes that work, and what adding it would change, may need someone familiar with the job and authorized to revise the estimate.
Where that decision belongs with the estimator, the assistant could reply:
I’ll include that for the estimator too: whether moving things is covered, and what would change if it needs to be added. They can review it with you before you approve the work.
That reply keeps the question intact and moves it toward someone who can answer it. It does not agree to extra work or invent a price.
When the estimator responds, they should explain what is covered, whether a change is needed and what the customer would be approving. Our article on helping customers understand what they’re saying yes to explains how to put the scope and reasoning beside that decision.
Keep the assistant’s role clear as your process changes. If your services, staff responsibilities or approval rules change, review the answers and routing that depend on them.

Give the next person a note they can use
For the unanswered call, a short receiving note could look like this:
| Detail | What the estimator receives |
|---|---|
| Request | Customer wants to discuss the preparation line on their existing estimate; include the reference collected during the call. |
| Question | Does preparation include moving things out of the way? If it needs to be added, what would change? |
| Already explained | The estimating team was unavailable. The customer agreed to a callback. No scope or price change has been agreed. |
| Next action | Estimator reviews the scope and calls the customer to explain the answer and any proposed change. |
| Contact | Confirmed callback number and any preference the customer supplied. |
| Status | Callback requested; conversation still outstanding. |
Keep this information where the person doing the follow-up works. If it is collected in one system but unavailable to the employee returning the call, address that gap with your team or provider.
The customer may also call again and reach someone else. If that colleague answers the question, update the open request with what was discussed and anything still unresolved. That keeps another employee from calling later as though the conversation never happened.
Try three situations with your team
Use a sample estimate and arrange the check with the people involved. Have someone take the customer’s role while another person follows what reaches the receiving team.
| Situation | Check the customer’s experience | Check the team’s side |
|---|---|---|
| The right person is available | Can the customer reach them and continue with the estimate question? | Does the employee have the question and the estimate needed to help? |
| Nobody answers | Does the customer receive a workable alternative and an accurate explanation of what follows? | Does the request reach an owner who can see it and act on it? |
| The question needs a job-specific decision | Is the question passed on without an unsupported answer or an unauthorized change? | Can the responsible person review the job, explain the answer and record the outcome? |
Follow the unanswered-call check through the return conversation. Seeing a request appear on a list proves it arrived there. Watching the responsible person receive it, contact the customer and update the outcome shows how the rest of the process works.
Use what you observe to decide what needs attention. If the employee has to ask the customer to start over, check what information arrived and whether it was accessible. If nobody sees the request, check its destination and ownership. If the call ends unexpectedly, have your provider trace the unanswered-transfer behavior.
Address the related gaps you find, then repeat the affected situation. Review it again when staffing, hours or routing changes. The goal is a customer who gets an answer or knows how their question will be handled, with a team prepared to follow through.
