> For the complete documentation index, see [llms.txt](https://docs.dapta.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.dapta.ai/dcal/what-guests-see.md).

# What your guests see

See your dCal booking pages the way your guests do: opening your link, picking a day and time in their own time zone, booking, and rescheduling or cancelling from their email. Also covers the 10-minut

This page walks through your booking pages from the guest's side, so you know exactly what people experience before you share a link. Everything here is the live behavior of your booking pages, which live on `book.dcal.ai`, apart from your dashboard on `app.dcal.ai`. A guest who opens an older link with `app.dcal.ai` in it lands on the same page on `book.dcal.ai`, with everything after the address kept, UTM tags included.

***

## Your profile page

Your profile page, at `book.dcal.ai/{account code}/{handle}`, is the address the dashboard calls **Your booking link**. It lists all your visible personal events. Team events are listed on the team's own page.

<figure><img src="https://3835013762-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FCy5rSNtQmtqYCGzJlNEB%2Fuploads%2Fgit-blob-cfc319372356baa593c1413f890e2ed273fa8c98%2Fdcal-key-concepts-01-profile-page.png?alt=media" alt="Jane Doe&#x27;s profile page with the initials JD, her name, a short bio and a card listing three events with their lengths: 30-minute meeting, Intro call and Consultation"><figcaption><p>A profile page. Each row opens that event's booking page.</p></figcaption></figure>

From top to bottom the guest sees:

* Your cover image and your workspace logo, when you set them.
* Your photo. If you have not uploaded one, dCal uses the photo of your connected calendar account, or your initials.
* Your workspace name above your name, when the two are different, then your name and your bio.
* One row per visible event, with its title, its description and its length in minutes. Events follow the order you set in **Settings** > **Booking Page**, or shortest first.

With no visible event, the page reads **No bookable events yet.** With exactly one, the profile link opens that event directly, unless you turned on **Always show my profile, even with one event type**. See [Your links and profile page](https://docs.dapta.ai/dcal/share/your-booking-page.md).

***

## An event's booking page

Each event has its own page at `book.dcal.ai/{account code}/{handle}/{event slug}`. Booking takes four steps on one page: pick a date, pick a time, fill in the details, see the confirmation.

On wider screens (768 pixels and up) the page has two panes: the event details on the left, and the month with the times of the selected day on the right. The details form replaces the right pane once a time is picked.

<figure><img src="https://3835013762-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FCy5rSNtQmtqYCGzJlNEB%2Fuploads%2Fgit-blob-250dd2980e927524d49ece7c4f1feefda0771da2%2Fdcal-what-guests-see-02-event-page.png?alt=media" alt="The Intro call booking page on desktop, opened from a browser in Madrid: Jane Doe, the title, 30 min, Online meeting and America/Bogota, the host&#x27;s time on the left, and the month with the times of Wed, Oct 21 on the right, shown in 12-hour format with 12h selected, with the time zone control reading Europe/Madrid"><figcaption><p>Event details on the left, the month and the open times on the right. The times are in the guest's zone, Europe/Madrid; the panel names the host's zone.</p></figcaption></figure>

The event panel shows:

* Your photo (or initials) and your name.
* The event title, its length (for example **30 min**) and its location, when you set one. An online meeting reads **Online meeting**.
* Your time zone, written as the zone and **the host's time**, for example "America/Mexico City, the host's time".
* The event description. A long description is cut at four lines with **Show more**, and keeps your line breaks.
* Your workspace logo, if your brand kit has one.

On a phone, one step fills the screen at a time, with a thin progress bar on top and back buttons to return to the previous step.

***

## Picking a day

The month view opens on the first month that has open times, with its first bookable day already selected. Days with times can be clicked; the others cannot. Guests move with the previous and next month arrows.

* Guests can book up to 60 days ahead, or fewer when the event has a shorter **Booking window (days)**: days past it show no times. Guests cannot go back before the current month or past the month where those 60 days end. See [How far ahead guests can book](https://docs.dapta.ai/dcal/events/event-settings.md#how-far-ahead-guests-can-book).
* The earliest time offered is now plus the event's minimum notice (2 hours on a new event).
* Weeks start on Sunday on English pages and on Monday on Spanish pages.

***

## Time zones

The page opens in the **guest's own** time zone, the one their browser reports, so they read times on their own clock from the start. The event panel keeps naming your time zone as **the host's time**. If the browser reports UTC or a zone the page cannot use, the page opens in your time zone instead.

Guests can still change it with the time zone picker: the line with a globe icon, the zone name and its GMT offset (for example "GMT+2") in the times column.

<figure><img src="https://3835013762-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FCy5rSNtQmtqYCGzJlNEB%2Fuploads%2Fgit-blob-d01d02b16cc83da6e9c79749131a14ca1f3c255c%2Fdcal-what-guests-see-04-time-zone-picker.png?alt=media" alt="The time zone picker of a booking page opened from a browser in Madrid, with a Search timezone box, Europe/Madrid under Showing times in, and the All time zones list below it"><figcaption><p>The page already shows the guest's zone. The picker lets them choose any other.</p></figcaption></figure>

The picker has a search box (**Search timezone…**) and up to three groups:

| Group                | What it lists                                                                                                                     |
| -------------------- | --------------------------------------------------------------------------------------------------------------------------------- |
| **Showing times in** | The zone the page uses right now.                                                                                                 |
| **Your time zone**   | The zone of the guest's device, shown only when the page is in another zone (for example after the guest picked a different one). |
| **All time zones**   | Every time zone, searchable by zone name or GMT offset.                                                                           |

Picking a zone moves every day and time at once, without reloading, and the page keeps the guest's choice for the rest of the visit (it is not remembered between visits). The zone on screen when the guest books is saved with the booking, and their emails and manage page show times in it.

***

## Picking a time

Next to the month, the guest sees **Times on** and the selected day, then the list of start times.

* **12h** and **24h** switch the time format. English pages start on 12h and Spanish pages on 24h. The choice is not remembered between visits.
* A button under the times jumps to the next day that has open times (**Next day with times:** and the day).
* On a group event, each time shows how many seats are left (for example **3 left**), or **Full** when nobody else can join it.

### When no times show

When nothing can be booked, the calendar is replaced by one sentence. Here is what each one means and what to check:

| The guest reads                                                            | What it means                                                                                                                           | What to check                                                                               |
| -------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------- |
| **No available times in this range.**                                      | No time in the next 60 days, or inside the event's booking window, is free inside your hours.                                           | Your weekly hours, date overrides, busy calendar and the event's **Booking window (days)**. |
| **No times are available right now. Please check back soon.**              | The event cannot offer times: for example its schedule has no hours.                                                                    | The event's **Bookable hours** and the schedule's hours.                                    |
| **We can’t read this calendar right now. Try again in a moment.**          | dCal could not read your connected calendar, so it shows no times rather than risk a double booking. The guest can click **Try again**. | **Calendars**: reconnect any account that says **Needs attention**.                         |
| **Lots of people are booking right now. The times will show in a moment.** | dCal is getting many requests at once. The times appear on their own.                                                                   | Nothing.                                                                                    |

***

## The hold and the details form

**Step 1:** The guest clicks a time. On a personal event with one seat, dCal holds that time for 10 minutes so nobody else can take it while they type. The form shows **Held until** and the time.

<figure><img src="https://3835013762-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FCy5rSNtQmtqYCGzJlNEB%2Fuploads%2Fgit-blob-43fc554000ebbdc6ae99509ce0a348e2401a5bee%2Fdcal-what-guests-see-05-details-form.png?alt=media" alt="The details form for Intro call on Wednesday, October 21, 2026, 12:30 to 1:00 PM, with Back to times, the Held until line boxed, Your name and Your email filled in for John Doe, the Company name and Phone number questions, Notes (optional) and the Confirm booking button"><figcaption><p>The details form. The chosen time stays held for 10 minutes.</p></figcaption></figure>

**Back to times** releases the hold, and so does picking another time. Team events and group events do not place a hold.

**Step 2:** The guest fills in the form:

* **Your name** and **Your email**, always asked and required.
* Your own booking questions, in the order you set. Required ones carry an asterisk.
* **Notes (optional)**, always last.

Empty required fields show **This field is required.**, and a mistyped email shows **Enter a valid email.** The guest clicks **Confirm booking**.

***

## Confirmation or request sent

**Step 3:** The guest sees one of two screens.

| Screen                             | When                                        | Line under the title                                                             |
| ---------------------------------- | ------------------------------------------- | -------------------------------------------------------------------------------- |
| **Booking confirmed** (check icon) | The event books instantly.                  | "A confirmation was sent to" the guest's email.                                  |
| **Booking requested** (clock icon) | The event has **Requires confirmation** on. | "Awaiting the host’s confirmation. We’ll email" the guest "once it’s confirmed." |

Both screens repeat the event title, the day and time with the time zone, your name and the location, and offer two buttons:

* **Add to calendar** downloads a calendar file (`.ics`) with the title, the time, the location and, for online meetings, the meeting link. Most calendar apps open it.
* **Manage your booking** opens the guest's manage page (see below).

If the event has a **Redirect after booking**, the guest goes to your page instead of staying on these screens, after a booking or a request alike. See [Redirect after booking](https://docs.dapta.ai/dcal/events/event-settings.md#redirect-after-booking).

### When a time cannot be booked

| The guest reads                                                                                              | Why                                                                                                | What they can do                                                  |
| ------------------------------------------------------------------------------------------------------------ | -------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------- |
| **You already have a booking**                                                                               | The event has **One booking per person** on, and this email already has an upcoming booking on it. | **Use a different email**: the time and answers stay filled in.   |
| **That time was just taken.**                                                                                | Someone else booked it first.                                                                      | **Pick another time**                                             |
| **Your hold expired**                                                                                        | More than 10 minutes passed after picking the time.                                                | **Pick another time**                                             |
| **We couldn’t confirm this time**                                                                            | dCal could not check your calendar at that moment, so nothing was booked.                          | **Pick another time**, or try again in a moment.                  |
| **Lots of people are booking right now. Your details are still here: press Confirm again in a few seconds.** | dCal is getting many requests at once.                                                             | Press **Confirm booking** again: the form keeps everything typed. |
| **That did not go through. Your details are still here: try again in a moment.**                             | The booking could not be sent.                                                                     | Try again: the form keeps everything typed.                       |

If dCal is getting too many requests to load the page at all, the guest sees a **Busy for a moment** card that counts down and tries again by itself, up to three times. After that it reads "Still busy. Try again in a minute." and offers **Try again**. This happens on profile, event and team pages, the manage page and one-off invite links.

***

## The emails and the manage link

After booking, the guest gets an email from dCal with times in the time zone they booked in. It uses the language of the page they booked on, unless you customized the email's wording. A confirmed booking's email carries the calendar invite and a **Manage your booking** button. A request's email says it is pending, has no invite yet, and carries a **Manage your request** button. Reminders follow, by default 24 hours and 1 hour before the meeting. See [Who gets which email](https://docs.dapta.ai/dcal/emails/who-gets-which-email.md).

The manage button opens the guest's manage page on `book.dcal.ai`: the meeting details and, until the meeting starts, the options to reschedule or cancel.

<figure><img src="https://3835013762-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FCy5rSNtQmtqYCGzJlNEB%2Fuploads%2Fgit-blob-d8b98d756f5e4810595fd268a16c1c5ef955a2cc%2Fdcal-what-guests-see-08-manage-page.png?alt=media" alt="The manage page of an Intro call with the eyebrow Manage your booking, the meeting details, the Cancel this booking section with a Reason (optional) box, and a month view with the open times to pick a new time"><figcaption><p>The manage page. Guests reschedule or cancel here, without an account.</p></figcaption></figure>

* **Reschedule** offers your open times in the next three weeks, in the guest's time zone. After a move, the guest gets a new email with the updated invite.
* **Cancel this booking** takes an optional reason and cancels at once. For a request that is still pending, the page offers **Cancel this request** only.
* Once the meeting has started, the page shows the details only.

> **⚠️ Note:** Each reschedule creates a new manage link, so the button in an older email opens a page that reads **This link is no longer active**. The most recent email always has the working link. For a request, the link arrives in the "Request received" email and the confirmation email you trigger later does not repeat it, so tell guests to keep that first email.

***

## One-off invite links

A one-off invite link (`book.dcal.ai/booking/...`) opens the same booking flow for one event, even a hidden one. After one booking the link is used, and anyone who opens it again sees **This invite link has already been used** and a line asking them to request a new one. These pages are never listed in search engines. See [One-off invite links](https://docs.dapta.ai/dcal/events/one-off-links.md).

***

## Language

There is no language switch on the booking pages. Each page shows in English or Spanish, following the guest's browser: Spanish when the browser prefers Spanish to English, English otherwise.

To force a language, add `?lang=es` or `?lang=en` to the link, for example `book.dcal.ai/{account code}/{handle}/{event slug}?lang=es`. It works on every public page: profile pages, event pages, team pages, team event pages, one-off invite links and the manage page.

***

## Light and dark

Your booking pages use the canvas you choose for them in **Settings** > **Booking Page**, never the guest's device setting and never your dashboard theme. A new host's page starts with a light canvas and a near-black accent. See [Colors, fonts and presets](https://docs.dapta.ai/dcal/design/look-and-presets.md).

***

## The Dapta badge

At the bottom of your pages a small badge reads **Made with dCal.ai by Dapta**. Your profile page and the confirmation screen also show the line **dCal is free for anyone.** with a **Create your free calendar** button, and your guests' emails end with a short **Made with dCal.ai by Dapta** line. They all lead to the dCal website, [dcal.ai](https://dcal.ai).

<figure><img src="https://3835013762-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FCy5rSNtQmtqYCGzJlNEB%2Fuploads%2Fgit-blob-c5759b6e07a0bf8f8627d917dba032b5d4a718f3%2Fdcal-what-guests-see-09-badge.png?alt=media" alt="The bottom of a profile page with the line dCal is free for anyone., the Create your free calendar button and the Made with dCal.ai by Dapta badge"><figcaption><p>The free-calendar invitation and the badge.</p></figcaption></figure>

Workspaces that pay for Dapta can hide all of them (only the page of an already used one-off invite link keeps the badge): an owner or an admin turns off **Show Dapta branding on my pages** in **Settings** > **General**. See [The Dapta badge](https://docs.dapta.ai/dcal/design/dapta-branding.md).

***

## Link previews

When you paste your profile or event link in a chat app or a social post, most apps show a preview card that dCal draws from your page: your photo or initials, your name, the event title, its description and length, and a **Book a time** button, in your page's colors.

The preview title of an event reads "{event} with {your name}", or just the event's name when it already names you (for example "An interview with Jane" for the host Jane Doe), and its description is the event description or a line with its length and your name. Team pages do not get a generated card. After you change your photo or an event, the card can take up to 10 minutes to update.

***

## If a link does not open

A guest who opens an address that does not lead to a bookable page sees **Page not found**, the line "This page does not exist. Check the link with the person who shared it." and a **Go home** link, in their own language. This happens when:

* the event is **Hidden** or was deleted,
* you changed your handle or the event's slug after sharing the link,
* or the address has a typo.

Copy the current link from **Events** or from **Your booking link** on **Home** and share it again.

## Related

* [Your links and profile page](https://docs.dapta.ai/dcal/share/your-booking-page.md)
* [Time zones](https://docs.dapta.ai/dcal/calendars-and-availability/time-zones.md)
* [Booking questions](https://docs.dapta.ai/dcal/events/booking-questions.md)
* [Reschedule and cancel](https://docs.dapta.ai/dcal/bookings/reschedule-and-cancel.md)
* [Embed on your website](https://docs.dapta.ai/dcal/share/embed.md)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

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

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.dapta.ai/dcal/what-guests-see.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
