Digitalisation9 min read

Enquiry form: required fields, photos, data protection and what comes next

Which fields should be required, how to ask for photos and the contact method, what the GDPR requires and what should happen after sending. With a test list.

Two hands on a bright marble table: one finger types a message on a smartphone, next to it an open silver laptop

A customer fills in your form, taps "Send" and sees a grey page with the word "Thanks". They don't know whether someone will call, when, or whether anything arrived at all. On your side, the message may land in your inbox, or maybe in spam. And when it does arrive, half of it is missing.

This article is for small trade and service businesses, and also for self-employed people and founders who want to get enquiries through their website. It covers required fields, the contact method, photos, data protection and what happens after someone clicks send. Which details you need before a quote is covered in the article Before the quote. Here it's about how to ask for them in the form.

In short

  • Few required fields: name, email address, preferred contact method and the request. Everything else is optional if you don't need it for the first step.
  • Let people choose how you get back to them: by email or by phone. The phone number is only required if someone wants a call.
  • Photos optional, with a clear request: no people, no documents with names.
  • Data protection: According to the GDPR (in German: DSGVO), when you collect the data you tell people what you use it for, how long you keep it and who receives it.
  • After sending, the customer sees what happens next, and on your side a person reads every enquiry.

Required fields: as few as possible, as many as necessary

Every required field is a hurdle, and every field is data you are responsible for. The GDPR calls this data minimisation: according to Art. 5(1)(c), personal data must be "adequate, relevant and limited to what is necessary in relation to the purposes for which they are processed".

So the question for every field is: do I need this to get in touch for the first time? A suggestion for a small trade business:

FieldRequired?Why
NameyesSo you know who you are talking to.
Contact method (email or phone)yesSo you get back to them the way the customer wants.
Email addressyesFor the reply, and as a second route if a call doesn't work.
Phone numberonly for "by phone"Otherwise optional.
RequestyesWithout it you don't know what it's about.
Town or postcodedepends on your businessIf you otherwise can't decide whether the journey fits.
PhotosnoHelpful, but not everyone has them to hand.
Time frame, budget rangenoGood to know, but no reason to let an enquiry fail.

Date of birth, a full postal address or "How did you find us?" as required fields don't belong in a first enquiry. You can clarify that later in conversation.

And make the requirement visible. According to the W3C's Web Accessibility Initiative, forms should indicate which fields are required and which are optional, ideally in the text of the field label itself. A placeholder in the field is not a replacement for a label. If something is missing, the error message says exactly which field and what is missing. "Error in form" helps nobody.

Let people choose the contact method

Some customers want a call, others can't talk on the phone during the day and would prefer an email. So ask in the form "How should we contact you?" with two options, "By email" and "By phone". The phone number only becomes a required field when someone chooses "By phone". Otherwise it stays optional, with the short note: "Needed if we should call you." That fits data minimisation, and the customer knows what to expect.

Test both: anyone who chooses "By phone" and leaves the number empty gets a friendly hint. Anyone who chooses "By email" doesn't have to give a number.

If you call back, say in the form or in the confirmation roughly when. How to promise and keep callbacks is covered in Organising callbacks.

Photos: helpful, but in moderation

For many trades a photo says more than three sentences: the crack in the wall, the fuse box, the rating plate of the heating. But photos often also show personal things, such as faces or names on letters in the background. This keeps it manageable:

  1. Optional. Anyone without photos should still be able to send.
  2. Limited. A few pictures are enough for a first impression. Set a maximum file size.
  3. With a request next to it. For example: "Please no people and no documents with names or addresses."
  4. Keep location in mind. According to Stiftung Warentest (a German consumer testing organisation), photo files can contain metadata such as date, time, camera model and, if available, GPS coordinates. You don't need that for an enquiry. A short note in the form can help, or you only ask for photos after your first reply.
  5. Don't store them publicly. Uploaded pictures don't belong in a folder anyone on the internet can open. Ask whoever looks after your website where the files end up.

Without an upload, a sentence like this is often enough: "You can send photos by email after our first reply."

Data protection: what you need to clarify for your form

Note: This section gives an overview and does not replace legal advice. As of: November 2026.

A form collects personal data, so the GDPR applies. You should be able to answer five questions:

