Where Is My Technician? Handling Calls When the ETA Is Unknown

When a caller asks where the technician is, an unanswered ETA is not a reason to invent a time. Confirm that the question concerns an existing visit, identify the correct service request and pass the question to someone who can check the team’s actual schedule.

This is a different conversation from booking a new job. A customer may already have rearranged work or waited at home. Repeating an entire sales intake can make the exchange frustrating, while a confident but unsupported arrival estimate creates another problem for the dispatcher.

Start with the visit already arranged

A useful opening is: “Are you calling about a visit you have already requested?” If the answer is yes, ask for the minimum information the team needs to find that request: the name, callback number and service address.

Treat the information as a lookup request, not proof that an appointment exists. If your organization has not connected the assistant to a verified scheduling source, say that a team member needs to check. Do not tell a caller that a job has disappeared merely because the assistant cannot find it.

Confirm details discreetly. A shared phone number can belong to more than one person, and two customers may have similar names. Avoid reading another customer’s address or job notes to someone who has not been identified appropriately.

Separate three kinds of time information

A requested window is what a customer asked for. A confirmed appointment is what the business has accepted. A current technician ETA is information about when the team expects to arrive now. One does not automatically establish the next.

For example, a caller might say, “I asked for the morning.” That statement should not become “Your technician will be there before noon” unless someone has checked an authoritative source. Record the caller’s expectation accurately and let the team resolve the mismatch.

Use a clear response when the ETA is unknown

Consider this illustrative exchange:

• Caller: “It is nearly lunchtime. Where is the plumber?”
• Assistant: “I can ask the team to check your visit. I do not have a confirmed arrival time.”
• Assistant: “What is the best number for the team to call you back?”
• Handoff note: “Existing-visit question. Caller expected a morning visit; arrival time unconfirmed. Please check the schedule and respond.”

This example describes a communication pattern, not a recording from a customer or proof that a particular integration is enabled. Do not invent a callback deadline to make the response sound complete. If the business has an established callback policy, use the current approved wording.

Give the dispatcher a useful question

A good handoff identifies what needs checking. “Customer called” is less useful than “Customer asks whether the previously requested morning visit is still expected today.” Include the confirmed callback details and the caller’s own stated expectation.

If the caller requests a person, use the organization’s configured handoff path. A transfer attempt and a completed conversation are different events. If the destination is unavailable, explain the actual fallback rather than implying the technician has received a message that nobody has verified.

Test the existing-job path before relying on it

floGPT’s inspected home-service template distinguishes existing-job questions from new bookings and requests to speak with a person. That configuration is a starting point; the business still needs to verify its own sources, routing and fallback behavior.

Test an exact address, an ambiguous address and a caller whose visit cannot be matched. The useful result is an accurate next step, including an honest unresolved question. Explore floGPT for home-service businesses to plan phone and chat intake around your team’s actual workflow.

Original conceptual illustration; not a photograph, actual application screenshot or representation of measured results.