Answer the questions people have before they contact you
Before someone fills in your form, they are trying to work out whether contacting you will be worth the effort. They may be comparing providers during a lunch break. They may have no idea how their project is normally priced.
Your website can help them arrive better prepared. It does not have to explain every technical detail or look like a large corporation.
Make the basics visible
Explain what you do, where you do it and the types of project you are best equipped to handle. Show genuine examples of relevant work with enough context to understand them. A photo of a finished kitchen is more useful when the reader knows what you changed and what constraints you solved.
Describe the first step. Will someone call? Is a visit necessary? Is an initial conversation free? Does a detailed assessment cost money? State a response expectation you can maintain and distinguish it from an emergency service.
If you can provide a meaningful starting price or range, explain the scope and assumptions behind it. If projects vary too much, describe the factors that move the price and what you need to narrow it. Avoid an attractive “from” figure that few realistic projects can achieve.
Let people recognize a mismatch
A mover can state the areas served and the details needed for access. A planner can explain whether they offer full planning, coordination or both. An installer can clarify whether they supply equipment, fit customer-supplied equipment or assess both separately.
These details save customers from writing long inquiries for work you do not offer. They also save you from repeating the same explanation.
Test the experience yourself
Use a real phone and follow the journey from the service page to the confirmation message. Check labels, required fields, error messages, photo uploads and the alternative contact route. Use a clearly identified internal test and remove its record afterward.
Confirm that the inquiry reaches the person who will act on it. A beautiful confirmation page does not prove anyone received the submission. Make sure the customer knows the next step without needing to search the website again.
A useful confirmation: “We have received your project details. [Team or name] will review them and respond by [realistic window]. If you need to add anything, reply to [working route].”
Keep the page focused on helping someone decide. Claims about being innovative or using advanced software do less work than a clear explanation of what happens after they press Send.
Ask enough to decide what happens next
A long form can feel efficient because it collects everything at once. It can also ask a customer to do the technical assessment they came to you for.
Collect what you need for the next decision. You can ask for more once you know the job fits. Offer a phone route for people who find it easier to explain aloud or need help using the form.
Start with five areas
- What would you like done, and where?
- What is happening now, and what would you like to change?
- When do you need it, and how flexible is that timing?
- What budget or spending range are you considering?
- What photos, measurements or existing information can you easily share?
Ask for contact details and the preferred way to respond alongside these questions. Adapt the fields to the service. For a wedding planner, location means venue or destination and timing means a fixed event date. For an agency, access may mean access to existing materials and the person approving the work.
Make uncertainty acceptable
Give budget questions an “I need guidance” answer. Explain why you ask: “A rough range helps us suggest a realistic scope before you spend time on a detailed proposal.” Do not imply that stating a budget guarantees you will charge all of it.
Mark photos optional unless they are genuinely necessary for the next step. Explain what would help: a wide view of the room, a photo of the access route or an example of the desired outcome. Tell people not to include sensitive information they do not need to share.
Review before promising
An inquiry should produce a brief that a person can understand. Highlight unknowns. The owner or responsible team member then decides whether to ask a question, arrange a call, book an assessment, suggest a different scope or decline.
Automatic acknowledgment is useful. Automatic acceptance of price, dates or suitability needs much more care.
In one public contractor discussion, an administrator proposed exactly this kind of questionnaire before a quote visit. Replies also argued for short forms and human conversations. That disagreement is a useful reminder to test completion and lead quality together. [R1]
Check after ten suitable inquiries. What did customers struggle to answer? Which field actually changed your decision? Remove questions that create work without helping you decide. Keep the information that prevents an unnecessary visit or a second round of basic questions.
Go further: Questions to ask before quoting, the eight answers that tell you whether a request deserves a quote.
Respond reliably while you are doing the work
You cannot always answer the phone while you are carrying equipment, driving or meeting a customer. A response process should reflect that reality.
Separate acknowledging an inquiry from giving a useful answer. An automatic message can confirm receipt. It cannot claim that you have reviewed the project when you have not. The useful answer tells the customer whether you can help and what happens next.
Choose a promise you can keep
Set a response window for normal inquiries and publish it where appropriate. It might be the next working day or two scheduled review periods. Choose it from your actual capacity and the urgency of your service, then measure whether you keep it.
Do not borrow someone else's response-time statistic as a reason to promise instant availability. Urgent repair, a large renovation and next summer's wedding have different expectations.
Assign an owner
For a team, name who reviews new inquiries and who covers absences. “The office” is not enough if three people assume someone else replied. For a solo business, create a recurring review slot and a reliable place for missed calls and form submissions.
A useful first response refers to what the person asked:
Thanks for the details about the move from [area] to [area]. We cover that route. Before we can price it, could you confirm the floor and elevator access at each address? Once we have that, we can tell you whether a survey is needed.
That message makes progress. “Thanks, someone will be in touch” may leave the same uncertainty in place.
Handle missed calls without creating another queue
Use a short voicemail greeting with working hours and the best way to leave project details. If you offer a callback window, make sure someone owns it. Only send automated texts where the contact context and applicable rules allow them; keep marketing separate from service responses.
Record the outcome after you call. An unanswered callback needs either an agreed further attempt or a clear close-out rule. Otherwise, the phone log becomes another list nobody knows how to finish.
A weekly check: take five recent inquiries and compare the promised response with the first useful human response. If you regularly miss the promise, change the coverage, reduce unnecessary handling or adjust the promise. An accurate expectation builds more trust than a fast-sounding one that repeatedly fails.
Go further: How fast to reply to a quote request, with realistic response times by type of request.