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

# Default glossary

> Definitions of the terms used in Default: queues, routing policies, round robin, weighting, tiebreakers, Rules of Engagement, events, workflows, triggers, nodes, waterfalls, credits, the Pixel, Reveal, and more.

This glossary defines the terms a buyer, admin, or rep meets in Default. Terms are grouped by area,
and each one links to the page with the full detail. Labels in bold match the Default app.

## Routing terms in Default

| Term | What it means in Default |
| - | - |
| Queue | A named group of people that points at 1 routing policy. Default picks 1 active member of the queue for each lead, CRM record, or meeting. See [Queues](/queues). |
| Routing policy | A reusable set of routing rules: the distribution rule, tiebreaker, weighting, availability exclusions, and credit behavior. 1 policy can drive many queues, and each edit creates a new version. See [Policies](/policies). |
| Distribution rule | How a policy scores queue members: **Take turns equally**, **Most available calendar time**, or **Least recent assignment**. See [Distribution rule](/policies#distribution-rule). |
| Round robin | Default's **Take turns equally** rule. The member with the fewest assignments since the last reset receives the next one. See [Policies](/policies#distribution-rule). |
| Weighting | With **Enable weighted distribution** on, each member's weight sets their share. A member with a weight of 2 receives about 2 assignments for every 1 that a member with a weight of 1 receives. See [Distribution settings](/policies#distribution-settings). |
| Tiebreaker | The **Tiebreaker rule** picks the winner when 2 or more members share the best score: **Recency** or **Random**. See [Distribution settings](/policies#distribution-settings). |
| Assignment Units | The kinds of work a policy routes and counts: **Objects** (CRM records), **Meetings**, or both. See [General](/policies#general). |
| Slots Rule | For a queue that hosts a Team event, whether the booking page shows times for **All Active Members** or for a **Single Member**. See [General](/policies#general). |
| Calibration | A manual change to 1 member's assignment count, for example to bring a new member up to the queue average. See [Calibration](/queues#calibration). |
| Credit Behavior | Policy settings that give a member a turn back when their meeting is cancelled, reassigned, or marked as a no-show. See [Credit Behavior](/policies#credit-behavior). |
| Assignment | The record of 1 routing decision: who received the lead or meeting, from which queue, and every scored member's score. See [Assignments](/queues#assignments). |
| Activity log | The record of changes to queues and their members in the **Routing** app. See [Activity log](/queues#activity-log). |
| Rules of Engagement | Reusable rules that choose a queue or owner for a record from CRM and enrichment data. Rules run from top to bottom, and the first rule that matches wins. See [Rules of Engagement](/rules-of-engagement). |
| Ruleset | A published set of Rules of Engagement rules. A workflow runs it through the **Rules of Engagement** node. See [Rules of Engagement](/rules-of-engagement). |

## Scheduling terms in Default

| Term | What it means in Default |
| - | - |
| Event | A bookable meeting type with a name, duration, hosts, availability, booking questions, and messages. Also called an event type. See [Events](/events). |
| Quick event | An event that 1 fixed member hosts, such as a personal intro-call link. See [Create an event](/events#create-an-event). |
| Team event | An event that 1 or more members or queues can host. A queue host picks the member for each booking through the queue's policy. See [Create an event](/events#create-an-event). |
| Booking link | A URL where a lead books an event. **Permanent** links work until you delete them, and **Expiring** links stop on their expiration date. See [Booking links](/events#booking-links). |
| Scheduler | The booking page where a lead picks a time. A **Display Scheduler** node shows it inside a workflow, and the API returns it as a `scheduler` outcome. See [Display Scheduler](/workflows/steps-routing-scheduling#display-scheduler). |
| Meeting status | Where a meeting stands: **Booked**, **Rescheduled**, **No show**, or **Canceled**. **Held** also appears in the status list, but Default doesn't mark meetings as held. See [Meetings](/meetings). |
| No show | A meeting status that a teammate sets in **Meetings** or in the Chrome extension. Default doesn't detect no-shows automatically. See [Review a meeting](/meetings#review-a-meeting). |
| Messages | Reusable templates for meeting notifications and reminders, which Default sends by email and SMS. Events assign templates to each notification and reminder. See [Messages](/scheduling-messages). |
| Working hours | The weekly hours when a member can be booked. See [Working hours](/settings/availability/working-hours). |
| Out of office | Time off set in Default or on a member's calendar. Default can skip members who are out of office when it routes. See [Out of office](/settings/availability/ooo). |
| Scheduling username | The identifier in a member's own booking links. See [User details](/settings/users#user-details). |

## Forms and website terms in Default

| Term | What it means in Default |
| - | - |
| Pixel | The script you add to your website. It captures page activity and submissions from the forms you add to Default, and sends them to Default. See [Forms](/forms). |
| Signals | Where you connect the websites the Pixel tracks and copy the Pixel script. It is in the sidebar under **Automation**. See [Signals](/forms/signals). |
| Your Forms | The list of forms Default captures submissions for: forms you add from your site with **Catalog forms**, and forms you create in Default. You map each form's fields to Person and Company records. See [Your Forms](/forms/your-forms). |
| Field mapping | Telling Default which record field each form field fills, such as a person's email or a company's name. See [Map form fields](/forms/your-forms#map-form-fields). |
| Reveal | Identifies the companies, and in batches the people, behind visits to pages you choose, including visitors who never submit a form. See [Reveal](/forms/reveal). |
| Website Intent | The providers that identify anonymous website traffic: Clearbit Reveal, Demandbase, and Vector. They are available at an additional cost. See [Website Intent](/settings/integrations/enrichment#website-intent). |
| Account Signal and People Signal | The 2 versions of the **Website Intent Signal** trigger. **Account Signal** identifies the visitor's company as the page loads. **People Signal** identifies the person in batches, about every 30 minutes. See [Website intent signal](/workflows/triggers#website-intent-signal). |
| Consent | The visitor's choice for `analytics` and `marketing` tracking, which your consent banner passes to the Pixel with `setConsent`. See [Consent gating](/forms/privacy#consent-gating). |

## Enrichment terms in Default

| Term | What it means in Default |
| - | - |
| Enrichment | Filling in person and company fields from outside data providers. Default supplies provider access, so you don't need an account or API key with any provider. See [Enrichment providers](/settings/integrations/enrichment). |
| Waterfall | An ordered list of up to 5 enrichment providers, where the order sets each provider's priority. The **Enrich Data** node and form pre-enrichment call every provider at once and merge the results. **Tables** and the Chrome extension try providers in order and stop at the first result. See [Waterfalls](/settings/configurations/waterfalls). |
| Primary waterfall | The workspace's default waterfall. Workflows use it when they don't name a waterfall. See [Primary waterfall](/settings/configurations/waterfalls#primary-waterfall). |
| Credits | The unit Default uses to count enrichment provider calls. Each provider has a set cost per call. See [Enrichment credits](/overview/plans-and-limits#enrichment-credits-in-default). |
| Company and Person | The 2 core record types in Default. For each field, you set which data sources can fill it and in what order. See [Objects](/settings/configurations/objects). |
| Deep Research | A workflow node, in beta, that researches the live web through Parallel and returns fields you define. See [Deep Research](/workflows/steps-research). |

## Workflow terms in Default

| Term | What it means in Default |
| - | - |
| Workflow | An automation that starts from 1 trigger and runs a chain of nodes. See [Workflows](/workflows). |
| Trigger | What starts a workflow. There are 8: **Form Submission**, **Meeting Status**, **Website Intent Signal**, **CRM Record Created**, **CRM Record Updated**, **Incoming Webhook**, **Extension**, and **API**. See [Triggers](/workflows/triggers). |
| Node | 1 step on the workflow canvas, such as **Enrich Data**, **Match Record**, **Round-Robin**, or **Send Slack Message**. See the [Node reference](/workflows/node-reference). |
| Draft and Publish | Workflow edits save to a draft that everyone in the workspace shares. **Publish** makes the draft a new live version. See [Publish a workflow](/workflows#publish-a-workflow). |
| Deployment switch | The switch in the workflow builder's top Context Bar that sets a published workflow live, so its status reads **Live**, or pauses it. See [the deployment switch](/workflows#the-enabled-switch). |
| Run log | The record of 1 workflow run: the trigger, the path it took, and what each node did. See [Run logs](/workflows/run-logs). |
| Round-Robin node | A node that assigns a member of a queue through the queue's policy. Later nodes use the member as **Latest assigned user**. See [Round-robin](/workflows/steps-routing-scheduling#round-robin). |
| Display Scheduler node | A node that shows a booking page, waits, and then follows **Booked** or **Not booked**. See [Display Scheduler](/workflows/steps-routing-scheduling#display-scheduler). |
| Match Record | A node that finds 1 record in Salesforce or HubSpot and follows **Match** or **No Match**. See [Match Record](/workflows/steps-crm#match-record). |
| Incoming webhook | A trigger that starts a workflow when an outside system sends a request to a webhook URL Default gives you. See [Incoming webhook](/workflows/triggers#incoming-webhook). |
| Webhook secret | The single bearer secret that authenticates every incoming webhook in a workspace. See [Webhook Secret](/settings/webhook-secret). |
| Send to Webhook | A node that sends an HTTP request to an outside endpoint and passes the response to later nodes. See [Send to Webhook](/workflows/steps-actions#send-to-webhook). |

## Workspace and access terms in Default

| Term | What it means in Default |
| - | - |
| Sidebar | The navigation on the left of the app. Its sections, such as **Automation**, **Routing**, **Scheduling**, and **Configuration**, open each part of Default. |
| Admin, Member, and Viewer | The 3 workspace roles. **Admin** has access to all features, **Member** has access to selected features, and **Viewer** has read-only access. See [Users](/settings/users). |
| Single sign-on (SSO) | Signing in to Default through your identity provider after an admin verifies your email domain and sets up a connection. See [Single Sign-On (SSO)](/settings/enterprise). |
| Integration mapping | The link between a member's Default user and their ID in a connected tool, such as their Salesforce User ID. Routing and CRM writes use it. See [Integrations](/settings/users#integrations). |
| Tables | Your workspace's company and person records. In beta and available where enabled. See [Tables](/tables). |

## Developer and AI terms in Default

| Term | What it means in Default |
| - | - |
| API key | A key an admin creates in **Settings** → **API Keys** to call the public API. Each key carries only the permissions selected for it. See [Authentication](/api/route-and-book#authentication). |
| API trigger | A workflow trigger that your server fires through the public API. See [API](/workflows/triggers#api). |
| MCP server | Default's server for MCP-compatible AI clients, such as Claude or Cursor. MCP, the Model Context Protocol, is a standard way for AI clients to call tools. It is in beta. See [MCP server](/mcp-server). |
| Chrome extension | A browser side panel where reps look up, enrich, route, and book leads from any tab. See [Chrome extension](/chrome-extension). |
| Agent | Default's own AI assistant. Coming soon. See [Agent](/agent). |

Related: [Default product overview](https://www.default.com/product)


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