Forms
Build public forms and review submissions.
Forms collect information from leads, customers, or internal teams.
Use forms when you need structured intake instead of free-form email. A good form creates cleaner CRM data, easier follow-up, and better workflow triggers.
Start with the action your team needs after submission. The form should collect only the information required to qualify, route, or complete that action.
Build a Form
Open CRM > Forms, create a form, then add the fields you need. Keep forms short enough for the person filling them out, but include the fields your team needs to act on the submission.
Before publishing, confirm required fields, field labels, placeholder text, custom-field mapping, submission destination, and any workflow that should run after submission.
Start by deciding what record the submission should create or update. Lead capture may create a contact and deal, support intake may create a ticket, and onboarding intake may create tasks or update custom fields. The record outcome should guide the fields you ask for.
Use required fields carefully. Required fields should block submission only when the team cannot act without that answer.
Publish and Share
After the form is ready, publish it and share the public link. Test the public form before putting it on a website or sending it to customers.
Open the public link in a private browser window, submit a test response, and confirm the submission appears in Agiled with the expected processed record.
If you embed the form on a website, test the embedded page separately from the direct public link. Website scripts, layout, and security settings can affect the embedded form even when the standalone link works.
Submissions
Submissions store the answers received through the public form. Review submissions from the form detail page. Use the submission details to create CRM follow-up, assign work, or trigger automation.
Check submissions daily for active public forms. A form can collect useful information even when mapping, notification, or workflow setup needs adjustment. If a submission did not create the expected record, inspect the submission payload before editing the form.
When reviewing a submission, compare the raw answers with the created record. Confirm important values landed on the contact, account, deal, ticket, task, or custom fields where the team will actually work.
Form Templates
Use form templates for repeatable lead capture, intake, feedback, support, or onboarding forms.
Decide Submission Ownership
Every live form should have a named owner. The owner reviews first submissions, checks whether records are created correctly, fixes field mapping, and confirms workflows or notifications route to the right team. Without ownership, forms can quietly collect submissions without follow-up.
For public forms tied to campaigns, review submissions daily during launch and after any change to fields, mappings, or workflows.
Keep Forms Maintainable
Review forms after changing custom fields, workflows, pipelines, ticket types, or campaign offers. Public forms should not keep asking for fields the team no longer uses, and mappings should stay aligned with the records your team expects to create.
Archive or unpublish old forms when campaigns end. Leaving outdated forms live can create records with old owners, stale pipeline stages, wrong ticket types, or missing required fields.
Form Review Routine
For active public forms:
- Submit a test response after major changes.
- Check the created or updated record.
- Confirm notifications went to the right owner.
- Confirm workflows ran once.
- Review first real submissions for data quality.