An online form creator is only worth using if every answer lands in a field you can filter, report and automate on. This article answers one question: how do you build your first form on the levelpartner.ai platform so that each answer maps to the right place on the contact record? Get the mapping right and a submission becomes a usable contact, an owner and a next step. Get it wrong and you have a tidy form feeding a pile of notes nobody can search.
Why field mapping decides whether a form is useful
Most form creator tools make it easy to drag in a question. Few make you think about where the answer goes. On the platform, every field on a form is tied to a field on the contact. Standard fields such as first name, email and phone write to the matching contact fields. Anything else needs a custom field, and the type of that custom field decides what you can do with the answer later.
A dropdown with five fixed options can drive a workflow branch, a pipeline choice and a report. A free text box with the same information can only be read by a person. So the first design decision is not how the form looks. It is which answers need to be data, and which can stay as text.
Decide the data before you build
Write down every question you want to ask, then put each one into one of three groups.
- Routing answers: they decide who handles the contact or what happens next. Make these single-choice fields.
- Record answers: they describe the contact and you will filter on them later, such as company size or region. Make these dropdowns, numbers or dates.
- Context answers: useful for the first conversation but never filtered on. A short text box is fine.
If a question fits none of these groups, drop it. The form gets shorter and the contact record stays clean.
Before you start
You need access to Sites and to Settings in your account. Agree with whoever acts on the submissions which answers they actually use. Check the existing custom fields first, because a second field called "Budget" next to an older "Monthly budget" is how reports quietly break. Have the page or link location ready where the form will go.
How to set it up
- Go to Settings, then Custom Fields, and review the Fields tab.
- Click Create field for each answer with no home yet.
- Choose the Field type that matches the answer.
- Enter the Field name, pick a Folder name and click Create custom field.
- Go to Sites, then Forms, and click + Create New Form.
- Start blank, then add Name, Email and Phone.
- Add your custom fields in natural answering order.
- Mark as required only the answers you cannot proceed without.
- Use Styles & Options to set layout, colours and buttons.
- Choose a confirmation message or a redirect after submission.
- Save, preview and submit a test entry.
- Check the entry in the Submissions tab and on the contact.
- Click Integrate to copy the embed code or the form link.
What this replaces in a company with flat revenue
In a 60-person firm, the form usually replaces an email address on the contact page and a person who copies enquiry emails into the CRM. That copying is slow, and it is where details go missing: a phone number typed wrongly, a budget recorded in the notes instead of a field, a source never recorded at all.
When the answers write straight to fields, three things become possible that were not before. A workflow can route and reply the moment the form is sent. You can count enquiries by source and by answer. And your sales lead can filter contacts by the answers that matter, rather than reading notes one at a time.
Imagine a form that sends an email with eight answers, about 30 enquiries a week, and an assistant spending roughly three hours copying them into the CRM. Rebuild it with four custom fields, two of them single choice, and every answer would write straight to the contact. A workflow could then assign each enquiry by service line. Those three hours a week would be free for calling the new leads instead of retyping them.
The running cost is low. Expect to spend half a day on the first form, most of it on deciding fields. After that, a monthly ten-minute check of recent submissions is enough to catch a field nobody fills in properly.
Creating a new custom field for every form. Within a year you have four versions of "service interested in", each filled on a different form, and no single report covers them. Reuse one field across every form that asks the same question.
When not to build a new form
If an existing form already asks most of the same questions, add a hidden field to tell the placements apart instead of building a copy. If the person filling it in is already a client and you need a long questionnaire, a survey that shows one question at a time is usually the better format. Read building an online survey for that case.
For the layout and wording side of the same form, see designing a form people finish. If the form is an enquiry form, the fields worth asking on a lead capture form covers the qualifying question. And when more than one team starts making forms, keeping a growing set of forms under control explains ownership and naming.
Troubleshooting
An answer is missing from the contact. The form uses a generic field that is not tied to a contact field. Swap it for the matching custom field and resubmit a test.
A workflow branch never fires. The condition checks for an option value that was edited after the workflow was built. Open the custom field, copy the exact option text and paste it into the condition.
Every contact shows the same source. The hidden field is set to a fixed value rather than reading the link. Set it to pick up the campaign value from the page address.
Dates arrive in the wrong format. The answer was collected as text. Change the custom field to a date type and the picker will enforce one format.
Frequently asked questions
What is the difference between a form creator and a form builder?
They are the same thing under different names. What matters is whether the answers write to contact fields you can act on, or arrive as an email someone must process.
Do I need a custom field for every question?
No. Use custom fields for answers you will route, filter or report on. Context that is only read before the first call can sit in a single text field.
Can one form feed different pipelines?
Yes. Use a single-choice question as the routing answer and branch the workflow on it, so each answer creates an opportunity in the right pipeline.
Will editing a field break past submissions?
Past answers stay on the contact. Renaming an option can break workflow conditions that check for the old text, so update those at the same time.