Save Form Templates
Save a CRM form structure as a reusable template.
Form templates are saved from the CRM form builder.
Save a template after you have tested the form and know the structure is worth reusing. Templates should be clean starting points, not archived copies of every form variation.
Save a template only when another teammate should be able to create a future form from it without knowing the history of the original form.
Save a Form as a Template
- Open a form in the form builder.
- Open the save menu.
- Select Save as template.
- Enter a name and description.
- Save the template.
Use a name that explains the workflow, such as “Lead Qualification Form” or “Client Onboarding Intake”. Use the description to explain who should use it and what it creates.
What Gets Reused
The template keeps the form structure and setup so future forms can start from the same baseline. Review mappings, submission actions, and copy before using a template in a new customer-facing form.
Depending on the form setup, the saved template can preserve fields, labels, descriptions, placeholders, required flags, options, mappings, appearance, and submission behavior. It should not preserve customer-specific copy that belongs only to one campaign or client.
If the original form contains workflow-specific owner, pipeline, ticket status, redirect, or notification assumptions, rewrite those before saving the template. A saved template should be reusable without quietly sending future submissions to the wrong team or process.
Good Form Templates
- Contact intake.
- Account intake.
- Deal qualification.
- Support ticket.
- Task request.
- Feedback form.
- Onboarding intake.
Template Ownership
Assign an owner for reusable form templates. The owner should review the template when custom fields, pipelines, ticket statuses, workflows, or notification rules change.
Without ownership, old templates can keep creating new forms that map to stale fields or notify the wrong team.
Before Saving
- Remove temporary test fields.
- Replace customer-specific wording with reusable language.
- Confirm required fields are intentional.
- Confirm mappings do not point to the wrong custom fields.
- Confirm submission actions are safe for future forms.
- Confirm the template description tells teammates when to use it.
After Saving
Create a new form from the saved template and submit one test response. If the new form needs several edits every time, update the template so the next form starts closer to the finished workflow.
Review saved templates after custom field, pipeline, ticket, workflow, or notification changes. A template can keep creating forms even when the downstream mapping is no longer correct.
Test The Template As A New Form
The best test is creating a new form from the template, not only reviewing the template record. Submit a test response and confirm required fields, mappings, submission actions, notifications, and workflows behave as expected. This proves the template is reusable by someone who did not build the original form.
If the test form sends notifications or creates customer-facing records, use an internal email and clearly label the test submission.
Cleanup Routine
Archive duplicate or outdated form templates before major campaigns. Keep the template list short enough that teammates can choose the right starting point without guessing.
When Not To Save A Template
Do not save a template when the form is campaign-only, contains customer-specific copy, uses temporary owners, or depends on a one-time workflow. Clone or reuse the individual form instead if it will not become a shared baseline.