Agiled Docs

Form templates help teams create consistent forms without rebuilding the same fields every time.

Open Form Templates

Open Templates.
Go to Form templates.
Review template cards by name, field count, and category.

Use form templates for lead capture, support requests, job applications, event registration, feedback, onboarding intake, and other repeatable public forms.

Templates are starting points, not final public forms. After choosing a template, review the generated form in CRM before publishing it.

Use a template when the structure repeats across teams or customers. Create a one-off CRM form when the wording, fields, or follow-up process is unique.

Review Before Publishing

When you create a CRM form from a template, review the final form before sharing it. Confirm field labels, required fields, mappings, notification email, redirect URL, and submission action.

Also check whether the form creates a contact, account, deal, ticket, task, or another record. If the template contains generic labels, rewrite them in the language your customer will understand.

Open each important field and confirm where the response will go. Customer identity fields should map to contact or account fields, sales qualification fields should map to deal fields or custom attributes, and support fields should map to ticket context. Do not leave valuable answers only in the raw submission payload when the team needs them on a record.

Customize A Template-Based Form

After applying a template:

Remove fields that do not apply to this workflow.
Add required fields only when the team truly needs them.
Map important fields to CRM or custom attributes.
Confirm the submission success message or redirect.
Test one private-window submission before sharing.

If the form is embedded on a website, test the embedded version separately from the direct public link.

After the test submission, open the created record and check that the name, email, phone, company, source, owner, pipeline, stage, ticket status, and custom fields landed in the right places. This is the fastest way to catch a template that looks correct but creates incomplete CRM data.

Template Ownership

Assign one owner for shared form templates. That owner should review changes when CRM fields, custom attributes, workflows, or notification rules change.

Do not let every team edit the same shared template for local wording changes. Clone or create a new template when a department needs different questions, record mappings, or customer-facing language.

Keep Templates Useful

Update the template when your repeatable intake process changes. If only one form needs special wording, edit that form instead of changing the shared template for everyone.

Review saved form templates after changing CRM pipelines, custom attributes, ticket statuses, or workflow triggers. A template may still create a form, but its mappings or follow-up process can become outdated after those operational changes.

Archive templates that are no longer used. Old templates can create outdated forms with wrong fields, wrong notification owners, or obsolete workflow triggers.

First Form From Template

After creating a form from a template, submit one internal test response before publishing it. Confirm the form creates the expected CRM record, maps fields to the right places, sends the right notifications, and starts the intended workflow.

If the test record is incomplete, update the form or template before embedding it on a website or sharing it with customers.

Form Templates