New format
Website feedback form: goals, fields, and placement rules
A feedback form is a simple module: name, contact, request gist. In practice it drives leads, response speed, and trust in the site.
Below: form goals, field structure, placement, antispam, and handling rules — with a focus on clear UX and message delivery, not another widget for the checklist.
Form goals and jobs
The form is a “visitor → team” channel. It doesn’t replace phone and messengers, but it logs the request in one place and lowers the barrier to reach out.
Typical jobs:
- questions, complaints, suggestions
- product or service requests
- callback
- contact capture for a list (with personal-data consent)
- lead qualification surveys (topic, budget, region)
How messages are delivered
Classic path: after submit, mail goes to the admin via hosting SMTP or a transactional service. Set SPF/DKIM/DMARC or leads die in spam.
Second path — write to a CMS or CRM database: handy for shops, queues, and reports. CRM + notification is usually safer than email alone.
Check at launch:
- a test request reaches the inbox and/or CRM
- a backup channel (messenger/phone) exists if mail fails
- send errors are logged on the server
Field structure
Mark required fields clearly. Validate in the browser and on the server. Name, contact, and request text are the base; phone for a call — only if you actually call.
Common set:
- name
- email and/or phone
- topic (dropdown)
- message / task description
- optional attachment (size and format limits)
- personal-data processing consent checkbox
Form type and field focus
| Scenario | Minimum fields | Don’t overcomplicate |
|---|---|---|
| Callback | Name + phone + convenient time | A long essay |
| Support question | Contact + gist + page/order | Ten required fields |
| Service request | Contact + service + city/deadline | Full brief before first reply |
Where to place the block
A dedicated contacts page suits a full form. On commercial pages — a short “leave a request” block next to the offer.
On a landing the form often sits in the first screen or right after the benefit. A full form in every footer rarely helps: better a compact “call me back” or a button to contacts.
Working placements:
- Contacts
- service and category cards
- end of a blog article with an offer
- landing — by the CTA
- modal on click (don’t pop aggressively on entry)
Spam protection
Captcha, honeypot field, per-IP rate limits, server checks on required fields — the base set. Old captcha scripts get bypassed; update protection with the CMS.
Antispam minimum:
- server checks, not only JS
- honeypot or invisible captcha
- submit rate limit
- filter links/stop-words in the message (carefully, avoid false positives)
How to raise completion rate
A short headline (“Leave a request” / “Ask a question”), a clear reply window, and a live contact nearby. After submit — a thank-you with expectations, not an empty “success.”
What strengthens the form:
- few required fields
- mobile layout and large inputs
- a reply-time promise you keep
- a backup channel (phone, messenger)
- a polite auto-reply and a real manager response
Short takeaway
A form works when it has a clear goal, short fields, a sensible place on the site, spam protection, and a reply process. Technically it’s HTML + server handling; in meaning — a dialogue promise the team must keep.
FAQ
Where’s the best place for the form?
On Contacts, on a service card, and at the end of strong landings. On a landing — next to the offer. Duplicating a full form on every page usually adds noise.
How many fields should the form have?
The minimum for the job: name + phone or email + gist. Extra required fields cut conversion; details can wait until after first contact.
Where do submissions go: email or CRM?
Both work. More reliable: write to CMS/CRM + email/notification to the manager. Make sure mail doesn’t land in spam.
Do I need a captcha?
Yes if there’s spam. Modern bots beat simple image captchas — better honeypot, rate-limit, server checks, and current protection (including invisible captcha from a provider).
What should I show after submit?
A short confirmation and a real reply window (“we reply in business hours within N hours”). Promising “within an hour” without a process kills trust.
Need a site form that actually delivers leads?
We’ll set short fields, antispam, and delivery to CRM/email — with a reply window the team can keep.
Discuss the task
