Skip to content
SWARE CRM
Sign in Request a demo
Features Security Integrations Docs Sign in Request a demo
Documentation Communication

Forms & lead capture

Build a public form, share the link, and turn submissions into deals.

What a form does

A capture form is a public page at its own web address. Anyone can fill it in without signing in, and each submission creates or updates a contact and opens a deal on your pipeline — so a lead arrives as a record you can work, not an email you have to re-key.

Building one

In Forms, admins and above can create a form from three kinds of field:

  • Standard contact fields — name, email, phone, country. Name is always required.
  • Contact custom fields — any field you have defined, including multi-selects.
  • File uploads — attachments that land on the contact record.

Each field can carry its own label, help text and required flag.

Every form is attached to an offering, so deals created from it point at the right product.

Presentation

  • An optional intro page before the form, with a heading, rich-text description, call-to-action wording and a background image.
  • A web address you can customise, published at /f/your-form-name.
  • Active and public switches — a form is only reachable when both are on.

After submission

Choose one of:

  • a thank-you page with your own heading and message; or
  • a redirect to any web address you choose.

What happens to a submission

  1. The contact is matched by email, then by phone. An existing contact is updated — never renamed — and custom field answers are merged in. Otherwise a new contact is created.
  2. An opportunity is opened, titled after the form and contact, pointing at the form's offering, in the first pipeline stage, with its source recorded as the form.
  3. Any uploaded files are attached to the contact and enter the virus-scanning queue.

Every submission is listed against the form with its data, the resulting records, and the submitting address.

Spam protection

Add your Cloudflare Turnstile keys in account settings and every form is protected. Verification happens on the server, and fails closed. Required fields, file types and file sizes are all validated server-side too, with errors shown inline without losing what was typed.

Something inaccurate or missing? Tell us — we would rather fix the docs than have you guess.