> 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/bookings/book-for-someone.md).

# Book for someone

Book a meeting for a client yourself from the dCal dashboard, for example after a phone call: pick the event, choose one of your open times or any time you like, fill in the guest's details, and dCal

Sometimes the booking starts with a phone call, a chat or a walk-in, not with your link. **+ New booking** lets you book the meeting yourself, on one of your open times or at any time you choose. Your guest receives the same emails as if they had booked on your page.

***

**Step 1:** Click **Bookings** in the left menu, then **+ New booking** at the top right. You can also go straight to [app.dcal.ai/admin/bookings/new](https://app.dcal.ai/admin/bookings/new).

<figure><img src="https://3835013762-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FCy5rSNtQmtqYCGzJlNEB%2Fuploads%2Fgit-blob-2305ea3b4123d5a971f7b6f3a37c8c6543cfcc57%2Fdcal-book-for-someone-01-new-booking-button.png?alt=media" alt="The top of the Bookings page with the line Times shown in America/Bogota and the + New booking button boxed"><figcaption><p><strong>+ New booking</strong> opens the booking form.</p></figcaption></figure>

The **New booking** page opens. Two messages can appear at the top:

* **Create an event first.** You have no events yet. Create one, then come back. See [Create an event](https://docs.dapta.ai/dcal/events/create-an-event.md).
* A notice that starts with "You haven't set your public handle yet", with a **Set your handle** button. Your public booking page is not published until you set a handle, but bookings you make here still work.

***

**Step 2:** Choose the **Event**. Each option shows the title and length, for example **Intro call · 30 min**. Only your own events are listed, and hidden events are left out.

***

**Step 3:** Set the **Attendee timezone** to your guest's time zone. It starts on New York time, so change it first: the times you see and pick on this form follow this zone, and your guest's emails show times in it.

***

**Step 4:** Pick the time, in one of two ways.

* **From available slots** (the default): the form lists your open times for the next 3 weeks as buttons, in the dashboard's language, for example `20 Mon, 3:00 PM`. Click one. These are the same times your booking page offers.
* **Any time (outside availability)**: pick a date and a time in the picker, for example outside your working hours. The picker moves in steps of the event's slot interval (or its length when it has none).

<figure><img src="https://3835013762-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FCy5rSNtQmtqYCGzJlNEB%2Fuploads%2Fgit-blob-91a5e2e62bb995c6c72b5bfc8755d5612fa0b4ef%2Fdcal-book-for-someone-02-event-and-slots.png?alt=media" alt="The New booking form with the event Intro call, From available slots active, a grid of time buttons with 20 Tue, 1:00 PM selected, and the Attendee timezone field set to America/New York"><figcaption><p><strong>From available slots</strong> shows your open times in the guest's time zone.</p></figcaption></figure>

<figure><img src="https://3835013762-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FCy5rSNtQmtqYCGzJlNEB%2Fuploads%2Fgit-blob-a072d9f29dcde81751936fcb1c61fa429457e58b%2Fdcal-book-for-someone-03-any-time.png?alt=media" alt="The New booking form in Any time (outside availability) mode with the Date &#x26; time (host timezone) picker open on Sat, Oct 24 at 18:00"><figcaption><p><strong>Any time (outside availability)</strong> lets you pick a time your hours do not offer.</p></figcaption></figure>

If no time shows up in **From available slots**, the form tells you why, with a link to the fix:

| Message                                                    | What to do                                                                                                             |
| ---------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------- |
| **No slots in range.**                                     | Nothing is free in the next 3 weeks. Use **Any time (outside availability)**, or open up your hours.                   |
| "This event's schedule is missing"                         | Click **Open event settings** and choose a schedule for the event.                                                     |
| **No working hours configured for this event’s schedule.** | Click **Open Availability** and add hours to that schedule.                                                            |
| "You don't have a schedule yet"                            | Click the button to create default working hours (Monday to Friday, 9 to 5), or **Open Availability** to set your own. |
| "Couldn't reach the connected calendar"                    | dCal hides the times so it cannot double-book you. Click **Check Calendars**, then try again.                          |
| **Couldn’t load times. Try again in a moment.**            | Wait a moment and reload the page.                                                                                     |

See [Set your hours](https://docs.dapta.ai/dcal/calendars-and-availability/set-your-hours.md) and [Connect your calendar](https://docs.dapta.ai/dcal/calendars-and-availability/connect-a-calendar.md).

***

**Step 5:** Under **Questions**, fill in **Attendee name** and **Attendee email**, then the event's own booking questions. Required questions are marked with `*`. A phone question gets a phone field; every other question is a text box where you type the answer.

<figure><img src="https://3835013762-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FCy5rSNtQmtqYCGzJlNEB%2Fuploads%2Fgit-blob-cfac76f7929e5c4611e0b9d43b0f26a72ad2590f%2Fdcal-book-for-someone-04-questions.png?alt=media" alt="The whole New booking form for Intro call with a time selected and, under Questions, Attendee name John Doe, Attendee email docs-test+1@example.com, Company name Acme Corp and a phone number filled in, with the Create booking button at the top right"><figcaption><p>The guest's name and email are required. The rest are the event's own questions.</p></figcaption></figure>

***

**Step 6:** Click **Create booking**. The button stays disabled until the name and email are filled in. If you have not picked a time, the form says **Pick a time.** (or **Pick a date and a time.** in **Any time (outside availability)** mode).

When it works, you see **Booking created** and **The attendee has been notified.** Click **Back to bookings** to return to the list.

<figure><img src="https://3835013762-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FCy5rSNtQmtqYCGzJlNEB%2Fuploads%2Fgit-blob-6e5ef7198bf50b75bc635b08097b3b24314cdd4e%2Fdcal-book-for-someone-05-created.png?alt=media" alt="The Booking created screen with the line The attendee has been notified. and the Back to bookings button"><figcaption><p>Done. Your guest has their confirmation email.</p></figcaption></figure>

***

## What happens next

* Your guest receives **Booking confirmed**, with the calendar invite and a **Manage your booking** button, exactly as if they had booked on your page.
* You receive **New booking**, with the guest's details and answers.
* The event is added to your connected calendar, and the event's reminders and follow-up are scheduled.
* Your webhooks receive `booking.created`.

> **⚠️ Note:** **Requires confirmation** still applies. On an event that has it on, the booking you create starts as a request: your guest receives **Request received**, and the booking waits under **Pending confirmation** until you confirm it. See [Confirm or decline requests](https://docs.dapta.ai/dcal/bookings/confirm-or-decline.md).

A booking made here does not record a language for your guest, so their emails are written in English. See [Who gets which email](https://docs.dapta.ai/dcal/emails/who-gets-which-email.md#language-and-time-zone).

## Rules for bookings you make

| Rule                                                                         | From available slots                 | Any time (outside availability)    |
| ---------------------------------------------------------------------------- | ------------------------------------ | ---------------------------------- |
| Your working hours, minimum notice and the event's **Booking window (days)** | Followed: only open times are listed | Not checked                        |
| Your other bookings and pending requests                                     | Never overlapped                     | Never overlapped                   |
| Busy times on your connected calendar                                        | Never overlapped                     | Never overlapped                   |
| How far back                                                                 | Not in the past                      | No more than 5 minutes in the past |
| How far ahead                                                                | The next 3 weeks                     | Up to 2 years                      |
| **One booking per person** on the event                                      | Does not apply                       | Does not apply                     |

If dCal can't reach your connected calendar when you click **Create booking**, it blocks the booking so it cannot double-book you, and the form says "Couldn't reach the connected calendar". Check **Calendars** and try again. If someone took the time a moment before you, pick another one.

## Related

* [See your bookings](https://docs.dapta.ai/dcal/bookings/see-your-bookings.md): find the booking you just made.
* [Confirm or decline requests](https://docs.dapta.ai/dcal/bookings/confirm-or-decline.md): for events that require confirmation.
* [Booking questions](https://docs.dapta.ai/dcal/events/booking-questions.md): the questions this form asks.
* [Time zones](https://docs.dapta.ai/dcal/calendars-and-availability/time-zones.md): how dCal shows times to you and your guests.
* [Who gets which email](https://docs.dapta.ai/dcal/emails/who-gets-which-email.md): what your guest receives.


---

# 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/bookings/book-for-someone.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.
