# Default

Default is a scheduling platform that provides embeddable booking queues. Spara can embed Default calendars directly within the chat interface, allowing leads to schedule meetings without leaving the conversation.

{% hint style="warning" %}
Default provides limited API support for data prepopulation and reading. Because of this, Spara does not recommend Default as a primary calendar solution. Consider [Cal.com](/integrations/calendar-integrations/cal.com.md) for the most complete integration.
{% endhint %}

## Data flows

<table data-full-width="true"><thead><tr><th>Spara can prepopulate...</th><th>Spara can read from submitted calendar...</th><th>Integration Notes</th></tr></thead><tbody><tr><td><ul><li>Email</li></ul></td><td><ul><li>Email</li></ul></td><td>Default only supports email prepopulation. Spara should capture the lead's email before showing the calendar.</td></tr></tbody></table>

## Setup

{% stepper %}
{% step %}

#### Get your Default calendar URL

Log in to your Default account and find your scheduling queue URL. It follows this format:

```
https://scheduler.default.com/<team_id>/queue/<queue_id>
```

{% endstep %}

{% step %}

#### Provide the URL to Spara

Contact your Spara account manager or CSM with your Default calendar URL. Spara will configure the integration on your behalf.
{% endstep %}
{% endstepper %}

{% hint style="info" %}
Default calendar integration is configured by Spara internally. Please contact your customer service representative to get started.
{% endhint %}

## How it works

Default calendars are embedded as an iframe within Spara's chat interface. When your agent determines a lead is ready to schedule, it presents the Default booking widget. The lead can select a time and complete the booking without leaving the conversation.

Spara captures the lead's email address before showing the calendar and prepopulates it in the Default form to reduce friction.

## Default Forms SDK

The Forms SDK is Default's programmatic embed for triggering the scheduling drawer directly from your own website code, bypassing the native Default form. Most Spara customers use the Forms SDK approach because it gives Spara — and your existing site — full control over when the calendar drawer opens and what data is passed in.

**Why use the Forms SDK instead of the native Default form?**

* The Default form lives inside Default's hosted UI. With the Forms SDK, the form lives on your own page and you control the styling, validation, and submission flow.
* You can call the SDK from a CTA, after a custom qualification step, or from Spara's chat — instead of redirecting the lead off-page.
* It allows Spara and your own JavaScript to share the same booking surface, so the lead experiences a single seamless flow.

### What Spara needs from you

To wire up the Forms SDK on your site, share the following with your Spara CSM:

* **`form_id`** — the unique identifier for the Default form you want to trigger
* **`team_id`** — the Default team that owns the form
* **Submission script** — the snippet that calls Default's SDK to open the drawer (see Default's official guide: [Default Forms SDK](https://docs.default.com/articles/3276343596-forms-sdk?lang=en))

Spara will use these to configure the integration so the calendar drawer opens correctly from within the chat experience.

### What the drawer looks like

When the Forms SDK fires, Default opens a drawer over your page containing the booking flow. The lead picks a time and completes the booking without leaving your site. See Default's [Forms SDK documentation](https://docs.default.com/articles/3276343596-forms-sdk?lang=en) for live examples of the drawer in action.

## FAQ

### Why can Spara only prepopulate email?

Default's embed API currently supports limited field prepopulation. Unlike other calendar providers (such as Cal.com, which supports name, email, phone, and company), Default only accepts email as a prepopulated field.

### Does Spara know when a meeting is booked?

Yes. Spara detects when a calendar event has been scheduled through Default and can react accordingly — for example, by sending a confirmation message or progressing the lead through a workflow.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.spara.com/integrations/calendar-integrations/default.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.