NextoraThe web form that looks like it works: why enquiries arrive and the CRM stays empty
Notifications land, submissions pile up, and nothing reaches a record. Wiring answers to fields is a step with a name of its own — and the reason a form is a CRM feature, not a website feature.
Key takeaways
- A web form has two jobs, collecting answers and filing them as a record, and they fail independently.
- The number to check in any form builder is how many answers out of how many reach a field on the record.
- Answers with no standard field deserve custom fields of their own, so they can be filtered later instead of buried in a message blob.
- Form views, submissions and conversion rate show whether a form has a field problem or a placement problem.
Here is a failure mode almost every team has lived through. The website form is up. The notification emails arrive. Submissions accumulate in some list. And three weeks later somebody asks how many enquiries came in last month, and the CRM has nine leads while the form has ninety submissions.
Nothing was broken. The form was simply never told what to create.
Collecting and filing are two different jobs
A form does two things, and they fail independently:
- Collect — show fields, validate them, store the answers.
- File — turn the answers into a record: a lead, a contact or a task, with each answer landing in a named field.
Most form builders are excellent at the first and indifferent to the second, because the second is not a website problem. It is a CRM problem: it needs to know what a lead is, which fields exist, and what should happen when an answer has nowhere to go.
In Nextora the wiring is a build step with a name of its own, and the bottom of the screen states plainly how many answers out of how many reached a field. If an answer has nowhere to land, the form still builds — but a line above the result names the questions that will stay in the submission and never reach the record. Not lost, but not in the CRM either, and you are told which.
The one number to look for in any form builder
"N of M answers reach a record." If your tool cannot tell you that, the honest assumption is zero, and the way to check is to submit the form yourself and go looking for the lead.
Fields you did not plan for
Real enquiries ask real questions: make, model, colour, deadline, budget, square metres. None of those exist on a standard lead. The wrong answers here are to drop them, or to shovel everything into one "message" blob that no filter can read.
The right one is to create the field. When you describe a form in words — "a kitchen quote request: contacts, size, deadline and budget" — answers with no built-in lead field get custom lead fields of their own, visible in the leads list and usable in its filters. A month later "show me quote requests over 20,000 with a deadline this quarter" is a filter, not an afternoon of reading submissions.
Form or survey — a choice you cannot take back
Two types, and the type governs everything afterwards; it cannot be changed later, only recreated.
| Type | How it looks to the customer | Choose it for |
|---|---|---|
| Form | Every field on one page, one submit button | An enquiry, contact details, a quote request |
| Survey | Several pages, a progress bar, logic-driven jumps | NPS, research, a branching questionnaire |
The instinct to make everything a survey because it looks thorough is worth resisting: a quote request that takes four screens converts worse than one that takes one.
Measure the form, not the traffic
A forms gallery that shows each form with its views, its submissions and its conversion rate answers the question people actually ask — "is this form working" — without a detour through web analytics. A form with high views and low conversion is a field problem; low views is a placement problem. Two different fixes, and the card tells you which.
What happens after the record exists
Filing the enquiry is the start of the loop, not the end. Once the lead is a real record with real fields, the rest is ordinary automation: "when a lead is created" assigns the owner, sends the welcome email from a template, and starts the follow-up sequence — see pipeline, workflow, form or template for which tool does which. And if the enquiry arrived as a conversation rather than a form, it lands in the same place as everything else customers send you: one queue for every channel.
A five-minute audit
- Submit your own form with a recognisable name.
- Open the CRM. Is there a lead? How long did it take to appear?
- Open the lead. How many of the answers are in fields, and how many are in one text blob?
- Try to filter the leads list by the thing you actually care about — budget, deadline, product. Can you?
- Check the owner. Did anyone get told, or is the lead sitting unassigned?
Most teams find at least two of the five broken, and all five are configuration rather than engineering. The form builder itself lives on the marketing page, and the records it feeds are covered in the CRM record model.
Questions people ask
Why are my form submissions not showing up in the CRM?
Usually because the form collects answers but was never told what record to create or which field each answer belongs to. Notifications still arrive, so the problem goes unnoticed. Check that the form creates a lead or contact, that each answer maps to a field, and that an owner is assigned.
Should I use a form or a survey for lead capture?
Use a form for enquiries and quote requests: every field on one page and one submit button. Use a survey for research, NPS or branching questionnaires across several pages. A quote request split over several screens usually converts worse than one short page.
How do I test whether my website form works?
Submit it yourself with a recognisable name, then find the record in the CRM. Check how long it took to appear, how many answers landed in fields, whether you can filter by the answers you care about, and whether an owner was assigned and notified.
See it on your own process.
Nextora brings CRM, projects, ERP, omnichannel conversations and AI employees onto one record model. Start a 14-day free trial and bring the process you want to fix.