CRM Forms

CRM forms can create or update People, Organizations, custom Records, Tickets, Interactions, Signals, Customer Requests, and service requests.

Workspace managers choose the fields, required values, defaults, source, duplicate matching, relationship mappings, consent questions, success message, automation triggers, and optional file limits. Public forms must be assigned to at least one Pages domain before they can be enabled.

Open CRM → Forms to create or edit a definition and review its submissions. Each field has a stable field ID, visible label, type, destination field, validation, and optional Relationship mapping. Advanced lists use commas; consent mappings use field:channel:purpose, for example email_opt_in:email:marketing.

Choose access

  • Private forms are available to workspace members with CRM management access.
  • Portal forms require an active customer portal session. A Person form can update only the signed-in customer's email-matched Person.
  • Public forms accept anonymous new submissions on their assigned Pages domains. They cannot update a caller-selected record.

Public submissions use a bot-trap field, minimum completion time, and shared rate limits. Bnder does not use Turnstile for CRM forms.

Enable file upload and set both a maximum file count and per-file byte limit. Files use the workspace's existing type policy, storage quota, malware scan, and audit log. If the form submission fails, newly uploaded files are removed.

Consent questions must be boolean fields on a Person form. Every answer stores the channel, purpose, source, timestamp, and form-submission evidence; leaving out a consent question never implies permission.

Duplicate review and success

Select stable fields such as email, phone, domain, or a record identifier for duplicate matching. One match updates that item, no matches creates it, and multiple matches create a reviewable submission without choosing automatically. After an accepted submission, Bnder shows the configured success message or redirect and emits the form's automation trigger keys.