Build reusable forms
Define fields and validation once, then place the same form wherever that workflow belongs.
Rolling out on ProLead capture and intake
Website Forms with a Submissions Inbox
Create reusable forms, place them on website pages, collect structured responses, reduce spam, and review every website form submission from one focused management workflow.
- Available to Pro workspaces
- Four current Local Service templates can start with a canonical inquiry placement
- Public Form execution and the submissions Inbox require a Forms-enabled plan
Forms and Submissions
Website intake workspace
Submissions inboxLive concept
Review every website response in one place
The submission remains the source of truth even when email notification or future CRM ingestion needs to retry.
Collect structured information
Use controlled fields, required rules, product context, and access policies instead of relying on unstructured email.
Manage submissions in one place
Review responses, update status, perform bulk actions, and export bounded records for follow-up.
Forms and Submissions features
The core form lifecycle is live: define, place, publish, collect, review, and connect eligible submissions to CRM.
Visual form builder
Add, edit, remove, reorder, and validate common field types from the dashboard.
Reusable form definitions
Keep a workspace-managed form definition separate from the pages where it is placed.
Publishing and revision history
Publish an immutable revision, archive or restore the form, and inspect where the definition is used.
Submissions management
Review details, unread state, status, stars, spam state, bulk actions, and bounded export.
Spam and abuse protection
Use field validation, honeypot, request limits, idempotency, and optional Turnstile protection.
CRM and notification routing
Save the submission first, then deliver notifications and eligible CRM ingestion through retryable follow-up work.
How Forms and Submissions works
Define the information you need, publish a stable form revision, place it on the right page, and manage the resulting requests.
- 01
Build the form
Choose fields, validation, access policy, messages, spam protection, and optional CRM mapping.
- 02
Publish and place it
Publish the current revision and connect the reusable definition to the site experience where it belongs.
- 03
Review and act
Inspect submissions, update workflow state, use bulk actions, export when needed, and follow up from CRM context.
Who Forms and Submissions is for
Support more than a generic contact box without becoming a full workflow automation platform.
Contact and support requests
Collect visitor, subject, message, and source page for a useful response.
Product inquiries
Capture selected product, requested details, quantity context, or quote requirements.
Booking and applications
Collect required information before scheduling or eligibility review.
Feedback and qualification
Use structured choices and required fields to understand visitor intent.
Forms capture information; they do not become every workflow
The first goal is a dependable definition, placement, submission, and inbox system.
- Submission PII does not enter public AI retrieval
- CRM retries do not block public submission success
- A product request is not a commerce order
- Authenticated forms require server-side membership checks
Forms and Submissions questions
Are forms generally available?
Forms and Submissions are rolling out to Pro workspaces with reusable definitions, publishing, placement tracking, submission management, and CRM mapping.
Where do website form submissions go?
Responses are saved with site, form, and revision context and can be reviewed by authorized workspace members from the dashboard workflow.
Will forms create CRM contacts automatically?
No. A published or template-provisioned Form is not automatically CRM-connected. Eligible fields enter CRM only through explicit CRM Mapping, and the original submission remains the source record before any CRM follow-up.
Can forms require a signed-in site member?
Yes. Forms support public or authenticated access policies, and authenticated submissions are checked against the site membership boundary on the server.
Explore connected website tools
Continue with the most relevant parts of the Cogo Site workflow.