Agiled Docs

CRM forms collect information from leads, customers, prospects, and internal teams.

Create forms when you want structured intake that can become CRM records, tickets, tasks, or workflow triggers.

Plan the form around what should happen after submission. A lead form, support intake form, and internal task request need different fields, mappings, and notifications.

Write the desired outcome before building: create a contact, create an account, create a deal, open a ticket, create a task, notify a team, or trigger a workflow. The fields should support that outcome.

Create a Form

Open CRM > Forms.
Select Create Form.
Choose Start from scratch, a starter, or a saved template.
Complete form setup.
Add fields in the builder.
Configure appearance.
Save the form.

Creation Options

Start from scratch gives you a blank form.
Starters provide common form structures such as contact intake, account intake, deal qualification, support ticket, and task request.
Saved templates reuse form templates your team has saved.

Choose a starter when the intake pattern is common. Choose a saved template when your team already standardized the exact fields, wording, and mappings.

Plan The Destination

Before adding fields, decide where the submission should land: contact, account, deal, ticket, task, workflow, or notification. Field labels and required status should support that destination.

Use one primary destination when possible. A form that tries to create several different records can be harder to test and harder for users to understand after submission.

Required Setup

The form needs a name and title before it can be saved. If those are missing, the editor opens the settings panel and highlights the required fields.

Before publishing, also configure submission action, field mappings, notifications, success message, redirect URL, and any workflow trigger that depends on the form.

Use required fields only where the team truly needs the answer. Too many required fields reduce completion, while too few fields create manual cleanup.

Submit the form yourself before sharing it. Confirm the public page, required fields, success behavior, created record, field mapping, notifications, and workflow runs all behave as expected.

Test from a private browser too. This confirms customers can submit without a workspace session and that the public experience matches the internal preview.

If the form should update an existing contact or account, test with a known record and confirm duplicate behavior. A form that creates duplicates can make campaign and support follow-up much harder.

Empty State

If the forms page is empty, create the first form from the empty state. Start with a starter when you need a working structure quickly.

After saving the first form, submit a test response from the public link and confirm the submission and processed record appear correctly.

Troubleshooting

If submissions do not create the expected record, check the submission action and field mappings.

If notifications are missing, review notification recipients and workspace email settings.

If public submissions work but records look incomplete, inspect one submission and compare each field to its mapping before editing the form structure.

Form Launch Checklist

Before publishing:

confirm name, title, and destination
test required and optional fields
confirm mappings on the created record
confirm notification recipients
confirm workflows triggered as expected
test direct link and embedded page if both are used

Create a CRM Form