Most businesses do not have a lead problem. They have a form problem. Someone was interested enough to click, landed on a wall of questions written for the convenience of whoever built it, and left. Learning how to create an online form properly is one of the cheapest improvements available to a small business, because the traffic is already there.
An online form is a small machine with one job: turn an interested stranger into a record you can act on. That record might be an enquiry, a booking, an order, a registration, a signed waiver or a paid invoice. The mechanics are the same every time, and once you understand them you can build any of these in an afternoon.
This guide covers the whole path — deciding what the form is for, choosing the type, writing fields that get answered, adding logic, designing for the phone, taking payments, publishing and embedding it, handling what comes after submit, and reading the responses well enough to improve the thing next month.
What an online form is, and what it replaces
An online form is a page of questions that writes answers into a structured list you own. That sounds obvious until you compare it with what most small businesses do instead: back-and-forth email, direct messages, phone notes on the back of a receipt, and a spreadsheet somebody updates from memory on Friday.
The value is not the questions. It is the structure. When every enquiry arrives with the same fields in the same order, you can sort them, filter them, count them, follow up on them in batches and spot the week you got twice as many. Unstructured enquiries cannot be managed, only survived.
The second thing an online form replaces is your availability. A form works at 11pm on a Sunday when you are asleep and the customer is deciding. Anything you handle by conversation only happens while you are awake and holding your phone.
- Email threads that lose details in the middle
- Direct messages you cannot search three weeks later
- Paper sign-up sheets that have to be typed up
- Phone calls where you did not write down the postcode
- Spreadsheets filled in by hand from all of the above
Start with the decision the form has to produce
Before you add a single field, write down the sentence that follows a submission. Not the topic — the action. For example: I will send a quote within one working day. I will confirm a Tuesday slot. I will post the parcel. I will add them to the class list.
That sentence tells you which fields are genuinely required, because a required field is any field you cannot complete the sentence without. Everything else is curiosity. Curiosity is expensive: in our experience each extra question costs you a slice of completions, and the questions nobody reads afterwards cost you those completions for nothing.
It also tells you what the form is not for. A quote request does not need a full project brief; it needs enough to price a call. Save the deep questions for after somebody has said yes, when they are far more willing to answer them.
Types of online form, and which one you need
Most online form examples fall into a handful of shapes. Naming the shape you need saves you from designing from scratch, because each shape has a known set of fields and a known failure mode.
Pick the closest shape, then adapt. A booking form and an order form look similar but behave differently: one is constrained by your calendar, the other by your stock. An event registration form is an order form with a capacity limit and a check-in list attached.
If two shapes are fighting inside one form, that is usually a sign you need two forms with two links. Trying to make one page serve enquiries and payments and bookings is how you end up with something nobody finishes.
- Contact or enquiry form — name, contact, one open question
- Lead capture form — a short trade for a guide or a quote
- Quote request form — enough detail to price without a call
- Order form — items, quantities, delivery, payment
- Booking form — service, date, slot, deposit
- Event registration form — ticket type, attendee details, capacity
- Application form — longer, structured, often with file upload
- Feedback or survey form — short, anonymous-friendly, one screen
- Waiver or consent form — signature, date, stored securely
Form fields explained: which type to use when
The field type you choose decides how much work the person has to do. A free text box makes them think and type; a set of choices makes them tap once. Where an answer belongs to a known set, never make them type it. Typing on a phone is the single biggest source of drop-off in a long form.
Use short text for names and reference numbers, email and phone types so mobile keyboards switch correctly, dropdowns when there are more than about six options, radio buttons when there are fewer and you want them all visible, and checkboxes only when multiple answers are genuinely allowed.
Reserve the long text box for the one question that actually needs prose. One good open question — tell me what you need and when — beats five narrow ones, because people explain their situation better in their own words than in your categories.
- Short text: name, company, reference
- Email and phone: use the typed fields so keyboards adapt
- Number and currency: quantities, budgets, amounts
- Dropdown: long known lists such as service or country
- Radio: two to six visible options, one answer
- Checkbox: multiple answers, plus consent boxes
- Date and time: bookings, deadlines, event dates
- File upload: photos of the job, briefs, documents
- Hidden field: which page or campaign the person came from
How many questions to ask on an online form
The honest rule is that a form should be as short as the next step allows, and no shorter. Cutting a form to two fields is not automatically better if it leaves you unable to reply usefully and you end up in an email thread anyway.
A practical test: for every field, ask what changes if the answer is missing. If the answer is nothing, delete it. If the answer is I would have to ask them, keep it. If the answer is it would be nice to know for reporting, make it optional and expect half of them to be blank.
Where a form genuinely needs to be long — an application, a detailed brief, an intake questionnaire — split it into steps with a progress indicator. Multi-step forms feel shorter than they are, because people judge length by what is on screen, not by what is coming.
Conditional logic: one form, many paths
Conditional logic is what separates a form that works for one customer type from a form that works for your whole business. It shows or hides questions depending on earlier answers, so nobody sees questions that do not apply to them.
A cleaning company can ask one question — home or office — and branch into two different sets. A photographer can ask about guest count only when someone chooses wedding. A repair shop can ask for the model number only after the device type is picked. Each person sees a short, relevant form; you receive rich, sorted answers.
Logic can also route the outcome, not just the questions. Send commercial enquiries to a different inbox, show a different confirmation message, or skip payment for an option you quote manually. Build the branches after the basic form works, or you will spend an hour debugging rules on a form that was wrong anyway.
- Show or hide fields based on a previous answer
- Skip whole steps for people who do not need them
- Change the price or deposit shown by option chosen
- Route notifications to the right person or inbox
- Send a different confirmation message per path
How to create an online form people finish on a phone
Assume the phone. Most forms are now opened from a link in a bio, a message, a QR code on a counter or an email read while somebody is standing up. A mobile friendly form is not a nice extra here; anything that requires pinching, horizontal scrolling or precise tapping will lose you completions before the first answer.
Keep one field per row, make tap targets large, label fields above the input rather than inside it so the label does not vanish when typing starts, and let the page breathe. A form that looks like it takes one minute gets treated like it takes one minute.
Test it the way a customer will: open your own link on your own phone, on mobile data, standing outside. You will find the field that triggers the wrong keyboard, the dropdown that scrolls badly and the submit button hidden under the browser bar in about ninety seconds.
How to create an online form that takes payments and bookings
The most useful upgrade to any online form is finishing the transaction inside it. An online form with payment turns an enquiry into revenue in one sitting: the person answers your questions, sees the total, pays, and you get a single record containing both.
There are three common patterns. A fixed price form, where everyone pays the same. A calculated form, where the total comes from the answers — number of guests, size of job, chosen add-ons. And a deposit form, where you take a smaller committing amount now and the balance later. Deposits are especially effective for services, because they filter out people who were never going to show up.
Bookings add a calendar constraint on top: the form shows real availability, holds the slot while the person completes, and blocks it once paid. Event registration adds capacity: a ticket count that decrements, closes at zero and can push the next person onto a waitlist. Both are still forms — they just have a number they must respect.
Validation and error handling that does not lose people
Validation exists to stop bad data, but badly done it stops good customers. The classic failures are all avoidable: rejecting a phone number because of a space, wiping the whole form on one error, showing a red message at the top of a long page with no indication of which field caused it.
Validate gently and in place. Check the field when the person leaves it, put the message directly under that field, say what to do rather than what went wrong, and never clear answers they already gave. Accept the messy formats people actually type and clean them up on your side.
Be careful with required fields too. Marking everything required feels safe and costs you completions on questions you did not need. Mark only what the next step requires, and let the rest be optional.
- Show errors next to the field, not only at the top
- Never wipe entered answers on a failed submit
- Accept spaces, dashes and country codes in phone numbers
- Write messages as instructions: add an email so we can reply
- Disable the submit button while sending to prevent doubles
How to publish and embed an online form
A finished form is worthless until it is somewhere people meet it. You have three ways to publish, and most businesses should use all three. The hosted link is the flexible one: it works in a social bio, an email signature, a text message, a printed flyer or a QR code, and it needs no website at all.
The embed puts the form inside a page on your own site so the person never leaves your domain. This usually converts slightly better for people already reading your page, and it lets the form inherit its surroundings. If you want to know how to put a form on your website, this is the snippet you paste — one block of code into the page or a widget block in your site builder.
The QR code is the offline bridge. Printed on a counter card, a van, a menu, a receipt or an event badge, it takes a physical moment and turns it into a structured record. Use a code that points at a link you can re-target later, so reprinting is never required when the form changes.
What happens after submit: confirmations and notifications
The submit button is the middle of the process, not the end. Three things should happen automatically. The person sees a confirmation page that tells them what happens next and by when. They get an email that repeats it, so they have a record with your name in their inbox. You get a notification that contains enough of the answers to act without opening a dashboard.
Confirmation pages are wasted real estate in most businesses. The person is at peak trust — they have just committed. Use that space for the genuinely useful next step: how to prepare, what to have ready, a link to book the call, or the one related thing they will need anyway.
Set expectations you can keep. We reply within one working day is better than an immediate promise you break twice a week. If you go quiet longer than the confirmation promised, the enquiry is usually gone before you get back.
Spam, privacy and consent
Any public form will eventually get bot submissions. Use whatever invisible protection your builder offers first, because visible puzzles cost you real people as well as bots. Simple deterrents — a hidden field bots fill in and humans cannot see, or a minimum time-to-complete — remove most of the noise without adding friction.
On privacy, collect the minimum and be explicit about what happens to it. Add a plain-language line near the submit button saying what you will use the details for, and a separate, unticked checkbox if you also want to add them to a mailing list. Marketing consent should never be bundled into the act of enquiring.
Keep the data somewhere you can export and delete from, and know how you would answer if somebody asked you to remove them. That is both good practice and, in most places, a legal expectation.
Analysing responses and improving the form
Four numbers tell you almost everything. Views: how many people opened the form. Starts: how many typed anything at all. Completions: how many submitted. And, for forms with money attached, paid completions. The gaps between these numbers point at the specific problem.
A big gap between views and starts is a message problem — the form opens and does not look worth the effort, or the first field is intimidating. A big gap between starts and completions is a friction problem — length, a broken field, a required question people will not answer, or a payment step that scares them. Fix one thing at a time and watch the number that should have moved.
Then look at the answers themselves. The questions everybody leaves blank should be deleted. The clarifications you keep having to email about should become a field or a better label. A form is not a thing you build once; it is a thing you edit every few months as you learn what people actually ask you.
If you want all of this in one place — the form, the logic, the payment, the QR code and the responses — you can build it free at onesol.io and share it as a single link.