Contact form best practices: fields, wording, and what to skip
A good contact form has three to five fields: name, email, an optional topic dropdown, and a message box. Everything else — phone, company, budget, 'how did you hear about us' — belongs on a sales or intake form, not a contact form. Tell people when they'll hear back, confirm receipt on the thank-you screen, and never make the message box the only large field on a page of required extras.
The contact form is the lowest-commitment form on your site. Someone has a question and wants to ask it — that's the whole transaction. Every best practice below follows from one principle: remove anything that stands between the visitor and hitting send.
Which fields belong on a contact form?
| Field | Field type | Keep it? |
|---|---|---|
| Name | Short text | Yes — required |
| Yes — required, it's how you reply | ||
| Topic / reason for contact | Dropdown | Yes if messages go to different people; otherwise skip |
| Message | Long text | Yes — required, make it the visual focus |
| Phone number | Phone | Optional at most; require it and watch submissions drop |
| Company name | Short text | Skip — ask in your reply if it matters |
| Budget / company size | Dropdown | Skip — this is a lead-qualification question, not a contact question |
| How did you hear about us? | Dropdown | Skip — adds friction for zero value to the visitor |
What does good contact form wording look like?
- Heading: 'Get in touch' or 'Questions? Send us a message' — plain beats clever.
- Above the form: 'We reply within one business day.' A response-time promise is the single most reassuring sentence you can add.
- Topic dropdown: 'What's this about?' with options like Support, Billing, Partnerships, Press, Something else.
- Message field label: 'How can we help?' with placeholder text showing a real example, not instructions: 'e.g., I'm trying to export my data and getting an error…'.
- Submit button: 'Send message' — not 'Submit', which describes the database operation, not the human action.
- Thank-you screen: 'Got it — we'll reply to you at the email you provided within one business day. For urgent issues, call us at…'.
Route with a dropdown, not with multiple forms. One 'What's this about?' dropdown that directs Support, Billing, and Partnerships messages to the right inbox beats maintaining three separate contact pages — and with conditional logic you can show a follow-up field (like an order number) only when 'Billing' is selected.
How should you handle spam without punishing humans?
Spam is the classic excuse for hostile contact forms. Before reaching for an aggressive CAPTCHA, try gentler defenses: required email validation filters out the laziest bots, a topic dropdown breaks single-purpose spam scripts, and reviewing submissions in a dashboard (rather than piping raw form mail to your inbox) keeps junk contained. If you do add a CAPTCHA, use an invisible or one-click variant — making a human decode blurry crosswalks to ask you a question is a tax on your most interested visitors.
What are the most common contact form mistakes?
- Requiring a phone number. Many people would rather not be called, and a required phone field tells them a sales call is coming.
- Ten fields for a one-sentence question. If your contact form looks like a job application, visitors will email you instead — or no one at all.
- No confirmation. A form that just resets after submission leaves people wondering if it worked, and you'll get duplicate messages.
- No response-time expectation, which guarantees follow-up emails asking 'did you get my message?'
- A message box three lines tall. Make the long-text field generous; it signals you actually want to read what they have to say.
- Generic error messages. 'Something went wrong' helps nobody — inline validation should say exactly which field needs fixing.
- Hiding the form behind 'Contact' → another page → a click-to-reveal. Every extra step sheds real messages.
A contact form checklist before you publish
- Three to five fields, with only name, email, and message required
- Response-time promise visible above or below the form
- Email field uses a real email type with inline validation
- Topic dropdown wired to route or tag messages (if you need routing)
- Thank-you screen confirms receipt and repeats the response time
- Tested on a phone — fields large enough to tap, no horizontal scrolling
- Test submission sent and received by the right person
If your site doesn't have a form back end, a free builder like Formkii lets you build the form, embed it on any page (or link to it), get notified of new submissions, and keep every message in one dashboard with CSV export — no code required.
Frequently asked questions
How many fields should a contact form have?
Three to five: name, email, message, and optionally a topic dropdown. Contact forms are low-commitment by nature, so every additional field — especially required ones like phone number — measurably discourages people from sending the message.
Should a contact form require a phone number?
No. A required phone field signals an unwanted sales call and stops privacy-conscious visitors from submitting. If some conversations genuinely need a call, make the field optional and label why: 'Phone (optional — only if you'd prefer we call).'
What should the thank-you message say after someone submits?
Confirm the message was received, say when they'll hear back, and offer an urgent-path alternative if one exists. For example: 'Got it — we reply within one business day. For urgent issues, call us at (555) 010-0199.'
How do I stop contact form spam?
Start with email validation and a topic dropdown, which defeat most basic bots, and review submissions in a dashboard instead of raw email. If spam persists, add an invisible or one-click CAPTCHA rather than an image puzzle that frustrates real visitors.