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

# Round robin and group meetings in Default

> Book round robin meetings with a Team event hosted by a queue, choose how the booking page offers times with the Slots Rule, and book meetings with several hosts, optional teammates, fixed invitees, and guests.

Default books round robin meetings through a Team event hosted by a queue: each time someone
books, the queue's routing policy picks 1 member to host. The same Team event can hold several
hosts, members or queues, so 1 booking can bring in an account executive, a solutions engineer,
and optional teammates together.

## Meeting setups Default supports

| Meeting setup | How to build it in Default | Who's on the invite |
| - | - | - |
| Round robin across a team | A **Team event** with a queue as its host. | The member the queue's policy picks, and the guest. |
| Several reps in 1 meeting | A **Team event** with several members or queues as required hosts. | Every host. Each queue adds the 1 member it picks. |
| Round robin plus a named rep | A **Team event** with a queue and a member as hosts. | The picked member, the named member, and the guest. |
| Optional teammates | Mark a host optional in the event. | Optional hosts are invited as optional attendees. |
| The same invitees on every booking | **Add additional participants** in the event. | Those email addresses, each required or optional. |
| The guest's colleagues | The booking page's **Invite guests** field. | Up to 10 more email addresses the booker enters. |
| 1 fixed host | A **Quick event**. | That member and the guest. |

Group sessions where many guests book the same time slot, with a seat limit, aren't available.
Webinar events, for many hosts to many attendees, are coming soon. See
[What Default doesn't support for group meetings](#what-default-doesnt-support-for-group-meetings).

## Set up a round robin Team event hosted by a queue

<Steps>
  <Step title="Build the queue">
    In the **Routing** app, create a [queue](/queues) with the reps who share the meetings, and
    point it at a [routing policy](/policies). Each member needs a connected, active primary
    calendar to receive meetings.
  </Step>

  <Step title="Create a Team event">
    In the **Scheduling** app, select **Create new event** and choose **Team event**. Creating Team
    events needs permission to create shared events.
  </Step>

  <Step title="Add the queue as the host">
    In the event's **Hosts and Attendees** section, add the queue under **Host assignment**.
  </Step>

  <Step title="Save and share">
    Select **Save**. Share the event's booking link, or show the event in a workflow with a
    **Display Scheduler** node.
  </Step>
</Steps>

Each booking becomes a meeting assignment in the queue. The policy's distribution rule picks the
member: **Take turns equally**, **Most available calendar time**, or **Least recent assignment**.
Member weights apply when **Enable weighted distribution** is on, and the **Tiebreaker rule**
settles ties. See [Policies](/policies#assignment).

<Tip>
  Include **Meetings** in the policy's **Assignment Units** on the **General** tab. A policy counts
  only the kinds of work it routes, so a queue that hands out meetings needs Meetings counted to
  keep its rotation balanced.
</Tip>

## Choose how the booking page offers times with the Slots Rule

The policy's **Slots Rule**, under **Scheduler Settings** on the **General** tab, sets how a
queue-hosted event offers times:

| Slots Rule | Times the booking page shows | When Default picks the host |
| - | - | - |
| **All Active Members** | Times when any active member of the queue is free. | When the guest books, from the members free at that time. |
| **Single Member** | Times for 1 member only. | Before times appear. The pick holds for that booking session. |

New policies start on **Single Member**. The **Most available calendar time** distribution rule
works only with **All Active Members**.

**All Active Members** offers the widest set of times. **Single Member** shows only the picked
member's calendar, which keeps the rotation exact at the cost of fewer times.

## Book several hosts into the same meeting

A Team event can have several hosts. Each host is a member or a queue, and each has 2 settings:

* Primary host: 1 host carries the **Primary** badge. Select **Make primary** on another host to
  change it. The primary host organizes the meeting, so the calendar event is created on their
  calendar.
* Required or optional: each host shows **Required** or **Optional**. On any host except the
  primary, select **Make required** or **Make optional** to switch it. A required host must be free
  for a time to appear. An optional host is invited as an optional attendee and doesn't limit the
  times.

Default shows only the times when the primary host and every required host are free. A queue
counts as free when a member it can pick is free: any active member under **All Active Members**,
or the member picked for that session under **Single Member**.

For example, an event with an account executive queue as the primary host and a solutions engineer
queue as a required host books 1 account executive and 1 solutions engineer into every meeting, at
times when both queues have someone free. Each queue records its own assignment, so both rotations
stay balanced.

Add a sales manager as an optional host to keep them on the invite without limiting the times.

## Add fixed invitees and guests to meetings

* **Add additional participants**, in the event's **Hosts and Attendees** section, adds the same
  email addresses to every booking. Mark each one required or optional.
* The booking page's **Invite guests** field lets the person booking add up to 10 more email
  addresses, for example their colleagues.
* When a rep books from the
  [Chrome extension](/chrome-extension#book-a-meeting-or-copy-a-booking-link-through-a-routing-workflow),
  the booking page's **Additional hosts** list adds teammates as optional or required hosts, up to
  10 in all. Default adds the booking rep there as an optional host. The same page has its own
  **Invite guests** field for up to 10 email addresses.

## Offer a fallback host in a workflow

When a workflow shows the event with a **Display Scheduler** node, set **Fallback Host (Optional)**
to cover a queue with no open times. When the event's hosts have no available times, the booking
page offers the fallback host's times instead. The node can also replace the event's hosts with
custom hosts: turn off **Use event hosts** and pick members or queues, with 1 primary and the others
required or optional. See [Display Scheduler](/workflows/steps-routing-scheduling#display-scheduler).

## Share a round robin or multi-host booking link

* The event's **Booking links** drawer starts with a link for each host. For a queue host, the link
  uses the queue's identifier. Select **New** to create a link with a different set of members or
  queues as hosts. See [Booking links](/events#booking-links).
* In the Chrome extension's **Events** tab, **Custom** creates a link with the members and queues
  you pick. See [the Chrome extension](/chrome-extension#share-an-events-booking-link-from-the-events-tab).

## What Default doesn't support for group meetings

* Group sessions with seats: Default books 1 meeting per booking. It has no seat or capacity limit
  that lets many separate guests book the same time slot.
* Webinar events: an event type for many hosts and many attendees, such as group office hours. It's
  coming soon and can't be created yet.

To bring several people into 1 meeting today, add them as hosts, additional participants, or
guests, as described above.

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.