1. What for, and on what legal basis? According to Art. 6(1)(b) GDPR, processing is lawful among other things if it is necessary "in order to take steps at the request of the data subject prior to entering into a contract". Whether that fits your form, and whether you need separate consent for other purposes such as a newsletter, is something you clarify with your privacy policy or with professional advice.

2. Inform people when the data is collected. According to Art. 13 GDPR, "at the time when personal data are obtained" you tell people, among other things, who is responsible, what the data is used for, who receives it and how long it is kept. The Datenschutzkonferenz (DSK, the joint body of the German data protection authorities) adds: if you refer to information available electronically, it must be easy to find. For your form this means: a visible link to your privacy policy right next to the send button.

3. Who receives the data? If a form service, your web host or an email provider processes the enquiries, they are recipients. According to Art. 13(1)(e) GDPR, recipients or categories of recipients belong in the information. Check whether your privacy policy names the services you use.

4. How long do you keep it? Art. 5(1)(e) GDPR requires that data permits identification for no longer than is necessary for the purpose. Set a simple deletion rule for enquiries that don't lead to a job. If an enquiry turns into a job, retention obligations may apply.

5. How secure is the route? According to Art. 32 GDPR you take appropriate technical and organisational measures. As an example, the article explicitly names the encryption of personal data. In practice this means: the website runs over https, the mailbox has a good password, and only those who handle enquiries have access.

What should happen after sending

For the customer the work ends with the click. For you it starts there. This sequence helps:

  1. Confirmation on the page. The customer immediately sees that the enquiry has arrived, how you will get back to them (the way they chose) and roughly when. If they gave a preferred date: say clearly that this is not yet a fixed booking.
  2. Notification for you. The enquiry goes to an address that is read every day, ideally with a notification on your phone.
  3. A person reads and checks. Even if enquiries are transferred automatically into a list or your trade software: one person checks whether the details are correct, whether it's spam and what happens next. The form should not automatically accept, decline or assign appointments.
  4. An entry on a list. Every enquiry ends up somewhere you can find it again: callback list, spreadsheet or software. With date, contact method and status.
  5. Reply via the chosen route. Whoever wanted an email gets an email. Whoever wanted a call gets a call.
  6. Clean up. Enquiries that come to nothing are deleted according to your rule, photos included.

A fictional example of the text after sending:

Thank you, your enquiry has arrived. We will get back to you by Friday, the way you chose: by email or by phone. Your preferred date is not yet fixed; we will agree it with you.

Only write a time you can keep. A later day that holds is better than "right away" and then not.

Checklist: test your form once a month

  • Test enquiry from your phone, with a different email address, once with "by email" and once with "by phone".
  • With "by phone" and no number, an understandable hint appears.
  • Required fields are marked in the label, and there are no more than necessary.
  • A photo from your phone can be uploaded, if you offer an upload.
  • After sending, the page says what happens next.
  • The enquiry arrives, with the right person, not in spam.
  • The link to the privacy policy sits right next to the send button and works.
  • The privacy policy names the services you really use and your deletion rule.
  • Old test enquiries and enquiries without a job are deleted.

Many website builders and trade software programs already have forms with these functions built in. Then you only set up what's missing.

How we can help

We look at your form and the route behind it with you: which fields are too many, where do enquiries end up, who reads them? Often a few changes to your existing form are enough. If your website builder or trade software can already do this, we'll tell you. In the area of Website & visibility we build forms that fit your processes, and in the area of Automation we set things up so enquiries land on your list in an orderly way and you get notified. We support you with data protection, but we do not replace legal advice.

In the initial consultation we look together at where enquiries get stuck for you and which simple step helps first.

#Anfrageformular#Kundenanfragen#Datenschutz#Website#Handwerk

Sources & further reading

  1. Datenschutz-Grundverordnung (EU) 2016/679, Art. 5, 6, 13 und 32 (EUR-Lex) eur-lex.europa.eu
  2. Datenschutzkonferenz (DSK): Kurzpapier Nr. 10, Informationspflichten bei Dritt- und Direkterhebung (PDF) datenschutzkonferenz-online.de
  3. W3C Web Accessibility Initiative: Form Instructions w3.org
  4. Stiftung Warentest: So entfernen Sie Metadaten aus Bildern test.de