Guide · Building & launching
Website forms that convert: a practical guide
Forms are where visitors turn into leads, customers and bookings — and where many of them give up. A form that asks for too much, rejects a phone number because of a space, or shows a cryptic error after submission loses people who were ready to act. Small changes to forms often produce larger improvements than a full redesign.
[ 01 ]
In short
In short
- 01
Ask only for what you need at this step; every extra field costs completions.
- 02
Use clear labels above fields, not placeholders that disappear.
- 03
Validate helpfully: accept common formats and explain errors next to the field.
- 04
Offer alternatives — WhatsApp, a call — for people who prefer not to fill in forms.
- 05
Tell people what happens next, and make sure it does: submissions must reach someone who replies.
[ 02 ]
Guide
How many fields
For an enquiry, name and one contact method are often enough; a short "what do you need?" field adds context. Each additional required field should be justified by what sales actually needs before the first reply. Information needed later can be asked for later — in the conversation or in a second step.
Labels and hints
- Labels above the field remain visible while typing.
- Placeholders can show an example format, but should not replace labels.
- Mark optional fields as optional rather than marking every required field.
- Short hints explain unusual requirements: "We will only use this to reply to you."
Phone numbers and local formats
Azerbaijani numbers can be written in many ways: with or without +994, with a leading 0, with spaces or dashes. The form should accept all reasonable formats and normalise them on the server, not reject them. Use the telephone input type so phones show a number keyboard.
Validation and errors
- Validate as the visitor finishes a field, not on every keystroke.
- Show errors next to the field, in plain language, in the page's language.
- Never clear the form after an error.
- Validate on the server as well — browser checks can be bypassed — and return the same friendly messages.
Multi-step forms
For longer forms — quotes, applications, bookings — splitting into steps with a progress indicator reduces the sense of effort. Put easy questions first; ask for contact details once the visitor is invested.
Spam protection
Public forms attract bots. Use protection that does not burden real visitors: invisible challenges, honeypot fields, rate limits and server-side checks. Visible puzzles should be a last resort.
Messenger alternatives
In Azerbaijan, many people prefer to write in WhatsApp or Telegram. A button next to the form — with a pre-filled message mentioning the page — captures them. Track these clicks as conversions. See messengers for business in Azerbaijan.
After submission
- A clear confirmation on the page: what happens next and when.
- An automatic email or message confirming receipt, if you have the contact.
- Delivery to the CRM or inbox with the source and page, and a notification to the responsible person. See CRM integration.
- A reply within the promised time.
The fastest way to lose leads is a form that sends submissions to an unmonitored inbox. Test forms regularly and monitor delivery.
Privacy
Link the privacy policy next to the form and ask for consent where required, with separate consent for marketing messages. Collect only what you need.
Measuring
Track form starts, submissions and errors; field-level analytics show where people abandon. Test changes with real traffic where volume allows. See A/B testing.
[ 03 ]
FAQ
Frequently asked questions
Should we ask for email or phone?
Ask for the contact method your team actually uses to follow up, and let visitors choose where possible.
Do CAPTCHA puzzles hurt conversions?
Visible puzzles add friction. Invisible or low-friction checks protect most forms without affecting real visitors.
Is a form better than a chat?
They serve different preferences. Offering both — plus a messenger link — lets visitors choose.