Home-service businesses · Before the estimate

Before the estimate, make the site visit useful.

A site visit should answer a specific question before an estimate is prepared. Keep the customer’s request, the confirmed visit details and the person preparing the estimate connected. A requested day is not a booked visit, and a visit is not approval to begin the work.

By JetSynapse AI · Practical guide · Examples are fictional

Give the visit a job.

“Take a look and send a quote” leaves several decisions open. Does the field person need to measure something, inspect the condition, confirm access or discuss the work the customer wants? Name the question the visit should answer.

Use this guide when a service needs a visit before the business can prepare an estimate. It is not a rule that every inquiry needs an appointment. Your team decides when existing information is enough and when a person needs to see the work.

One request, three different states.

Fictional example: A home-maintenance business receives a request to repair a damaged side gate. The customer asks whether someone can visit on Thursday. Jo handles the first reply, Sam reviews the site, and Lee prepares estimates. These names and events are invented; they are not a client result.

At first, the record says “visit requested.” Jo checks the team’s availability and confirms the appointment with the customer through the business’s agreed process. Only then does the record say “visit confirmed.” After Sam returns usable findings, the next state is “ready for estimate review.”

None of those states means the repair has been sold, started or completed. Keep the meaning plain enough that another team member can explain it without guessing.

Keep a confirmed appointment separate from the work that follows.

Send a short visit-purpose card.

Put the useful facts in the business’s existing approved workspace. A short note can be enough. Do not make the field person search several conversations to learn why they are going.

  • Requested work: review the damaged side gate; other work has not been agreed.
  • Question to answer: what needs repair, and what information does Lee need to price it?
  • Visit state: Thursday is confirmed, or Thursday is still only a preference. State which is true.
  • Current instructions: use the latest customer-confirmed access details in the approved workspace.
  • People: Sam reviews the site; Lee prepares the estimate; Jo keeps the customer informed.
  • Return step: Sam passes the findings and unresolved questions to Lee. A price is not promised yet.

Ask for only the information the next decision needs.

Let new findings change the next step.

Suppose Sam finds that the gate post also needs review. That changes the information Lee needs. Sam records the finding and its source rather than quietly enlarging the promised repair.

Lee decides whether an estimate can be prepared or whether another question needs answering. Jo tells the customer what is actually known. A useful message might be: “The gate review is complete. We also need to check the post before we can confirm the proposed work. Lee is reviewing that next.”

Add a date for the next update only when the responsible person has agreed to it. An automatic reminder cannot make an unresolved technical or pricing decision for the team.

Close the office-to-field loop.

The visit owner passes back the findings, remaining questions and the current scope. The estimate owner acknowledges what they received and identifies anything still missing. “Visited” alone does not tell the office whether a usable estimate can now be prepared.

Once an estimate is sent, use a different routine for revisions, delays, acceptance or an unanswered quote. The next action should follow the customer’s current situation, not keep replaying the pre-visit message.

Choose the next step after an estimate has been sent.

Keep the routine helpful and the decisions human.

An agreed setup can carry the request, visit details, messages and reminders. Your business still checks the work, confirms availability, prepares prices, makes the sale and delivers the service. Inspection, dispatch and field-service requirements need their own review; this example does not promise a complete dispatch system.

Try the handoff with a fictional request first. Ask the office and field person to name the current state and the next responsible person. A clear rehearsal is a useful check, not proof that every future inquiry will work or become a sale.

Sources and limits.

The worked example is fictional. It does not describe a tested client installation or a customer result.

BusinessOS scope and responsibilities explain the starting package. Your written scope decides the page, messages, timings and responsibilities for your business.

Find more customer-path examples for local service businesses or return to Inquiries and bookings.