> ## 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.

# Following up with leads who didn't book a meeting in Default

> When a visitor submits a form but doesn't book, a Default workflow takes the Display Scheduler node's Not booked branch, where you can alert your team in Slack, assign an owner, create a CRM task, and add the lead to a sequence in Apollo, Outreach, Salesloft, Amplemarket, Smartlead, Gong Engage or HubSpot.

When a visitor submits a form but doesn't book a meeting, a Default workflow sends the lead down
the **Display Scheduler** node's **Not booked** branch. Nodes on that branch follow up: they alert
your team in Slack, assign an owner, create or update the CRM record, give the owner a task, and
add the lead to a sequence in Apollo, Outreach, Salesloft, Amplemarket, Smartlead, Gong Engage or
HubSpot.

## How Default catches leads who don't book

1. The **Form Submission** trigger starts the workflow on every submission, whether or not the
   visitor books. See [Triggers](/workflows/triggers#form-submission).
2. A **Display Scheduler** node shows the visitor a calendar and waits for a booking. See
   [how Default books a meeting from a form submission](/forms/scheduler).
3. The node continues down 1 of 2 branches: **Booked** or **Not booked**.
4. The nodes you place on **Not booked** run the follow-up.

Default has no sequencing product of its own. It adds the lead to a sequence, cadence, campaign,
or flow in the tool your team already uses.

## When the Not booked branch runs

The **Display Scheduler** node takes the **Not booked** branch when:

* The visitor closes the scheduler, closes its tab, or leaves the page without booking. The branch
  runs right away.
* The node's **Timeout** passes without a booking. The **Timeout** is set in minutes, with a
  minimum of 3 and a default of 5. Default keeps this timer itself, so the branch still runs when
  the visitor's browser never reports that they left.

On the **Not booked** branch, the meeting's date, event, and hosts are empty, since no meeting
exists. The trigger's data, such as the form answers and the lead's email, is still available to
every node.

To send the visitor to another page when they don't book, set **Add redirect on meeting not booked**
on the node, for example to a resources page. See
[Display Scheduler](/workflows/steps-routing-scheduling#display-scheduler).

## Follow-up actions for leads who didn't book

| Goal | Node to add on Not booked | Notes |
| - | - | - |
| Alert the team in Slack | **Send Slack Message** | Post to a channel, message teammates directly, or both. Type `{{` to insert form answers. See [Notification nodes](/workflows/steps-notifications). |
| Email teammates | **Send Internal Email** | Emails internal Default users only. It can't email the lead. |
| Assign an owner | **Round-Robin** | Picks a member of a queue. Later nodes use them as **Latest assigned user**. See [Routing and scheduling nodes](/workflows/steps-routing-scheduling#round-robin). |
| Find, create, or update the CRM record | **Match Record**, **Create Record**, **Update Record** | For example, set a lead status that marks the lead as not booked. See [CRM nodes](/workflows/steps-crm). |
| Give the owner a follow-up task | **Create Activity** (Salesforce) or **Create Engagement** (HubSpot) | Create a Salesforce Task or a HubSpot Task on the lead's record. |
| Add the lead to a sequence | **Add to Apollo Sequence**, **Add to Outreach Sequence**, **Add to Salesloft Cadence**, **Add to Amplemarket Sequence**, **Add to Smartlead Campaign**, **Enroll in HubSpot Sequence**, **Add to Gong Engage Flow** | Each tool must be connected under **Settings → Integrations**. See [Sequencing nodes](/workflows/steps-sequencing). |
| Treat leads differently | **Multi-Branch** | For example, send enterprise leads to a rep and everyone else to a sequence. See [Logic and timing nodes](/workflows/steps-logic-timing). |
| Wait before acting | **Time Delay** | Pause the workflow for a set time before the next node. |
| Hand the lead to another system | **Send to Webhook** | Post the lead's data to a URL you choose. See [Action nodes](/workflows/steps-actions). |

## Example: a demo request that didn't book

This workflow follows up on every demo request that ends without a meeting. It assigns an owner
only to new leads and leaves existing owners in place.

<Steps>
  <Step title="Trigger on the demo form">
    Start the workflow with the **Form Submission** trigger and your demo request form as the
    **Connected Form**.
  </Step>

  <Step title="Show the scheduler">
    Add a **Display Scheduler** node with your demo event. The **Booked** branch handles leads who
    book.
  </Step>

  <Step title="Check the CRM on Not booked">
    On **Not booked**, add **Match Record** to look for the lead in Salesforce or HubSpot by email.
  </Step>

  <Step title="Existing lead: task the current owner">
    On **Match**, add **Create Activity** (Salesforce) or **Create Engagement** (HubSpot) to create
    a follow-up task, with the owner taken from the matched record. The record keeps its owner.
  </Step>

  <Step title="New lead: assign, create, and sequence">
    On **No Match**, add **Round-Robin** with your inbound queue, then **Create Record** with the
    owner set to **Latest assigned user**. Then add a sequencing node, for example **Add to
    Outreach Sequence**, with a sequence written for leads who didn't book and the assigned rep's
    mailbox as the sender.
  </Step>

  <Step title="Tell the new owner">
    Still on **No Match**, add **Send Slack Message** with **Latest assigned user** as a
    recipient, so the rep knows the lead is theirs.
  </Step>
</Steps>

The sending mailbox for a sequence comes from the integration mappings that link each Default user
to their account in the sequencing tool. See [Users](/settings/users).

## Follow up when a booked meeting is cancelled

A lead who books and then cancels needs a follow-up too. Start a separate workflow with the
**Meeting Status** trigger and select **Canceled** under **Meeting statuses**. The workflow gets the
meeting's details, the **Primary host**, and the cancellation reason when one was given.
Add the same follow-up nodes as above, for example **Send Slack Message** to the host and a
sequencing node for the lead. See [Triggers](/workflows/triggers#meeting-status).

For guests who don't show up, see [Reminders and no-shows](/scheduling/reminders-and-no-shows).

## See which leads didn't book

Open the workflow and select **Runs** in the top Context Bar. Each run shows the path it took, so
runs that ended on **Not booked** are easy to spot, and the node summaries show what each follow-up
node did. When a recording of the visitor's scheduler session is available, the run also shows a
**View Scheduling Replay** button. See [Run logs](/workflows/run-logs).

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.