How to capture leads from your website, step by step

Ask for less than you think you need

Every field you add is a reason to stop. A name, one way to reach them, and a line about what they need is enough to start a conversation. The rest you can ask when you reply.

Long forms feel like paperwork. Short forms feel like a note to a person. The second one gets filled in by people who were only half sure, and those are often the ones worth talking to.

The form on a Website Builder Studio site is on every page, so a visitor never has to go looking for it. It is written into the page along with the rest, from a conversation about your business.

• Name, so you can greet them
• Phone or email, one is enough
• What they need, in their own words
• Nothing a form should not ask for, such as a card number

The moment a visitor presses send

The submission leaves your site and is delivered to the place you connected. That can be HubSpot, Salesforce, Zoho CRM, Pipedrive, GoHighLevel, Mailchimp, Kit, ActiveCampaign, Slack, Microsoft Teams, SMS, email, or any webhook.

It also appears on the Leads screen inside the builder, with a status and a note you can edit. So you have two places to see it: the tool you chose and the builder itself.

Connecting takes one pasted credential you generate yourself in the other tool. There is no sign-in screen inside the builder for your CRM, which means the builder never holds your CRM password.

Every delivery is signed, so your end can check it

Signed means each delivery carries a signature your receiving system can verify. If someone tries to post a fake lead straight at your webhook, your end can tell it apart from a real one.

You will not notice this most days. It matters on the day someone tries to fill your CRM with junk. The in-app assistant can walk you through the connection on your side, step by step.

If you deliver to a webhook of your own, the signature is the thing your developer will ask about first. It is there on every delivery, and it does not change how you use the form.

Existing contacts get updated, not duplicated

A person who fills in your form twice is one person, not two. Deliveries to HubSpot, Zoho and Pipedrive look up the contact by email and update it instead of creating a duplicate.

That keeps your CRM honest. One record per person, with the newest note on top, rather than five copies of the same name that nobody ever merges.

Prove the path before a real lead needs it

Press Send test lead beside the connection and go look. The test should appear in your CRM or your channel within moments. If it does not, fix it now, not after a real person has been waiting.

Test again whenever you change a credential or move to a new tool. A path that worked last spring is not proof it works today.

This is the step people skip because it feels like nothing. It is the step that stops a month of leads landing in a channel nobody reads.

One place for every lead, across every site

If you run more than one site, every lead from every one of them lands on the same Leads screen. Each has a status and a note you can edit, so a lead from your second location is not lost behind your first.

When you want the list outside the builder, export every lead across every site to a spreadsheet in one click, as CSV or Excel. Hand it to whoever needs it.

The export is the same whether you run one site or many. Every lead, every site, one file, and nothing is stuck inside the builder.

What capture does not do

Capture gets the lead to you. It does not reply, and it does not promise how many people will write. That part is the words on your pages and how quickly a human answers.

The pages themselves are written from a conversation about your business. They pass a check that runs before anything publishes, validated against Google Search Essentials and modern web standards. That is the builder's half. The reply is yours.