Lead Capture Form Checklist: Fields, Routing & Testing

What makes a lead capture form useful to a sales team?

Collect the information needed for a clear next action, map identity fields to the CRM and tell the visitor what happens after submission. Test the published form on a phone, confirm the contact record and verify the follow-up owner. In Chirply, a completed native form creates or matches a contact and fires the Form submitted event.

Give every question a purpose

Start with the decision the receiving team needs to make. An inquiry form might ask for the requested service, a preferred contact method and the best time to respond. Make a question required only when the team needs that answer to handle the request. A shorter form is useful when it still supplies the information needed for the next action.

Use the worksheet to name the question, its type, CRM destination and reason for collecting it. Keep the visitor's wording understandable. A field called Service requested is easier to answer than an internal campaign code.

Distinguish contact information from permission to send particular communications. Use wording and consent collection appropriate to your business and channels. The existence of a phone field alone does not tell your team what the person requested or authorized.

Build and publish the form deliberately

Chirply's native form builder separates editing, sharing and results. Test the public experience after publishing.

1. Open Forms and choose New form. Select a relevant starting point such as Contact form or Client application, or Start from scratch.
2. In Build, select each question and review its wording, type and required setting. In the Question panel, map supported identity fields to the intended CRM field; email and phone map themselves.
3. Use Logic for conditional questions when the form has at least two questions. Test both the condition that shows a question and the condition that hides it.
4. Review the Design and Settings controls, including One question at a time, Show progress and Save partial responses. Choose the behavior that fits the form rather than assuming a template's settings.
5. Save the draft, then Publish when its wording and handoff are ready. Open Share to obtain the hosted link or the website iframe embed.
6. Submit the published form using a controlled address, then inspect Results, the matched or created contact and any configured Form submitted workflow.

Test a complete inquiry and a repeat visitor

For an illustrative consultation inquiry, collect a name, email and short description of the requested help. The expected result is a contact with the correct source and a task for the coordinator. Confirm the message shown to the visitor matches the actual response process.

Submit again with the same controlled email. Native forms match by email, then phone, so inspect the resulting contact and workflow behavior. Test a phone-sized viewport and any embedded version separately; the host page can affect how an iframe fits.

Results distinguishes complete and partial responses. Partial responses become eligible for the normal completed-form path after completion. The overview tiles show lifetime counts, and the table and export show the 500 most recent responses. Label any reporting built from those views accurately.

Follow the handoff one record at a time

If a visitor can see only a draft or the link fails, confirm publication and the Share link. If a question is absent, check its show/hide conditions. If the contact exists but follow-up is absent, inspect the selected workflow's enrollment state and form filter.

Record the form, test date, contact and run in the worksheet. Recheck after changing field mappings, conditional questions or the workflow trigger. This makes the form a maintained entry point into the business process.

Common questions