Create, publish and test a lead-capture form in 6am

Turn one business request into a short, testable form in app.6am.ag. Finish with a working public link, a checked submission history and a named person responsible for reviewing new requests.

• Owner: A workspace member with permission to manage contacts.
• Outcome: A published form whose fields, privacy notice, confirmation and contact behavior have been verified.
• Before starting: Choose the correct company, the request you want to collect, the responsible person and the company's approved privacy notice and HTTPS policy URL.

1. Define one clear request

Use a specific title such as Request a home repair estimate. Ask for only what the team needs to assess the request. Do not promise a reply time the team cannot meet.

The current form supports First name, Last name, Email, Phone, Company and Message. Email is always required; the other selected fields are optional. Use Message for the service requested or extra context. You can select up to 10 existing active custom contact fields; their labels, help and options become public, and all remain optional. Follow SOP 076, custom contact fields for types, preservation rules and QA. Conditional questions, required-field settings beyond Email, file uploads and appointment booking remain outside this version.

Each form has one public language: English or Brazilian Portuguese. To offer both, create two forms with distinct internal names and translated public content. They have separate public links and histories. The administrator's interface language does not change the form's public language.

2. Create the draft

1. Sign in to 6am, choose the company and open Lead Forms. Create a new form.
2. Enter a unique Internal name, such as Home repair estimate — EN. Archived forms also reserve their names.
3. Choose Public language. Enter Public title and, if useful, a short Introduction explaining what to provide.
4. In Fields to collect, keep Email and select only the other fields needed. Phone, when supplied, must use +, country code and digits only.
5. Leave Tags applied on submission empty or choose existing company tags. Use SOP 087 to configure and verify this rule.
6. Enter the approved Privacy notice, the real Privacy policy URL (HTTPS) and a Confirmation message. For example: “We received your request. Our team will review the details.” This message appears on screen; the form does not send email or SMS.
7. Save. Confirm the row is Draft. Saving an existing form also takes it offline, so plan edits before changing a form that is already shared.

3. Publish and test the public link

1. Review the saved configuration, return to the list and choose Publish. Confirm that the row shows Published.
2. Open Share / embed, copy Public link, and open it in another tab. Check the company name, language, title, fields, privacy link and readable layout on desktop and phone.
3. Try submitting without Email. The browser must block the attempt. Confirm that no completed submission was added.
4. Search Contacts for a controlled test email first. Use clearly marked test details that do not belong to a customer; leave Phone empty unless testing a controlled number. Submit once and confirm the on-screen message.
5. Open Form submissions, filter by the form and choose View submission on the new row. Check received time, submitted values, form version, privacy notice and tags applied at receipt.
6. Confirm Contact created, or Existing contact if that email already existed. Use the Contact link to find the record and verify the expected tags. Message remains in submission history; it is not copied into contact notes.
7. Reopen the public link for a fresh request. Submit the same email with a different first name and message. Expect a second history row, the same contact and unchanged existing contact fields. A browser retry of the same completed request is deduplicated; reopening the form starts a new request.

4. Handle review cases

The public confirmation does not reveal whether a contact was created, matched or held for review. Always check the private history.

Needs review means the submission did not modify a contact or apply tags. Read the reason: conflicting or ambiguous email/phone, an archived contact, or an identifier retained after a merge. Verify identity through an established channel, then use the existing contact-management process. The history does not provide an automatic “approve and replay” action. Do not create a replacement contact merely to bypass the conflict.

A successful submission is an unverified request, not proof of identity, qualification or marketing consent.

5. Share or embed

After the checks pass, share the public link. For a website, copy Embed code from Share / embed into the site's HTML/embed block. Publish that page and repeat a test from the actual page. Confirm that the full form and confirmation are accessible on mobile; adjust iframe height if needed. If the site's content security policy blocks the frame, ask its maintainer to allow the form's origin. The form does not require third-party cookies.

6. Maintain and recover

• Assign a person and a review cadence for Form submissions, including Needs review. This version does not send submission notifications.
• After any edit, save, Publish again and reopen the link. Previously opened copies can expire after two hours or become invalid after changes; use Reload form and retry.
• If a configured tag is deleted, the public form becomes unavailable even if its saved status still says Published. Edit the form, remove or replace missing tags, save, publish and test again.
• Unpublish pauses new submissions. Archive also moves the form out of the active list. Both preserve history and contacts. Use the archived filter and Restore as draft when needed, then review and publish again.
• For a temporary “too many requests” response, wait at least one minute before retrying. Avoid repeated automated test submissions.

Completion evidence

Record the company, form name, public URL, test date, submission IDs, expected contact and responsible reviewer. Keep test data clearly identified and handle it through the company's normal retention process.

Related procedures

• SOP 085 — Manage contact tags
• SOP 086 — Create dynamic contact lists
• SOP 087 — Apply tags to form submissions