Contact forms that do not quietly lose your leads

Fibvo editorial · 17 July 2026 · 5 min read

A freight forwarder's sales head notices that website enquiries have dried up, although traffic looks normal. The team eventually finds that the form's notification emails have been going to spam for weeks. Nobody noticed, because the form still showed 'Thank you' on screen. Contact forms fail in small, silent ways, and each failure costs an enquiry you worked to attract.

Ask only for what the first reply needs

Every field is a small decision, and some visitors stop at the one they cannot or will not answer. Ask one question of each field: do we need this to send a useful first reply? If not, collect it later in the conversation.

For a freight quote, that might be name, email or phone, origin, destination and a free-text box for cargo details. Company turnover, designation and how they heard about you can wait.

• Label optional fields as optional instead of leaving people to decode asterisks.
• Let people choose phone or email when either would do, instead of requiring both.
• Use a dropdown only where the answers are genuinely limited; a few typed words beat scrolling a long list.
• Set the correct input types and autocomplete attributes, so phones show a number pad for phone fields and can fill in name and email automatically.

Write errors that help people finish

Many forms reject valid input. A phone field that refuses a number typed with a +91 prefix and spaces, or an email check that does not recognise a newer domain ending, turns a willing buyer into an annoyed one. Accept the formats people naturally type, then tidy the data on your side.

• Show each error next to the field it concerns, not only in a banner at the top.
• Say what is wrong and how to fix it: 'Enter a phone number, including country code for numbers outside India' rather than 'Invalid input'.
• Check a field when the person leaves it, not on every keystroke.
• Never clear the form when a submission fails. Retyping a long message is exactly where people give up.

Confirm the enquiry and make sure it arrives

After a successful submission, send people to a dedicated thank-you page. A separate page reassures the visitor, gives you a dependable point to record a key event in GA4 or a conversion in Google Ads, and leaves room to say what happens next: who will reply, through which channel and by when. Follow it with an automatic email repeating the details they sent.

The less visible risk is delivery. Some form setups send the notification with the visitor's address in the From field. Receiving servers use SPF, DKIM and DMARC to check whether a message really comes from the domain it claims, so a message claiming to be from Gmail but sent by your web server fails and may be rejected or filed as spam.

A thank-you message on screen proves only that the button worked, not that anyone received the enquiry.

• Send notifications from an address on your own domain, such as enquiries@yourcompany.in, and put the visitor's address in the Reply-To field.
• Send through an authenticated mail service instead of the web server's default mail function, with SPF, DKIM and DMARC set up for your domain.
• Store every submission in the website database, a connected sheet or your CRM as well as emailing it, so a delivery problem never means a lost lead.
• Submit a test enquiry every week, and again after any change to the site, its plugins or its hosting.

Stop spam without stopping customers

Once a form is live, bots find it. Heavy protection such as image puzzles also stops real people, especially on small screens, so layer lighter checks instead.

• A honeypot: a hidden field that people never see and bots fill in. Hide it from screen readers and keyboard users too, and discard any submission where it is filled.
• A time check that rejects forms completed faster than a person could read and type.
• A score-based or invisible challenge, such as Cloudflare Turnstile or Google reCAPTCHA, which only asks for a test when behaviour looks automated.
• Server-side filters for obvious junk, such as messages stuffed with links.

Whatever you use, say in your privacy notice what the form collects and why. India's DPDP Act 2023 is bringing in its notice and consent duties in phases under the DPDP Rules 2025, and the GDPR covers visitors in the EU, so build to that standard now. Keep newsletter sign-up as a separate, unticked checkbox.

Reply while the buyer is still deciding

A form only starts the sale. Buyers who request quotes often contact several suppliers at once, and the first useful reply shapes the shortlist. Speed depends less on effort than on routing.

• Send each enquiry to a named person, or to a shared inbox with a clear owner, not a general address that everyone assumes someone else checks.
• Copy a second person on every notification, so leave, travel or a busy day does not hold up the reply.
• Route by the answers in the form where it helps: export enquiries to the export desk, spare parts requests to service.
• Push an instant alert to the owner's phone through your CRM or email app during working hours.
• Set an out-of-hours auto reply that says when the team will respond, so a Saturday evening enquiry is not met with silence.

Once a month, compare the enquiries received with the replies sent: who responded, how quickly, and which enquiries were never answered. Fix those gaps before spending more on bringing visitors to the form.

---

Written by Fibvo — Bengaluru and Erode, India — working with clients in other time zones. Questions, or think we have it wrong? Tell us.