Web-to-lead forms

A form you build once and put on your own website, so an enquiry from a stranger lands straight in your leads pipeline — nobody has to retype an email.

When you would use this: whenever you want your own site to feed leads in automatically, without a person on your side keying them in.

Building one: name it, then build the form on a two-pane screen — a palette of fields on one side (lead fields, your own custom fields, and heading, paragraph and divider blocks for layout) and the form itself on the other. Add a field by dragging it from the palette onto the form, or, without a mouse, by selecting it and pressing Enter or Space to add it to the end. Drag a field to reorder it, or use its Move up / Move down buttons instead. Each field can be marked required and mapped to a lead field (name, company, email…) or to one of your own custom fields; exactly one field has to map to the lead's name. A field can also be set to take up half the row instead of the full width, for shorter fields like a name and a phone number side by side. What you see while building is exactly what a visitor gets — there is no separate preview that can drift from the real thing. You can also set a headline, colours, a submit button label, and what happens after somebody submits — a thank-you message or a redirect elsewhere.

Defaults and notifications: choose the status, source and assignee a lead from this form starts with, and who gets told when one arrives — named people, or everyone holding a role you choose.

Publishing: once saved, the form has its own public web address to embed or link to from your site. Turning it off (or deleting it) stops new submissions without touching leads it already created.

Protecting it: an invisible trap catches automated bots, and a limit on how many submissions one address or one visitor can make in an hour keeps the form usable during a flood — a firm's own submissions log shows what came through and what was quietly turned away.

What happens next: a genuine submission creates a lead (or, for some fields, fills in a matching custom field) exactly as if you had typed it in yourself.

When it refuses: a visitor sees only a plain "something went wrong" if the form is off or the address is wrong — nothing about why, on purpose. You, building the form, are told exactly which field is missing or invalid when you save it.