Start here.
Ask for a reliable way to reply and the details your team needs for its first decision. Make a question required only when the customer can answer it and your team needs it to take the next step. Try the form with an ordinary request, one with missing information, and one that needs a different reply.
- Work back from the first reply staff need to send.
- Ask for the least detail needed to choose that reply.
- Test what the customer and the person answering actually receive.
Start with the reply your team needs to send
Imagine a small upholstery shop that gets a message saying, “Can you quote my chairs?” The owner has to ask how many chairs there are and whether the seats come off. Another customer gives all those details but gets stuck because the form demands a fabric choice they have yet to make.
Pull a few recent enquiries and look at the first reply staff sent. Did they give an estimate, ask for a photo, arrange a visit, or explain that the job was outside their service? Circle the missing answer that held up that decision. Start there when choosing what the form asks.
Give each question a job
Ask for a way to reply and enough detail to choose a next step. A service choice can help send a repair to the right person. A town or postal code can help a business decide whether it covers a location. If the shop only needs a full address when someone books a visit, ask for it at that point.
Mark a field as required when staff cannot take the next step without it and customers can reasonably answer it. If an answer helps but may be unknown, give customers a way to say so. When a photo would be useful, explain what to photograph and give people a route to continue if they cannot upload one.
Try three real kinds of request
Give these sample enquiries to the person who answers requests. Ask them to read only what the form collects and say what they would do next. If they need information you do not ask for, decide whether the customer can provide it or the team should follow up.
| Enquiry | What helps now | What can wait |
|---|---|---|
| Recover four dining chair seats | The number of seats and a way to reply. | Final fabric choice. |
| Repair a damaged armchair | A description and, if available, a photo of the damaged area. | Details the shop can only confirm after seeing the chair. |
| Arrange pickup for a sofa | The town or postal code to check pickup coverage. | Full street address once pickup is agreed. |
Tell customers what sending the form does
If someone has requested a quote, tell them the request arrived and say what your team does next. If some jobs need an inspection before anyone can price them, explain that before the customer presses send. Give a reply window only if the team can keep it.
Decide where the request lands and who checks it when the usual person is away. Send a test from a phone, check the acknowledgement, and have staff find the message and any photo. Try sending without a photo and try a failed upload to see whether the customer can recover without losing the rest of their answers.
Keep the questions that help on a busy day
After a short trial, look at which enquiries got a useful first reply and which still needed a basic question answered. Ask staff which fields they used and where customers got stuck. A longer form can bring in more detail while still leaving the same first decision unanswered.
If most requests are clear after a small change, adjust the form you already use. Consider a separate step or a connection to your job system when staff keep copying the same answers or sending requests to the wrong person. Bring one of those cases to a supplier and ask them to show the whole handoff.
Use this checklist before changing your form
Review the last few requests with the person who replies to them.
- The first decision
- What should staff be able to decide when the request arrives?
- The essential answer
- Which detail changes that decision, and can the customer provide it today?
- The handoff
- Who gets the request and what should the customer expect to happen next?
Planning something with a similar workflow?
Discuss your project with usA couple of common questions.
Should a quote request form ask for a budget?
Ask when it changes whether or how you can respond. If customers may be unsure, offer an unknown option or leave the question for your first conversation.
Should customers have to upload a photo?
Require a photo only when staff cannot take the next step without one and customers can reasonably provide it. Explain what to show and give people another way to get help if they cannot send it.
Should the website give an instant quote?
Test whether the answers are enough to price a routine job and handle common exceptions. If someone still needs to inspect the work or confirm details, call it a quote request and explain what comes next.