Forms
Forms in LadVen OS collect requests from a website, landing page, or external page and turn them into managed CRM work. They are useful for demo requests, customer inquiries, consultation requests, support requests, and other inbound flows.
A form should collect only the data needed for the next step: who contacted you, how to reach them, what they need, and where the request should go.
When to Use Forms
Use forms to collect website requests, route them into the right CRM pipeline, standardize inbound fields, review submissions, separate spam from work, and understand which published version is live.
If a request arrives by email or chat, do not copy it manually without a reason. Link the message or conversation to CRM when that keeps better context.
Build and Publish
In the builder, set the name, code, primary language, title, description, submit button, and fields. Fields should be clear for an external person: name, contact, company, question, preferred contact time, and comment.
Saving a form does not always change the live website. Before publishing, check the preview, required fields, languages, appearance, anti-spam settings, and CRM routing.
CRM Routing
Choose the pipeline, starting stage, and routing rules for new submissions. Good routing makes it clear who sees the request first, where it appears, which fields qualify it, who handles CRM errors, and when it is accepted.
Submissions
Review submissions regularly. A submission should become accepted, spam, or retried after CRM errors are fixed. For CRM errors, check required fields, route, permissions, and customer data before retrying.
Safety
Do not collect passwords, tokens, passport data, payment details, or other unnecessary sensitive information through public forms. Check allowed domains and active published forms as regularly as public file links.