What should your website enquiry form ask?

Decide what the first response needs to achieve

Before adding form fields, decide what your team will do with the enquiry. Will they confirm a routine request, assess whether the job fits or arrange a conversation to understand it?

That decision gives each question a purpose. A service area may determine whether you can help. A deadline may change who needs to respond. The customer's preferred equipment model may tell you very little if they need your advice on the equipment.

For every required question, check:

• Will the answer change our first useful response?
• Can this customer reasonably answer it now?
• What would we do if they left it blank?

If the team would ask it during the conversation anyway, decide whether collecting it beforehand genuinely helps. Some detail is necessary; some is simply convenient for your internal spreadsheet.

Contact form best practices need that context. TBH Creative's form guide also recommends deciding what is needed before follow-up and collecting further detail later. The practical work is choosing where that boundary sits for your customers.

Two enquiries that need different starts

In one website kickoff, an owner described regular customers arranging familiar work through a short phone call. The team still wanted a website form as an alternative, with enough context to start a conversation.

Coordinating known work and helping someone define unfamiliar work call for different first questions.

Consider a fictional commercial maintenance company. It wants more planned maintenance contracts while continuing to help existing customers arrange work. Its office manager receives enquiries and passes new contract discussions to the operations manager.

An existing customer needs another service visit

This customer already knows the company and the property being discussed. Give them a direct route to the office during its actual contact hours, with a written option if they prefer.

The first exchange needs to identify the customer and site, establish what they need and confirm how to reach them. Ask about the required date if it affects arranging the visit.

There is little value in making them repeat the company's size, explain the whole property portfolio or complete a new-business questionnaire. The office manager can refer to existing records, then check anything that may have changed.

Leave the visit's final scope, access arrangements and availability for confirmation. Sending a request does not reserve a technician or establish an appointment.

For this route, “Request another visit” is an honest action label. Explain that the team will confirm the arrangements. Use “Book a visit” only if the process actually completes a booking.

A new customer wants a maintenance arrangement

This visitor manages several properties and knows the current problems. They may not know which maintenance tasks, schedule or staffing arrangement will solve them.

The form should establish the organisation, a way to reply, the properties' general location and what needs attention. An intended start date is useful when known. A technical maintenance plan can wait until the operations manager understands the properties.

Use a message prompt such as:

Tell us about the properties and what you need help with.

Add short guidance: “A brief description is enough to start. Include the suburbs and any important timing.” Let them explain an uncertain requirement rather than choose a package they do not yet understand.

The office manager checks the request and passes it to the operations manager for assessment. That manager can then clarify the work and recommend the next step, which may include a site discussion before quoting.

Both routes can sit on one Contact page and reach the same office. Clear instructions or a simple enquiry-type choice may be enough. Different needs do not automatically require separate pages, software or forms.

Choose what is required, optional or left until later

For this new maintenance enquiry, use the following field plan. Each question has a purpose in the operations manager's first response.

Mark optional fields clearly. If you offer a choice of reply method, ask for the corresponding detail and confirm that the team will use it.

Budget is another judgement to make explicitly. Ask for a range when it changes whether the team can help or how the first discussion should proceed. Let someone request guidance when they do not know, rather than making them invent an amount to continue.

For a more familiar, specification-led service, detailed questions may belong earlier. A buyer submitting approved drawings for a quote is in a different position from someone seeking a recommendation.

Keep the distinction grounded in the actual job. A short form missing an essential location is no more useful than a long form collecting details nobody reads.

Where a technical detail is genuinely needed, explain it and give people a way to say they are unsure. Do not turn an unfamiliar abbreviation into a compulsory guessing exercise.

Your service-page explanation should establish what the business handles before the visitor reaches the form. The form can then collect the next useful information instead of trying to explain the whole offer again.

This also applies to different customer groups. Familiarity and available project information may matter more than the label attached to the customer.

Make the response part of the plan

Choose the actual recipient before approving the form. Agree who checks incoming requests, who takes the next action and who covers an absence.

For the example, the office manager owns the request until the operations manager accepts the new-contract follow-up. Existing-customer requests stay with the office for coordination. Forwarding a message should not leave both people assuming the other has replied.

The customer needs a useful confirmation too. Once the system has accepted the submission, a message could say:

Thanks for your enquiry. Our team will review the details and contact you using your chosen reply method to discuss the next step.

That wording suits the proposed example only if the team will work that way. Add a response window when the business can reliably meet it, using its real operating days and hours.

If requests are not monitored continuously, say so where timing matters and provide the actual alternative contact route. Do not present an ordinary enquiry form as an urgent-response service.

Keep any newsletter signup distinct from the service enquiry. Have collection, privacy and consent wording checked against the business's actual practices and applicable requirements. Avoid copying assurances about data use that nobody has verified.

An existing inbox or business system can remain if it supports the agreed flow. Confirm any connection with the developer; a website rebuild does not by itself require a new CRM.

Check both routes before launch

Ask someone to follow each proposed route without coaching them through the form. Use safe test details, including a case where the customer does not know the technical answer.

Check that they can:

• Find a suitable contact method from the relevant service page, including on a phone.
• Understand the questions, identify optional fields and correct an error without losing the rest of the message.
• Submit successfully and understand what will happen next.
• Reach the intended recipient, with the information needed for that person to respond.

Include any agreed attachments and alternative contact methods in the checks. A visible thank-you message alone does not prove that the team received the request.

Your website launch checks should carry these scenarios through to the working site. Later, review suitable enquiries and what happened to them through your website success measures. More submissions alone will not tell you whether the form is bringing the right work.

Bring the questions and response responsibilities into the wider website plan. With SOL, we work through the required customer flow and agree the functionality and any connections within the website development scope.

Show us how enquiries arrive now, which work you want more of and what your team needs before it can help.