> ## Documentation Index
> Fetch the complete documentation index at: https://docs.os.default.com/llms.txt
> Use this file to discover all available pages before exploring further.

# How Default books a meeting from a form submission

> How Default turns a website form submission into a booked meeting: the Pixel captures the form, the Form Submission trigger starts a workflow, routing picks the host, the Display Scheduler opens a calendar on the same page, and the workflow follows up when the visitor doesn't book.

Default books a meeting from a form submission by opening a calendar on the same page the
moment a visitor submits a form on your website. The Pixel captures the submission, a
workflow picks the right host, and the visitor books a time without filling in a second form.

This page follows 1 submission from the form to the booked meeting. For the setup inside a
specific form tool, see [HubSpot forms](https://docs.os.default.com/forms/hubspot.md), [Marketo forms](https://docs.os.default.com/forms/marketo.md), and
[Pardot forms](https://docs.os.default.com/forms/pardot.md).

## Form to booked meeting at a glance

Every form-to-meeting flow in Default runs the same 6 steps:

1. **The Pixel captures the form.** The Default Pixel on your page picks up the submission
   from a plain HTML, HubSpot, or Marketo form. Pardot forms report the submission through the
   Forms SDK.
2. **The submission starts a workflow.** The workflow's **Form Submission** trigger fires for
   the form, with the visitor's answers.
3. **Routing picks the host.** The **Display Scheduler** node uses the event's hosts, for
   example a queue that picks the next rep, or a host you choose from workflow data.
4. **The scheduler opens on the page.** A loading indicator in your branding appears, then the
   calendar opens over your page.
5. **The visitor books.** They pick a time and confirm it. Default books the meeting on the
   host's calendar, and the workflow continues on its **Booked** branch.
6. **If the visitor doesn't book,** the workflow continues on its **Not booked** branch, so you
   can alert the owner or add the lead to a sequence.

## What you need before a form can book meetings

| Requirement | Where | Why |
| - | - | - |
| The Pixel on the page with the form | **Settings → Domains**. See [Set up the Pixel and Forms SDK](https://docs.os.default.com/pixel-sdk-setup.md). | The Pixel captures the submission and shows the scheduler. It must load with the page. |
| The form added in Default, with its fields mapped | **Forms** → **Create new** → **Catalog forms**. See [Your forms](https://docs.os.default.com/forms/your-forms.md#add-forms-from-your-site). | Default only accepts submissions from forms it knows. Adding forms needs admin access. |
| An email field on the form | Your form | A submission without an email address does not start the workflow. |
| An event to book | **Scheduling** → **Event Types**. See [Events](https://docs.os.default.com/events.md). | The scheduler offers this event's times. |
| Hosts with a connected calendar | Each host's **Preferences** settings, on the **Calendar** tab under **Calendars**. See [Preferences](https://docs.os.default.com/settings/availability.md#calendars). | Default books the meeting on the host's calendar. |
| A published, live workflow with a **Form Submission** trigger and a **Display Scheduler** node | **Workflows**. See [Routing and scheduling nodes](https://docs.os.default.com/workflows/steps-routing-scheduling.md#display-scheduler). | The workflow decides who hosts and what happens after the visitor books or leaves. |

## Step 1: The Pixel captures the form submission

The Default Pixel is the script you install on your site. It picks up submissions from forms
that already exist on your pages. You add each form to Default once with **Catalog forms**,
or [create it in Default](https://docs.os.default.com/forms/your-forms.md#create-a-form-in-default) when catalog mode can't
add it. Then map its fields so submissions land on the right person and company records. See
[Your forms](https://docs.os.default.com/forms/your-forms.md#add-forms-from-your-site).

![A customer page in catalog mode, with the demo request form outlined and marked Not added next to an Add form button](https://mintcdn.com/default-b6d0c477/-0oUq0bwOsCpwsAM/images/forms/catalog/catalog-overlay-not-added.png?fit=max\&auto=format\&n=-0oUq0bwOsCpwsAM\&q=85\&s=deafb3db2badda7714c64d377abc2bdf)

| Form on your page | How the submission reaches Default | Guide |
| - | - | - |
| Plain HTML `<form>` | The Pixel captures it automatically. | [Your forms](https://docs.os.default.com/forms/your-forms.md) |
| HubSpot embedded form | The Pixel captures it automatically, through HubSpot's own submission events. | [HubSpot forms](https://docs.os.default.com/forms/hubspot.md) |
| Marketo embedded form | The Pixel captures it automatically, through Marketo's Forms 2.0 API. | [Marketo forms](https://docs.os.default.com/forms/marketo.md) |
| Pardot form | Your page reports it with the Forms SDK. The Pixel recognizes Pardot forms but does not capture their submissions on its own. | [Pardot forms](https://docs.os.default.com/forms/pardot.md) |
| A custom form, for example in React | Your page reports it with the Forms SDK. | [Set up the Pixel and Forms SDK](https://docs.os.default.com/pixel-sdk-setup.md) |

Default drops a submission, and starts no workflow, when:

* The form has not been added to Default, or it is set to inactive.
* **Accept submissions** is off on the form's **Fields** tab.
* The form is limited to specific pages (**Track submissions on** on the form page), and the page is not one of them.

A submission with no valid email address starts no workflow. Default uses the email fields set
up in the Default form. When there are several, a field named `email`, `Email`, `work_email`,
`Work_email`, `workEmail`, or `WorkEmail` wins, then a required field, then the first in the form's
order. Its submitted name must match exactly, including capitalization. If that answer is missing,
blank, or invalid, Default does not try another answer. A cataloged form without an email field
has no submitter identity. Only legacy forms with no field list use named-email, whole-answer,
and free-text discovery. If the field list temporarily cannot be loaded, the workflow stays
blocked while ingestion can use its legacy identity lookup.

### Why the handoff is fast

The Pixel does its slow work before the visitor clicks submit:

* **On page load,** it fetches the list of your domain's forms that are wired to a scheduler,
  so it knows which submissions to hold on the page.
* **When the visitor leaves the email field,** it sends the email to Default while the visitor
  finishes the form. If the form's workflow has a **Match Record** node, Default can start that
  CRM lookup now. If your workspace has a
  [primary waterfall](https://docs.os.default.com/settings/configurations/waterfalls.md#primary-waterfall), Default also
  starts enriching the person.
* **On submit,** the workflow runs right away and hands the calendar link back in the same
  response.

This only works when the Pixel loads with the page. A Pixel added inside a submit handler
starts too late, and the calendar can take longer to appear or not appear at all. See
[Initialize on page load, not at submit](https://docs.os.default.com/pixel-sdk-integration-guide.md#initialize-on-page-load-not-at-submit).

### How the Pixel keeps the visitor on the page

A form that navigates away after submit would close the scheduler before it opens. For forms
wired to a **Display Scheduler** workflow, the Pixel holds the page:

* **Plain HTML forms:** the Pixel stops the browser from following the form's `action` URL.
  Your page's own submit handlers still run. If another system receives the form through that
  URL, that post no longer happens, so send the data to that system another way.
* **Marketo forms:** the Pixel tells Marketo to skip the form's follow-up page.
* **HubSpot forms:** HubSpot runs its own after-submit behavior. Set the form to show a
  thank-you message instead of redirecting. See [HubSpot forms](https://docs.os.default.com/forms/hubspot.md).

## Step 2: The submission starts a workflow

In **Workflows**, the **Form Submission** trigger starts a run for every submission to the
form you choose in **Connected Form**. Later nodes can use the submitted answers, plus the page
URL, referrer, and UTM parameters. See [Form submission](https://docs.os.default.com/workflows/triggers.md#form-submission).

![A form selected as a Form Submission trigger in the workflow builder](https://mintcdn.com/default-b6d0c477/39YvaBpPGQDPEJa1/images/forms/workflow-form-submission-trigger.png?fit=max\&auto=format\&n=39YvaBpPGQDPEJa1\&q=85\&s=d10dcb737db0a7bf8a5035cc3f382721)

A form can start more than 1 workflow. Only 1 of them can respond to the visitor, meaning it
contains a **Display Scheduler** or **Redirect** node. Publishing a second one for the same
form, while the first is live, fails with an error saying that another workflow attached to this
trigger already responds to the visitor. The other workflows for the form run in the background.

Nodes placed before the **Display Scheduler** run while the visitor waits, so keep that part of
the workflow to the steps that decide the host. Put CRM updates, notifications, and other steps
the booking does not depend on after the scheduler, on the **Booked** and **Not booked**
branches.

## Step 3: Routing picks the host

The **Display Scheduler** node's **Booking Details** section decides who the visitor can book
with:

| Option | How it works | When to use it |
| - | - | - |
| **Use event hosts** on, with a queue as the event's host | The event is a Team event with a [queue](https://docs.os.default.com/queues.md) as a host. The queue's routing policy picks the member. | Round robin across a team of reps. |
| **Use event hosts** on, with named members | The event's own hosts, required or optional. | A fixed person or pair, for example an account executive (AE) and a sales engineer. |
| **Use event hosts** off, with a host from workflow data | Pick a host from earlier nodes: **Latest assigned user** from a **Round-Robin** node, **Latest resolved user** from a **Rules of Engagement** node, or an owner ID that a CRM node found. | The account already has an owner, or [Rules of Engagement](https://docs.os.default.com/rules-of-engagement.md) decides the owner. |
| **Fallback Host (Optional)** | A backup host for when the primary host is out of office or unavailable. | Any of the above. |

For a queue host, the policy's **Slots Rule** sets which times the calendar shows: times when
any active member is free (**All Active Members**), or 1 member's times (**Single Member**).
Include **Meetings** in the policy's **Assignment Units** so the queue counts these bookings.
See [Policies](https://docs.os.default.com/policies.md#general).

> [!TIP]
>
> If the lead's account already has an owner in your CRM, book them with that owner instead of
> the next rep in the queue. Find the record with **Match Record**, pass its owner as the host,
> and set a **Fallback Host** for when the owner is away. Default converts the CRM owner to a
> Default user through each member's connection mapping in [Users](https://docs.os.default.com/settings/users.md).

## Step 4: The scheduler opens on the page

After submit, a short loading indicator appears in your booking-page colors, set in
[Scheduling settings](https://docs.os.default.com/settings/scheduler.md), with your workspace logo. The calendar then
replaces it in a full-screen overlay on your page, so by default the visitor stays on the page
they submitted from.

The calendar follows the visitor's device setting: a visitor on a dark system gets your dark
look, and a visitor on a light system gets your light look. Set the colors of each look with
the **Appearance** switch in [Scheduling settings](https://docs.os.default.com/settings/scheduler.md). Until you set a dark
look, Default derives one from your light colors. A page can force one look by passing
`theme: "light"` or `theme: "dark"` to `submitForm()`, or by adding `theme=light` or
`theme=dark` to a scheduler URL it loads itself. See the
[Pixel SDK reference](https://docs.os.default.com/pixel-sdk-reference.md#submitform).

You can change where the calendar appears:

* **Inside your page:** set `autoDisplayScheduler: { target: "#meeting-section" }` in the
  Pixel install snippet, and the calendar mounts in that element. See
  [The scheduler experience](https://docs.os.default.com/pixel-sdk-integration-guide.md#the-scheduler-experience).
* **Inside your own popup:** mount it inline as above and pass `background: "transparent"`
  (with `theme` set to match your popup), and the calendar leaves its card unpainted so your
  popup shows through. See the [Pixel SDK reference](https://docs.os.default.com/pixel-sdk-reference.md#submitform).
* **On another page:** set **Redirect to scheduler page** on the **Display Scheduler** node.
  The Pixel sends the visitor to that URL, and the calendar opens there. That page needs the
  Pixel installed too.

The calendar shows a countdown, "Complete your booking in", that matches the node's **Timeout**
in minutes (at least 3, 5 by default). These settings in the event's **Scheduler Settings**
section change what the visitor sees:

| Setting | What it does |
| - | - |
| **Scheduler appearance** | Shows the **Full** or **Compact** scheduler. |
| **Calendar Slots** | Shows the **Current Month**, or a **Rolling Month** that starts today. |
| **Hide booking countdown** | Hides the countdown. The workflow's timeout still applies. |
| **Hide close button** | Hides the close button when a form shows the scheduler. |

## Step 5: The visitor books the meeting

The visitor picks a time and confirms it. Default already has their email from the form, so
there is no second form to fill in. Default then:

* Books the meeting on the host's calendar and applies the event's calendar invite
  and sequence messages. See [Events](https://docs.os.default.com/events.md#messages) and [Events: Sequence](https://docs.os.default.com/events.md#sequence).
* Shows the visitor a confirmation page. With **Add redirect on meeting booked** set, the
  visitor moves on to that URL after the **Redirect delay** (10 seconds by default, up to 300).
* Lists the meeting in [Meetings](https://docs.os.default.com/meetings.md).
* Continues the workflow on the **Booked** branch. Later nodes can use the meeting's date and
  time, the event, and the primary and additional hosts.

Put the steps that depend on the booking on the **Booked** branch, for example a Slack message
to the host or a CRM update.

## What happens if the visitor doesn't book

The **Display Scheduler** node takes its **Not booked** branch in each of these cases:

| What the visitor does | What they see | When the workflow continues |
| - | - | - |
| Closes the calendar | The close button asks "Cancel your session?" with **Keep booking** and **Cancel session**. | Right away, after **Cancel session**. |
| Declines the reminder | With 90 seconds left, "Still there?" offers **Resume booking** and **Not interested**. | Right away, after **Not interested**. |
| Runs out of time | "Session ended" shows, and the calendar closes after 5 seconds. | Shortly after the timeout. |
| Leaves the page or closes the tab | Nothing. | Right away. If the browser drops that signal, shortly after the timeout. |

**Resume booking** only dismisses the reminder. It does not add time.

The submission and the person's record stay in Default whether or not the visitor books. On the
**Not booked** branch, the meeting values are empty. Common follow-ups:

* Send the visitor to a thank-you page with **Add redirect on meeting not booked**. Its
  **URL Parameters** can carry values from the workflow.
* Alert the owner with [Send Slack message](https://docs.os.default.com/workflows/steps-notifications.md#send-slack-message)
  so they can reach out while the lead is fresh.
* Add the lead to a sequence in Apollo, Outreach, Salesloft, or another
  [sequencing tool](https://docs.os.default.com/workflows/steps-sequencing.md).

## Set up a form that books meetings

This example books every demo request with the next rep in a queue named `Inbound AEs`.

**1. Add the form and map its fields**

In **Forms**, select **Create new**, then **Catalog forms**. Add the form on its
page, then map at least the email field in **Forms**. A mapping belongs to the field name,
so it applies on every form with a field of that name. See
[Your forms](https://docs.os.default.com/forms/your-forms.md#add-forms-from-your-site).

**2. Create the event**

In **Scheduling**, create a Team event, for example `30-minute demo`. Add the
`Inbound AEs` queue as a host. See [Events](https://docs.os.default.com/events.md#hosts-and-attendees).

**3. Add the trigger**

In **Workflows**, create a workflow and add the **Form Submission** trigger. Set
**Connected Form** to the demo request form.

**4. Add the Display Scheduler node**

Add **Display Scheduler**. Set **Event** to `30-minute demo` and leave **Use event hosts**
on. Set a **Timeout**, and optionally the redirects under **Redirect Settings**.

**5. Add the follow-up steps**

On the **Booked** branch, add the steps that depend on the meeting. On the **Not booked**
branch, add the follow-up for leads who left, for example a Slack alert.

**6. Publish, set live, and test**

Select **Publish**, then check that the status next to the
[deployment switch](https://docs.os.default.com/workflows.md#the-deployment-switch) reads **Live**. A new workflow goes live when you first
publish it. If the status reads **Paused**, turn the switch on.
Submit the form on your live page with a test email. The calendar opens on the page.

> [!WARNING]
>
> Booking from a test submission creates a real meeting on the host's calendar and counts
> toward the queue's round robin. Cancel the test meeting in [Meetings](https://docs.os.default.com/meetings.md) afterward.

Embedding the form in your own code? The
[integration guide](https://docs.os.default.com/pixel-sdk-integration-guide.md#the-scheduler-experience) covers how to
control where the calendar appears.

## Troubleshoot form scheduling

| What you see | What to check |
| - | - |
| The form submits, but no calendar appears | Check that the workflow is published and live, that it contains the **Display Scheduler** node, and that the submission includes an email. Then check the Pixel loads in the page `<head>`. |
| The page navigates away before the calendar opens | For HubSpot, set the form to show a thank-you message. For other forms, load the Pixel on page load so it knows the form is wired to a scheduler before the visitor submits. |
| The calendar takes a long time to appear | Move slow steps after the **Display Scheduler** node, and load the Pixel on page load. |
| Publishing fails because another workflow already responds to the visitor | 1 form can have only 1 workflow with a **Display Scheduler** or **Redirect** node. Pause the other workflow, or combine both into 1. |
| The run stops at the **Display Scheduler** node | Select **Runs** in the workflow's top Context Bar and open the run. See [Run logs](https://docs.os.default.com/workflows/run-logs.md). The node logs when it is waiting for a booking, when the visitor books, and when it resumes without a booking. |
| No submissions from the form reach Default | See [Troubleshooting](https://docs.os.default.com/forms/troubleshooting.md). |

Related: [Sales scheduling software from Default](https://www.default.com/product/sales-scheduling-software)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.