On this page

A customer fills out your website form. They describe the job, tell you where they are and ask whether you can help. Your reply asks them to describe the job and give their location.
The business has responded, but the customer is starting over.
A useful customer inquiry process carries the conversation forward. It answers the question, asks for missing details and helps the customer take an appropriate next step. When someone else picks up the request, they should have enough information to continue it.
You can review that process by following one inquiry through your business. Look at the answer the customer receives, the details your team keeps and who is responsible for what happens next.
Answer the question they asked
Consider a customer who writes:
Our back gate has started to sag and no longer latches. We’re on the east side of town. Do you handle gate repairs, and how do we get started?
They have described the problem and given a general location. They want to know whether you handle that work and how to begin.
For a company that repairs gates and serves that area, the first sentence can answer directly: “Yes, we repair gates that sag or won’t latch, and we cover the east side of town.” Then explain how to get started.
If the answer depends on something, name it. You may handle certain gate materials or need the address to confirm that it falls within your service area. Ask for the detail that lets you answer accurately. If the work is outside your scope, say so before taking the customer through an intake that cannot help them.
Your website can answer some of these questions before anyone contacts you. Our six-question website checklist covers service fit, scope, location and what follows an inquiry. The reply can build on those answers and apply them to the person’s request.
Ask for the information the next step needs
Start with what the customer has already provided. Then identify what your team needs to decide or do next.
In the gate example, the company might need photos of the hinges and latch, the gate material and a full address before planning a visit. Each request should have a purpose. The photos help the team understand the problem; the address confirms the service location.
Explain what to send and how to send it. “Could you reply with a photo of the hinges and the latch?” is easier to act on than “Please provide more information.” Offer a suitable alternative when the customer cannot supply something.
Use the channels your business actually supports. If photos need to go to a particular email address or phone number, give that route in the reply. Ask for contact details when they are missing, and retain the customer’s preferred way to hear from you.
Review your standard intake questions too. If nobody uses an answer to make a decision or carry out the work, consider whether you need to ask for it.
Choose a next step that fits the request
Some inquiries can end with a useful answer. Others need an estimate, a visit or a conversation with someone who knows the work. Let the customer’s question and the information available guide that choice.
A person asking whether you handle a service may still be deciding what to do. Give them the answer and an easy way to continue. Someone ready to arrange a visit needs a clear scheduling step.
Our Hanna Assist booking example illustrates that progression. A customer asks to book a first visit. Mia asks about their preference, an available time is offered, the customer accepts and a confirmation follows. Each exchange supplies what the next action needs.
When your process collects preferred times for the team to review, tell the customer that they have requested an appointment. Confirm the appointment once the time has been checked and agreed. The message should match what has actually happened.
The same principle applies beyond scheduling. A request for an estimate, a question passed to a colleague and a completed answer are different outcomes. Make the current one clear.
Keep the details with the inquiry
A customer’s reply may arrive tomorrow. A colleague may return the call. The person handling the next step needs the original question and what has happened since.
Keep the useful context together:
- What the customer needs and where the work is.
- What they asked and what they have already been told.
- Information requested, received and still missing.
- Any relevant preferences or constraints.
- Who holds the next action and what that action is.
Use the record your team actually works from. If a form collects useful details but the person making the callback cannot see them, the collection has not helped that person continue the conversation.
Try a simple check: could a colleague who did not see the original exchange pick up the request? If they would have to ask the customer to explain everything again, find where the context stopped moving.

Give the next action an owner
“Passed to the team” leaves a practical question unanswered: who will do something with it?
Name the person or role responsible for the next action. “Our estimator will review your photos and call you about the next step” gives both the customer and your colleagues a clearer expectation.
That owner also needs the knowledge and authority to handle the question. Routine service information can come from approved business answers. A recommendation about a particular job needs someone qualified to explain it. Whether a gate should be adjusted or replaced, for example, calls for more than collecting the customer’s details.
Our guide to helping customers understand what they are approving explains how to put job-specific evidence and an explanation beside that decision.
For an inquiry process, the immediate task is to get that question to the right person with the context they need. The detailed arrangements for unavailable staff and unanswered transfers deserve their own review.
Tell the customer where things stand
End the exchange with an accurate next step. What have you received? What will happen now? Who will act, and does the customer need to do anything?
Give a response window when your business has an agreed one it can meet. Otherwise, explain what the next action depends on rather than inventing a deadline. If you are waiting for photos, say that. If a colleague needs to review the request, identify the review and who will follow up.
When the status changes, update the customer. A confirmed appointment should have a clear record of the day, time and location. A question answered by a specialist should reach the person who asked it.

Put the reply and the team note together
If the customer has not supplied a callback number, a company that reviews photos before arranging a visit could reply:
Note for the team
| Detail | What to retain |
|---|---|
| Request | Back gate is sagging and no longer latches; east side of town. |
| Customer’s question | Do we handle the work, and how do they get started? |
| Already explained | We handle this work in the area. Photos, gate material, full address and callback number requested. |
| Still needed | Requested details and a usable callback number if it was not supplied. |
| Owner and next action | Estimator reviews the details and calls to discuss the next step. |
| Current status | Waiting for the customer’s details; no visit arranged. |
The customer has a manageable action to take. The estimator knows why the request is coming to them and what the customer expects. Both sides can continue from the same point.
Review one recent inquiry
Choose a request your business has already handled. Remove identifying customer details before sharing it for review. Follow the exchange from arrival to the next useful outcome.
- Answer: Did the first reply address the customer’s question?
- Missing details: Did you use what they had already supplied and ask only for what was needed?
- Next step: Did the action fit the request, with its status made clear?
- Context: Could the next person continue without making the customer start over?
- Owner: Was someone responsible for the next action?
- Confirmation: Did the customer know what would happen next?
Pick one gap and improve it. That might mean changing a standard reply, carrying a form answer into the team’s working record or assigning an owner to a request that previously sat in a shared inbox.
Then review the next inquiry that follows the updated process. Look for whether the customer and the person helping them can both tell what to do next.
