GUIDES

What should a website enquiry form include?

Visitors need an easy way to describe what they need. You need enough information to give a useful reply. A good form serves both purposes, whether you provide trades, consulting, repairs or another service.

Start with what you need for the first reply

List the questions you normally ask at first contact. A name, email address and message can be a starting point for a simple enquiry. Add fields to suit your service. A telephone number need not be compulsory if you can reply by email.

Do not try to settle every detail of the project in the first form. Clarify other information when replying. Require only the fields you genuinely need for the next step.

  • Name or contact person.
  • An email address for your reply.
  • A short description of the request.
  • Other details only where the service needs them.

Adapt the questions to your service

A trade may need the work location and a description of the current condition. A consultant may need the topic and intended outcome. A repair service may need the device and fault symptoms. These are illustrative examples; choose fields around your own process.

If you offer several services, a short selection helps identify the request. Budget, date or attachment fields are useful only when you use the information. Visitors may not know the technical solution or exact cost before the first conversation.

Explain what to write and what happens next

Use familiar labels and a short example, such as “Describe what you need, where and when.” Keep labels visible after the fields are filled; placeholder text alone is not enough.

“Send a no-obligation enquiry” is more specific than “Continue”. Explain the next step and offer a direct email address too. State a response time only if you can meet it. Do not automatically promise a confirmed price or reserved appointment.

Check mobile use and error states

Fields, instructions and the button must be readable on a phone. Email fields should support the appropriate keyboard and autofill. Also try completing the form using only a keyboard, with a visible focus indicator.

Identify the specific problem when something fails and retain the visitor's message. Show when submission is in progress. A failed attempt should be retryable without typing everything again.

  • Comfortable use on smaller screens.
  • Visible labels and clear required fields.
  • Keyboard access and visible focus.
  • Useful errors with retained input.

Test actual message delivery

A form is not complete just because it displays “sent”. Before launch, check that the full message reaches the correct mailbox and that you can reply to the visitor. Test delivery failure too; the website must not claim success without confirmation.

A simple email enquiry differs from booking, payments, a price calculator or an internal system integration. These need their own rules and an agreed scope. On an existing website, improving the form and the route to contact may be enough.

Common questions

How many fields should the form have?

Enough for the next step. Start a simple enquiry with contact details and a message, then add fields only for a clear reason.

Must visitors give a phone number?

If email is sufficient, a phone number can be optional. Require it only when the service genuinely needs it, and explain why.

Can I keep my current form?

Yes, if it works, is technically suitable and fits your process. Updating fields, instructions or its placement may be enough.

Does a standard form calculate a price automatically?

Not automatically. An enquiry collects information for a conversation. Calculators and booking functions are assessed and quoted separately according to your service rules.

Need a clearer route to enquiries?

Send your current website or describe your service. We will discuss what you need to learn from customers and how the form should fit your offer.

Discuss my website and enquiry form

You can change your preferences in the footer at any time. You can browse without accepting optional cookies.

About cookies and language selection