Ask for enough information to answer the enquiry. Each extra field should serve a clear purpose, and optional questions should be visibly optional.
Start with the essentials
For many service businesses, a name, one reply channel and a description of the need are enough to begin. Ask for a phone number when you need to respond by phone; do not require both email and phone without a reason.
Add questions that help route the enquiry
A service category or location may help determine whether you can take the work. A source question can support measurement, but let visitors skip it. Explain why sensitive or unusual information is needed and avoid requesting it in a general contact form.
Offer another way to reach you
Keep a public email address, phone or WhatsApp link nearby. Different visitors prefer different channels. Use labels outside the fields, clear validation and controls that are comfortable on a phone or keyboard.
Make success and failure truthful
Confirm success only after the server has accepted the submission. If delivery fails, preserve the visitor's message, explain how to retry and show an alternative contact channel. A browser animation is not evidence that an email arrived.
State a reply timeframe only if you can meet it. Avoid a generic promise such as “today” when someone may submit at night or during a holiday. Prevent accidental repeated submissions while keeping errors recoverable.
Test the complete journey
Send an identifiable test from another device, confirm it reached the intended inbox and check that replying goes to the correct address. Also test an invalid email, an empty required field and a connection failure. Recheck after changing the form, hosting or email setup.
Anti-spam checks should not silently discard real enquiries. A device with an inaccurate clock or a helpful autofill feature should not receive a false success message.
Content reviewed: 2026-11-04