Ask what you need to know to follow up.
Start with the questions you always ask.
Think about your first questions when someone calls. What do they need? Where is the job? Is it work you take on? Those are a better starting point for your form than copying someone else’s.
Service
Use service names customers understand, and give them room to explain if they aren’t sure which one fits.
Location
A city or ZIP code may be enough to check whether you cover the area. Ask for a full address when you need it.
Project description
Give people room to describe the job. A prompt like “What needs work, and what would you like done?” can help them get started.
Timing
Ask when they hope to start, and include an option for people who are still planning. Make it clear this doesn’t reserve a date.
Let customers show you what they mean.
Photos can help explain peeling paint, a damaged panel, or a difficult-to-reach area. They give you context, but they won’t always replace a visit or inspection.
If your form accepts photos, explain the file and size limits up front. Let people see what they selected and remove a mistake. Test that the photos arrive with the request.
Keep the form easy to finish.
If a detail can wait until the first call, make it optional or leave it out. Give each field a readable label and use words your customers understand.
Ask for a name and a way to reply. If customers can choose between phone and email, make sure your team can follow through on either. Leave out personal details you don’t need.
Tell people whether their message was sent.
Show when a message is sending and whether it went through. If something fails, keep the customer’s answers so they don’t have to type everything again. Prevent repeated clicks from sending the same request twice.
Tell customers their request was sent and what happens next. Don’t call it a confirmed booking unless it is one. If the form fails, give them a phone number or email address they can use instead.
Check what arrives in your inbox.
Send yourself a test request. Check that the service, location, project details, contact information, and any photos arrive. Can you find what matters at a glance?
If you track where inquiries come from, include that information when it’s available. If a chatbot collects the request, keep the customer’s words alongside any summary. The message should help you pick up the conversation without losing the details.
A few things you might be wondering
Should every field be required?
No. Require what you need to reply and understand the request. Make the rest optional, especially details the customer may not know yet.
Can we use the same inquiry form for every service?
Usually, yes. Keep the basic contact fields, then ask a few different questions based on the service if that helps your team.
How do we know the form really works?
Send a request and check that it arrives, including any photos. Test what customers see when sending fails too.