Build reusable forms
Define fields and validation once, then place the form on the pages where it belongs.
Create reusable forms, place them on website pages, collect structured responses and supported files, reduce spam, and review every website form submission in one focused inbox.

The submission remains the source of truth even when email notification or future CRM ingestion needs to retry.
Define fields and validation once, then place the form on the pages where it belongs.
Use controlled fields, required rules, files, and product context instead of an unstructured email.
See the response, source, status, attachments, and activity without searching a shared mailbox.
Forms and submissions are being shaped into a canonical workspace definition and inbox flow before release.
Build contact, feedback, booking, application, and inquiry forms with common field types.
Separate a reusable workspace form schema from its placement on a specific page.
Review responses with read, starred, archived, assigned, and timeline state.
Use validation, honeypot, rate limits, idempotency, and optional captcha boundaries.
Accept controlled file types and sizes while preserving submission ownership.
Save first, then feed notifications and future CRM ingestion through retryable jobs.
Define the information you need, place the form on the right page, and manage resulting requests.
Choose fields, validation, access rules, messages, and stored context.
Place the form in the site builder so it inherits design and records source context.
Inspect details and attachments, update workflow state, and follow up.
Support more than a generic contact box without becoming a full workflow automation platform.
Collect visitor, subject, message, and source page for a useful response.
Capture selected product, requested details, quantity context, or quote requirements.
Collect required information before scheduling or eligibility review.
Use structured choices and required fields to understand visitor intent.
The first goal is a dependable definition, placement, submission, and inbox system.
Responses are saved with site and form context and reviewed by authorized workspace members in the dashboard inbox.
The submission system includes controlled attachment support; availability depends on form configuration.
CRM ingestion is planned. The original submission is always saved first.
Forms and submissions are coming soon. The release will include reusable definitions, a submissions inbox, and controlled attachments.
Continue with the most relevant parts of the Cogo Site workflow.
We use cookies
We use cookies to enhance your browsing experience and analyze site traffic. By clicking 'Accept', you consent to our use of cookies. Learn more about our cookie policy