Forms
Go to: CRM → Forms
A CRM form is a public lead-capture form. You build it in ERPX, share it as a link or embed it on your website, and every genuine submission creates a lead automatically — already owned, already sourced, already in your pipeline.
How a submission becomes a lead
Every path is recorded as a submission, so even the rejections are visible to you.
Building a form
Create the form
Go to CRM → Forms and click New. Give it a Form Name and an internal Description.
Add fields
In the Fields panel, drag in the field types you need:
| Type | Use for |
|---|---|
| Text Input | Names, job titles, free text |
| Email addresses — validated on submission | |
| Number | Quantities, budgets |
| Phone | Contact numbers |
| Dropdown | A single choice from a list |
| Checkbox | One or more choices from a list |
| Text Area | Longer messages |
| Date | Requested dates |
Each field needs a label and a unique ID. Dropdown and checkbox fields need at least one option. Fields can be marked required and given length limits.
Map fields to lead fields
In the Mappings panel, connect each form field to the lead field it should fill — lead name, first/middle/last name, email, phone, mobile, website, street, state, postal code, gender, and description.
Only simple text fields can be mapped. Territory, industry, and other reference fields are deliberately not mappable from a public form — an anonymous visitor cannot be trusted to pick your internal master data. Set those on the lead afterwards, or default them in the settings.
Unmapped fields are still saved with the submission; you just read them on the submission rather than on the lead.
Configure the settings
See the settings table below.
Activate and share
Make sure the form is Active, then use Share to copy the link or embed code.
If no Lead Name is mapped, ERPX builds one from first and last name, or the email address, or failing both “Form Submission”. A form with only an email field still produces a usable lead.
Form settings
| Setting | What it does |
|---|---|
| Page Title / Page Description | Shown on the hosted form page |
| Submit Button | The button text |
| Success Message | Shown after a successful submission |
| Redirect URL | Send the visitor to your own thank-you page instead. Must be a full http(s) URL |
| Duplicate Check By | Which mapped fields identify a repeat submitter — email by default, optionally phone |
| Default Lead Source | Tags every lead from this form with a lead source |
| Default Status | The status new leads start in |
| Auto-assign Owner | The user every lead from this form is assigned to |
| Notification Emails | Addresses told about submissions |
| Honeypot | Bot trap. On by default |
| Allowed Sites | Domains permitted to submit this form |
Set Default Lead Source and Auto-assign Owner on every form. Without them, web leads arrive unattributed and unowned — and unowned leads are the ones nobody follows up.
Sharing a form
| Option | What you get |
|---|---|
| Shareable Link | A public URL hosting the form on its own page |
| Embed Code | A <script> tag that renders the form inline in your site’s HTML |
An inactive form cannot be submitted. Activate it before sharing, and remember that deactivating takes down a page your website may link to.
Spam protection
Four layers run on every submission, and none need configuring beyond the allowed-site list:
| Layer | What it stops |
|---|---|
| Rate limiting | More than 10 submissions per minute from one IP address |
| CAPTCHA | Automated submissions, via Cloudflare Turnstile |
| Honeypot | Bots that fill in a hidden field a human never sees |
| Domain checks | Submissions posted from a site not on the allowed list |
A honeypot hit is silently accepted — the bot is told everything went fine — but no lead is created.
Allowed Sites falls back to your organisation’s configured domains when the form’s own list is empty, so a form embedded on your own site works without extra setup.
Duplicate handling
Before creating a lead, ERPX checks whether one already exists with the same email — or phone, if configured. If so, the submission is stored as a duplicate and linked to the existing lead. The global email uniqueness rule applies too: an address already belonging to a prospect or contact produces a duplicate rather than a conflicting lead.
Reviewing submissions and performance
Submissions lists every submission with its status, values, IP address, and timestamp:
| Status | What happened |
|---|---|
| Processed | A lead was created |
| Duplicate | Matched an existing lead. No new lead |
| Spam | Came from a disallowed domain. No lead |
| Failed | Honeypot triggered or processing errored. No lead |
Analytics shows total submissions, processed, leads generated, duplicates, spam, and failed — plus a submission trend over time.
A rising duplicate count usually means people are submitting twice because your success message is unclear — not that your traffic is bad.
Deleting a form removes it and all of its submissions permanently. The leads it created are not affected.
Everyday tips
- Ask for less. Every extra required field costs you submissions. Name and email are usually enough.
- Set Default Status to Open and let your team qualify — do not have web forms create Qualified leads.
- Keep one form per campaign or placement, so lead source and analytics stay meaningful.
Related pages
- Leads — what a successful submission becomes
- CRM Masters — the lead sources you default on a form
- CRM Workflows — what to do with a web lead once it lands