What Should Happen After Someone Requests a Quote?

By Paul Foster

A quote request should become an assigned next action, not another message someone hopes to remember. Record the request, check what is missing, put one person in charge, and tell the customer what happens next. You can begin with a shared spreadsheet and a controlled inbox if those fit your team.

The important distinction is between receiving an inquiry and handling it. A form submission proves that information arrived. It does not prove that someone read it, that you can do the work, or that the customer received a useful answer.

1. Put the request somewhere the responsible people can find it

Choose one working record for each inquiry. Record the business or customer name, the service requested, the date received, the assigned person, the current status and the next action. Keep only the information the work requires. Do not collect payment-card details or unnecessary personal information in a general inquiry form.

If inquiries arrive through several channels, decide who records phone calls and messages. The system will not be complete if website requests are organized but the owner’s text messages remain invisible to everyone else.

2. Check whether you have enough information

Do not rush from “interested” to “quoted” when the scope is unclear. Separate a question you can answer now from a request that needs a conversation, photographs or a visit. Ask for the smallest amount of additional information that allows the next decision.

For example, a cleaning inquiry might describe the location, type of space, desired frequency and preferred time for a walkthrough. It should not imply that a price is final before the actual scope is understood. A plumbing inquiry may need a human decision about whether the request belongs in the planned-work process at all.

3. Assign one owner, even when several people help

“The team will handle it” is not an assignment. Name one person responsible for the next action and give that person a way to acknowledge it. The estimator might prepare the scope while the office coordinator owns scheduling. A handoff is complete when the receiving person knows what to do, not merely when someone forwarded an email.

Choose a backup for absences. This can be a simple written rule: when the assigned coordinator is away, the office manager reviews new requests at the start of the workday. Use a response commitment your actual staffing can support.

4. Make the next step specific

Useful next actions have a verb and a date: “Call to confirm walkthrough access on Tuesday,” or “Review the customer’s requested schedule before preparing the proposal.” “Follow up” without context leaves the next person reconstructing the whole conversation.

An acknowledgment can explain what to expect without promising a result: “We received your request. Our coordinator will review the details and contact you about the next step.” Do not describe an automatic acknowledgment as a completed estimate.

A fictional cleaning-company example

Bayou Office Cleaning receives a request for twice-weekly service. This is a fictional business and process example, not a customer result. The coordinator records the request and notices that the location and access hours are missing. The next action is to request those details. After the customer answers, the estimator takes ownership of the walkthrough. Following the visit, the estimator prepares a reviewed proposal and records when to check back.

If the customer accepts, the operations lead receives the agreed scope, access arrangements and start-date request. That handoff does not authorize extra work or replace the company’s normal agreement and billing process.

5. Review the process before adding automation

Pick five recent requests. Can you identify who owned each one, what happened, and what the next action was? Count records missing an owner or dated action. This gives you a concrete starting point without inventing a dollar value for every unanswered inquiry.

Fix the missing rule first. Then consider a reminder or automatic assignment that supports the rule. Test duplicates, missing information, replies and absences before relying on the workflow. An automation that moves incomplete information faster does not resolve the underlying problem.

Next, build a simple estimate follow-up process, or map the work before buying another app. You can also explore FSF’s existing resources. Start with a process you can actually maintain.

AI-assisted content, published under Paul Foster’s authorization. How FSF creates articles. Fictional examples are illustrations, not client results.