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

# Overview

> What Scheduled Calls is, when to use it, and how bookings fit into your product

**Scheduled Calls** lets your customers book a future video meeting
with one of your agents, receive reminders, and join the meeting
when the slot arrives — all tied to an ApifyCloud video app.

## What it is

A scheduling layer that sits on top of [Video](/guides/video/overview).
Instead of joining a call right now, a customer books a time; an
agent is assigned; both sides get the same meeting link when the
time comes.

* **Bookings** can be created by agents, admins, customers (via a
  public page), or an external system (via the API).
* **Availability** is driven by each agent's working hours, with
  exceptions and ad-hoc "do not disturb" windows.
* **Reminders** are sent automatically before the meeting.
* **Status** of every booking is tracked through a full lifecycle
  (scheduled → confirmed → started → completed, or cancelled /
  no-show).

<Note>
  The meeting itself uses the exact same Video runtime described in
  [Video — Overview](/guides/video/overview). Scheduled Calls adds the
  "when" and the "who" on top; the actual room is the same one the
  customer would enter from an instant link.
</Note>

## When to use it

Scheduling is a fit whenever the call can't (or shouldn't) happen
the moment the customer clicks:

<CardGroup cols={2}>
  <Card title="Sales demos" icon="presentation-screen">
    High-AOV or consultative sales that require preparation on
    both sides.
  </Card>

  <Card title="Onboarding & KYC" icon="id-card">
    Scheduled document review, identity verification, or guided
    setup.
  </Card>

  <Card title="Consultations" icon="stethoscope">
    Healthcare, legal, or advisory sessions delivered remotely.
  </Card>

  <Card title="Tier-2 support" icon="headset">
    A follow-up slot after a front-line ticket gets escalated.
  </Card>
</CardGroup>

## How it fits together

<Steps>
  <Step title="Customer books a time">
    Through the public booking page, an agent-assisted flow, or an
    external system calling the API.
  </Step>

  <Step title="An agent is assigned">
    Either explicitly (URL-forced or customer-picked) or
    automatically from the pool of available agents.
  </Step>

  <Step title="Reminders go out">
    Invitation on booking, plus reminders at configured intervals
    before the meeting (24h / 1h / 15m by default).
  </Step>

  <Step title="Both sides join the same meeting">
    When the slot arrives, the customer opens their reminder link
    and the agent opens theirs — they land in the same Video
    meeting.
  </Step>

  <Step title="The lifecycle closes">
    On end, the booking moves to `completed`. If nobody joined, it
    auto-transitions to `no_show`.
  </Step>
</Steps>

## What you bring vs. what ApifyCloud brings

| Responsibility                                                | You            | ApifyCloud |
| ------------------------------------------------------------- | -------------- | ---------- |
| Agents (users with access to the video app)                   | ✅ (in console) |            |
| Working hours, exceptions, DND                                | ✅ (in console) |            |
| Scheduling preset configuration (reminders, limits, channels) | ✅ (in console) |            |
| Destination for reminders (customer's phone, email)           | ✅              |            |
| Public booking page, console booking UIs                      |                | ✅          |
| OAuth-gated API                                               |                | ✅          |
| Reminder dispatch, retries, status tracking                   |                | ✅          |
| Outbound webhooks to your systems                             |                | ✅          |
| Integration with the Video runtime                            |                | ✅          |

## What's next

<CardGroup cols={2}>
  <Card title="Booking surfaces" href="/guides/scheduled-calls/booking-surfaces">
    The four ways a booking can be created.
  </Card>

  <Card title="Agent availability" href="/guides/scheduled-calls/agent-availability">
    Working hours, exceptions, and do-not-disturb windows.
  </Card>

  <Card title="Reminders" href="/guides/scheduled-calls/reminders">
    What gets sent, when, and through which channel.
  </Card>

  <Card title="Webhooks" href="/guides/scheduled-calls/webhooks">
    Lifecycle events pushed to your systems.
  </Card>
</CardGroup>