Loading
Because most forms send email. It arrives in a shared mailbox, competes with everything else there, and the enquiry is answered in a day and a half by whoever happened to look.
A web form, embedded on your site or hosted by Treepie, writes directly to the lead record with its source, the page it sat on and any consent it captured.
The submission creates a lead with an owner assigned by routing rules and a clock running from the moment it arrived. Known contacts are matched rather than duplicated, and consent is recorded with the form that captured it.
A pricing-page form was averaging 31 hours to first response as email. Landing as an owned, queued lead took it to 40 minutes, and the form itself did not change at all.
It will not stop spam by itself. Field validation and rate limiting help; a form open to the internet still needs a person to look at what it catches.
Routing rules assign it, lead scoring reads its fields, Growth attributes it to the page and campaign that produced it, and consent is written to the contact record.
Yes, post to the API. The lead, the source and the routing behave identically.
Yes, per purpose, with the form and timestamp recorded on the contact.
They are matched to the existing contact instead of creating a duplicate.
Fourteen days, every module, no card. Or half an hour with someone who will run it on your own records and tell you where it does not help.