> ## 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. # Introduction to Default > What Default does and how its parts fit together: lead routing, scheduling, forms and the Pixel, enrichment, workflows, the Chrome extension, the API, and the MCP server. Default is a platform for lead routing, meeting scheduling, enrichment, and workflows. It captures inbound interest from your website, your CRM, and your own systems, decides who should own each lead, and books the meeting on that person's calendar. This page explains each part of Default and how the parts work together. Each section links to the page with the full detail. ## What Default does Default handles the steps between a lead showing interest and a rep meeting them: * **Capture.** The Pixel picks up form submissions on your website and identifies visitors. CRM changes, webhooks, the API, and the Chrome extension bring in leads from other places. * **Enrich.** Enrichment providers and waterfalls fill in person and company data. Default supplies the provider access and bills it in credits. * **Route.** Queues and routing policies pick 1 owner for each lead, CRM record, or meeting, and Default records every decision. * **Book.** The scheduler shows the chosen rep's open times, books the meeting, and sends the confirmations and reminders. * **Act.** Workflows chain these steps together and update your CRM, notify your team in Slack, or add people to a sequence in your sales engagement tool. ## The parts of Default at a glance You open each part of Default from the sidebar on the left of the app. | Part | What it does | Docs | | - | - | - | | Routing | Queues, reusable routing policies, Rules of Engagement, and the record of every assignment. | [Queues](/queues), [Policies](/policies), [Rules of Engagement](/rules-of-engagement) | | Scheduling | Bookable event types, booking links, the meetings list, and meeting messages. | [Events](/events), [Meetings](/meetings), [Messages](/scheduling-messages) | | Forms and the Pixel | A script on your website that captures submissions from the forms you add to Default and identifies visitors. | [Forms](/forms), [Your Forms](/forms/your-forms), [Reveal](/forms/reveal), [Privacy and data handling](/forms/privacy) | | Enrichment | Providers and waterfalls that fill in person and company fields, billed in credits. | [Waterfalls](/settings/configurations/waterfalls), [Enrichment providers](/settings/integrations/enrichment) | | Workflows | A trigger plus a chain of nodes that route, enrich, update the CRM, notify, and book. | [Workflows](/workflows), [Triggers](/workflows/triggers), [Node reference](/workflows/node-reference) | | Tables (Beta) | Your workspace's company and person records. Available where enabled. | [Tables](/tables) | | Chrome extension | Look up, enrich, route, and book a lead from any browser tab. | [Chrome extension](/chrome-extension) | | Public API | Fire a routing workflow and book meetings from your own server. | [Route and book through the API](/api/route-and-book) | | MCP server (Beta) | Lets an MCP-compatible AI client read and act on your workspace data. | [MCP server](/mcp-server) | | Agent | Default's own AI assistant. Coming soon. | [Agent](/agent) | ## How the parts of Default fit together A typical inbound demo request moves through Default like this: 1. **A visitor submits a form on your website.** The [Pixel](/forms) captures the submission from a form you added to Default. See [Your Forms](/forms/your-forms). 2. **The submission starts a workflow.** The workflow's **Form Submission** [trigger](/workflows/triggers#form-submission) names that form, so every submission runs it. 3. **The workflow enriches the lead.** An **Enrich Data** node fills in company and person fields from a provider or a [waterfall](/settings/configurations/waterfalls). 4. **The workflow checks your CRM.** A **Match Record** node looks for an existing record in Salesforce or HubSpot and branches on **Match** or **No Match**. See [CRM nodes](/workflows/steps-crm). 5. **The workflow routes the lead.** A **Round-Robin** node picks a member of a [queue](/queues), using the queue's [routing policy](/policies). A **Rules of Engagement** node picks an owner or a queue from the lead's data, and when it picks a queue, it selects the member the same way. 6. **The workflow books the meeting.** A **Display Scheduler** node shows the visitor a booking page for a scheduling [event](/events), then follows **Booked** or **Not booked**. See [Routing and scheduling nodes](/workflows/steps-routing-scheduling). 7. **Default follows up.** Later nodes create or update the CRM record, post to Slack, or add the lead to a sequence. Default sends the meeting confirmation and reminders from the event's [messages](/scheduling-messages). 8. **Everything is on record.** The workflow's [run log](/workflows/run-logs) shows the path the run took, and **Routing** keeps the decision record for each assignment. The same routing and booking steps run when a lead comes from a CRM change, an incoming webhook, a call to the [API](/api/route-and-book), or a rep using the [Chrome extension](/chrome-extension). ## Routing in Default Routing in Default picks 1 person to own each lead, CRM record, or meeting. A **queue** is a group of people, and each queue points at 1 reusable **routing policy** that holds the rules: * **Distribution Rule**: **Take turns equally** (round robin), **Most available calendar time**, or **Least recent assignment**. * **Enable weighted distribution**: gives some members a larger share. * **Tiebreaker rule**: **Recency** or **Random** when 2 or more members tie. * **Credit Behavior**: gives a member a turn back when their meeting is cancelled, reassigned, or marked as a no-show. [Rules of Engagement](/rules-of-engagement) chooses a queue or owner from CRM and enrichment data before a queue distributes the lead. Default keeps a decision record for every assignment, with the score of each member it considered. See [Queues](/queues) and [Policies](/policies). ## Scheduling in Default Scheduling in Default turns a routing decision into a meeting on a rep's calendar. An **event** is a bookable meeting type with a duration, hosts, availability, booking questions, and messages: * **Quick event**: 1 fixed member hosts the meeting. * **Team event**: 1 or more members or queues can host. A queue host routes each booking through the queue's policy. Default writes each booked meeting to the host's Google Calendar or Outlook Calendar and can add a Zoom, Google Meet, or Microsoft Teams link. It sends email and SMS confirmations and reminders from reusable [message templates](/scheduling-messages). The [Meetings](/meetings) list shows every meeting in the workspace with its status: Booked, Rescheduled, No show, or Canceled. A teammate marks a meeting as a no-show in **Meetings** or in the Chrome extension. Default doesn't detect no-shows automatically, and it doesn't mark meetings as held. See [Events](/events). ## Forms and the Pixel in Default The **Pixel** is a script you add to your website. You add each form on your pages to Default with **Catalog forms**, which recognizes plain HTML forms and HubSpot, Marketo, and Pardot embedded forms. You can also create a form in Default with **Create new**, then **New form**. You set its fields in Default, but Default doesn't design or host it, so the form still lives on your website. To put it there, copy **Embed this form** from the editor's **Install** tab: a working HTML form with its fields and submission already wired up, which you place and style on your site. You map each form's fields to Person and Company records, and from then on each submission can start a workflow. See [Your Forms](/forms/your-forms). The Pixel captures submissions from HTML, HubSpot, and Marketo forms on its own. For a Pardot form, your site sends each submission with the Forms SDK `submitForm()` call. Your own server can also send submissions through the [API trigger](/workflows/triggers#api). The Pixel also tracks page views, and [Reveal](/forms/reveal) identifies the companies and people behind visits to pages you choose. A **Display Scheduler** node can show a booking page right after a submission. See [Forms](/forms), [Set up the Pixel and Forms SDK](/pixel-sdk-setup), and [Privacy and data handling](/forms/privacy) for what the Pixel never captures. ## Enrichment in Default Enrichment in Default fills in person and company fields from outside data providers. A **waterfall** is an ordered list of up to 5 providers, and the order sets each provider's priority. The **Enrich Data** workflow node and form pre-enrichment call every provider in the waterfall at the same time and merge the results, so a field from a higher provider wins. **Tables** and the Chrome extension call providers 1 at a time and stop at the first provider that returns data. The providers are Clearbit, Apollo, People Data Labs, and Wiza, with optional email validation through Abstract or Icypeas. Default supplies access to every enrichment provider, so you don't need an account or API key with any of them. Provider calls use enrichment credits. See [Plans and limits](/overview/plans-and-limits#enrichment-credits-in-default) for what each call costs. Workflows enrich through the **Enrich Data** node, and [Deep Research](/workflows/steps-research) (Beta) researches the live web through Parallel. See [Waterfalls](/settings/configurations/waterfalls) and [Enrichment providers](/settings/integrations/enrichment). ## Workflows in Default A workflow in Default starts from 1 **trigger** and runs a chain of **nodes** on a canvas. There are 8 triggers: | Trigger | Starts the workflow when | | - | - | | **Form Submission** | Someone submits a form you track with Default. | | **Meeting Status** | A meeting changes status, for example to No show or Canceled. | | **Website Intent Signal** | Default identifies a visitor to your website. | | **CRM Record Created** | A new record appears in Salesforce or HubSpot. | | **CRM Record Updated** | A record changes in Salesforce or HubSpot. | | **Incoming Webhook** | An outside system sends a request to your workspace's webhook URL. | | **Extension** | A rep books or routes a lead from the Chrome extension. | | **API** | Your server fires the workflow through the public API. | Nodes route and book, create and update CRM records, add people to sequences, send Slack messages and internal emails, enrich data, prompt an AI model, branch on conditions, and wait. Edits save to a draft, and **Publish** makes a new version live. See [Workflows](/workflows), [Triggers](/workflows/triggers), and the [Node reference](/workflows/node-reference). ## The Chrome extension The Default Chrome extension puts routing, booking, and lead lookup in a browser side panel. On Gmail, Salesforce, and HubSpot pages it offers the lead you are viewing. A rep can look the lead up in the CRM, request enrichment, book a meeting or copy a booking link through a routing workflow, and reassign, reschedule, cancel, or mark a no-show on upcoming meetings. See [Chrome extension](/chrome-extension). ## The API and MCP server Default has 2 ways for your own software and AI tools to work with a workspace: * **Public API.** Your server fires a workflow's **API** trigger, gets the scheduler the workflow chose, and books a meeting, in 4 requests. The API also lists events and reschedules or cancels meetings. It uses API keys and allows 30 requests per minute per key. See [Route and book through the API](/api/route-and-book) and the [API reference](/api-reference/triggers/list-triggers). * **MCP server (Beta).** An MCP-compatible AI client, such as Claude, Cursor, or Codex, signs in to Default and calls tools that query company, person, and CRM data, explain routing decisions, check open slots, and create booking links. See [MCP server](/mcp-server). [Booking meetings through AI agents and the API](/api/agent-tools) compares the options for AI agents. ## Agent in Default Agent is Default's own AI assistant. It is coming soon, and Default publishes its documentation when the feature set is final. See [Agent](/agent). Agent is separate from outside AI agents. An AI agent you build or use elsewhere can already work with Default through the public API and the MCP server. ## Integrations in Default | Category | Tools | | - | - | | CRM | Salesforce and HubSpot | | Calendar | Google Calendar and Outlook Calendar | | Conferencing | Zoom, Google Meet, and Microsoft Teams | | Sequencing | Apollo, Outreach, Salesloft, Amplemarket, Smartlead, Gong Engage, and HubSpot Sequences | | Notifications | Slack | | Enrichment | Clearbit, Apollo, People Data Labs, and Wiza, plus Abstract and Icypeas for email validation | | Website Intent | Clearbit Reveal, Demandbase, and Vector | Default adds people to sequences in your sequencing tool. It has no sequencing product of its own. Tools without a native integration can send data in through an **Incoming Webhook** trigger or the API, and a **Send to Webhook** node can send data out. See [Integrations](/settings/integrations). ## Where to start with Default * Admins setting up a workspace: [Set up your workspace](/get-started). * Members joining a workspace: [Member onboarding](/member-onboarding). * Teams moving from a previous Default workspace: [Migrating your workspace](/migrate). * Terms you meet in the product: [Default glossary](/overview/glossary). Related: [Default](https://www.default.com) and [the Default product overview](https://www.default.com/product) This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.