How many fields should a contact form have?

Five or six covers most of the examples above. Add a field only when the message cannot be routed or answered without it. Count the fields you would miss if you removed them: anything you would not miss is a field a visitor has to fill in for nothing.

Should contact form fields be required?

Mark a field required only if you cannot act without it. For most contact forms that is a name, an email address or another way to reply, and the message itself. Everything else should be optional, and the label should say so.

Does a contact form need a consent checkbox?

Not for a message you only reply to. If you will add the details to a mailing list or use them for marketing, add a separate checkbox for that purpose and leave it unticked. The visitor has to tick it themselves; a pre-ticked box is not valid consent under EU GDPR rules.

Can one contact form handle every kind of enquiry?

Yes, with a subject dropdown that sorts each message before anyone reads it. Split it into a separate form when one type needs fields the others do not, such as a quote that must ask about scope, or when a different team owns the replies.

← Guides

Contact form examples

A contact form example is a working set of fields for one kind of message. Most websites need one of eight layouts: a basic contact page, a sales inquiry, a support request, a quote request, an event inquiry, feedback, a partnership inquiry or an appointment request. Each example below lists its fields, the field type, whether it is required, and when to use it, with a template you can copy into Seagit Forms.

1. Basic contact form

The default for a website contact page. It asks for enough to reply and nothing more, so a visitor with one question can finish in under a minute. Use it when you do not yet know what the visitor wants.

Name (text, required)
Email (email, required)
Subject (dropdown, optional): general, sales, support, other
Message (long text, required)

Copy this layout: the contact form template →

2. Sales inquiry

For visitors asking about pricing or a demo. Ask for the details that decide whether a sales call is worth booking, not the whole company profile. Use it when the visitor is evaluating a paid product and you want to qualify them before replying.

First name (text, required)
Work email (email, required)
Company (text, required)
Team size (dropdown, optional)
What do you need? (long text, optional)

Copy this layout: the lead capture form →

3. Support request

For existing customers reporting a problem. The category and urgency fields let you sort the queue before anyone opens the message, so the urgent ones are not waiting behind the rest.

Name (text, required)
Email (email, required)
Account or product (text, optional)
Category (dropdown, required)
Urgency (radio, required)
Describe the problem (long text, required)

Copy this layout: the support request form →

4. Quote request

For services priced by scope, such as building work or removals. The price depends on what the work involves, so the form has to collect the scope before you can answer. Use it when a reply without the details would only start a second round of questions.

Name (text, required)
Email (email, required)
Company (text, optional)
Project scope (long text, required)
Budget range (dropdown, optional)
Target start date (date, optional)

Copy this layout: the quote request form →

5. Event inquiry

For a venue, caterer or organiser who needs the date and headcount before they can check availability. Ask for the numbers first, because they decide whether the enquiry is possible at all.

Contact name (text, required)
Email (email, required)
Event date (date, required)
Expected guests (number, required)
Event type (dropdown, required)
Special requirements (long text, optional)

Copy this layout: the venue booking request form →

6. Feedback

For a visitor who has just bought, attended or visited. Keep it short enough that people finish, and make the rating the first thing they answer. Use it when you want a view on the experience, not a support case.

Overall rating (rating, required)
What worked well (long text, optional)
What should we improve (long text, optional)
Email for a reply (email, optional)

Copy this layout: the feedback form template →

7. Partnership inquiry

For brands, suppliers or other businesses proposing to work with you. The partnership type sorts the proposals, and the summary tells you whether a call is worth having.

Company name (text, required)
Website (URL, required)
Partnership type (dropdown, required)
Proposal summary (long text, required)
Contact email (email, required)

Copy this layout: the business partnership inquiry form →

Job applications need a different layout, with a CV upload and screening questions. Use the job application form for those.

8. Appointment request

For a clinic, salon or studio where you confirm the appointment yourself rather than letting the visitor book a live slot. The form takes a request, and you reply with the time that works.

Name (text, required)
Phone (phone, required)
Preferred date (date, required)
Preferred time (dropdown, optional)
Reason for visit (long text, required)

Copy this layout: the appointment request form →

Best practices for any contact form

Field count. Ask only for what you need to act on the message. The examples above run from five to six fields. If a form needs much more than eight, it is usually two forms.
Required fields. Require a field only when you cannot reply or route the message without it. Phone numbers and company names are optional on most layouts.
Spam protection. Every public Seagit form is checked for automated submissions with Cloudflare Turnstile, on by default. Read the spam protection notes for what that does and does not stop.
Confirmation message. Tell the visitor what happens next and when. Promise only a reply time you keep, such as the next working day.
Privacy and consent. If you will use the details for marketing, add a separate checkbox that the visitor ticks themselves, next to a link to your privacy policy. The consent checkbox guide covers the wording. This is a design rule, not legal advice; check the requirements where you operate.
Routing. Give each form a destination before you publish it. Messages can go to Slack, a webhook or Google Sheets. A form nobody reads fails whatever its fields are.

Build one in Seagit Forms

Each link above opens a template with its fields already set up. Copy the layout, then edit the labels to match your business and remove any field you would not miss. Use a dropdown for a choice with several fixed answers, radio buttons for a short list you want visible, and long text for anything that needs a sentence or more. The contact form template is the starting point for a general contact page.

Common questions

How many fields should a contact form have?: Five or six covers most of the examples above. Add a field only when the message cannot be routed or answered without it. Count the fields you would miss if you removed them: anything you would not miss is a field a visitor has to fill in for nothing.
Should contact form fields be required?: Mark a field required only if you cannot act without it. For most contact forms that is a name, an email address or another way to reply, and the message itself. Everything else should be optional, and the label should say so.
Does a contact form need a consent checkbox?: Not for a message you only reply to. If you will add the details to a mailing list or use them for marketing, add a separate checkbox for that purpose and leave it unticked. The visitor has to tick it themselves; a pre-ticked box is not valid consent under EU GDPR rules.
Can one contact form handle every kind of enquiry?: Yes, with a subject dropdown that sorts each message before anyone reads it. Split it into a separate form when one type needs fields the others do not, such as a quote that must ask about scope, or when a different team owns the replies.

Keep reading

Customer satisfaction survey questionsRating and follow-up questions for after a purchase or visit.Double barreled questionsWhy a field that asks two things at once returns answers you cannot use.Spam protectionHow every public Seagit form is checked for automated submissions.GDPR consent checkboxAdding a consent box that the visitor ticks themselves.