Did the first response answer the customer's actual question and ask for only the missing information?
A customer intake checklist that keeps service jobs from going sideways.
An inquiry is not a confirmed job. Before you promise a price or schedule, establish the scope, location, access, timing, and the customer's actual approval. Here's a repeatable process, ready-to-use messages, and a practical worksheet you can copy without collecting anyone's personal information on this page.
For a local service business, faster responses matter—but a rushed promise can create an underquoted job, a missed appointment, or a dispute. The fastest useful response is the one that asks for only the missing information and gives a clear next step. Use this process for recurring cleanups, home services, lawn care, small installations, or other jobs where the actual location and work conditions determine what can be delivered.
What you must know before saying yes.
Too many operators treat every message as a sales opportunity that needs an immediate price. But if you haven't established where the service will happen, what the work includes, and what conditions may change it, you're not quoting a defined job. You're quoting an assumption.
Use a minimum viable intake: a small set of questions that can establish whether the inquiry is in scope. Once the customer is qualified and ready for a firm quote, collect only the additional information required to perform that specific service.
| First-pass question | Why you ask | When to go deeper |
|---|---|---|
| Which service do you need? | Reject work you don't offer; identify the right price model. | After the customer selects a service, ask condition-specific questions. |
| What neighborhood or ZIP code? | Check territory and route feasibility without requiring an exact address immediately. | Collect the service address once a quote or site visit is being arranged. |
| What's the job's scope? | Distinguish a routine task from a first-time or exceptional cleanup. | Ask for measurements, frequency, object counts or photos if genuinely needed. |
| Is there a deadline or preferred window? | Check actual crew/owner availability; urgency does not create capacity. | Offer a specific available window only after schedule confirmation. |
| Any access or safety constraints? | Avoid dispatching work that can't be performed safely or lawfully. | Confirm gates, animals, permits, hazards and disposal before acceptance. |
For a pet-waste-cleanup inquiry, dog count, first-visit accumulation and gate access can materially affect the quote. For a lawn-care job, dimensions, growth, terrain and debris handling may matter. For an agency or implementation service, deliverables, dependencies and acceptance criteria replace yard conditions. The information changes; the decision structure remains.
A person seeking a service you actually offer, in an area or context you can serve, with enough information to propose the next concrete step. A request for “pricing?” with no location or scope is an inquiry—not yet an approved quote or a booked job.
Don't collect every detail just because you can.
Start with the minimum information needed to determine fit. A neighborhood and preferred contact method are often enough for a first reply; a full home address is usually needed later for dispatch, not for a visitor reading your public pricing page. Don't ask for payment-card numbers in a text message, social DM, or public comment.
When a customer shares photos, ask for only the area relevant to quoting. Avoid collecting images of children, license plates, private documents, house keys or unrelated property. Keep the material in an authorized business system and restrict access to the staff who actually need it. Have a retention and deletion policy appropriate to your legal requirements and operations.
The FTC's Start with Security guidance recommends limiting personal information collected and keeping it only for a legitimate business purpose. This is a general data-minimization principle, not a substitute for the privacy and consumer-protection requirements that apply to your business.
Practical boundary: This public article does not accept or transmit customer details. The worksheet below is a blank template you copy into a suitable private system. Do not fill it with real addresses in a shared browser or public document.
What “ASAP” should trigger—and what it shouldn't.
Ah Crap Cleanup's early Chandler workflow required a practical separation between a customer saying they needed work quickly and the company confirming when the work could actually be performed. A service request might arrive with photos and a short description. Those photos are useful evidence of scope, but they do not automatically establish the right price, whether the job is inside the service boundary, or whether a team can perform it tomorrow.
For an urgent inquiry, the first business decision is whether the service area and job type fit. Next: identify the few scope or safety facts still missing. Only then should the operator offer an available date or arrange a site-specific estimate. If the soonest credible opening is later than requested, say so plainly. Never turn the customer's urgency into an invented booking promise.
This case reflects founder-described operating practices, not a claim that any particular customer booked, paid, or received a service through this guide. Actual customer photos, addresses, names and private messages are not reproduced.
Use a simple handoff, not a dozen tools
- Capture the inquiry. Record the channel, general service area and the requested outcome without overcollecting details.
- Resolve the uncertainty. Ask the smallest number of questions that affect price, scheduling, or safety.
- Prepare the scope. Decide what is included, excluded, conditional and subject to a revised quote.
- Check capacity. Verify the real route, travel, staff, materials and safe access before proposing a window.
- Ask for approval. Send the customer the exact scope and price. Save their explicit acceptance before dispatching.
A visible status in a CRM is not proof that a customer approved work. Keep the customer's actual acceptance linked to the version of the quote they accepted.
Two first replies that move the conversation forward.
The goal is not to convince every person to buy immediately. It is to show that you understood the request, determine whether you can perform the work, and give the customer one clear next action. These messages deliberately avoid invented availability, unapproved pricing, and collection of sensitive details.
Thanks for reaching out. I can check whether this falls within our service area and give you a clear quote. What type of service do you need, what neighborhood is it in, and is this a one-time job or recurring work? If there are unusual conditions or access restrictions, include those too. I'll review the scope before confirming a price or time.
Thanks for sending the details. I understand you'd like this done as soon as possible. Before I promise a window, I need to confirm the job's scope and our availability. Can you confirm [one missing scope detail] and [service area]? I'll respond with the earliest time we can reliably offer and the quote for your approval.
Thanks for asking. That request is outside the work we're currently equipped or scheduled to perform, so I don't want to accept it and disappoint you. If the scope changes or we're able to extend coverage, we'd need to confirm that separately before quoting.
For lead generation and follow-up experiments before someone inquires, use the separate first-customers field guide. This article begins after a customer has asked for help.
A quote should be testable, not merely attractive.
The purpose of intake is to make a price meaningful. Your quote should describe the work, service area, expected conditions, schedule assumptions, price, taxes or fees where applicable, what's excluded, and what happens if the conditions are different on arrival.
| Quote element | Clear example | Avoid |
|---|---|---|
| Scope | Routine cleanup for the agreed yard and number of animals | “We'll take care of everything” |
| Price | One stated amount for the defined visit; explicit recurring frequency if agreed | A price quoted without any scope |
| Timing | One offered window, subject to customer acceptance | “Tomorrow for sure” when the route isn't confirmed |
| Access | Confirm gate procedure, pet handling and disposal arrangement | Assuming the operator can enter any yard |
| Changes | Additional work requires a revised quote and acceptance | Unapproved extras or surprise charges |
| Payment | When and how the invoice will be issued and paid | Marking a sent invoice as settled revenue |
A $25 founder offer can still become an expensive mistake if the visit was quoted without travel, labor, and first-cleanup conditions. See the actual pet-waste-removal launch case and route calculator or the general job-pricing framework for contribution math.
Changes after acceptance
If the scope materially changes, don't silently expand the job. Explain what changed, document the revised price or service boundary, and obtain approval before proceeding. If the safe response is to stop or reschedule, do that. The point of good intake is to prevent the customer from discovering your assumptions after the bill arrives.
The handoff belongs in one accountable record.
Once the customer accepts, make sure the operator can see the right scope and service window—not a stale quote or incomplete social-media exchange. Your job record should identify the owner, assigned team or contractor, task, timing, safety/access notes, approved price and an escalation route for unexpected conditions.
| State | Evidence before advancing |
|---|---|
| New inquiry | An actual customer request with a contact channel |
| Qualified | Service fits the territory, capability and known scope |
| Quoted | Specific scope, conditions and price actually sent |
| Approved | Customer accepted the quote version and timing |
| Scheduled | Capacity and access conditions confirmed |
| Delivered | Completed work and any exceptions recorded |
| Invoiced | Invoice issued for the approved work |
| Paid | Settlement reconciled against provider or bank record |
These states are intentionally separate. An appointment on the calendar doesn't establish that work happened; a completion message doesn't establish payment. If a customer disputes the work, your record should help you see the authorized scope, what was actually delivered, and what remedy was discussed. This is the ITI Method's principle of evidence for each business decision.
Copy the intake checklist and put it to work.
This is a plain-text starting point, not an online form that stores customer data. Customize it for your service and keep the completed records in a secure, authorized business system. Ask only what you need at the stage you're in. The blank prompts can be used for a phone call, email, or intake form.
Service inquiry → approved quote
SERVICE INQUIRY — BLANK INTAKE TEMPLATE INQUIRY (do not treat as a booking) Date / channel: [date and origin] Service requested: [plain-language problem] General service area: [neighborhood or ZIP] One-time or recurring: [frequency] Preferred reply channel: [agreed contact method] SCOPE TO CONFIRM Included work: [deliverables and boundaries] Approximate size / count / condition: [as needed] Special first-visit conditions: [yes/no + details] Safety, animals, gates or access: [relevant limits] Photos genuinely needed? [optional / consent] Requested timing: [customer preference] Capacity actually checked? [yes/no] QUOTE (do not imply approval) Price and billing unit: [amount and what it covers] Taxes / extra fees: [what applies] Excluded tasks: [specific boundaries] Validity or re-quote conditions: [terms] Actual available window: [confirmed offer] CUSTOMER ACCEPTANCE Quote version and date: [reference] Approval recorded? [yes/no + channel] Schedule and access confirmed? [yes/no] DELIVERY / PAYMENT — LATER STAGES Work delivered? [observed completion] Exceptions communicated? [record] Invoice issued? [reference] Payment actually reconciled? [yes/no] Only keep details your service actually needs.
Never paste this completed template into a public support thread, public AI chat, or social comment with customer identifiers. Remove sensitive details before using it for teaching, marketing, or internal case studies.
Measure the gap between inquiry and completed payment.
Counting every inquiry as revenue misrepresents the business. Track the stages independently and inspect where a real customer became uncertain or dropped away. The most useful early metrics are operational: time to first useful reply, fraction of inquiries within your territory, fraction with enough scope information, quotes sent, accepted work, jobs delivered, and payments settled.
Could another operator understand exactly what is included and excluded?
Did the crew see the accepted quote and correctly record delivery and exceptions?
Don't optimize toward a higher lead count if the leads are outside your territory or the quotes lose money. Compare qualified requests by channel to accepted, delivered, collected work. When something fails, change one part of the intake procedure and observe the next real cases.
A useful business system does not confuse recording an activity with demonstrating a result. Record the actual decision, supporting evidence, and the next action—not just a completion checkbox.
Before you build another intake form.
What should be on a service business customer intake form?
At minimum: requested service, general service area, scope, timing preference, contact channel and constraints that could affect safe delivery. Add exact address, access details or supporting photos only when needed for a firm quote and scheduling. A template is useful if it reflects your actual workflow.
Should I collect a customer's full address on the first reply?
Not automatically. Neighborhood or ZIP code may be enough to check eligibility. For an approved dispatch or a location-sensitive estimate, the exact service address can become necessary. Follow your actual privacy and legal obligations, restrict access and retain the information only as appropriate.
Does an urgent request mean I should reserve a slot?
No. First verify your ability to deliver the scoped work safely. State a real available window only when capacity has been checked. If you cannot meet the requested deadline, propose a credible alternative rather than an invented guarantee.
Can I quote without seeing photos?
Sometimes. It depends on the service, available measurements and scope uncertainty. Photos are optional when a reliable quote can be given without them. If images would contain unnecessary personal or property details, ask for a narrow image or arrange another appropriate assessment.
When is a quote considered accepted?
When the customer agrees to a sufficiently clear version of the scope, price and any required terms through an appropriate, recorded channel. Sending a quote is not approval, and booking software should not silently treat it as one.
Is this a replacement for CRM software?
No. It is a small operating procedure that can work inside a spreadsheet, email inbox, scheduling system or CRM. Choose software after you know what information your staff needs and what customer events must be recorded.
Sources and editorial boundaries
- FTC — Start with Security: personal data collection and sensible retention/access choices.
- FTC — Protecting Personal Information: keep only legitimate business information.
- From Idea to Invoice free field guides: related acquisition, pricing and founder case resources.
- Founder advisory context: Bryan Leonard and the real operating-business background.
This is an educational procedure, informed by Ah Crap Cleanup founder-described operating decisions. It does not reproduce real customer data, claim all scenarios were independently audited, guarantee conversions, or determine your legal, privacy, consumer, labor or insurance obligations.
From first inquiry to an invoice that makes sense.
These blank questions are free. The complete ITI course shows how to connect inquiry, scope, delivery, reconciliation and improvement through operating records, downloadable tools and the actual Ah Crap Cleanup case.