More than Salesforce web-to-lead

Turn form fills into routed,booked Salesforce leads

Default routes each form fill to a Salesforce owner and opens that rep's calendar after submit.

WorkOS
Air
Cortex
Dust
Decagon
Owner
Airbyte
Listen Labs
Profound
Wispr Flow
fal ai
Perplexity
Rillet
New Form Submission

Form submission

The workflow starts when a visitor submits the demo form on your site.

Match Record

Account owner matching

Find the Salesforce account for each email's domain, so a new lead goes to the rep who owns it.

Enrich Data

Email-only forms

Enrichment fills in company, size, and title, so the form can ask for just an email.

Create Record

Lead creation from your form

Create the Salesforce Lead from the form already on your site, which the Pixel picks up.

Display Scheduler

Book with the lead owner

Right after submit, the calendar of the rep who owns the new lead opens over your page.

Workflows start fromthe form you already have

The Pixel picks up plain HTML, HubSpot, and Marketo forms on your site, and Pardot forms report through the Forms SDK. Map the fields once, and the Form Submission trigger starts a workflow on every submit.

HTML, HubSpot, Marketo, and Pardot forms feeding 1 Form Submission trigger with mapped fields

Forms

Add forms with Catalog forms and map their fields to person and company records.

Pardot forms

Report Pardot submissions with submitForm() and open the calendar after submit.

Form submission trigger

Start a workflow on every submission, with the answers, page URL, and referrer.

Each submit becomes1 lead with an owner

Match Record checks Salesforce for an existing lead or contact first. When there's no match, a rule or round robin picks the rep, and Create Record makes the lead with that Owner ID.

Workflow from a form submission to Match Record, Rules of Engagement, and Create Record with the lead owner

Create record

Map Email, Last Name, Company, and Owner ID onto the new lead.

Rules of engagement

Pick the owner by territory, company size, or a form answer.

Queues

Take turns across a team with weights and paused reps.

Qualified visitors bookbefore they leave

Default can start the Salesforce lookup and enrichment when the visitor leaves the email field, so the assigned rep's calendar opens right after submit. If the visitor leaves without booking, Default still has their email and can follow up.

Form submission opening the assigned rep's calendar on the same page

Calendar on the form

The calendar opens over your page, with no second form to fill in.

Follow up on unbooked leads

Alert the owner in Slack or add the lead to a sequence when nobody books.

“It’s the control layer we’re using to run GTM from the same brain.”
Matt McGonegleDirector of GTM Operations @ Cortex
FAQ

Questions about Salesforce web-to-lead

  • With Default, you keep the form already on your site: add it with Catalog forms, map its fields, and a Form Submission trigger starts a workflow whose Create Record node makes the Salesforce lead. Salesforce's own Web-to-Lead setup generates an HTML form that posts each submission to Salesforce.

  • Web-to-lead turns website form fills into Salesforce leads, and Default does it with a workflow: the Pixel captures the submit, Match Record checks for an existing lead or contact, and Create Record makes the lead with an owner. Salesforce's built-in Web-to-Lead feature creates a lead from each submission of a form it generates.

  • Default creates form leads with a workflow's Create Record node, which calls the Salesforce REST API, so those calls count toward your org's API request limits. Salesforce's own Web-to-Lead accepts up to 500 requests in 24 hours and holds the overflow in a pending queue.

  • In a Default workflow, a Rules of Engagement or Round-Robin node picks the owner and Create Record writes it as the Owner ID on the new lead. On leads from Salesforce's own Web-to-Lead forms, the active lead assignment rule picks the owner.

  • Add the Pardot form in Default with Catalog forms, and have your page send each submission with the Forms SDK's submitForm(), since the Pixel skips Pardot submissions. The workflow then routes the lead and can open the rep's calendar, and your submit handler keeps sending the submission to Pardot, because Default doesn't forward it.

  • The Default Pixel sends the email when the visitor leaves the email field, so Default can start the Salesforce lookup and enrichment early. Workflows start only on submit, so an unfinished form creates no lead and shows no calendar.

The marketing engine behind the best teams

One platform to manage workflows, enrich records, route leads, and schedule meetings.