Help · Leads and lead capture
Form fields, mapping and required rules
What each field on a form does, where its answer lands on the lead, and the trade-off behind every field you add — each one collects more and converts less.
Updated August 2026
A form is a trade: every field collects more information and costs you some submissions. Getting that balance right matters more than any styling decision.
The second half is mapping — making sure an answer lands on the right field of the lead rather than in a note nobody reads.
Who this is for
Anyone building lead capture forms.
Before you start
- Permission to create and publish forms.
- A clear idea of what happens to a submission next — that is what decides which fields you actually need.
Map fields, do not just collect them
A question whose answer is not mapped to a lead field arrives as text nobody filters or reports on. Mapping is what turns 'company size' from a sentence in a submission into a field you can score, route and segment by. An unmapped question is barely better than not asking.
Build the form
- Start from what happens next
If a submission goes straight to a rep for a call, you need very little. If it feeds routing and scoring, you need the specific fields those rules read. - Ask for name and one contact route
A lead needs a name and at least one of email or phone. That is the genuine minimum — everything beyond it is a choice. - Pick the right field type
There is a wide range of field types. A dropdown for known options beats a text box that collects six spellings of the same answer. - Map each field to a lead field
Point the question at the lead field its answer belongs in, so routing, scoring and filtering can read it. - Require only what you cannot proceed without
Every required field costs submissions. Requiring something a genuine prospect cannot answer means you lose them entirely. - Submit it yourself
Fill in your own form and look at the lead it produced. Anything unmapped or mis-typed is obvious immediately.
What you get
- Submissions arriving as structured leads, not free text.
- Fields that routing and scoring can actually read.
- A form short enough that people finish it.
- A tested path from submission to lead record.
Frequently asked questions
What is the minimum a form must collect?
A name and at least one of email or phone — that is what a lead requires. Everything else is a trade between information and completion rate.
What happens to a field I do not map?
The answer arrives as unstructured text rather than on a lead field, so nothing can filter, score or route by it. Map anything you intend to use.
How many fields is too many?
When completion drops. Test with the minimum and add a field only when you can say what decision it changes.
Should I make fields required?
Sparingly. A required field a real prospect cannot answer does not improve your data, it removes the lead.
Related articles
Embed a form on your website
Take a form you've already built in KudosCRM and add it to your own site — either embedded inside a page or as a clean hosted page you link to.
Read articleHow to build a lead capture form
Build a form in the drag-and-drop builder using any of the 13 field types, mark the fields you need, and publish it so every submission lands as a tracked lead.
Read articleRead the submissions inbox
Every form submission lands in one place with its answers and its source. This is where you check that capture is working — and notice when it quietly stops.
Read articleHave an account issue this guide doesn't cover?
Start free today
Ready to give your team a CRM they'll actually use?
Start free. Bring your whole team. Cancel whenever (you won't).