Automatically tag form submissions in 6am

Apply a consistent source tag to contacts who submit a specific native form in 6am. The rule lives in the form itself: no separate workflow needs to be created.

• Owner: A workspace member with permission to manage contacts.
• Outcome: Verified tag assignment on new submissions, with private evidence in the form history and the contact record.
• Requirements: The correct company, a saved native form, existing company tags and controlled test details. Follow SOP 074 if the form is not ready.

1. Choose an honest label

Choose a tag such as Form — Home repair estimate submitted. It means that an unverified request reached this form at least once. It does not establish that the person owns the email address, is qualified, booked an appointment or consented to marketing.

Reuse an existing tag with the same meaning. If needed, create one in Contact Tags using SOP 085. This form rule applies the same selected tags to every accepted submission. It does not branch on Message or other answers.

2. Configure this form

1. Open Lead Forms in the correct company and edit the exact form.
2. In Tags applied on submission, choose up to 10 existing company tags. Confirm each tag belongs to the intended event and is not already used with a different meaning.
3. Save. Saving takes a published form offline and leaves it as Draft. Return to the list, review the configuration and select Publish.
4. Open Share / embed and use the current Public link for testing. The link remains the same after edits, but an already-open form may need to be reloaded.

The configuration affects future accepted submissions only. It does not backfill older contacts or remove tags previously applied. It preserves all other contact tags. Adding the same tag again does not duplicate its membership.

3. Prove the rule works

1. Search Contacts for a controlled test email. Choose data that do not belong to a customer. Record whether the contact and selected tag already exist.
2. Submit the published form. In Form submissions, filter by the form and open View submission on the new row.
3. Expect Contact created or Existing contact. Check Tags applied at receipt, the received time, submitted values and form version. Open the Contact link and verify the exact tag on the contact.
4. Reopen the public link and submit a second request using the same email, with a different Message. Expect a second history entry, the same contact and one membership for each tag. Existing contact fields remain unchanged. A browser retry of one completed request is deduplicated and is not a new submission.
5. If a second controlled contact is available, confirm that one which did not submit this form did not receive the tag. Do not use a customer record just to create this comparison.

The public confirmation alone is insufficient evidence: it intentionally does not reveal whether the contact was matched or held for review.

4. Use the tag in a dynamic list

Follow SOP 086 to create a Smart List whose tag rule includes the selected tag. Refresh the preview or reopen Contacts with that list selected. Confirm the tested contact meets all of the list's conditions. Other AND/OR conditions can exclude it even when the tag is present.

Tags can be changed manually later. Tags applied at receipt records what the form applied at that time; the contact and Smart List show the current state. Removing a tag from a contact does not rewrite old submissions. A new accepted submission can apply it again while the form still has that rule.

5. Resolve failures without losing evidence

• Needs review: Read the reason. Conflicting identities, archived contacts and identifiers preserved after a merge do not modify contacts or apply tags. Verify identity and use the contact-management process; there is no automatic approval/replay action in submission history.
• A configured tag is missing: Edit the form, remove or replace the missing tag, save, publish and test again. Deleting a tag can make the public form unavailable even while its saved status says Published. Recreating the same tag name does not repair the old configuration; select the new tag explicitly.
• Form changed or expired: Reopen the public link. A loaded copy expires after two hours and becomes invalid after configuration or publication changes.
• Tag missing from a Smart List: Check the contact's current tags, list rules and any deleted-tag warning. Do not broaden a list just to make a test pass.
• Need to stop the rule: Unpublish the form to stop intake. To keep receiving requests without these tags, edit the tag selection, save and publish again. Existing tags and history remain.

Completion evidence and limits

Record company, form name, tag names, publication/test date, submission IDs, contact and Smart List checks. Assign a person to review new submissions and conflicts; this version does not notify the team automatically.

Tagging does not itself create opportunities or tasks. To add that behavior to a native form, configure the separate sales follow-up option using SOP 075. This procedure does not send messages, enroll contacts in campaigns, perform answer-based branching, verify identity or record marketing consent.