Let’s work!

Website

Enquiry form for trades businesses: structure and example

Reading time: about 5 minutes for the main text. Use templates and details as needed.

An enquiry form should help your business understand a project and prepare for the first conversation. In the bathroom renovation example below, we use four core details: name, email address, project location and the enquiry itself. The customer does not need a measured survey or finished plans at this stage. [a]

A complete form also needs a process for what happens after submission. Only a test enquiry shows whether the message reaches you in full and the person responsible can reply. The message displayed on the website alone does not confirm this. [b]

What information you need at first contact

A dedicated form makes sense if you regularly have to ask for the same basic information. If enquiries vary widely, a selection that includes ‘Other enquiry’ may be enough to start with. This also lets someone get in touch when they cannot yet name the service they need. [b]

For each field, consider why your business needs the answer now. You might need the project location to check whether it falls within your service area. Billing details can wait until a later discussion. Ask only for the personal data you need for the particular purpose. This is the principle of data minimisation. [2]

Our example uses four required details:

Field Purpose in the example
Your name Address the customer and find their message again
Your email address Reply personally to the enquiry
Project postcode and town Check the service area
What would you like to change? Make an initial assessment of the work requested

Email is the default contact method. If the customer chooses a callback, their phone number is also required. The email address remains required because, in this example, it provides an alternative way to respond to the same enquiry if phone contact cannot be made. Explain this next to the field. This choice of fields is a working example, not a general legal requirement. A business that works exclusively by phone needs a different selection to suit its process. [a]

You can use this extract from the template for the email field: [a]

Your email address (required): ____________________

Help: If you choose email as your contact method, we will send our reply to this address. If we cannot reach you for a requested callback, we will contact you personally at this address about the same enquiry. If an acknowledgement is set up, you will also receive it here.

The service and preferred timeframe can be added as optional fields. Allow answers such as ‘Not sure yet’ and ‘Still open’. The preferred timeframe does not reserve a date for the work. [b]

For some projects, a budget, type of home or measurements can also help with an initial assessment. These fields need a specific purpose in your process. Technical questions should allow an answer such as ‘I don’t know yet’ if customers do not need to know the detail at this stage. [b]

What a bathroom renovation enquiry could look like

The label ‘What would you like to change?’ lets customers describe their project in their own words. A few sentences are enough for this example:

Fictional example: ‘We would like to replace the bath with a shower in our existing bathroom. The property is in 1010 Vienna. The timeframe is still open. Please let us know what information you need for an initial conversation.’ [a]

This lets the business check whether the work and location are a good fit. Exact measurements and further planning can be discussed later.

Non-interactive example of a bathroom renovation enquiry with name, email, project location and enquiry details. Email is selected by default; a phone field is only needed for a callback. The privacy notice appears before submission.
This is what a first enquiry could look like. We have chosen four core details; the phone field is only needed for a callback. The image shows an example, not a working form or a real customer project. [c]

The full template with field text to copy also includes the help text and ‘Send enquiry’ button. Adapt these texts to the features of your website. Photos remain optional; the file formats and sizes offered must match the actual settings. [a]

This further extract explains the purpose of the enquiry above the fields: [a]

Your bathroom renovation enquiry

Briefly describe what you would like to change in your bathroom and where the project is located. We will review your enquiry and discuss the next steps with you. Photos are optional. Please send only the information we need for this enquiry.

What to give your website support provider

Pass on your chosen fields and contact process. Also decide which inbox or system should receive the enquiry and who will handle it. This includes cover for absences. The template supplies the wording; your website support provider turns it into a working form. [b]

If you state a response time, explain which hours or days count towards it. The commitment must reflect when someone is actually available, including during absences. Offer only contact methods that someone actively handles. A business without an emergency service should not promise one through the form. [b]

Required fields must be recognisable, for example with the word ‘required’. Example text inside an empty field does not replace a permanent label. [3] If information is missing, the message should name the field and explain the correction needed. [6] For a callback, suitable wording would be: ‘We need your phone number for the callback you requested.’ Information already entered should be kept. [b]

Other errors can be described just as clearly. For a missing name, the example says ‘Please enter your name.’ For a file, the template includes this message: ‘The website could not accept your file. Please check the stated format and size limit.’ [a]

The explanation belongs next to the affected field. A red border alone does not tell the customer what to correct. [6]

Your website support provider checks that the callback option works as described at a technical level too. They also check the optional photos and protection against unwanted messages. The details of field validation and error messages provide the basis for this testing brief. [b]

For optional photos, it helps to explain what kind of shot is enough for a first impression. Ask customers to leave people and unnecessary personal documents out of the picture. [b]

Before submission, there needs to be a visible link to your business’s privacy information, describing the actual data processing. [4] A blanket checkbox saying ‘I agree to the GDPR’ replaces neither this information nor an appropriate legal basis. [4] [12] The explanation of data protection and consent helps with further discussions; the example wording is not a finished privacy statement for your business.

Check receipt with a test enquiry

Use fictional project details, but an email address of your own whose inbox you can check. A made-up address cannot prove delivery. Mark the enquiry ‘FORM TEST – not a customer job’. [b]

  1. Open the form on a smartphone. Fill it in with the fictional project and check that the labels and button remain readable. Send the marked test enquiry.
  2. Read the message on the website. It must match what has actually been confirmed. Clear feedback on success or failure is part of the form. [6]
  3. Find the same original enquiry in the intended business inbox or system. Are the details complete and accessible to the person responsible? An acknowledgement email to the customer does not replace this check.
  4. Have the person responsible reply. For email, the reply must reach your test inbox. For a callback, test the agreed phone contact. Check any additional acknowledgement separately, if one has been set up. [b]

For the message in the second step, the template includes this example: [a]

