Someone lands on your site, decides they want to book, and then hits your form. Twelve fields. Company name, VAT number, preferred date, backup date, how they heard about you. They close the tab. You never know they existed.

The leak is real, even if you can’t see it

You won’t find an abandoned form in your inbox. There’s no notification that says “someone nearly bought.” The only signal is a conversion rate that feels lower than it should be — and most people blame the traffic, not the form.

Here’s a rough way to sense-check your own numbers. Take last month’s form page visits from Google Analytics. Multiply by your completion rate. Now imagine that rate was ten points higher. How many extra enquiries is that? At your average job value, what’s the monthly revenue difference?

Run it. Most people are surprised.

Why long forms fail

Every field is a micro-decision. Each one asks the person to stop, think, and type. Some fields also feel intrusive before trust is established — asking for a VAT number before you’ve even spoken is the equivalent of asking someone their salary in the first ten seconds of a meeting.

The person filling in your form has already decided they’re interested. Your job at that moment is not to gather data. It’s to get them over the line so a conversation can happen.

The fix: three fields, then a sequence

Cut your form to this:

  • Name — first name is enough
  • Phone or email — whichever they prefer
  • One need field — a single open line: “What do you need help with?”

That’s it. Submit. Done.

Everything else — company size, preferred dates, budget range, how they found you — gets gathered afterwards, either by a human on the first call or by an automated follow-up sequence that asks one question at a time over the next 48 hours.

People answer follow-up questions readily once they’ve committed. The form is the commitment. Don’t put the interrogation before the commitment.

What the follow-up sequence looks like

If you’re using something like Make (formerly Integromat) or n8n, the pattern is straightforward. A form submission triggers a webhook. The webhook fires a short SMS or email sequence. Each message asks one thing.

A bare-bones Make webhook listener looks like this:

POST https://hook.eu1.make.com/YOUR_WEBHOOK_ID
Content-Type: application/json

{
  "name": "Sarah",
  "contact": "07700900123",
  "need": "Monthly bookkeeping for a 3-person team"
}

From there, your scenario routes to an SMS tool (Twilio, for instance) and sends:

Hi Sarah — thanks for getting in touch.
One quick question before we speak:
Roughly how many transactions does the business process each month?
Reply here and we’ll have everything we need for the call.

That single reply gives you more useful context than a dropdown field ever would, because it’s in the person’s own words.

The key field name to watch in your form tool is usually submission_data or form_response — check your platform’s webhook payload docs to confirm the exact key your “need” field sends through, then map it in Make’s module as {{1.need}} (or whatever your field label resolves to).

A real example to anchor this

Walk On The Wild Side Reptiles & Aquatics in Ashford launched with a site built by Bad Boy Labs. In month one: 1,500 visits, 39 enquiries, roughly 20 sales and 8 reservations, with 75% of traffic coming from Google. The enquiry form was short by design. The volume of enquiries relative to visits is what a low-friction form looks like in practice.

That’s not magic. It’s removing the obstacles between interest and contact.

Do this today

Open your current booking or enquiry form. Count the fields. If there are more than four, pick the three that are truly essential to getting a conversation started. Archive the rest. Set a reminder to check your completion rate in 30 days.

If you want a follow-up sequence to gather the remaining data automatically, that’s a straightforward automation build — usually a few hours of work once the form is sorted.

If you’d like us to look at your setup, see what a system build involves at our pricing page.