> ## Documentation Index
> Fetch the complete documentation index at: https://docs.dmly.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Meetings

> Meetings is DMLY's older booking hub — it no longer appears in the sidebar, and Appointments and Offerings replace it.

**Meetings** is DMLY's original booking hub. Everything it does is now done better somewhere
else: the bookings it lists are the same bookings you see in
[Appointments](/appointments/overview), and the meeting types it edits are the same rows you
edit in [Offerings](/offerings/overview) under **Services**. There is no separate "meeting"
record and no separate "meeting type" record — two screens, one set of data.

This page exists mainly so you stop looking for it.

## Meetings is not in the sidebar

If you are hunting the sidebar for a **Meetings** item, stop. It is not there and it is not
hidden behind a plan, a permission or a setting. The sidebar's business section lists
**Appointments**, **Offerings**, **Finance** and **Reputation** — that is all.

<Note>
  Meetings still works if you land on it, and nothing about it is broken. It is simply older
  than the pages that replaced it, and DMLY no longer routes you there. Use
  [Appointments](/appointments/overview) and [Offerings](/offerings/overview) instead.
</Note>

There are exactly two ways in.

**Bookmark the address.** If you have an old link or bookmark to the bookings list or the
meeting types list, it still opens.

**Take the Inbox detour.** One link in the product still points at Meetings, buried two levels
down:

<Steps>
  <Step title="Open a conversation">
    Go to **Messaging → Unified Inbox** and open any conversation.
  </Step>

  <Step title="Open the booking-link menu">
    In the message composer's toolbar, select the calendar icon — its tooltip reads
    **Insert booking link**.
  </Step>

  <Step title="Select Manage meeting types">
    At the bottom of that menu, select **Manage meeting types**. That opens the meeting types
    page.
  </Step>

  <Step title="Switch to Bookings">
    From the meeting types page, the **Bookings** tab is the only way to reach the meetings
    list. Nothing else in DMLY links to it.
  </Step>
</Steps>

That entry point has a catch worth understanding, because it is why most people never see it
at all: the calendar icon only appears when your workspace already has at least one active
service with a working booking link. With no bookable service, there is no calendar icon, no
menu, and therefore no route to Meetings from anywhere in the interface. And if you *do* have
bookable services, you created them in **Offerings → Services** — which is where you would
manage them anyway. The hub is hardest to reach exactly when you might want it.

## Use these instead

<Columns cols={2}>
  <Card title="Appointments" icon="calendar-days" href="/appointments/overview">
    The same bookings, with a calendar view, staff, classes and payments. This is where your
    bookings live now.
  </Card>

  <Card title="Offerings" icon="tags" href="/offerings/overview">
    Under **Services** — the same rows a meeting type edits, plus price, category, credits and
    payment settings.
  </Card>
</Columns>

## What a meeting type is

A meeting type is a **Service**. The two names describe one thing: DMLY renamed meeting types
to services, and the older screen kept the older word.

A meeting type sets what someone can book and when:

* **Duration (min)** and **Slot interval (min)** — how long the booking runs, and how far apart
  the offered start times sit.
* **Location** — **Google Meet (auto link)**, **Zoom (auto link)**, **Phone call**,
  **In person**, or **Custom (your own link/notes)**. Only Google Meet and Zoom generate a
  joining link for you; the rest use whatever you type into **Location details**.
* **Weekly availability** — the time windows you accept bookings in, per weekday.
* **Buffer before** and **Buffer after** — padding around each booking.
* **Min notice (min)** and **Days ahead** — how soon someone can book, and how far out.
* **Reminders**, **Confirmation message**, **Reminder message**, **Cancellation message**.
* **Active (available for booking)** — the on/off switch.

<Warning>
  Creating a meeting type here does not set a price, a category, credits or a payment mode.
  You get a bare bookable service that then shows up half-configured under
  **Offerings → Services**. If money is involved, create the service in
  [Offerings](/offerings/overview) instead and set it up once, properly.
</Warning>

Every one of the booking settings above also exists in **Offerings → Services**, with the same
labels. There is nothing you can configure on the Meetings screen that you cannot configure in
Offerings.

Deleting a meeting type that already has bookings does not delete it — DMLY deactivates it
instead, which protects the booking history. The confirmation dialog warns you before you
commit — **If it has bookings it will be deactivated instead.** Afterwards you only get a
generic **Done** toast, so check the meeting type's **Active** state if you need to know which
of the two happened.

## Bookings, cancel and reschedule

The **Bookings** tab lists confirmed upcoming meetings and past ones, with the **Contact**,
the **Meeting**, **When** and the **Source** it came from. On an upcoming booking you can:

* **Join Google Meet** or **Join Zoom Meeting** — shown only when the booking has a meeting
  link, and the label matches the link.
* **Open booking page** — opens that one booking's management page in a new tab. That is the
  page where your contact cancels or reschedules the booking themselves.
* **Reschedule** — pick a new time from the open slots on that meeting type's availability,
  then **Confirm new time**. If someone takes the slot first, DMLY tells you the time is no
  longer available.
* **Cancel meeting** — the contact is notified and the calendar event is removed. The
  cancellation is recorded as made by an agent.

On past or cancelled bookings, only the join link and **Open booking page** appear.

<Tip>
  Cancelling and rescheduling here are staff actions, done by you from inside DMLY. Contacts
  never touch these screens. To get *new* bookings you share a different link — the meeting
  type's own public page, from **Copy booking link** on the **Meeting types** tab, or straight
  into a WhatsApp reply with the composer's **Insert booking link** menu.
</Tip>

Rescheduling and cancelling from **Appointments** run the exact same logic. There is no
behaviour here you lose by staying in Appointments.

## Google Calendar is optional

Google Calendar is **not** required. Bookings are recorded either way, and the meeting type
editor offers **No calendar (don't sync)** on purpose.

Without a calendar connected you still take bookings, but:

* Meetings do not appear on your Google Calendar, so your own availability elsewhere is not
  visible to DMLY and DMLY's bookings are not visible to you outside the app.
* Google Meet links are not generated. The **Google Meet (auto link)** location has nothing to
  generate from.

The meeting types page says as much in a banner: **No Google Calendar connected. You can still
create meeting types, but meetings won't sync to a calendar or generate Meet links until you**
**connect one**. To connect one, see [Calendar sync](/appointments/calendar-sync).

## If the page asks you to connect a channel

Open Meetings in a workspace with no connected channel and you get a "connect a channel first"
prompt instead of your bookings — even though meeting types are workspace-wide and have nothing
to do with channels. Connect a channel (see [Channels](/channels/overview)) and the page loads
normally. This is another reason to work in [Appointments](/appointments/overview) instead.

<Accordion title="Why does this page exist at all if nothing links to it?">
  Meetings came first. Appointments and Offerings were built over the same data and grew past
  it, but the old screens were never removed — so old bookmarks keep working. Nothing about
  the arrangement is documented as deliberate or as an oversight, so treat Meetings as legacy:
  safe to open, not worth building a habit around.
</Accordion>