Example after confirmed acceptance: ‘Thank you. The website has received your enquiry. We will review it and get back to you using your chosen contact method.’

An additional acknowledgement email does not automatically need to repeat the photos and the full project description. The confirmed status and next step, together with a contact method that someone handles, are enough. [b]

Record the date, device, case tested and result. If the enquiry is missing at the business, the delivery test has failed. The six detailed test cases extend this first attempt to cover required field errors and other states. After changes to the form or email configuration, the contact process needs to be tested again. [b]

When filling in the form on a smartphone, check autofill too: the name and email address should end up in the right fields. If photos are offered, also test submission with and without a test photo. [b]

On a computer, it must also be possible to complete and submit the form without a mouse, including when an error needs correcting. [7] A visible indicator shows which field or button is currently selected. [8] These trials can reveal individual problems; they do not replace a full accessibility assessment. [9]

Resolve an uncertain submission

If the connection is interrupted, it may be unclear whether the enquiry arrived. The website must not claim certain success in that case. Receipt can be checked through the stated contact method, which someone needs to handle. Repeated submission without checking can create duplicate enquiries. [a]

Two messages from the template show the difference: [a]

Example for a submission that has definitely failed: ‘The website could not send your enquiry. Your entries have been kept. Please use the alternative contact method provided if needed.’

If the outcome is unclear, the message says: ‘We could not confirm receipt of your enquiry. Please use the contact method provided to check whether it arrived.’

For a definite submission failure and an uncertain outcome, there are different example messages. Deliberate faults belong in a test environment; do not change a live recipient address for this purpose. [b]

And if the message is missing, give your website support provider the specific findings. Name the fields tested and the message displayed, and identify the point beyond which the enquiry can no longer be traced. For help with setup or delivery, see BrandHoop’s services.

Sources as checked for the previous version dated 16 October 2026; editorially revised on 17 October 2026. Numbers lead to the sources; letters explain editorial examples or recommendations. Each note states what the source supports.

[a] Editorial examples. Content labelled as an example or fictional illustrates possible situations. It does not describe real customer cases or provide evidence of a measured effect.

[b] Practical recommendations. The suggested processes and decision aids are editorial applications of the principles cited. Their specific effect on enquiries or jobs has not been measured here.

[c] Editorial illustration. The illustration explains a relationship. It is neither a real customer reference nor evidence of a measured effect.

Sources and context (12 sources)
  1. Validating Input — W3C Web Accessibility Initiative

    Explains required fields, checks of common input formats and the need for server-side validation in addition to checks in the browser. A format check confirms neither that an inbox exists nor that an email has been received. Checked: 2026-10-16.

  2. Datenschutzgrundsätze im Überblick — Wirtschaftskammer Österreich

    The WKO explains that personal data should be limited to what is necessary for the purpose. This does not establish a general rule of four form fields or mean that the example fields are lawful in every case. Checked: 2026-10-16.

  3. Form Instructions — W3C Web Accessibility Initiative

    Supports making required and optional information recognisable, explaining data formats and recognising the limits of placeholder text as a substitute for labels. Does not prescribe a binding choice of fields for trades businesses. Checked: 2026-10-16.

  4. Datenschutzerklärung DSGVO: Pflichten für Unternehmen — Wirtschaftskammer Österreich

    Supports the timing and content of information when data is collected directly, and a form notice visible before submission. The article covers selected points and does not provide a complete privacy statement for a business; statutory exceptions may still apply. Checked: 2026-10-16.

  5. Labeling Controls — W3C Web Accessibility Initiative

    Supports associating a label with its input field, positioning labels above fields and providing mobile input assistance. Does not measure conversion or provide evidence for a particular form. Checked: 2026-10-16.

  6. User Notification — W3C Web Accessibility Initiative

    Supports clear error and success messages, notices next to the affected field and an explanation of the correction needed. The source does not test inboxes or email delivery; the delivery test in this article is a separate practical aid. Checked: 2026-10-16.

  7. Understanding Success Criterion 2.1.1: Keyboard — W3C Web Accessibility Initiative

    Explains operation through a keyboard interface. Applied in this article to form entry, submission and error correction; does not provide test evidence or a complete WCAG conformance assessment. Checked: 2026-10-16.

  8. Understanding Success Criterion 2.4.7: Focus Visible — W3C Web Accessibility Initiative

    Explains the visible indication of keyboard focus. The example in this article refers to the field or button currently selected; it does not amount to an assessment of a real website. Checked: 2026-10-16.

  9. Easy Checks – A First Review of Web Accessibility — W3C Web Accessibility Initiative

    The page, labelled Draft when accessed, explicitly explains that simple checks identify only some problems and do not replace a full assessment. Cited only to establish this limit. Checked: 2026-10-16.

  10. DSGVO Begriffe einfach erklärt — Wirtschaftskammer Österreich

    Defines personal data and gives names and email addresses as examples. Used in this article in the context of an identified or identifiable person making an enquiry. Checked: 2026-10-16.

  11. Vertragserfüllung als Basis zur Verarbeitung personenbezogener Daten — Wirtschaftskammer Österreich

    Explains necessary steps before entering into a contract, taken at the data subject’s request, and explicitly refers to Article 6(1)(b) GDPR. Does not automatically provide a basis for every contact or additional purpose. The EUR-Lex legal text could not be read when accessed directly in a separate check. Checked: 2026-10-16.

  12. Einwilligung als Basis zur Verarbeitung personenbezogener Daten — Wirtschaftskammer Österreich

    Supports freely given, specific and informed consent expressed through a clear affirmative action. The WKO page treats a newsletter as a separate case requiring consent. Does not provide a complete guide to advertising law or a specific consent statement. Checked: 2026-10-16.

BrandHoop · English edition for Austria · Practical guide