Agiled Docs

Saved form templates appear when creating a new CRM form.

Templates are best when the form structure is proven and repeated. Starting from a template is faster than rebuilding fields, mappings, and submission actions, but every new form still needs a review before it is shared.

Use templates for repeated lead capture, support intake, onboarding questions, event registration, feedback, and qualification forms.

Create From a Template

Open CRM > Forms.
Select Create Form.
Open Saved templates.
Search for the template.
Select it.
Review form setup, fields, mappings, appearance, and submission action.
Save the new form.

The create dialog includes starter forms, saved templates, and scratch creation. Use search when the template library is large. If no saved template appears, check whether the template exists in the current workspace and whether your user can access form templates.

Customize the New Form

After selecting the template, change any campaign-specific text, hidden fields, redirect URL, notification recipients, field mappings, and automation triggers. The new form should match the current audience, not only the old template.

Also update internal labels that help the team recognize submissions later. A public title can stay customer-friendly, but the internal form name should make the source campaign, audience, or use case obvious.

Check Template Age

Before using a saved template, check when it was last updated and whether custom fields, pipelines, ticket statuses, or workflows have changed since then. Old templates can create forms that look right but map submissions incorrectly.

Review Before Publishing

Even when the template is trusted, check the new form before sharing it. Update copy, notification email, redirect URL, required fields, and mapping for the new use case.

If the form will create contacts, deals, tickets, or tasks, verify the owner, pipeline, status, and custom-field mappings before publishing. A form copied from an old template may still point submissions to the wrong team workflow.

Reuse Checklist

Change the title so submissions are easy to identify later.
Remove fields that do not apply to this audience.
Add missing required fields before the form is public.
Check every field option and placeholder.
Confirm contact and custom-field mappings.
Test the public form and verify the submission record.
Confirm any workflow trigger points to the new form, not only the original template source.

Test the Form

Submit the public form with test data. Confirm the submission appears in CRM, contact fields map correctly, notifications send to the right people, and any workflow runs against the new form.

Keep the test submission until you have verified the full path. It is easier to inspect the created contact, deal, ticket, notification, and workflow run while the exact test data is still available.

Troubleshooting

If submissions map to the wrong CRM fields, edit the form mapping rather than the template unless every future form needs the same change.

If workflows do not run, check whether the workflow trigger targets the new form or only the original form that inspired the template.

If the new form needs the same edits every time, update the saved template so future forms start cleaner.

Use Form Templates