Which fields should a contact form for German prospects ask for?

1. A form is part of the offer

When a prospect reaches a form, they are deciding whether the company understands their situation. A field should therefore have a clear job: identify the person, classify the request or provide context for the first reply.

Four core fields are enough for many first contacts: name or company, email, request type and message. Phone, budget, project address, schedule and uploads are useful only where the business genuinely needs them.

2. Choose fields by route

B2B and purchasing: ask for company, intended application, rough quantity or scope, delivery country or region, time frame and optional documents. Technical or on-site service: ask for location or service region, the task, preferred time and optional photos. Hotel and restaurant: link to the real booking or reservation system for standard cases; use a German enquiry form for group requests, events or special requirements.

Do not turn an initial enquiry into a complete tender. If the first human response can clarify the missing detail, let the form stay short.

3. Make the German next step explicit

Use labels that a German visitor would naturally understand, such as Angebot anfragen, Rückruf erbitten or Reservierung anfragen. Tell people what language the reply can use, which channel is monitored and what happens after submission. If the company is abroad, say how German customers are served and where the work or delivery takes place.

Keep an alternative email address or phone route visible. A booking button should go to the actual booking system, not to a decorative page that cannot complete a reservation.

4. Keep the interaction accessible and proportionate

Every field needs a visible label, required fields need a clear mark, and errors should explain how to fix them. On mobile, the keyboard type, spacing and confirmation state matter. If a file is optional, say what it helps with and what formats are accepted.

Data minimisation is a planning principle, not a substitute for checking the real controller, processor, retention and privacy notice for the chosen form service. The page should link to the applicable privacy information before submission.

Checklist for a German enquiry route

• The first screen explains what the form is for.
• Labels and help text are natural German, not literal interface translations.
• The required fields are limited to what the next response needs.
• B2B, service and hospitality routes have different relevant context.
• File upload, phone and budget are optional unless their purpose is clear.
• The success message states receipt and the realistic next step.
• A real booking system is linked for bookings and reservations.
• The form works with keyboard, screen reader and a narrow mobile viewport.

Questions companies ask

Should we require a phone number?

Only if the process genuinely depends on a call or the visitor selects a callback. Otherwise an email route can lower friction without removing useful context.

Should every German prospect use the same form?

No. A manufacturer, a technical service company and a hotel have different decisions to support. Reuse the design language, but let the fields follow the actual route.

Can the form qualify every lead automatically?

It can collect helpful context, but it should not create false precision. A short form and a clear human follow-up are often more useful than a long questionnaire.